All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux acpi <linux-acpi@vger.kernel.org>
Cc: Alexey Starikovskiy <astarikovskiy@suse.de>
Subject: 2.6.28-rc1: rapid hotkeys break on eeepc again :(
Date: Tue, 28 Oct 2008 23:49:37 +0000	[thread overview]
Message-ID: <4907A511.3040603@tuffmail.co.uk> (raw)

Similar but different to the original symptoms of bugzilla #11089 (which
is closed, fixed by the specific patch I tested).  Hotkeys give up the
ghost after being held down for a while, or pressed rapidly.  However
they don't get "out of sync" as in that bug.  I've already tried the
acpi-test tree, but that didn't fix it.

Bad: v2.6.28-rc1
Good: v2.6.27-89-g3156d1e

I can't see any non-trivial changes to the EC or eeepc-laptop drivers in
that range, so it looks like I have to do this the hard way.

Bisecting: 3857 revisions left to test after this

Ow.

Alan

             reply	other threads:[~2008-10-28 23:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 23:49 Alan Jenkins [this message]
2008-10-29  0:03 ` 2.6.28-rc1: rapid hotkeys break on eeepc again :( Alexey Starikovskiy
2008-10-29  9:44   ` Alan Jenkins
2008-10-29 14:12     ` Alexey Starikovskiy
2008-10-29 14:27       ` Alan Jenkins
2008-10-29 20:27         ` Alan Jenkins
2008-10-29 20:34           ` Alexey Starikovskiy
2008-10-31 10:26             ` Bisection result: eeepc hotk breakage Alan Jenkins
2008-10-31 13:51               ` Alexey Starikovskiy
2008-10-31 13:53                 ` Alan Jenkins
2008-10-31 14:15                   ` Alexey Starikovskiy
2008-10-31 14:16                     ` Alan Jenkins
2008-10-31 14:54                       ` Alexey Starikovskiy
2008-10-31 15:46                         ` Alan Jenkins
2008-10-31 16:05                           ` Alexey Starikovskiy
2008-11-03  1:03                         ` Zhao Yakui
2008-10-31 14:58                   ` Rafael J. Wysocki
2008-10-31 15:04                     ` Alan Jenkins

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=4907A511.3040603@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=astarikovskiy@suse.de \
    --cc=linux-acpi@vger.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.