Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762076AbZJNWbR (ORCPT ); Wed, 14 Oct 2009 18:31:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757589AbZJNWbQ (ORCPT ); Wed, 14 Oct 2009 18:31:16 -0400 Received: from mga01.intel.com ([192.55.52.88]:35613 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755355AbZJNWbP (ORCPT ); Wed, 14 Oct 2009 18:31:15 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.44,561,1249282800"; d="scan'208";a="736444757" Date: Wed, 14 Oct 2009 15:30:38 -0700 (Pacific Daylight Time) From: "Brandeburg, Jesse" To: Tejun Heo cc: Jesse Brandeburg , Frans Pop , "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , Ingo Molnar , "hpa@zytor.com" Subject: Re: bisect results of MSI-X related panic (help!) In-Reply-To: <4AD3E875.5040800@kernel.org> Message-ID: References: <1252699744.3877.15.camel@jbrandeb-hc.jf.intel.com> <200909120623.49764.elendil@planet.nl> <4AAE0F7B.5050203@kernel.org> <4AAE105E.1080005@kernel.org> <4807377b0910091724k2a332e90i9941971f6032663c@mail.gmail.com> <4AD2E05A.6060700@kernel.org> <4AD3E875.5040800@kernel.org> User-Agent: Alpine 2.00 (WNT 1167 2008-08-23) ReplyTo: "Brandeburg, Jesse" X-X-Sender: amrjbrandeb@imapmail.glb.intel.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1675 Lines: 41 On Mon, 12 Oct 2009, Tejun Heo wrote: > 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; I'm working on it, but now that I've added a bunch of debug including the above printk, my system panics (with a stack protector canary overwrite) when loading the first network adapter with 30+ MSI-X vectors. I can boot single user mode and bring up netconsole, but then as soon as I brought up the first port with lots of MSI-X vectors, the system hard locks, no panic message. I have a bit of a theory that the node = -1 (numa_node) stuff might be playing some havoc with the code in numa_migrate.c. I'm not sure if that is contributing, but the code in there doesn't seem written to handle node = - 1 very well. As in I never see it do an smp_processor_id at the bottom before accessing the node value. Not sure if that is relevant, but I wanted to mention it before I went home. What next? I made it worse so I guess that is something. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/