On Sat, 07 Jul 2012 19:23:08 -0700, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
wrote:
> Also, what does the "lspci -vv" output show for the controller if you
> run it with superuser permissions?
[Sat Jul 07 12:50:10 -0700 -- alvarezp@octavio:/sys/kernel/debug/usb]
$ sudo lspci -vv -s 0000:00:0b.1
0b.1 is the EHCI controller. We want to see the OHCI controller, 0b.0.
Sorry about that.
[Sat Jul 07 20:41:28 -0700 -- alvarezp@octavio:~]
$ sudo lspci -vv -s 0000:00:0b.0
00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a2)
(prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. A8N-VM CSM Mainboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at d5006000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ohci_hcd
I also bisected the "3.2 doesn't sleep due to ohci" problem and found
this:
commit a6eeeb9f45b5a417f574f3bc799b7122270bf59b
Author: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
Date: Mon Sep 26 11:23:38 2011 -0400
USB: Update USB default wakeup settings
Yes, that commit enables wakeup for USB host controllers by default.
Before that, you had to enable wakeup by hand. The question is: Why
does the controller think it needs to wake up the system?
Can you also post a dmesg log showing a full suspend/immediate-resume
cycle with CONFIG_USB_DEBUG enabled?
Will do as soon as I reboot into a suitable kernel.
Thanks for your help.
--
Octavio.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
