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: <1174482929.10840.75.camel@localhost.localdomain>
Date:	Wed, 21 Mar 2007 14:15:29 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Stefan Prechtel <stefan.prechtel@...glemail.com>
Cc:	Andi Kleen <ak@...e.de>,
	Grzegorz Chwesewicz <grzegorz.chwesewicz@...lan.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 Wed, 2007-03-21 at 14:04 +0100, Stefan Prechtel wrote:
> I uploaded the output of dmesg (kernel 2.6.21-rc4-git5) (battery / ac)
> and dmidecode
> I can boot on battery with nolapic_timer and the second core is online, too.
> /proc/acpi/processor/C000/ shows the same as before but
> /proc/interrupts has changed:
> 
> (battery)
>            CPU0       CPU1
>   0:      47131          0  local-APIC-edge-fasteoi   timer
> LOC:          0      46978
> 
> (ac)
>            CPU0       CPU1
>   0:      59137          0  local-APIC-edge-fasteoi   timer
> LOC:          0      58984

That's correct. We keep the PIT alive and trigger the lapic timer
interrupt via an IPI.

	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/