From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: Alexey Starikovskiy <aystarik@gmail.com>,
linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: 2.6.28-rc1: rapid hotkeys break on eeepc again :(
Date: Wed, 29 Oct 2008 20:27:00 +0000 [thread overview]
Message-ID: <4908C714.5040104@tuffmail.co.uk> (raw)
In-Reply-To: <490872BF.2010908@tuffmail.co.uk>
Alan Jenkins wrote:
> Alexey Starikovskiy wrote:
>
>> Alan Jenkins wrote:
>>
>>> Alexey Starikovskiy wrote:
>>>
>>>> Please check if changing msleep to udelay helps.
>>>> Alan Jenkins wrote:
>>>>
>>>>> 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.
>>>>>
>>> That was in acpi-test, unless I misread the changelog. It's the main
>>> reason I tried that, I should have mentioned it, sorry. So no, it
>>> didn't help.
>>>
>> Any luck with bisect?
>>
>
> It didn't seem to like what I gave it. I ended up at a commit which
> lacked the EC rewrite - when as far as I'm concerned, I'm tracking a
> regression from after that point.
>
> So I tried some manual fiddling, and I'm now starting a bisect between
> two different points on mainline. That's got to work :). It looks like
> it broke sometime after the main merge from the acpi tree.
>
> $ git-describe
> v2.6.27-7166-g765426e
> $ git-bisect good
> $ git-bisect bad v2.6.28-rc1
> Bisecting: 215 revisions left to test after this
>
Well, that didn't work.
I wasn't quite methodical enough. It depends on my doing something...
it might be the lid switch, or using the sound, or network, or switching
from battery to AC, or removing the battery...
So it needn't be a regression from the patches I tested before. More
likely it's a problem with certain action(s) that I've only performed
recently.
Alan
next prev parent reply other threads:[~2008-10-29 20:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 23:49 2.6.28-rc1: rapid hotkeys break on eeepc again :( Alan Jenkins
2008-10-29 0:03 ` 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 [this message]
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=4908C714.5040104@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=astarikovskiy@suse.de \
--cc=aystarik@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox