public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Jiri Kosina <jkosina@suse.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: 2.6.30: suspend-to-ram, second s2r wakes up immediately
Date: Thu, 18 Jun 2009 00:24:41 +0200	[thread overview]
Message-ID: <200906180024.42998.elendil@planet.nl> (raw)
In-Reply-To: <1245275412.22520.7.camel@localhost>

On Wednesday 17 June 2009, Thomas Meyer wrote:
> Sure. Rearranging the usb devices and removing some hubs makes the
> problem go away in most cases...

I see that you still have the Broadcom "Wireless RNDIS device" attached 
that was my initial suspect after looking through your boot log.

Does removing that device make the problem go away? Can you reproduce the 
problem at all without that device connected (during boot)?

Probably moving that device to a different controller than used for your 
keyboard and mouse will also get rid of the problem. Correct?

If removing that device does solve the problem, I would guess that without 
it you will also no longer have that "PME+" value in the output of lspci 
for the USB Controller it is connected to.

Hopefully someone else can then explain how/why that device forces the 
PME+ setting for the controller.

But I must also say that to me it seems rather fragile that in default 
configuration a random USB device can suddenly cause wakeups as result of 
a change caused by a totally different device.

Cheers,
FJP

  reply	other threads:[~2009-06-17 22:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 16:13 2.6.30: suspend-to-ram, second s2r wakes up immediately Thomas Meyer
2009-06-14 16:28 ` Rafael J. Wysocki
2009-06-14 16:44   ` Thomas Meyer
2009-06-14 17:01     ` Rafael J. Wysocki
2009-06-14 18:31       ` Frans Pop
2009-06-14 18:57         ` Rafael J. Wysocki
2009-06-15 15:37           ` Thomas Meyer
2009-06-14 19:07         ` Thomas Meyer
2009-06-14 19:29           ` Rafael J. Wysocki
2009-06-14 20:44             ` Alan Stern
2009-06-14 20:50             ` Jiri Kosina
2009-06-15 16:29               ` Thomas Meyer
2009-06-16  8:15                 ` Jiri Kosina
2009-06-16 17:13                   ` Thomas Meyer
2009-06-16 14:26                 ` Alan Stern
2009-06-16 17:47                   ` Thomas Meyer
2009-06-16 18:50                     ` Alan Stern
2009-06-17 21:50                       ` Thomas Meyer
2009-06-17 22:24                         ` Frans Pop [this message]
2009-06-29 17:30                           ` Thomas Meyer
2009-06-17 22:53                         ` Alan Stern
2009-06-29 18:13                           ` Thomas Meyer
2009-06-29 20:16                             ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200906180024.42998.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    --cc=thomas@m3y3r.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox