Paul Menzel <[email protected]> : [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656331] > I experienced this problem (only) three times until now. If I remember > correctly the last time with 3.2.1. I still do not know how to reproduce > this.
(good PR, nice) An 'ethtool -d' and a 'mii-tool -v' of the device after a successful resume and a failed one could help if it's a driver thing. You may check if runtime power management is enabled or not, especially after a failed resume. See the /sys/devices/pci....:../....:..:..../power directory and its control, runtime_enabled and runtime_status files (control = on -> runtime PM disabled, see Documentation/power/runtime_pm.txt) If it is enabled and the link does not come up fast enough (5 s), runtime PM will suspend the device. It should not matter as long as the link is still present because the device should (TM) soon generate a power management event. The latter not happening or the PME being ignored could explain the bug. If so, temporarily disabling runtime PM for your device after a failed resume instead of removing the module or the cable may be enough to recover the link. It's just a guess though. Please stay with v3.2 or above in the meantime. -- Ueimor -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
