All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: akpm@linux-foundation.org, andi@firstfloor.org,
	linux-acpi@vger.kernel.org, hmh@hmh.eng.br, maxi@daemonizer.de,
	stable@kernel.org
Subject: Re: [patch 2/2] acpi: Avoid dropping rapid hotkey events (or other GPEs) on Asus EeePC
Date: Sat, 23 Aug 2008 12:31:35 +0100	[thread overview]
Message-ID: <48AFF517.90205@tuffmail.co.uk> (raw)
In-Reply-To: <48AE99E3.7090702@tuffmail.co.uk>

Alan Jenkins wrote:
> Alexey Starikovskiy wrote:
>   
>> Here is the patch.
>>
>> Please try/review.
>>
>>     
> Sorry, I can't help with testing this any more.  The "bad state" I
> complained about earlier seems to be permanent now.
>
> I left the laptop with AC and battery disconnected last night.  This
> morning both 2.6.22 and 2.6.24-19-generic (ubuntu) are locking up or
> rebooting as soon as I press a hotkey.  The patch resets the default
> behaviour back to 2.6.24, so it won't make any difference.
>
> None of these kernels should have the GPE polling problem.  There are
> many people using Ubuntu on the EeePC without complaint; I must have
> damaged the hardware or firmware.
>
> OTOH 2.6.21.4-eeepc (the pre-installed kernel from Xandros/Asus) is
> immune.  I will work on it, but don't expect anything soon.
>   
I was able to bisect this to a config option, X86_UP_IOAPIC.  I can get
rid of it on all kernels by just booting with noapic.

I was then able to try your patch, which works fine.  I see the warning
in the kernel log, but no hotkey keypresses are lost.

Thanks
Alan

  reply	other threads:[~2008-08-23 11:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 23:41 [patch 2/2] acpi: Avoid dropping rapid hotkey events (or other GPEs) on Asus EeePC akpm
2008-08-21 12:12 ` Alexey Starikovskiy
2008-08-21 12:22   ` Andi Kleen
2008-08-21 16:18     ` Andrew Morton
2008-08-21 13:35   ` Alan Jenkins
2008-08-21 13:55     ` Alexey Starikovskiy
2008-08-21 14:42       ` Alan Jenkins
2008-08-21 16:01         ` Alexey Starikovskiy
2008-08-22 10:50           ` Alan Jenkins
2008-08-23 11:31             ` Alan Jenkins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-21 18:42 Alan Jenkins
2008-09-21 19:17 ` Alexey Starikovskiy
2008-09-22  1:31   ` Zhao Yakui
2008-09-22  9:08   ` Alan Jenkins
2008-09-22 11:02     ` Alan Jenkins
2008-09-22 11:36       ` Alexey Starikovskiy
2008-09-22 11:49         ` Alexey Starikovskiy
2008-09-22 12:30           ` Alan Jenkins
2008-09-22 12:35             ` Alexey Starikovskiy
2008-09-22 13:44               ` Alan Jenkins
2008-09-22 19:36                 ` Alexey Starikovskiy
2008-09-23  6:19           ` Zhao Yakui
2008-09-22  1:20 ` Zhao Yakui

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=48AFF517.90205@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=astarikovskiy@suse.de \
    --cc=hmh@hmh.eng.br \
    --cc=linux-acpi@vger.kernel.org \
    --cc=maxi@daemonizer.de \
    --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.