lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.LFD.2.00.1006111258430.6282@localhost.localdomain>
Date:	Fri, 11 Jun 2010 13:07:35 -0400 (EDT)
From:	Len Brown <lenb@...nel.org>
To:	Jeffrey Merkey <jeffmerkey@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: Linux 2.6.34 causes system lockup on Compaq Presario 2200 Laptop

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ