Am 21.12.2012 18:02, schrieb Alan Stern: <snip> > On Fri, 21 Dec 2012, Frank Schäfer wrote: > >> 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. Ok, so the chipset doesn't matter ? <snip> >> 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. Is it possible to disable remote wakeup only for OHCI controllers with ASUS Bios ? Or would such a quirk be too complex ? Regards, Frank -- 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
