Bug 218799

Summary:	E810 doesn't resume successfully from system suspend, therefore prevents any further system suspend
Product:	Drivers	Reporter:	Kai-Heng Feng (kai.heng.feng)
Component:	Network	Assignee:	drivers_network (drivers_network)
Status:	NEW ---
Severity:	normal	CC:	en-wei.wu, jan.glaza, regressions
Priority:	P3
Hardware:	All
OS:	Linux
Kernel Version:	mainline, linux-next	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	lspci dmesg with ice debug log

Description Kai-Heng Feng 2024-05-02 03:49:57 UTC

On 1st system resume, ice gives some error:
ice 0000:02:00.1: Failure Adding VLAN 0 on VSI 4, status -5
ice 0000:02:00.1 enp2s0f1np1: Failed to open VSI 0x0004 on switch 0x0001
ice 0000:02:00.1: enable VSI failed, err -5, VSI index 0, type ICE_VSI_PF
ice 0000:02:00.1: PF VSI rebuild failed: -5
ice 0000:02:00.1: Rebuild failed, unload and reload driver
ice 0000:02:00.0: Failure Adding VLAN 0 on VSI 5, status -5
ice 0000:02:00.0 enp2s0f0np0: Failed to open VSI 0x0005 on switch 0x0000
ice 0000:02:00.0: enable VSI failed, err -5, VSI index 0, type ICE_VSI_PF
ice 0000:02:00.0: PF VSI rebuild failed: -5
ice 0000:02:00.0: Rebuild failed, unload and reload driver

On the 2nd system suspend attempt:
ice 0000:02:00.1: Device is not ready, no need to suspend it
ice 0000:02:00.1: PM: pci_pm_suspend(): ice_suspend [ice] returns -16
ice 0000:02:00.0: Device is not ready, no need to suspend it
ice 0000:02:00.1: PM: dpm_run_callback(): pci_pm_suspend returns -16
ice 0000:02:00.1: PM: failed to suspend async: error -16
ice 0000:02:00.0: PM: pci_pm_suspend(): ice_suspend [ice] returns -16
ice 0000:02:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -16
ice 0000:02:00.0: PM: failed to suspend async: error -16
PM: Some devices failed to suspend, or early wake event detected

Comment 1 Kai-Heng Feng 2024-05-02 03:51:04 UTC

Created attachment 306256 [details]
lspci

Comment 2 Kai-Heng Feng 2024-05-02 03:53:05 UTC

Created attachment 306257 [details]
dmesg with ice debug log

Comment 3 Kai-Heng Feng 2024-05-02 04:08:43 UTC

Not sure if it's related, but these are some errors during driver's probe routine:
ice 0000:02:00.0: Get PHY capability failed.
ice 0000:02:00.0: ice_init_nvm_phy_type failed: -5
ice 0000:02:00.1: Get PHY capability failed.
ice 0000:02:00.1: ice_init_nvm_phy_type failed: -5

Comment 4 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-05-30 07:41:49 UTC

Am I right assuming it worked with 6.8.y? Could you bisect? and is the problem still happening with 6.10-rc1?

Comment 5 Kai-Heng Feng 2024-05-30 08:18:32 UTC

No this is not a regression. I've tried kernels older than 6.8 and all of them have this issue.

Comment 6 Jan Glaza 2024-06-05 06:49:06 UTC

Could you provide the output of ethtool -i <device> ? It would be helpful in setting up local reproduction.