From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: e1000-devel@lists.sourceforge.net
Subject: 2.6.39.2: skb_over_panic: kernel BUG at net/core/skbuff.c:127!
Date: Mon, 27 Jun 2011 17:48:59 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1106271742310.6721@p34.internal.lan> (raw)
Hi,
Looks like I am not the first one:
https://bugzilla.redhat.com/show_bug.cgi?id=429868
Any thoughts on this one?
http://home.comcast.net/~jpiszcz/20110627/IMG_2703.JPG
Rough transcription:
skb_over_panic: text:ffffffff813d711c len:44117 put:44117 head:ffff880415d40000 data:ffff880415d40040 tail:0xac95 end:0x640 dev:eth2
-- [ cut here ] ---
kernel BUG at net/core/skbuff.c:127!
invalid opcode: 0000 [#1] SMP
Was playing a video over samba (eth0) and then the kernel panic'd on eth2?
I use all INTEL controllers:
00:19.0 Ethernet controller: Intel Corporation 82578DC Gigabit Network Connection (rev 05)
01:00.0 Ethernet controller: Intel Corporation 82598EB 10-Gigabit AT2 Server Adapter (rev 01)
03:00.0 Ethernet controller: Intel Corporation 82580 Gigabit Network Connection (rev 01)
03:00.1 Ethernet controller: Intel Corporation 82580 Gigabit Network Connection (rev 01)
03:00.2 Ethernet controller: Intel Corporation 82580 Gigabit Network Connection (rev 01)
03:00.3 Ethernet controller: Intel Corporation 82580 Gigabit Network Connection (rev 01)
Justin.
next reply other threads:[~2011-06-27 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 21:48 Justin Piszcz [this message]
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
[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.1106271742310.6721@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=e1000-devel@lists.sourceforge.net \
--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®