mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jak@rudolph.ccur.com (Joe Korty)
To: macro@ds2.pg.gda.pl
Cc: joe.korty@ccur.com (Joe Korty),
	mingo@chiara.elte.hu (Ingo Molnar),
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] irq0 affinity broke on some i386 boxes
Date: Fri, 1 Mar 2002 14:51:49 -0500 (EST)	[thread overview]
Message-ID: <200203011951.TAA12018@rudolph.ccur.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1020301181736.3130F-100000@delta.ds2.pg.gda.pl> from "Maciej W. Rozycki" at Mar 01, 2002 06:41:41 PM

> On Mon, 25 Feb 2002, Joe Korty wrote:
>
>>   The following patch fixes a bug that prevents a write to
>> /proc/irq/0/smp_affinity from actually changing the cpu affinity
>> of IRQ #0, on all the (Dell server) SMP machines I have access to.
> 
>  A nice spotting.  However what you describe is only a side effect of the
> bug, which is the IRQ is kept registered at the wrong pin.  It's only
> because the timer is special and it's edge-triggered it remained unnoticed
> for so long.
> 
>  I propose the following patch.  [...]
>
>  I don't know if the changes are relevant to your system as you haven't
> sent the relevant fragment of a bootstrap log from your system.  They
> affect all systems that have a bogus IRQ 0 entry in the MP table.  For
> other systems the patch is equivalent to yours.  Please test it if it
> works for you as I don't have a suitable system with IRQ 0 unconnected
> (I've been able to verify it builds only).  Everyone with such a system is
> invited to test the patch as well.


Thanks.  Your proposed patch works fine on the two of my five SMP systems
I have been able to get my hands on this afternoon.

Joe

PS: My original dmesg logs may now be found at
http://www.mindspring.com/~jakorty/irq0.bugreport.orig.

  reply	other threads:[~2002-03-01 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 18:56 Joe Korty
2002-03-01 17:41 ` Maciej W. Rozycki
2002-03-01 19:51   ` Joe Korty [this message]
2002-03-01 20:21     ` Maciej W. Rozycki

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=200203011951.TAA12018@rudolph.ccur.com \
    --to=jak@rudolph.ccur.com \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=mingo@chiara.elte.hu \
    /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

all inboxes | Powered by JetHome®