From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Tino Keitel <tino.keitel@tikei.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] /proc/acpi/wakeup regression in 2.6.39-rc3
Date: Wed, 20 Apr 2011 22:34:12 +0200 [thread overview]
Message-ID: <201104202234.12742.rjw@sisk.pl> (raw)
In-Reply-To: <201104192328.52652.rjw@sisk.pl>
On Tuesday, April 19, 2011, Rafael J. Wysocki wrote:
> On Tuesday, April 19, 2011, Tino Keitel wrote:
> > Hi,
> >
> > I reverted some wakeup and ACPI related commits. When I reverted commit
> > 7fa69baf29de8c77a6b32c054df2abb8f11f8aa4, wakeup using the keyboard
> > worked again and /proc/acpi/wakeup behaved as expected.
>
> Oh, I doubt that this particular one is the problem.
>
> > So check this, I reverted the following commits to avoid conflicts and
> > build failures:
> >
> > c19f9a84ec807da57fd75bbd9a3f2b8269611f79
> > 5190726765b40774c069e187a958e10ccd970e65
> > 2a5d24286e8bdafdc272b37ec5bdd9e977b3767c
> > f2b56bc808addb908a5bf435d9b942c02af9a7c4
> > 7fa69baf29de8c77a6b32c054df2abb8f11f8aa4
>
> OK, thanks for narrowing this down, I'll have a look at it shortly.
I can reproduce the problem, but it seems to affect USB controllers only
and, interestingly enough, it doesn't affect the EHCI controller on my test
system. So, it seems to be specific to USB at least to some extent.
Thanks,
Rafael
next prev parent reply other threads:[~2011-04-20 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110414222525.GA24365@mac.home>
2011-04-14 22:53 ` /proc/acpi/wakeup regression in 2.6.39-rc3 Rafael J. Wysocki
2011-04-15 14:38 ` [linux-pm] " Alan Stern
2011-04-15 14:54 ` Tino Keitel
2011-04-19 20:22 ` Tino Keitel
2011-04-19 21:28 ` Rafael J. Wysocki
2011-04-20 20:34 ` Rafael J. Wysocki [this message]
2011-04-20 23:50 ` Rafael J. Wysocki
2011-04-20 20:57 ` Rafael J. Wysocki
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=201104202234.12742.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
--cc=tino.keitel@tikei.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;
as well as URLs for NNTP newsgroup(s).