linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: Alan Jenkins <aj504@student.cs.york.ac.uk>,
	Pavel Machek <pavel@suse.cz>, 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 10:12:41 +0100	[thread overview]
Message-ID: <48F46289.5050508@tuffmail.co.uk> (raw)
In-Reply-To: <48F46053.6070306@gmail.com>

Alexey Starikovskiy wrote:
> Alan Jenkins wrote:
>> 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
>>   
> Did you try to disconnect all power resources (e.g. AC adapter and all
> batteries and wait for some time)?

Yes, I tried leaving it with AC + battery unplugged overnight.

> May be there are some default settings in the BIOS?
> This looks small enough to be a HW failure...

I also upgraded the BIOS to the latest version.  And tried the BIOS
setup option to restore defaults.  Maybe there is some more state, but
it's not like a desktop where I can easily remove the CMOS battery.

Thanks
Alan

  reply	other threads:[~2008-10-14  9:12 UTC|newest]

Thread overview: 6+ 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
2008-10-14  9:03     ` Alexey Starikovskiy
2008-10-14  9:12       ` Alan Jenkins [this message]
     [not found] <48F09658.8060502@au-79.de>
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=48F46289.5050508@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=aj504@student.cs.york.ac.uk \
    --cc=aystarik@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).