linux-kernel - Re: 2.6.30: suspend-to-ram, second s2r wakes up immediately

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200906142057.41716.rjw@sisk.pl>
Date:	Sun, 14 Jun 2009 20:57:40 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Frans Pop <elendil@...net.nl>
Cc:	thomas@...3r.de, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org, stern@...land.harvard.edu
Subject: Re: 2.6.30: suspend-to-ram, second s2r wakes up immediately

On Sunday 14 June 2009, Frans Pop wrote:
> Rafael J. Wysocki wrote:
> 
> >> 00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2) (prog-if 20 [EHCI])
> >>       Subsystem: Micro-Star International Co., Ltd. Device 7250
> >>       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 23
> >>       Region 0: Memory at fe9fac00 (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
> > 
> > PME+ means that the USB EHCI controller will signal a PME as soon as it is
> > enabled, so if PME is enabled on the controller before suspend, it will
> > wake up the system.
> > 
> > Please send a boot log.
> 
> Was already included in the initial message...
> 
> I wonder if this device could be the cause:
> [   40.232873] wlan0: register 'rndis_wlan' at usb-0000:00:02.1-6.1,
>                Wireless RNDIS device, BCM4320b based, 00:16:01:cf:56:29
> [   40.232907] usbcore: registered new interface driver rndis_wlan
> [...]
> [   41.705516] rndis_wlan 1-6.1:1.0: rndis media disconnect

Ah, thanks.

Thomas, please check the contents of

/sys/devices/pci0000:00/0000:00:02.1/power/wakeup
/sys/devices/pci0000:00/0000:00:02.0/power/wakeup

Best,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/