public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan De Luyck <ml_linuxkernel_20060528@kcore.org>
To: linux-kernel@vger.kernel.org
Subject: [2.6.17.13] nforce 57 MP-BIOS bug: 8254 timer not connected to IO-APIC
Date: Sun, 17 Sep 2006 15:45:14 +0200	[thread overview]
Message-ID: <200609171545.14701.ml_linuxkernel_20060528@kcore.org> (raw)

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
---

Prior to the BIOS upgrade I didn't have this problem - the system booted 
fine with the IO-APIC enabled. 

Using apic=debug, I see this:
--- SNIP ---
ENABLING IO-APIC IRQs
Synchronizing Arb IDs.
..TIMER: vector=0x31 apic1=0 pin1=- apic2=-1 pin2=-1
..MP-BIOS bug: 8245 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...  failed.
...trying to set up timer as Virtual Wire IRQ ... failed.
...trying to set up tijmer as ExtINT IRQ... failed :(.
Kernel panic - not syncing: IO-APIC + timer doesn't work! try using the 'noapic' 
 kernel parameter
--- SNIP ---

Using noapic, the system boots. Is there any performance impact that might be
occurring when using noapic? Anything else I can try?

Thanks,

Jan
-- 
The brotherhood of man is not a mere poet's dream; it is a most depressing
and humiliating reality.
		-- Oscar Wilde

             reply	other threads:[~2006-09-17 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17 13:45 Jan De Luyck [this message]
2006-10-21 14:11 ` [2.6.17.13] nforce 57 MP-BIOS bug: 8254 timer not connected to IO-APIC Fatih Asici

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=200609171545.14701.ml_linuxkernel_20060528@kcore.org \
    --to=ml_linuxkernel_20060528@kcore.org \
    --cc=linux-kernel@vger.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