aboutsummaryrefslogtreecommitdiff
path: root/scripts/cleanpatch
diff options
context:
space:
mode:
authorChen Yu <[email protected]>2022-03-08 09:20:30 -0800
committerJakub Kicinski <[email protected]>2022-03-09 19:53:03 -0800
commit91ec77924714b67a6fbe9f6631dd639012fb76eb (patch)
treed84c95ab2116b3133f15eeaa93a51a14d7926a12 /scripts/cleanpatch
parent013a3e7c79ac51e6cdd84e3580863a562c7597c7 (diff)
e1000e: Print PHY register address when MDI read/write fails
There is occasional suspend error from e1000e which blocks the system from further suspending. And the issue was found on a WhiskeyLake-U platform with I219-V: [ 20.078957] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x780 [e1000e] returns -2 [ 20.078970] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -2 [ 20.078974] e1000e 0000:00:1f.6: PM: pci_pm_suspend+0x0/0x170 returned -2 after 371012 usecs [ 20.078978] e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 According to the code flow, this might be caused by broken MDI read/write to PHY registers. However currently the code does not tell us which register is broken. Thus enhance the debug information to print the offender PHY register. So the next the issue is reproduced, this information could be used for narrow down. Acked-by: Paul Menzel <[email protected]> Reported-by: Todd Brandt <[email protected]> Signed-off-by: Chen Yu <[email protected]> Tested-by: Naama Meir <[email protected]> Signed-off-by: Tony Nguyen <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'scripts/cleanpatch')
0 files changed, 0 insertions, 0 deletions