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]

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


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

> Hi,
>
> I found a problem with APIC on a desktop PC equipped with Asus' 
> M2N, running the manufacturer's AMI BIOS - version 0803.
>
> I've tried booting Knoppix 5.3.1 (Kernel 2.6.24.4) and GParted 
> live (Debian's 2.6.26-13). Both will only boot if noapic parameter 
> is used. Otherwise I get "MP-BIOS bug: 8254 timer not connected to 
> IO-APIC" resulting in a kernel panic.
>
> apic=debug gives "ACPI: Core revision 20080321", "Version 
> 80050010" (twice), "ID: 0", "LVT0: 700", "LVT1:400" and "ESR value 
> before enabling vector: 0x00000004 after: 0x00000000".
>
> Hope it's of some use (and the best place to report it)

Any chance to build and run a more recent kernel on it, to see 
whether this issue still occurs? The latest APIC code is at:

  http://people.redhat.com/mingo/tip.git/README

And i suspect you should pick up the Knoppix .config and build with 
that to reproduce this issue. A digital picture of the panic would 
be useful as well.

	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/