public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christopher Schramm <debian@shakaweb.org>
To: Ingo Molnar <mingo@elte.hu>
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 18:44:52 +0100	[thread overview]
Message-ID: <49C28494.5030403@shakaweb.org> (raw)
In-Reply-To: <20090319154955.GA21034@elte.hu>

Ingo Molnar schrieb:
> 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.

Yes, you're right. Looking at the detailed kernel messages, the "8259A 
second-chance" seems to do the trick. So it's already tackled. :-)

Christopher

  reply	other threads:[~2009-03-19 17:46 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 [this message]
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=49C28494.5030403@shakaweb.org \
    --to=debian@shakaweb.org \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --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