From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: "linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>
Subject: Re: [REGRESSION] usb devices don't wake up the system
Date: Sun, 4 Jul 2010 01:27:53 +0200 [thread overview]
Message-ID: <201007040127.53975.rjw@sisk.pl> (raw)
In-Reply-To: <1278196923.14606.4.camel@localhost.localdomain>
On Sunday, July 04, 2010, Maxim Levitsky wrote:
> On Sun, 2010-07-04 at 01:41 +0300, Maxim Levitsky wrote:
> > On Thu, 2010-07-01 at 23:07 +0200, Rafael J. Wysocki wrote:
> > > On Thursday, July 01, 2010, Maxim Levitsky wrote:
> > > > On Thu, 2010-07-01 at 20:58 +0200, Rafael J. Wysocki wrote:
> > > > > On Thursday, July 01, 2010, Maxim Levitsky wrote:
> > > > > > On Thu, 2010-07-01 at 01:40 +0200, Rafael J. Wysocki wrote:
> > > > > > > On Thursday, July 01, 2010, Maxim Levitsky wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > >
> > > > > > > > This is my desktop, and I don't use it much.
> > > > > > > > I updated the kernel from 2.6.33 to 2.6.35-rc3, and my usb mouse (usb
> > > > > > > > 1.1 of course) doesn't wake the system anymore.
> > > > > > >
> > > > > > > Please wait for 2.6.35-rc4 to appear and see if there's any difference.
> > > > > > Why should I?
> > > > > > I always compile from git.
> > > > >
> > > > > Well, you didn't say that.
> > > > >
> > > > > > Just pulled Linus' tree, and nothing changed.
> > > > >
> > > > > If you have an Ethernet adapter in that box and you can set up for Wake-on-LAN,
> > > > > please check if that works.
> > > >
> > > > Ethernet adapter (e1000e) is broken by another regression (wol maybe
> > > > still works...) ;-)
> > >
> > > Well, what exactly do you mean by broken? It definitely works in my test box.
> > >
> > > > I test this, and probably bisect the problem anyway.
> > >
> > > It may not be necessary if the WoL test fails.
> > >
> > > > Note that wakeup from PS/2 keyboard does work.
> > > > (And it doesn't is I don't turn flags in /proc/acpi/wakeup...)
> > > >
> > > > Me thinks about doing a dual-bisect for both regressions at same
> > > > time....
> > >
> > > If you have the time for that ...
> >
> >
> > Alan. thanks for saving me from another bisect...
> > latest git tip works again.
>
> I mean, I think that
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=48826626263d4a61d06fd8c5805da31f925aefa0
>
> fixed the problem.
Good, thanks for the confirmation.
Rafael
next prev parent reply other threads:[~2010-07-03 23:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 23:31 [REGRESSION] usb devices don't wake up the system Maxim Levitsky
2010-06-30 23:40 ` Rafael J. Wysocki
2010-07-01 0:28 ` Maxim Levitsky
2010-07-01 14:42 ` Alan Stern
2010-07-01 18:58 ` Rafael J. Wysocki
2010-07-01 20:44 ` Maxim Levitsky
2010-07-01 21:07 ` Rafael J. Wysocki
2010-07-03 22:41 ` Maxim Levitsky
2010-07-03 22:42 ` Maxim Levitsky
2010-07-03 23:27 ` Rafael J. Wysocki [this message]
2010-07-04 12:51 ` Alan Stern
2010-07-04 15:44 ` Maxim Levitsky
2010-07-06 15:17 ` Alan Stern
2010-07-06 16:51 ` Maxim Levitsky
2010-07-06 17:07 ` Alan Stern
2010-07-06 20:51 ` Maxim Levitsky
2010-07-06 23:05 ` Rafael J. Wysocki
2010-07-07 15:33 ` 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=201007040127.53975.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.linux-foundation.org \
--cc=maximlevitsky@gmail.com \
/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