How to interpret PM_TRACE output
Hi folks,
I tried PM_TRACE to find the driver that breaks resume from suspend. I got working resume until I switched to the sk98lin driver (because sky2 doesn't support wake on LAN). That's why I was quite sure that sk98lin is the culprit, but I tried PM_TRACE anymay.
Here is the PM_TRACE output in dmesg:
Magic number: 0:150:255
hash matches drivers/base/power/resume.c:28
hash matches device 0000:00:1d.3
$ lspci | grep 1d.3 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4
/proc/interrupts:
17: 52387 0 IO-APIC-level uhci_hcd:usb5, eth0, i915@pci:0000:00:02.0 20: 1223105 1222776 IO-APIC-level ehci_hcd:usb1, uhci_hcd:usb2
Since UHCI #4 (usb5, as ehci is usb1) and eth0 (sk98lin) use the same interrupt, is it right to assume that the sk98lin driver does bad interrupt handling and therefore breaks the usb5 device on resume?
Regards,
Tino
Quoted 6 lines · Tino Keitel
Hi folks,
I tried
PM_TRACEto find the driver that breaks resume from suspend. I got working resume until I switched to the sk98lin driver (because sky2 doesn't support wake on LAN). That's why I was quite sure that sk98lin is the culprit, but I triedPM_TRACEanymay.
See Doc*/power/*.
Pavel
Signature · 1 line
Thanks for all the (sleeping) penguins.
Quoted 9 lines · Pavel Machek
Quoted 6 lines · Tino Keitel
Hi folks,
I tried
PM_TRACEto find the driver that breaks resume from suspend. I got working resume until I switched to the sk98lin driver (because sky2 doesn't support wake on LAN). That's why I was quite sure that sk98lin is the culprit, but I triedPM_TRACEanymay.See Doc*/power/*.
There is a nice mixture of documentation about swusp, video stuff, developer documentation, and one short paragraph about PM_TRACE that tells me nothing new. Could you point me to the documentation part that you are referring to, and that tells me what to do if PM_TRACE shows the usb device but the failure only occurs when I load the sk98lin driver?
Thanks and regards,
Tino
Hi!
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
I tried
PM_TRACEto find the driver that breaks resume from suspend. I got working resume until I switched to the sk98lin driver (because sky2 doesn't support wake on LAN). That's why I was quite sure that sk98lin is the culprit, but I triedPM_TRACEanymay.
Quoted 8 lines
Quoted 1 line
See Doc*/power/*.
There is a nice mixture of documentation about swusp, video stuff, developer documentation, and one short paragraph about
PM_TRACEthat tells me nothing new. Could you point me to the documentation part that you are referring to, and that tells me what to do ifPM_TRACEshows the usb device but the failure only occurs when I load the sk98lin driver?
Hmmm, so it fails somewhere in usb only if sk98lin is loaded? If you unload it again, resume works? Are usb interrupts shared? Where exactly in the usb does it fail?
Signature · 1 line
Thanks for all the (sleeping) penguins.
Quoted 16 lines · Pavel Machek
Hi!
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
I tried
PM_TRACEto find the driver that breaks resume from suspend. I got working resume until I switched to the sk98lin driver (because sky2 doesn't support wake on LAN). That's why I was quite sure that sk98lin is the culprit, but I triedPM_TRACEanymay.Quoted 8 lines
Quoted 1 line
See Doc*/power/*.
There is a nice mixture of documentation about swusp, video stuff, developer documentation, and one short paragraph about
PM_TRACEthat tells me nothing new. Could you point me to the documentation part that you are referring to, and that tells me what to do ifPM_TRACEshows the usb device but the failure only occurs when I load the sk98lin driver?
Quoted 2 lines
Hmmm, so it fails somewhere in usb only if sk98lin is loaded? If you unload it again, resume works? Are usb interrupts shared? Where
Yes, it works with sky2. Yes, the USB device that is reported to fail by PM_TRACE shares the interrupt with eth0, which is sk98lin (see my original posting in this thread).
Quoted 1 line
exactly in the usb does it fail?
I don't know, all I have is the PM_TRACE output.
Meanwhile, tried to remove uhci_hcd before suspend, and wakeup works then. However, my DVB-T box is dead after resume (reloading the driver doesn't work, only unplug/replug the device helps). It works with suspend to disk, though.
Regards,
Tino
Hi!
Quoted 13 lines
Quoted 8 lines
Quoted 5 lines
developer documentation, and one short paragraph about
PM_TRACEthat tells me nothing new. Could you point me to the documentation part that you are referring to, and that tells me what to do ifPM_TRACEshows the usb device but the failure only occurs when I load the sk98lin driver?Hmmm, so it fails somewhere in usb only if sk98lin is loaded? If you unload it again, resume works? Are usb interrupts shared? Where
Yes, it works with sky2. Yes, the USB device that is reported to fail by
PM_TRACEshares the interrupt with eth0, which is sk98lin (see my original posting in this thread).
Quoted 6 lines
Quoted 1 line
exactly in the usb does it fail?
I don't know, all I have is the
PM_TRACEoutput.Meanwhile, tried to remove
uhci_hcdbefore suspend, and wakeup works then.
Send a nice bug report to usb people, then...
Pavel
Signature · 1 line
Thanks for all the (sleeping) penguins.