linux-kernel - Re: 2.6.18-rc6-mm1 2.6.18-rc5-mm1 Kernel Panic on X60s

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060908125053.c31b76e9.akpm@osdl.org>
Date:	Fri, 8 Sep 2006 12:50:53 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Brandon Philips <brandon@...p.org>
Cc:	linux-kernel@...r.kernel.org, Brice Goglin <brice@...i.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Robert Love <rml@...ell.com>
Subject: Re: 2.6.18-rc6-mm1 2.6.18-rc5-mm1 Kernel Panic on X60s

On Fri, 8 Sep 2006 14:43:00 -0500
Brandon Philips <brandon@...p.org> wrote:

> On 12:13 Fri 08 Sep 2006, Andrew Morton wrote:
> > On Fri, 8 Sep 2006 12:44:37 -0500
> > Brandon Philips <brandon@...p.org> wrote:
> > > 2.6.18-rc4-mm3 boots ok.
> > > 
> > > I will try and bisect the problem later tonight-
> > 
> > Thanks.  First, try disabling CONFIG_PCI_MSI.
> 
> With CONFIG_PCI_MSI disabled the system boots.  

OK, thanks.

So likely candidates are:

- Brice's MSI changes

- The conversion of i386 to use the genirq code

- Eric's MSI/genirq changes

or a combination of the above.  Or something else.

<adds ccs, steps back expectantly>

> However, udev seems to very upset about network device names:
> 
> [udevd:3951]: Changing netdevice name from [eth1_temp] to [eth0]
> 
> That showed up a few hundred times.  I am running version 093 so I will
> try updating that later.

That's OK - it's a debug patch which was added to help us work out why one
or two people's net device names are getting trashed.  In fact we tracked
it down to some silliness in NetworkMonitor, regarding which certain parties
have yet to respond, iirc.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/