2.6.7: ehci_hcd prevents system from suspending properly
I've just compiled 2.6.7 and found that having ehci_hcd loaded (I've compiled it as a module) prevents system from suspending properly. I've got this dmesg messages:
PM: Preparing system for suspend
Stopping tasks: =======================================================================|
PCI: Setting latency timer of device 0000:00:1d.7 to 64
Could not suspend device 0000:00:1d.7: error -5
PCI: Setting latency timer of device 0000:00:1f.5 to 64
PCI: Setting latency timer of device 0000:00:1f.6 to 64
looks like device 0000:00:1d.7 can't be suspended. From lspci I get this:
0000:00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller (rev 03)
If I remove the module (modprobe -r ehci_hcd) the system suspends properly:
PM: Preparing system for suspend
Stopping tasks: ========================================================================|
PCI: Setting latency timer of device 0000:00:1d.0 to 64
PCI: Setting latency timer of device 0000:00:1d.0 to 64
PCI: Setting latency timer of device 0000:00:1d.7 to 64
PCI: Setting latency timer of device 0000:00:1f.5 to 64
PCI: Setting latency timer of device 0000:00:1f.6 to 64
PM: Entering state.
2.6.6 does suspend properly, as does 2.6.5 and 2.4.26. This
2.6.7 compilation is just a make oldconfig from the 2.6.6 settings I have, nothing more, nothing less.
My system: Toshiba A10
root@nemo:/home/miguel# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Mobile Intel(R) Celeron(R) CPU 2.40GHz stepping : 9 cpu MHz : 2394.737 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid bogomips : 4751.36
Quoted 3 lines · Miguelanxo Otero Salgueiro
I've just compiled 2.6.7 and found that having
ehci_hcdloaded (I've compiled it as a module) prevents system from suspending properly. I've got this dmesg messages:
Yeah, known issue, I'm trying to work on it.
thanks,
greg k-h