public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 5 Jun 2007 18:37:59 -0700	[thread overview]
Message-ID: <20070606013759.GI17143@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070605235707.GB16074@tree.beaverton.ibm.com>

On Tue, Jun 05, 2007 at 04:57:07PM -0700, Darrick J. Wong wrote:
> On Tue, Jun 05, 2007 at 02:14:51PM -0700, Siddha, Suresh B wrote:
>  
> > Can you send us your system's dmesg aswell as output of /proc/interrupts?
> 
> http://sweaglesw.net/~djwong/docs/dmesg
> http://sweaglesw.net/~djwong/docs/interrupts

Didn't find anything wrong in that information. Can you try this
appended debug patch and see if you see this error msg in dmesg, when you
hit the bug? Thanks.

diff --git a/arch/x86_64/kernel/io_apic.c b/arch/x86_64/kernel/io_apic.c
index d8bfe31..3409c1f 100644
--- a/arch/x86_64/kernel/io_apic.c
+++ b/arch/x86_64/kernel/io_apic.c
@@ -720,10 +720,13 @@ static int assign_irq_vector(int irq, cpumask_t mask)
 {
 	int err;
 	unsigned long flags;
+	int cpu = smp_processor_id();
 
 	spin_lock_irqsave(&vector_lock, flags);
 	err = __assign_irq_vector(irq, mask);
 	spin_unlock_irqrestore(&vector_lock, flags);
+	if (err && !cpu_isset(cpu, cpu_online_map))
+		printk("assigning irq to a vector failed : %d\n", err);
 	return err;
 }
 

  reply	other threads:[~2007-06-06  1:41 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 [this message]
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
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=20070606013759.GI17143@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox