Re: [PATCH 0/4] Fix forcedeth hibernate/wake-on-lan problems

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

 



Alan Stern wrote:> > > Also, you should run "lspci -vv" as root to see what wakeup signals the > > > USB controllers are issuing.[...]> > 00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2) (prog-if 20 [EHCI])> > 	Subsystem: ASUSTeK Computer Inc. Unknown device 8239> > 	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 B routed to IRQ 20> > 	Region 0: Memory at fe02e000 (32-bit, non-prefetchable) [size=256]> > 	Capabilities: [44] Debug port: BAR=1 offset=0098> > 	Capabilities: [80] Power Management version 2> > 		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)> > 		Status: D0 PME-Enable- DSel=0 DScale=0 PME+> > 	Kernel driver in use: ehci_hcd> > The EHCI controller settings, however, are strange.  The relevant part > is the Power Management Status line near the end:> > > 		Status: D0 PME-Enable- DSel=0 DScale=0 PME+> > This means the controller is in the D0 state (as expected) and > PME-Enable is currently turned off ("PME" stands for "Power Management > Event").  But the PME+ at the end means that as soon as PME does get > enabled -- like when the controller is suspended at the start of a > system sleep -- it _will_ send a PME signal.> > So for some reason your EHCI controller thinks a wakeup event is > pending.  This means you should examine the contents of the "registers" > file in the debugfs directory for the EHCI controller, not OHCI.
melchior:/mnt/ehci/0000:00:02.1# cat registersbus pci, device 0000:00:02.1 (driver 10 Dec 2004)EHCI Host ControllerEHCI 1.00, hcd state 1ownership 00000001SMI sts/enable 0xc0080000structural params 0x00101a8acapability params 0x0000a086status 0008 FLRcommand 010009 (park)=0 ithresh=1 period=256 RUNintrenable 37 IAA FATAL PCD ERR INTuframe 3f3aport 1 status 003400 POWER OWNER sig=kport 2 status 001000 POWER sig=se0port 3 status 003400 POWER OWNER sig=kport 4 status 003400 POWER OWNER sig=kport 5 status 001000 POWER sig=se0port 6 status 001000 POWER sig=se0port 7 status 001000 POWER sig=se0port 8 status 001000 POWER sig=se0port 9 status 001000 POWER sig=se0port 10 status 001000 POWER sig=se0irq normal 0 err 0 reclaim 0 (lost 0)complete 0 unlink 0
HTH,
-- Tobias						PGP: http://9ac7e0bc.uguu.deこのメールは十割再利用されたビットで作られています。_______________________________________________linux-pm mailing listlinux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx://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