From: Tomas Carnecky <tom@dbservice.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.19: skb_over_panic, followed by a BUG at net/core/skbuff.c:93
Date: Sat, 02 Dec 2006 14:17:13 +0000 [thread overview]
Message-ID: <45718AE9.8060202@dbservice.com> (raw)
I only have a screenshot with no backtrace, if you want to see the
function names in the backtrace, please tell me what I need to do.
http://dbservice.com/ftpdir/tom/kernel-bug.jpg
I was running a 2.6.19-ge??? kernel before (I don't remember which
version exactly) and it was running fine, today I upgraded to v2.6.19
and now I have this crash. 2.6.18 works fine, too.
The bug happens when gentoo wants to bring up eth0 (starting the lo
device works fine), even a simple 'ifconfig eth0 192.168.0.11' will
crash the kernel.
The computer is a Shuttle XPC with an AMD 64bit CPU, network card is
integrated in the nforce chipset.
tom
next reply other threads:[~2006-12-02 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 14:17 Tomas Carnecky [this message]
2006-12-02 15:40 ` 2.6.19: skb_over_panic, followed by a BUG at net/core/skbuff.c:93 Helge Deller
2006-12-02 17:29 ` Phil Oester
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=45718AE9.8060202@dbservice.com \
--to=tom@dbservice.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