mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: "Ronciak, John" <john.ronciak@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"e1000-devel@lists.sourceforge.net" 
	<e1000-devel@lists.sourceforge.net>
Subject: RE: [E1000-devel] 2.6.39.2: skb_over_panic: kernel BUG at net/core/skbuff.c:127!
Date: Thu, 30 Jun 2011 19:03:52 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1106301900500.16354@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.02.1106272006310.6864@p34.internal.lan>



On Mon, 27 Jun 2011, Justin Piszcz wrote:

>
> On Mon, 27 Jun 2011, Justin Piszcz wrote:
>
>> 
>> 
>> On Mon, 27 Jun 2011, Ronciak, John 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.
>
>

Hi,

Per:
http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg04232.html

I am using the drivers on e1000.sf.net for:
e1000e
igb
igbe

version:        1.3.17-NAPI
srcversion:     BA556C5C800B0D67E5F8B84
version:        3.0.22
srcversion:     45B8078075068728A5A5573
version:        3.3.9-NAPI
srcversion:     0734B0E06E21B50A92ADDFF

No crashes when I run mkfs.xfs (w/the eSATA card back in).

Will monitor throughout to see if it recurs.
When will the current -stable versions go into mainline?

Also, is there a kernel option to 'pause' or take a screenshot of a kernel 
console crash/dump/stack trace (besides kdump) and not reboot the machine 
when it crashes?

I do not have any option to reboot on panic, but sometimes it still does 
that.

Thanks!

Justin.

  parent reply	other threads:[~2011-06-30 23:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 21:48 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
2011-06-30 23:03           ` Justin Piszcz [this message]
     [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=alpine.DEB.2.02.1106301900500.16354@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=john.ronciak@intel.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

all inboxes | Powered by JetHome®