From: Ingo Molnar <mingo@elte.hu>
To: Christopher Schramm <debian@shakaweb.org>,
Yinghai Lu <yinghai@kernel.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: APIC problem report
Date: Thu, 19 Mar 2009 11:01:22 +0100 [thread overview]
Message-ID: <20090319100122.GA30358@elte.hu> (raw)
In-Reply-To: <49C1FE7D.9070605@shakaweb.org>
* Christopher Schramm <debian@shakaweb.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
next prev parent reply other threads:[~2009-03-19 10:02 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 [this message]
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
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=20090319100122.GA30358@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=debian@shakaweb.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/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