public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.h.duyck@intel.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "Ronciak, John" <john.ronciak@intel.com>,
	"e1000-devel@lists.sourceforge.net" 
	<e1000-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [E1000-devel] 2.6.39.2: skb_over_panic: kernel BUG at net/core/skbuff.c:127!
Date: Tue, 28 Jun 2011 08:50:43 -0700	[thread overview]
Message-ID: <4E09F853.2000103@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1106272006310.6864@p34.internal.lan>

On 06/27/2011 05:08 PM, Justin Piszcz wrote:
> Hi,
>
> Here's another crash: (see the dmesg, its right when powering the disks up)
> http://home.comcast.net/~jpiszcz/20110627/IMG_2704.JPG
>
> In this case, I was mkfs.xfs -f (some disks attached to a sata dock) over
> an Sil 3132 card, I disconnected the card and re-ran it w/ the on-board
> SATA controller and the problem no longer occurred (crashed repeatedly
> everytime with the NIC error), strange.
>
> In any case, will let you know if there are any further crashes after
> removing that PCI-e card.
>
> Justin.
Justin,

One other thing you might try is downloading and installing our latest 
igb driver from e1000.sf.net.  It looks like you are currently using the 
in-kernel driver and it is possible that there may be differences 
between the two that could resolve the issue you are experiencing.

If you are able to reproduce the issue with the Sourceforge driver then 
that will provide valuable information.  Once we have reproduced the 
issue with the Sourceforge driver, we would be able to provide you a 
debug driver so that we can narrow down this issue further.

Thanks,

Alex

  reply	other threads:[~2011-06-28 15:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 21:48 2.6.39.2: skb_over_panic: kernel BUG at net/core/skbuff.c:127! Justin Piszcz
2011-06-27 22:13 ` [E1000-devel] " Ronciak, John
2011-06-27 22:20   ` Justin Piszcz
2011-06-27 22:28     ` Ronciak, John
2011-06-27 22:34       ` Justin Piszcz
2011-06-28  0:08         ` Justin Piszcz
2011-06-28 15:50           ` Alexander Duyck [this message]
2011-06-30 23:03           ` Justin Piszcz
     [not found]           ` <alpine.DEB.2.02.1107012149480.8312@p34.internal.lan>
2011-07-02  1:53             ` Justin Piszcz

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=4E09F853.2000103@intel.com \
    --to=alexander.h.duyck@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=john.ronciak@intel.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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