From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261956AbTJNWjT (ORCPT ); Tue, 14 Oct 2003 18:39:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262036AbTJNWjT (ORCPT ); Tue, 14 Oct 2003 18:39:19 -0400 Received: from imap.gmx.net ([213.165.64.20]:14293 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S261956AbTJNWjP (ORCPT ); Tue, 14 Oct 2003 18:39:15 -0400 X-Authenticated: #555711 From: "Sebastian Piecha" To: linux-kernel@vger.kernel.org Date: Wed, 15 Oct 2003 00:39:01 +0200 MIME-Version: 1.0 Subject: Re: oops in skbuff.c in 2.4.22-ac4, but not2.6.0-test7 Message-ID: <3F8C9725.30722.1774B670@localhost> In-reply-to: <3F8ADA85.8256.10ABE6B1@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > several times I got an OOPS in skb_drop_fraglist or alloc_skb. Here's > a description of what has happened. Any help would be appreciated. > Please CC me on all further mail traffic. > > ... There are modifications in skbuff.c in kernel 2.6.0-test7. For what reason skbuff.c was changed? Due to bug fixes or general changes in the kernel? Could skbuff.c easily be backported to 2.4.20 or 2.4.22? > kernel 2.4.22-ac4 > > EIP c02518a3 refers to alloc_skb in vmlinux it also refers to skb_drop_fraglist > > Oops: 0000 > CPU: 0 > EIP: 0010:[] Not tainted > Using defaults from ksymoops -t elf32-i386 -a i386 > EFLAGS: 00010206 > eax: c525e660 ebx: 00200000 ecx: 00000000 edx: 00200000 > esi: c5c97d40 edi: c5c97da0 ebp: c038ba24 esp: c034ff18 > ds: 0018 es: 0018 ss: 0018 > Process swapper (pid: 0, stackpage=c034f000) > Stack: c5c97d40 c025194b c5c97d40 c5c97d40 c5c97d40 c025196c c5c97d40 > c5c97d40 > c5c97d40 c0251ab4 c5c97d40 c57acd00 00000000 c0255103 c5c97d40 > c038b4c8 > 00000001 fffffffd c03ac328 d3051000 c011e2cd c038b4c8 c03ac320 > c03729c0 > Call Trace: [] [] [] [] > [] > [] [] [] [] [] > [] > [] [] [] > Code: 8b 1b 8b 42 74 83 f8 01 74 0b f0 ff 4a 74 0f 94 c0 84 c0 74 > > > >>EIP; c02518a3 <===== > > >>eax; c525e660 <_end+4e6fe3c/14cc883c> > >>esi; c5c97d40 <_end+58a951c/14cc883c> > >>edi; c5c97da0 <_end+58a957c/14cc883c> > >>ebp; c038ba24 > >>esp; c034ff18 > > Trace; c025194b > Trace; c025196c > Trace; c0251ab4 <__kfree_skb+ec/f4> > Trace; c0255103 > Trace; c011e2cd > Trace; c010a32d > Trace; c0106d70 > Trace; c0105000 <_stext+0/0> > Trace; c010c7d8 > Trace; c0106d70 > Trace; c0105000 <_stext+0/0> > Trace; c0106d9c > Trace; c0106deb > Trace; c0105049 > > Code; c02518a3 > 00000000 <_EIP>: > Code; c02518a3 <===== > 0: 8b 1b mov (%ebx),%ebx <===== > Code; c02518a5 > 2: 8b 42 74 mov 0x74(%edx),%eax > Code; c02518a8 > 5: 83 f8 01 cmp $0x1,%eax > Code; c02518ab > 8: 74 0b je 15 <_EIP+0x15> > Code; c02518ad > a: f0 ff 4a 74 lock decl 0x74(%edx) > Code; c02518b1 > e: 0f 94 c0 sete %al > Code; c02518b4 > 11: 84 c0 test %al,%al > Code; c02518b6 > 13: 74 00 je 15 <_EIP+0x15> > > <0>Kernel panic: Aiee, killing interrupt handler! > ... Mit freundlichen Gruessen/Best regards, Sebastian Piecha EMail: spi@gmxpro.de