From: Tejun Heo <tj@kernel.org>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
Frans Pop <elendil@planet.nl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, "hpa@zytor.com" <hpa@zytor.com>
Subject: Re: bisect results of MSI-X related panic (help!)
Date: Tue, 13 Oct 2009 11:39:49 +0900 [thread overview]
Message-ID: <4AD3E875.5040800@kernel.org> (raw)
In-Reply-To: <alpine.WNT.2.00.0910120907170.11804@jbrandeb-mobl2.amr.corp.intel.com>
Brandeburg, Jesse wrote:
> On Mon, 12 Oct 2009, Tejun Heo wrote:
>>> any other debugging tricks/ideas?
>> Hmm... stackprotector adds considerable amount of stack usage and it
>> could be you're seeing stack overflow which would also explain the
>> random crashes you've been seeing. Do you have DEBUG_STACKOVERFLOW
>> turned on? This is on x86_64, right?
>
> Hi, thanks for your response,
>
> [root@jbrandeb-hc linux-2.6.32-rc1]# grep STACKO .config
> CONFIG_DEBUG_STACKOVERFLOW=y
>
> [root@jbrandeb-hc linux-2.6.32-rc1]# grep X86_64 .config
> CONFIG_X86_64=y
> CONFIG_X86_64_SMP=y
> CONFIG_X86_64_ACPI_NUMA=y
>
> stack size is 8K
>
> I tried Jarek's suggestion of CPUMASK_OFFSTACK and still panic.
> [66027.266057] Kernel panic - not syncing: stack-protector: Kernel stack
> is corrupted in: ffffffff810b4eb0
> [66027.266059]
> [66027.266070] Kernel panic - not syncing: stack-protector: Kernel stack
> is corrupted in: ffffffff81472856
> [66027.266071]
> [66027.266081] Pid: 0, comm: swapper Tainted: G W
> 2.6.32-rc2-git-debug #6
> [66027.266086] Call Trace:
>
> that was all I got. Interesting double fault, that hadn't happened
> before.
>
> the symbols might be off slightly since I rebuilt the kernel, but this was
> initial poke at offsets above in gdb
> (gdb) l *0xffffffff810b4eb0
> 0xffffffff810b4eb0 is in dynamic_irq_cleanup (kernel/irq/chip.c:86).
> 81 desc->handle_irq = handle_bad_irq;
> 82 desc->chip = &no_irq_chip;
> 83 desc->name = NULL;
> 84 clear_kstat_irqs(desc);
> 85 spin_unlock_irqrestore(&desc->lock, flags);
> 86 }
Can you please apply the following patch and try to retrigger the
panic?
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index c166019..f5a1482 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -63,6 +63,9 @@ void dynamic_irq_cleanup(unsigned int irq)
struct irq_desc *desc = irq_to_desc(irq);
unsigned long flags;
+ printk("XXX dynamic_irq_cleanup() called on %u\n", irq);
+ dump_stack();
+
if (!desc) {
WARN(1, KERN_ERR "Trying to cleanup invalid IRQ%d\n", irq);
return;
--
tejun
next prev parent reply other threads:[~2009-10-13 2:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 20:09 bisect results of MSI-X related panic (help!) Jesse Brandeburg
2009-09-11 21:05 ` Jesper Juhl
2009-09-12 4:23 ` Frans Pop
2009-09-14 9:40 ` Tejun Heo
2009-09-14 9:43 ` Tejun Heo
2009-10-10 0:24 ` Jesse Brandeburg
2009-10-11 9:24 ` Jarek Poplawski
2009-10-12 7:52 ` Tejun Heo
2009-10-12 18:00 ` Brandeburg, Jesse
2009-10-13 2:39 ` Tejun Heo [this message]
2009-10-14 22:30 ` Brandeburg, Jesse
2009-10-15 7:30 ` Tejun Heo
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=4AD3E875.5040800@kernel.org \
--to=tj@kernel.org \
--cc=elendil@planet.nl \
--cc=hpa@zytor.com \
--cc=jesse.brandeburg@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@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.