linux-kernel - Re: APIC problem report

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: <20090319154955.GA21034@elte.hu>
Date:	Thu, 19 Mar 2009 16:49:55 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Christopher Schramm <debian@...kaweb.org>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: APIC problem report


* Christopher Schramm <debian@...kaweb.org> wrote:

> Thanks for the quick replay, Ingo!
>
> Following your request, I installed Debian 5.0. Had to use noapic 
> again for getting the boot media to work (think it utilizes 
> 2.6.26).
>
> The kernel panic is the same for all three systems: "not syncing: 
> IO-APIC + timer doesn't work!".
>
> The installed system had the same problem (2.6.26 again), then I 
> compiled 2.6.28.8 (with default config). Booting that one with 
> APIC enabled throws the known "MP-BIOS bug" message, but then 
> continues booting - no kernel panic.
>
> I will try Knoppix' kernel config and your git code, when I find 
> some spare time.

By the looks of it, chances are that various APIC fixes and 
robustization patches might have fixed your problem:

 691874f: x86: I/O APIC: timer through 8259A second-chance
 03be750: x86: I/O APIC: keep the timer IRQ masked during set-up
 24742ec: x86: I/O APIC: unmask the second-chance timer interrupt
 d11d579: x86: I/O APIC: AEOI timer acknowledgement clean-ups

These first showed up in v2.6.27. Which would match your reported 
symptoms of v2.6.26 failig and 2.6.28 working. The bootup warning
about a BIOS problem is still there because there is an underlying 
problem - we just work it around and fall back more robustly.

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