From: "Martin J. Bligh" <mbligh@aracnet.com>
To: john stultz <johnstul@us.ibm.com>, lkml <linux-kernel@vger.kernel.org>
Cc: William Lee Irwin III <wli@holomorphy.com>,
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 23:17:47 -0700 [thread overview]
Message-ID: <79750000.1093673866@[10.10.2.4]> (raw)
In-Reply-To: <1093652688.14662.16.camel@cog.beaverton.ibm.com>
--john stultz <johnstul@us.ibm.com> wrote (on Friday, August 27, 2004 17:24:48 -0700):
> 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.
I'd say that means your hardware is horribly broken ... but I guess this
might be a suitable workaround given we're going to reprogram them all
later.
So ... do all your interrupts end up on the first cpu now, or does
irqbalance take care of it?
M.
next prev parent reply other threads:[~2004-08-28 6:20 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
2004-08-28 6:17 ` Martin J. Bligh [this message]
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='79750000.1093673866@[10.10.2.4]' \
--to=mbligh@aracnet.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 \
--cc=wli@holomorphy.com \
/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