From: James Courtier-Dutton <James@superbug.co.uk>
To: linux-kernel@vger.kernel.org
Subject: 2.6.9-rc2 oops due to UDP packet.
Date: Mon, 27 Sep 2004 02:35:36 +0100 [thread overview]
Message-ID: <41576E68.2010200@superbug.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
I attach an oops that causes my SMP Pentium 4 system to hang, requiring
me to press the reset button.
It seems to be due to an error in the processing of a UDP packet.
It happens quite rarely, about once every few days, but it is certainly
annoying.
Could anyone help me track this bug down?
James
[-- Attachment #2: crash.txt --]
[-- Type: text/plain, Size: 1663 bytes --]
new login: ------------[ cut here ]------------
kernel BUG at include/asm/spinlock.h:90!
invalid operand: 0000 [#1]
PREEMPT SMP DEBUG_PAGEALLOC
Modules linked in: md5 ipv6 ide_cd cdrom lp parport usbhid uhci_hcd usbcore e1000
CPU: 1
EIP: 0060:[<c02fecc0>] Not tainted VLI
EFLAGS: 00010202 (2.6.9-rc2)
EIP is at _spin_unlock+0x36/0x46
eax: 00000001 ebx: f1e8ef00 ecx: 00000002 edx: f33aa93c
esi: f33aa800 edi: f33aa93c ebp: c213bbb4 esp: c213bbb4
ds: 007b es: 007b ss: 0068
Process hotwayd (pid: 13950, threadinfo=c213a000 task=db25caa0)
Stack: c213bbd4 c0298e81 f33aa800 f1e8ef00 00000000 f6dc10e4 f6dc10fc d12aae08
c213bc0c c02aea71 c3951f54 d12aae24 c213bc10 c02afe71 d12aae44 c213bea0
00000000 f6dc10d0 c3951f54 c213bc48 c3951f54 d34daf04 c213bc58 c02b0cfe
Call Trace:
[<c01050e7>] show_stack+0x80/0x96
[<c010527a>] show_registers+0x15d/0x1d6
[<c01054a8>] die+0x112/0x19d
[<c01059a9>] do_invalid_op+0xee/0x10a
[<c0104d01>] error_code+0x2d/0x38
[<c0298e81>] dev_queue_xmit+0x23b/0x2d4
[<c02aea71>] ip_finish_output+0xda/0x24c
[<c02b0cfe>] ip_push_pending_frames+0x266/0x49a
[<c02ce758>] udp_push_pending_frames+0x12f/0x25a
[<c02cef22>] udp_sendmsg+0x661/0x7a9
[<c028f99f>] sock_sendmsg+0xbf/0xe3
[<c0290f7c>] sys_sendto+0xe8/0x107
[<c0290fd1>] sys_send+0x36/0x38
[<c029184d>] sys_socketcall+0x141/0x234
[<c0104277>] syscall_call+0x7/0xb
Code: e5 75 1e 0f b6 02 84 c0 7f 21 c6 02 01 b8 00 e0 ff ff 21 e0 83 68 14 01 8b 40 08 a8 08 75 16 5d c3 0f 0b 59 00 80 05 31 c0 eb d8 <0f> 0b 5a 00 80 05 31 c0 eb d5 5d e9 c6 f5 ff ff 55 89 e5 f0 81
<0>Kernel panic - not syncing: Fatal exception in interrupt
next reply other threads:[~2004-09-27 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 1:35 James Courtier-Dutton [this message]
2004-09-30 22:25 ` BUG in spinlock debug code. was: Re: 2.6.9-rc2 oops due to UDP packet James Courtier-Dutton
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=41576E68.2010200@superbug.co.uk \
--to=james@superbug.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.