All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <aj504@student.cs.york.ac.uk>
To: Pavel Machek <pavel@suse.cz>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	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: Tue, 14 Oct 2008 09:50:26 +0100	[thread overview]
Message-ID: <48F45D52.2010407@tuffmail.co.uk> (raw)
In-Reply-To: <20081013203648.GA3260@ucw.cz>

Pavel Machek wrote:
> 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?
> 

It could be a coincidence.  But it's suspicious enough to advise caution.  We know what the bug is, and we have a very nice workaround queued up now.  There's no reason to test any more of these specific systems to destruction :).

I did try re-installing off the vendor DVD and it was still broken.  I fear I bought it from the wrong place to get sympathetic _frontline_ support / warrantee.  I'm not interested in RMA back to Asus - too much work and downtime for a cheap system, when I have an easy workaround.  I haven't noticed any problems with "noapic".


The symptoms strongly suggest overflow in an event buffer or counter maintained by the Embedded Controller.  So the EC firmware may have a bug, of the sort that results in "unspecified behaviour".  A bug in a special purpose (read: not subject to wide testing) subsystem which has direct connections to things like frequency and voltage control.

Hopefully I'm wrong, and I don't really know what I'm talking about here.

Regards
Alan

  reply	other threads:[~2008-10-14  8:50 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
2008-10-14  8:50   ` Alan Jenkins [this message]
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=48F45D52.2010407@tuffmail.co.uk \
    --to=aj504@student.cs.york.ac.uk \
    --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=pavel@suse.cz \
    --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.