From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
linux-kernel@vger.kernel.org, ebiederm@xmission.com
Subject: Re: Device hang when offlining a CPU due to IRQ misrouting
Date: Mon, 18 Jun 2007 16:54:34 -0700 [thread overview]
Message-ID: <20070618235434.GB7160@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070618223819.GD9751@tree.beaverton.ibm.com>
On Mon, Jun 18, 2007 at 03:38:20PM -0700, Darrick J. Wong wrote:
> On Thu, Jun 07, 2007 at 05:57:26PM -0700, Siddha, Suresh B wrote:
>
> > As you have the failing system, you need to do more detective work and
> > help me out. Can you try this debug patch and send across the dmesg after the
> > bug happens and also can you try different compiler to see if something
> > changes..
>
> Hrm, I just updated to -rc5. Interrupts being handled by the IOAPIC
> don't suffer from this problem, but MSI interrupts are still affected.
> I added a few printks to the kernel to figure out what IRQ affinity
> masks were being passed around and saw this:
>
> [ 256.298773] Breaking affinity for irq 4341
> [ 256.298774] irq=4341 affinity=2 mask=d
> <call to set_affinity>
> [ 256.298787] irq=4341 affinity=d
> <ethernet on irq 4341 stops working>
And just to make sure, at this point, your MSI irq 4341 affinity
(/proc/irq/4341/smp_affinity) still points to '2'?
> I'll keep digging, but at least it appears that the problem has been
> shrunk down to something the MSI code.
thanks,
suresh
next prev parent reply other threads:[~2007-06-18 23:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 0:44 Device hang when offlining a CPU due to IRQ misrouting Darrick J. Wong
2007-06-01 19:39 ` Eric W. Biederman
2007-06-05 17:23 ` Siddha, Suresh B
2007-06-05 17:36 ` Darrick J. Wong
2007-06-05 18:13 ` Siddha, Suresh B
2007-06-05 18:33 ` Darrick J. Wong
2007-06-05 18:40 ` Siddha, Suresh B
2007-06-05 20:09 ` Darrick J. Wong
2007-06-05 21:14 ` Siddha, Suresh B
2007-06-05 23:57 ` Darrick J. Wong
2007-06-06 1:37 ` Siddha, Suresh B
2007-06-06 18:58 ` Darrick J. Wong
2007-06-06 19:35 ` Siddha, Suresh B
2007-06-06 23:16 ` Darrick J. Wong
2007-06-08 0:57 ` Siddha, Suresh B
2007-06-18 22:38 ` Darrick J. Wong
2007-06-18 23:54 ` Siddha, Suresh B [this message]
2007-06-19 0:51 ` Darrick J. Wong
2007-06-19 17:54 ` Eric W. Biederman
2007-06-19 18:00 ` Siddha, Suresh B
2007-06-19 18:55 ` Eric W. Biederman
2007-06-19 19:06 ` Darrick J. Wong
2007-06-19 19:59 ` Siddha, Suresh B
2007-06-19 20:49 ` Darrick J. Wong
2007-06-19 22:08 ` Siddha, Suresh B
2007-06-23 23:54 ` Rafael J. Wysocki
2007-06-23 23:58 ` Andrew Morton
2007-06-24 0:45 ` Eric W. Biederman
2007-06-24 0:51 ` Siddha, Suresh B
2007-06-24 12:50 ` Rafael J. Wysocki
2007-06-24 0:28 ` Siddha, Suresh B
2007-06-24 12:48 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2007-06-01 21:57 Emmanuel Fusté
2007-06-02 0:18 ` Eric W. Biederman
2007-06-02 2:19 ` Darrick J. Wong
2007-06-02 3:48 ` Eric W. Biederman
2007-06-03 21:03 Emmanuel Fusté
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=20070618235434.GB7160@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=djwong@us.ibm.com \
--cc=ebiederm@xmission.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 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.