All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Robert Goldner <robert@au-79.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux acpi <linux-acpi@vger.kernel.org>,
	linux-stable@vger.kernel.org
Subject: Re: Patch needed for ASUS EEEPC 701 2.6.27 (perhaps a regession)
Date: Sat, 11 Oct 2008 15:50:21 +0100	[thread overview]
Message-ID: <48F0BD2D.8000001@tuffmail.co.uk> (raw)

Robert Goldner wrote:

> Hi,
>
> I am a happy user of an asus eeepc 701 with an self-made kernel 2.6.27.
> Its working quite good, but there is one patch needed to avoid problems
> related to ACPI and Hotkeys.
> After using a few hotkeys there comes a message in syslog like:
> ACPI: EC: GPE storm detected, disabling EC GPE
> and no hotkey event is recognized any more. This is quite bad on a nettop.

Hi, I reported the original bug.  It is a regression, though the issue
has been present for a few kernel versions now.

I recommend that you avoid reproducing the problem.  I now have to add
"noapic" to the boot options on my EeePC, otherwise it randomly hangs /
reboots when I press hotkeys - I think it  damaged the hardware.

BTW you can avoid reproducing the issue on buggy kernels by not pressing
hotkeys quickly - and *never* holding them down; autorepeat is the main
problem.  Wait for the effect of the previous hotkey press to take
effect (e.g. decrementing the screen brightness) before you press a
hotkey again.  But it is safest to just not use them.
 
> The needed patch and the bug description is available at:
> http://bugzilla.kernel.org/show_bug.cgi?id=10919
> The patch is called 'patch vs 2.6.27-rc7'
>
> The patch fits also to 2.6.27 without any problems and works very fine.
> Thanks to everyone who was involved.
>
> I would suggest to include this patch in the mainline kernel very soon
> (e.g. 2.6.28 or if possible in 2.6.27.1).

The patch is part of Len's ACPI patch queue for the current merge
window, so it should appear in 2.6.28.  However it's not marked "CC:
linux-stable@vger.kernel.org", so it will not be automatically included
in 2.6.27.1.

I think it's up to the ACPI maintainers, if they think there's a risk it
might introduce other regressions.  As you say, it's been tested on a
range of problematic laptops, but OTOH this area has been a minefield. 
Maybe it needs to wait, at least until it's been in an -rc release or two.

Alan

             reply	other threads:[~2008-10-11 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 14:50 Alan Jenkins [this message]
2008-10-13 20:36 ` Patch needed for ASUS EEEPC 701 2.6.27 (perhaps a regession) Pavel Machek
2008-10-14  8:50   ` Alan Jenkins
2008-10-14  9:03     ` Alexey Starikovskiy
2008-10-14  9:12       ` Alan Jenkins
  -- strict thread matches above, loose matches on Subject: below --
2008-10-11 12:04 Robert Goldner
2008-10-11 16:46 ` Rafael J. Wysocki

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=48F0BD2D.8000001@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stable@vger.kernel.org \
    --cc=robert@au-79.de \
    /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.