Kernel panic

"Cho Soon Yim" <[email protected]>
Newsgroups gmane.linux.network.bridge.ebtables.devel
Message-ID <[email protected]>
Hi,

I got the following kernel panic messages,
------------------------------------------------------------------------
Warning: kfree_skb passed an skb still on a list (from c022069f).
kernel BUG at skbuff.c:323!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c021b9df>]    Not tainted
EFLAGS: 00010286
eax: 00000045   ebx: f79e3980   ecx: 00000000   edx: 00000001
esi: f79e3980   edi: c038a740   ebp: f7e20000   esp: c030fe98
ds: 0018   es: 0018   ss: 0018
Process swapper (pid: 0, stackpage=c030f000)
Stack: c02b23c0 c022069f f78beb80 f79e3980 00000081 f7e20000 00000000
00000081
       c022069f f79e3980 c021b767 00000063 f8995a3b 000000f7 000000f7
f79e3980
       00000040 c030ff04 f89663bc f79e3980 f7e20160 00000001 00000040
f79e3980
Call Trace:    [<c022069f>] [<c022069f>] [<c021b767>] [<f8995a3b>]
[<f89663bc>]
  [<f89631d5>] [<c022088f>] [<c01210db>] [<c010aa95>] [<c0106e90>]
[<c0106e90>]
  [<c0106e90>] [<c0106eb9>] [<c0106f42>] [<c0105000>]

Code: 0f 0b 43 01 ab 8b 2b c0 58 5a 8b 5c 24 1c 8b 43 2c 85 c0 74
 <0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
---------------------------------------------------------------------------
I used Kernel 2.4.21 + ebtables-brnf-2_vs_2.4.21.diff patch + 2.4.22-pre4.
The panic messages were occured when I enabled the network interface and
then connected the
system to Cisco Catalyst 3548 switch.
I got the same kernel panic when I used Kernel 2.4.21 +
ebtables-brnf-2_vs_2.4.21.diff patch.

Thanks in advance,
Yimbo





¡¡



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.