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: Mon, 27 Jun 2011 18:20:51 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1106271814200.6721@p34.internal.lan> (raw)
In-Reply-To: <D38E8E86660E514AB505863C19C9287C03A525@ORSMSX101.amr.corp.intel.com>
On Mon, 27 Jun 2011, Ronciak, John wrote:
> Sorry to hear of your problem. Please do not try to relate something that happened on REHL4 to something that is happening in the 2.6.39 .2 kernel.
>
> Is the problem reproducible? If so, does this happen every time? What interface had what HW associated with it? The info included below doesn't say. What in type of traffic was happening on eth2?
>
> Cheers,
> John
>
Hello John,
Not much actually, just regular cable modem network traffic (was not even
utilizing it heavily), vnstat below:
eth2 18:11
^ r
| r r
| r r
| r r
| r r r r
| r r r r r
| r r r r r
| r r r r r r r r
| r r r r r r r r r
| r r r r r r r r r
-+--------------------------------------------------------------------------->
| 19 20 21 22 23 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18
h rx (KiB) tx (KiB) h rx (KiB) tx (KiB) h rx (KiB) tx (KiB)
19 89730 8838 03 11249 620 11 126496 9383
20 10972 596 04 43551 1729 12 86326 6513
21 11489 611 05 12159 699 13 47805 3863
22 12073 630 06 12080 712 14 52322 4577
23 12153 654 07 11894 710 15 135715 8618
00 11536 594 08 7392 396 16 75680 6181
01 11159 560 09 0 0 17 33817 3213
02 11564 575 10 759 51 18 4315 190
The most recent crash was at 16:33.
The system crashed earlier too but I had X running so I couldn't get a
screenshot, there is no serial port on this machine and netconsole does not
work with this type of failure.
It is unfortunately not reproducible, is there any debugging options that
you would recommend I can enable that will expose this bug? I'm up for
anything at this point.
All of this may have started when I added a 4-port Intel NIC:
http://www.intel.com/Assets/PDF/prodbrief/323205.pdf
NIC = Intel Ethernet I340 Server Adatper
But this is just a guess..
Justin.
next prev parent reply other threads:[~2011-06-27 22:21 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 [this message]
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
[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.1106271814200.6721@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®