Re: [linux-usb-devel] ehci_hcd causes box to resume immediately after suspend to RAM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 11 Jun 2007, Rafael J. Wysocki wrote:

> > At that point, does "lspci -vv" show that the controller is trying to 
> > signal a wakeup event?  That is, is the PME# signal asserted?
> > 
> > (Not that knowing this will help very much -- I'm not sure what we 
> > could do with that information, and in any case there are other ways 
> > besides PME# for on-board devices to report wakeup requests.  I ask 
> > mainly out of curiousity.)
> 
> It shows this literally:
> 
> 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
> 	Subsystem: ASUSTeK Computer Inc. Unknown device 8089
> 	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
> 	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> 	Interrupt: pin D routed to IRQ 20
> 	Region 0: Memory at febffc00 (32-bit, non-prefetchable) [size=1K]
> 	Capabilities: [50] Power Management version 2
> 		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> 		Status: D3 PME-Enable+ DSel=0 DScale=0 PME-
> 	Capabilities: [58] Debug port

Which means that the controller is in D3 and it supports PME#, but PME#
isn't turned on.  But as I said, Intel controllers may signal wakeup
requests in a different way (UHCI controllers definitely do, but maybe
not EHCI).

> > The simplest workaround should be to disable remote wakeup for that 
> > controller:
> > 
> > 	echo disable >/sys/bus/pci/devices/.../power/wakeup
> 
> I tried that but it didn't help.  Namely, the box resumed right after
> suspending as it had done before.
> 
> The only way to prevent it from resuming immediately after the suspend is to
> 'rmmod ehci_hcd' before the suspend.

Hmmm...  If you turn on CONFIG_USB_DEBUG, what shows up in 
/sys/class/usb_host/usb_hostN/registers where N is the bus number of 
the controller?

Also, can you post a dmesg log (with CONFIG_USB_DEBUG enabled) showing 
what happens during the suspend and immediate resume?

Alan Stern

_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux