DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=g0TttOJuMBFPEZIbjznnzn5k1TlJQ+5xoLiiigaO/4OzCNAvknqsMT4MP7BZtUy+5D
         nPI+ISowB690pduSjDyXybmB7fkJ6pLTVe5ZnM3VIhWRTlqFfyVrCGyV5hAd5M7gFpJG
         pq0HkxtjTCVwwd3RXaJW+pkXZ1yxCvmYy510Q=
MIME-Version: 1.0
In-Reply-To: <alpine.LFD.2.00.1006111258430.6282@localhost.localdomain>
References: <AANLkTil6GGSoc8TpzRacr1LZBZS3ee3H1ejYDSqfdul4@mail.gmail.com>
	<20100529202253.0bd18bbd.akpm@linux-foundation.org>
	<alpine.LFD.2.00.1006091821060.1402@localhost.localdomain>
	<AANLkTilrLYu6H3GtAcP-cHpFvrm3v22uCw2EUeW_ZK0k@mail.gmail.com>
	<alpine.LFD.2.00.1006111258430.6282@localhost.localdomain>
Date: Fri, 11 Jun 2010 15:19:09 -0600
Message-ID: <AANLkTimYYAD3hKRi9IXPSn428YqeGnR1Ig02FpVIbVgL@mail.gmail.com>
Subject: Re: Linux 2.6.34 causes system lockup on Compaq Presario 2200 Laptop
From: Jeffrey Merkey <jeffmerkey@gmail.com>
To: Len Brown <lenb@kernel.org>, linux-kernel@vger.kernel.org,
       linux-acpi@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2261
Lines: 57

On Fri, Jun 11, 2010 at 11:07 AM, Len Brown <lenb@kernel.org> wrote:
> On Fri, 11 Jun 2010, Jeffrey Merkey wrote:
>
>> Len,
>>
>> I am having trouble getting a trace of this because its down hard to
>> reproduce. ?The reason is the lockup happens before I log into the
>> laptop. ?i.e. I boot 2.6.34 and if I let the laptop just sit there is
>> happens. ?If I log in and start doing work on it, it does not seem to
>> happen. ?It's related to using the laptop on battery mode with the
>> charger removed. ?I have a 2U appliance setup I am working on today
>> and this frees up the laptop to try to reproduce this. ?The flaky
>> battery power misreporting was in fact accurate. ?The battery in that
>> laptop is 6 years old and does have low power. ?I am certain the
>> lockup if related though. ?I will try to reproduce today and setup the
>> trace to run after boot. ?I have had it sitting there for an ?hour and
>> it has not reoccurred. ?Let me try through today and if I cannot
>> reproduce, close the bug.
>
> Good to know, Jeff.
>
> One possibility is that the old battery is confusing
> the embedded controller -- possibly exposing a firmware bug.
> The EC, in turn, is fully capable of hanging the OS.
>
> If you *can* reproduce it, it may be interesting to bisect
> recent changes to drivers/acpi/ec.c
>
> Also, if you can reproduce it, it would be good to verify
> that the problem occurs only when the battery driver is loaded.
>
> thanks,
> -Len
>
>> > Please attach the output of acpidump here:
>> >
>> > https://bugzilla.kernel.org/show_bug.cgi?id=16136
>
> We could still use this output -- note that you can
> capture it at any time, independent of the failure,
> and independent of the kernel -- as it is simply
> a copy of the tables that the BIOS is exporting to Linux.
>
> thanks,
> -Len Brown, Intel Open Source Technology Center
>

I can tell you for certain it does only happen when the battery driver
is loaded.  Still has not ocurred.  Just rebooted it 15 minutes ago --
trying again.

Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/