From: Pavel Machek <pavel@suse.cz>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: Robert Goldner <robert@au-79.de>,
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: Mon, 13 Oct 2008 22:36:49 +0200 [thread overview]
Message-ID: <20081013203648.GA3260@ucw.cz> (raw)
In-Reply-To: <48F0BD2D.8000001@tuffmail.co.uk>
On Sat 2008-10-11 15:50:21, Alan Jenkins wrote:
> 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.
I guess your hw went bad for some other reason. Restore original
system and if it is still broken, RMA?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-10-13 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 14:50 Patch needed for ASUS EEEPC 701 2.6.27 (perhaps a regession) Alan Jenkins
2008-10-13 20:36 ` Pavel Machek [this message]
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=20081013203648.GA3260@ucw.cz \
--to=pavel@suse.cz \
--cc=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.