From: Stephen Hemminger <shemminger@vyatta•com>
To: Jesse Brandeburg <jesse.brandeburg@intel•com>
Cc: Ed Ravin <eravin@panix•com>,
roger.oksanen@cs•helsinki.fi,
"e1000-devel@lists•sourceforge.net"
<e1000-devel@lists•sourceforge.net>,
Stephen Hemminger <stephen.hemminger@vyatta•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: [E1000-devel] recent e100 fixes cause kernel panic?
Date: Fri, 19 Mar 2010 13:16:39 -0700 [thread overview]
Message-ID: <20100319131639.733c53bf@nehalam> (raw)
In-Reply-To: <1269027740.3029.33.camel@jbrandeb-mobl3.amr.corp.intel.com>
On Fri, 19 Mar 2010 12:42:20 -0700
Jesse Brandeburg <jesse.brandeburg@intel•com> wrote:
> 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@panix•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@cs•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@cs•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.
>
Davem found one thing, the memset wasn't initializing the whole maximum possible
tx ring.
--
next prev parent reply other threads:[~2010-03-19 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12968172.251031268372359953.JavaMail.root@tahiti.vyatta.com>
2010-03-19 19:42 ` [E1000-devel] recent e100 fixes cause kernel panic? Jesse Brandeburg
2010-03-19 20:16 ` Stephen Hemminger [this message]
2010-03-19 20:46 ` Ed Ravin
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=20100319131639.733c53bf@nehalam \
--to=shemminger@vyatta$(echo .)com \
--cc=e1000-devel@lists$(echo .)sourceforge.net \
--cc=eravin@panix$(echo .)com \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=roger.oksanen@cs$(echo .)helsinki.fi \
--cc=stephen.hemminger@vyatta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox