From: Robert Hancock <hancockrwd@gmail.com>
To: Christopher Schramm <debian@shakaweb.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: APIC problem report
Date: Fri, 20 Mar 2009 18:43:54 -0600 [thread overview]
Message-ID: <49C4384A.5030802@gmail.com> (raw)
In-Reply-To: <49C1FE7D.9070605@shakaweb.org>
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..
next prev parent reply other threads:[~2009-03-21 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 8:12 APIC problem report Christopher Schramm
2009-03-19 10:01 ` Ingo Molnar
2009-03-19 14:30 ` Christopher Schramm
2009-03-19 15:49 ` Ingo Molnar
2009-03-19 17:44 ` Christopher Schramm
2009-03-21 0:43 ` Robert Hancock [this message]
2009-03-21 10:09 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49C4384A.5030802@gmail.com \
--to=hancockrwd@gmail.com \
--cc=debian@shakaweb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox