From: Jarek Poplawski <jarkao2@o2.pl>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG][2.6.21] af_key: kernel BUG at net/core/skbuff.c:93
Date: Tue, 27 Feb 2007 10:01:27 +0100 [thread overview]
Message-ID: <20070227090127.GA1625@ff.dom.local> (raw)
In-Reply-To: <20070226220841.GA7727@dreamland.darkstar.lan>
On 26-02-2007 23:08, Luca Tettamanti wrote:
> Hello,
> I'm running 2.6.21 (current git, at 9654640d0af). kernel blows up at
> startup, when running setkey. Kernel 2.6.20 runs fine. A couple of words
...
> ------------[ cut here ]------------
> kernel BUG at /home/kronos/src/linux-2.6.git/net/core/skbuff.c:93!
> invalid opcode: 0000 [#1]
Hi!
Could you repeat this with: CONFIG_4KSTACKS=n ?
Regards,
Jarek P.
next prev parent reply other threads:[~2007-02-27 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 22:08 [BUG][2.6.21] af_key: kernel BUG at net/core/skbuff.c:93 Luca Tettamanti
2007-02-26 22:13 ` Luca Tettamanti
2007-02-26 23:21 ` David Miller
2007-02-27 9:01 ` Jarek Poplawski [this message]
2007-02-27 16:34 ` Luca Tettamanti
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=20070227090127.GA1625@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).