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]

Date:	Mon, 19 Mar 2007 20:27:56 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Stefan Prechtel <stefan.prechtel@...glemail.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu,
	Len Brown <lenb@...nel.org>, Andi Kleen <ak@...e.de>,
	john stultz <johnstul@...ibm.com>
Subject: Re: BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4})

Stefan,

On Mon, 2007-03-19 at 19:53 +0100, Stefan Prechtel wrote:
> You can find the files here:
> http://bugzilla.kernel.org/show_bug.cgi?id=8235

thanks for providing the data. Your ACPI tables don't provide
information about the power states (C-States), but your BIOS seems to
switch the CPUs into deeper power states, when it runs on battery. In
those deeper power states the local APIC timers and the TSC are stopped.
So the machine waits for ever on the next timer interrupt.

We have a broadcast mechanism for this, which gets activated from ACPI,
but the broadcast mechanism is not activated:

[    3.798000] Clock Event Device: pit
....
[    3.798000] tick_broadcast_mask: 00000000

Can you please boot with 2.6.20 or earlier and check the output
of /proc/interrupts ?

IRQ#0 and the LOC (local APIC timer) Interrupts should increment in the
same frequency.

	tglx

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