All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akkana Peck <akkana@shallowsky.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: stable@kernel.org, bugme-daemon@bugzilla.kernel.org,
	Dmitry Torokhov <dtor@mail.ru>,
	linux-acpi@vger.kernel.org,
	"linux-pm@lists.linux-foundation.org"
	<linux-pm@lists.linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 9555] New: Suspend to RAM horks keyboard autorepeat, system bell, trackpad
Date: Wed, 12 Dec 2007 22:45:32 -0800	[thread overview]
Message-ID: <20071213064532.GA7618@shallowsky.com> (raw)
In-Reply-To: <20071212183349.f81464bf.akpm@linux-foundation.org>

[Replying again with all CCs]

Andrew Morton writes:
> > http://bugzilla.kernel.org/show_bug.cgi?id=9555
> > 
> >            Summary: Suspend to RAM horks keyboard autorepeat, system bell,
> >                     trackpad
[ ... ]
> > With 2.6.23.8, when I suspend to RAM (using /usr/sbin/hibernate -F
> > /etc/hibernate/ram.conf) from within X, when I resume I see the
> > following odd behavior:
> > 
> > 1. The system bell is now half a second long.
> > 2. Keyboard autorepeat has a very long delay -- like 7 seconds before the first
> > repeated character shows up.
> > 3. If I configure X to use the (Alps) trackpad via the synaptics  driver, after
> > resuming, clicks from the trackpad don't work at all -- not only are taps
> > ignored (which is how I've configured xorg.conf) but the physical buttons don't
> > generate click events either. If I configure X to use the trackpad just as a
> > PS/2 mouse, though, it still works normally after resuming.
[ ... ]
> 
> A regression in the -stable series.
> 
> IT'd be interesting to see if this has gone into 2.6.24-rc5 too.

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.

  reply	other threads:[~2007-12-13  7:15 UTC|newest]

Thread overview: 5+ 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
2007-12-13  2:33 ` Andrew Morton
2007-12-13  6:45   ` Akkana Peck [this message]
2007-12-13  7:03     ` [stable] " Greg KH
2007-12-13  6:45   ` Akkana Peck

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=20071213064532.GA7618@shallowsky.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.