Linux ACPI
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: Linux 2.6.34 causes system lockup on Compaq Presario 2200 Laptop
Date: Fri, 11 Jun 2010 13:07:35 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1006111258430.6282@localhost.localdomain> (raw)
In-Reply-To: <AANLkTilrLYu6H3GtAcP-cHpFvrm3v22uCw2EUeW_ZK0k@mail.gmail.com>

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

  reply	other threads:[~2010-06-11 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTil6GGSoc8TpzRacr1LZBZS3ee3H1ejYDSqfdul4@mail.gmail.com>
2010-05-30  3:22 ` Linux 2.6.34 causes system lockup on Compaq Presario 2200 Laptop Andrew Morton
2010-06-09 22:21   ` Len Brown
2010-06-11 16:29     ` Jeffrey Merkey
2010-06-11 17:07       ` Len Brown [this message]
2010-06-11 21:19         ` Jeffrey Merkey
2010-06-12 17:51           ` Jeffrey Merkey

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=alpine.LFD.2.00.1006111258430.6282@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=jeffmerkey@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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