public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, James <jamesclv@us.ibm.com>,
	keith maanthey <kmannth@us.ibm.com>,
	Chris McDermott <lcm@us.ibm.com>
Subject: Re: [RFC][PATCH] fix target_cpus() for summit subarch
Date: Fri, 27 Aug 2004 19:02:57 -0700	[thread overview]
Message-ID: <20040828020257.GX2793@holomorphy.com> (raw)
In-Reply-To: <1093652688.14662.16.camel@cog.beaverton.ibm.com>

On Fri, Aug 27, 2004 at 05:24:48PM -0700, john stultz wrote:
> I've been hunting down a bug affecting IBM x440/x445 systems where the
> floppy driver would get spurious interrupts and would not initialize
> properly. 
> After digging James Cleverdon pointed out that target_cpus() is routing
> the interrupts to the clustered apic broadcast mask. This was causing
> multiple interrupts to show up, breaking the floppy init code. 
> This one-liner fix simply routes interrupts to the first cpu to resolve
> this issue.
> Any comments or feedback would be appreciated.

You're using fixed delivery mode, so non-singleton destinations break.
If lowest prio delivery mode saw this, you'd have IO-APIC errata.


-- wli

  reply	other threads:[~2004-08-28  2:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-28  0:24 [RFC][PATCH] fix target_cpus() for summit subarch john stultz
2004-08-28  2:02 ` William Lee Irwin III [this message]
2004-08-28  6:17 ` Martin J. Bligh
2004-08-30 18:03   ` john stultz
2004-08-30 20:46     ` john stultz
2004-08-30 21:24     ` James Cleverdon
2004-08-31  1:06       ` john stultz

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=20040828020257.GX2793@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=jamesclv@us.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=kmannth@us.ibm.com \
    --cc=lcm@us.ibm.com \
    --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