From: Greg KH <greg@kroah.com>
To: Akkana Peck <akkana@shallowsky.com>
Cc: Dmitry Torokhov <dtor@mail.ru>,
stable@kernel.org, linux-acpi@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>
Subject: Re: [stable] [Bugme-new] [Bug 9555] New: Suspend to RAM horks keyboard autorepeat, system bell, trackpad
Date: Wed, 12 Dec 2007 23:03:36 -0800 [thread overview]
Message-ID: <20071213070336.GA12252@kroah.com> (raw)
In-Reply-To: <20071213064532.GA7618@shallowsky.com>
On Wed, Dec 12, 2007 at 10:45:32PM -0800, Akkana Peck wrote:
> The problem seems fixed in 2.6.24-rc5 (and I'd like to apologize for
> wasting everyone's time by not checking for a new version first).
> So the bug appeared in the patches that took 2.6.23.1 to 2.6.23.8, and
> was fixed by something between .23.8 and .24-rc5.
>
> I'm fine with closing the bug since it's working fine in .24-rc5,
> but if anyone is curious what the problem was, I'm happy to help
> with tracking it down. It's very easily reproducible on this machine.
Yes, it would be nice to find out the 2.6.23 patch that caused this, so
we can revert it as people are still using the 2.6.23 tree :)
Can you do a bisection with the releases between 2.6.23.1 and 2.6.23.8
and see which release and then which patch caused this to happen?
thanks,
greg k-h
prev parent reply other threads:[~2007-12-13 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9555-10286@http.bugzilla.kernel.org/>
2007-12-13 2:33 ` [Bugme-new] [Bug 9555] New: Suspend to RAM horks keyboard autorepeat, system bell, trackpad Andrew Morton
[not found] ` <20071212183349.f81464bf.akpm@linux-foundation.org>
2007-12-13 6:45 ` Akkana Peck
[not found] ` <20071213064532.GA7618@shallowsky.com>
2007-12-13 7:03 ` Greg KH [this message]
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=20071213070336.GA12252@kroah.com \
--to=greg@kroah.com \
--cc=akkana@shallowsky.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=dtor@mail.ru \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stable@kernel.org \
/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