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:	Fri, 20 Mar 2009 18:43:54 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Christopher Schramm <debian@...kaweb.org>
CC:	linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: Re: APIC problem report

Christopher Schramm 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)
> 
> Christopher

Try booting with acpi_use_timer_override kernel parameter. The problem 
is likely the same one that shows up on my Asus A8N-SLI Deluxe with the 
latest 1805 BIOS. The kernel ignores ACPI timer overrides on NVIDIA 
chipsets since they have historically been broken, however in later BIOS 
versions this has been fixed and the override is now apparently required 
for the 8254 timer to function properly through the IO-APIC.

That problem is still there in newer kernels, but it's not fatal since 
the kernel just routes the timer through the PIC instead..
--
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/