All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christopher Schramm <debian@shakaweb.org>
Cc: Yinghai Lu <yinghai@kernel.org>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: APIC problem report
Date: Thu, 19 Mar 2009 16:49:55 +0100	[thread overview]
Message-ID: <20090319154955.GA21034@elte.hu> (raw)
In-Reply-To: <49C25712.9010509@shakaweb.org>


* Christopher Schramm <debian@shakaweb.org> wrote:

> Thanks for the quick replay, Ingo!
>
> Following your request, I installed Debian 5.0. Had to use noapic 
> again for getting the boot media to work (think it utilizes 
> 2.6.26).
>
> The kernel panic is the same for all three systems: "not syncing: 
> IO-APIC + timer doesn't work!".
>
> The installed system had the same problem (2.6.26 again), then I 
> compiled 2.6.28.8 (with default config). Booting that one with 
> APIC enabled throws the known "MP-BIOS bug" message, but then 
> continues booting - no kernel panic.
>
> I will try Knoppix' kernel config and your git code, when I find 
> some spare time.

By the looks of it, chances are that various APIC fixes and 
robustization patches might have fixed your problem:

 691874f: x86: I/O APIC: timer through 8259A second-chance
 03be750: x86: I/O APIC: keep the timer IRQ masked during set-up
 24742ec: x86: I/O APIC: unmask the second-chance timer interrupt
 d11d579: x86: I/O APIC: AEOI timer acknowledgement clean-ups

These first showed up in v2.6.27. Which would match your reported 
symptoms of v2.6.26 failig and 2.6.28 working. The bootup warning
about a BIOS problem is still there because there is an underlying 
problem - we just work it around and fall back more robustly.

	Ingo

  reply	other threads:[~2009-03-19 15:51 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 [this message]
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=20090319154955.GA21034@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.