[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <68676e00702270834j17bf7e4bgd50b6e271404927f@mail.gmail.com>
Date: Tue, 27 Feb 2007 17:34:21 +0100
From: "Luca Tettamanti" <kronos.it@...il.com>
To: "Jarek Poplawski" <jarkao2@...pl>
Cc: "David Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [BUG][2.6.21] af_key: kernel BUG at net/core/skbuff.c:93
On 2/27/07, Jarek Poplawski <jarkao2@...pl> wrote:
> 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 ?
Actually I cannot repeat after a make clean, with either stack
configurations. The original kernel still consistently dies in the
same point though. Must have been a mis-compilation :(
Sorry for the noise.
Luca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists