linux-kernel - Re: [2.6.17.13] nforce 57 MP-BIOS bug: 8254 timer not connected to IO-APIC

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] [day] [month] [year] [list]

Date:	Sat, 21 Oct 2006 17:11:18 +0300
From:	"Fatih Asici" <asici.f@...il.com>
To:	"Jan De Luyck" <ml_linuxkernel_20060528@...re.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [2.6.17.13] nforce 57 MP-BIOS bug: 8254 timer not connected to IO-APIC

On 9/17/06, Jan De Luyck <ml_linuxkernel_20060528@...re.org> wrote:
> Hello list,
>
> Using kernel 2.6.17.13 on an AMD M2 64x2, motherboard ABIT KN9-SLI. Chipset
> on this board is an nForce 570 SLI MCP.
>
> Today I bumped into this, after upgrading my BIOS to fix a boot issue that I
> was having (sometimes it wouldn't go past the POST screen):
>
> ---
> MP-BIOS Bug: 8254 timer not connected to IO-APIC
> Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the 'noapic'
>  kernel parameter
> ---

I have the same problem with 2.6.18.1. I am using  ASUS M2NPV-MX ACPI
BIOS Revision 0405.
Interestingly, if I use "quiet" parameter, it succesfully boots, but
it gives those error messages and hangs without the "quiet" parameter.
 Would it be a race condition?
-
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/