[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.1.10.0809291935360.4022@jikos.suse.cz>
Date: Mon, 29 Sep 2008 19:36:20 +0200 (CEST)
From: Jiri Kosina <jkosina@...e.cz>
To: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
cc: LKML <linux-kernel@...r.kernel.org>, agospoda@...hat.com,
"Ronciak, John" <john.ronciak@...el.com>,
"Allan, Bruce W" <bruce.w.allan@...el.com>,
"Graham, David" <david.graham@...el.com>,
Karsten Keil <kkeil@...e.de>,
Thomas Gleixner <tglx@...utronix.de>,
chris.jones@...onical.com, arjan@...ux.jf.intel.com
Subject: RE: e1000e NVM corruption issue status
On Mon, 29 Sep 2008, Jiri Kosina wrote:
> > > We are missing 'break;' after the memset, and that is where the
> > > hanging machine comes from (the loop keeps spinning forever), right?
> > > I will verify this right away.
> > Yep, I think you're right. I'm almost done prepping our current patch
> > series, I'll include that fix. Please let me know if your test shows it
> > fixes it.
> Yes, it fixed the hang. It crashed later though
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000050
> IP: [<ffffffffa045211b>] inet6_net_init+0x98/0xf2 [ipv6]
> PGD 39d15067 PUD 39d14067 PMD 0
> Oops: 0000 [1] SMP
> last sysfs file:
> /sys/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0000:16:00.0/local_cpus
Hmm, this happens even if I put the e1000e module completely out of way
(and it happens when userspace is starting postfix), so it might be a
completely separate issue.
--
Jiri Kosina
SUSE Labs
--
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/
Powered by blists - more mailing lists