netdev - Re: [E1000-devel] recent e100 fixes cause kernel panic?

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-next>] [day] [month] [year] [list]

Message-ID: <1269027740.3029.33.camel@jbrandeb-mobl3.amr.corp.intel.com>
Date:	Fri, 19 Mar 2010 12:42:20 -0700
From:	Jesse Brandeburg <jesse.brandeburg@...el.com>
To:	Ed Ravin <eravin@...ix.com>, roger.oksanen@...helsinki.fi
Cc:	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	Stephen Hemminger <stephen.hemminger@...tta.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [E1000-devel] recent e100 fixes cause kernel panic?

Added netdev, the place to talk about in-kernel driver problems.

On Thu, 2010-03-11 at 22:39 -0700, Stephen Hemminger wrote:
> ----- "Ed Ravin" <eravin@...ix.com> wrote:
> 
> > I'm using the Vyatta "kenwood" Linux distribution, which is currently
> > at 2.6.31-1.  I upgraded to their latest version, and began seeing
> > kernel
> > panics shortly after starting to use ssh/scp on the network connected
> > to
> > an e100 NIC.  I was able to reproduce the problem immediately after
> > booting up - sometimes it even crashed during the boot.
> > 
> > One of the crash logs is attached.

Ed, thanks for the report, looks like these patches introduced a new
problem.  e100 hardware has a tricky data structure that seems to cause
some problems for (particularly arm) some cpu architectures.

> > 
> > Since the problem seemed to be related to e100.c, I reverted the two
> > commits to e100.c that had taken place since I last built the kernel
> > for this box:
> > 
> >   Author: Roger Oksanen <roger.oksanen@...helsinki.fi>
> >   Date:   Fri Dec 18 20:18:21 2009 -0800
> >   e100: Fix broken cbs accounting due to missing memset.
> > 
> >   Author: Roger Oksanen <roger.oksanen@...helsinki.fi>
> >   Date:   Sun Nov 29 17:17:29 2009 -0800
> >   e100: Use pci pool to work around GFP_ATOMIC order 5 memory
> > allocation failu
> > 
> > I rebuilt the kernel and it's not panicking anymore.

so you just reverted both, and its good news things are working again,
but can you try one or the other and let us know if things still break
for you?

> The Vyatta kernel for 2.6.31 is based on the 2.6.31.10 + unionfs.
> These two patches came from the 2.6.31.10 -stable update.

This is the only report of this issue I have heard so far, so something
must be a little unique to your system or workload such that the driver
works mostly.

I'm looking more closely into the panic trace now, maybe I can figure it
out from there.

-- 
Jesse Brandeburg
This email sent via Evolution, powered by Linux

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html