linux-kernel - Re: BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4})

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: <200703211342.59093.ak@suse.de>
Date:	Wed, 21 Mar 2007 13:42:58 +0100
From:	Andi Kleen <ak@...e.de>
To:	tglx@...utronix.de
Cc:	Grzegorz Chwesewicz <grzegorz.chwesewicz@...lan.com>,
	Stefan Prechtel <stefan.prechtel@...glemail.com>,
	linux-kernel@...r.kernel.org, mingo@...e.hu,
	Len Brown <lenb@...nel.org>, john stultz <johnstul@...ibm.com>
Subject: Re: BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4})

On Wednesday 21 March 2007 12:14, Thomas Gleixner wrote:
> On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
> > > The BIOS/ACPI is broken and does only expose C1, which should not
> > > switch off LAPIC. The BIOS is switching into deeper C-States behind the
> > > kernels back somehow.
> >
> > Hmm, perhaps we can check AMD && (cstate >= 2 || has a battery) ?
> > Should be doable by looking up the battery object in ACPI
>
> Which makes us rely on another ACPI feature. What guarantees that the
> ACPI tables are correct for this one ?

Nothing, but wrong C2 and wrong battery state together seems unlikely.

-Andi
-
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/