On Fri, 21 Dec 2012, Frank Schäfer wrote: > > The lspci output above shows that the host controller is _not_ > > suspended. Or at least, that's what it looks like -- maybe for some > > reason the runtime suspend code didn't put the controller into D3. > > Yes, but I checked > /sys/devices/pci0000:00/0000:00:02.0/power/runtime_status, and it > changed from 'active' to 'suspended'. > I double-checked the whole test. > > But guess what ? Today lspci changes... > > 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev > a2) (prog-if 10 [OHCI]) > Subsystem: ASUSTeK Computer Inc. Device 8234 > 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- > Interrupt: pin A routed to IRQ 23 > Region 0: Memory at fe02f000 (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: D3 NoSoftRst- PME-Enable+ DSel=0 DScale=0 PME- > Kernel driver in use: ohci_hcd That certainly looks right. And it says that the controller is not sending an erroneous wakeup signal (PME is off). Therefore we can conclude that the problem really does lie in the firmware. > [ 679.812204] usb 2-9: usb auto-suspend, wakeup 1 > [ 682.008063] hub 2-0:1.0: hub_suspend > [ 682.008072] usb usb2: bus auto-suspend, wakeup 1 > [ 682.008076] ohci_hcd 0000:00:02.0: suspend root hub > [ 682.008098] ohci_hcd 0000:00:02.0: hcd_pci_runtime_suspend: 0 Yep, that's right. > > What do you get in /sys/devices/pci0000:00/0000:00:02.0/power/ ? > > async = enabled > autosuspend_delay_ms = [I/O error] > control = auto > runtime_active_kids = 0 > runtime_active_time = 503003 > runtime_enabled = enabled > runtime_status = suspended > runtime_suspended_time = 287507 > runtime_usage = 0 > wakeup = enabled > wakeup_abort_count = 0 > wakeup_active = 0 > wakeup_active_count = 3 > wakeup_count = 3 > wakeup_expire_count = 3 > wakeup_last_time_ms = 538565 > wakeup_max_time_ms = 101 > wakeup_total_time_ms = 300 > > > The only thing I've changed is updating from kernel 3.6.10 to 3.6.11, > but that shouldn't matter, right ? No, it should not. > I also noticed that today auto-suspend is enabled by default while I had > to enable it before. > No idea what happened :( Maybe you booted a different kernel by mistake? Who knows... > Anyway, system still wakes up from S3 immediately. Okay. I dislike disabling remote wakeup for all nVidia/SiS OHCI controllers just to compensate for ASUS's mistakes, but there doesn't seem to be any alternative at this point. Alan Stern -- 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
