From: Alessandro Suardi <alessandro.suardi@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: non-fatal oops with EIP at skb_release_data, available for debugging
Date: Fri, 4 Mar 2005 21:48:18 +0100 [thread overview]
Message-ID: <5a4c581d05030412482a596ee5@mail.gmail.com> (raw)
This is my K7-800, 256MB RAM machine running as
ed2k/bittorrent 24/7 box... metacity died, but the
windows are still alive (and working) so if someone
wants to get more info about it, just ping me...
[root@donkey ~]# cat /proc/version
Linux version 2.6.11-rc3-bk8 (asuardi@donkey) (gcc version 3.4.2
20041017 (Red Hat 3.4.2-6.fc3)) #1 Sat Feb 12 00:01:28 CET 2005
[root@donkey ~]# lsmod
Module Size Used by
loop 15368 -
nls_iso8859_1 3840 -
parport_pc 29444 -
parport 24704 -
8139too 24896 -
floppy 57392 -
>From the dmesg ring:
kernel BUG at include/linux/mm.h:343!
invalid operand: 0000 [#1]
PREEMPT
Modules linked in: loop nls_iso8859_1 parport_pc parport 8139too floppy
CPU: 0
EIP: 0060:[<c02da6a2>] Not tainted VLI
EFLAGS: 00210256 (2.6.11-rc3-bk8)
EIP is at skb_release_data+0x92/0xa0
eax: 00000000 ebx: 00000000 ecx: cca36f80 edx: c11a97c0
esi: c4205f20 edi: c4205f20 ebp: cd149dcc esp: cd149dc4
ds: 007b es: 007b ss: 0068
Process metacity (pid: 2109, threadinfo=cd148000 task=ce8935d0)
Stack: c4205f20 00000000 cd149dd8 c02da6bb c6e9a0c0 cd149df8 c02da737 c5134250
00000000 c4205f20 c5134250 c4205f20 c5134250 cd149e4c c02feba6 00000000
00000040 cc68c454 00000000 00000001 cc68c444 cd148000 00000001 00000000
Call Trace:
[<c0102b2a>] show_stack+0x7a/0x90
[<c0102cad>] show_registers+0x14d/0x1c0
[<c0102ea4>] die+0xe4/0x180
[<c01032e3>] do_invalid_op+0xa3/0xb0
[<c01027a7>] error_code+0x2b/0x30
[<c02da6bb>] kfree_skbmem+0xb/0x20
[<c02da737>] __kfree_skb+0x67/0xf0
[<c02feba6>] tcp_recvmsg+0x5f6/0x710
[<c02da1e6>] sock_common_recvmsg+0x46/0x60
[<c02d6bbe>] sock_aio_read+0xee/0x100
[<c014e427>] do_sync_read+0x97/0xf0
[<c014e511>] vfs_read+0x91/0x120
[<c014e7ed>] sys_read+0x3d/0x70
[<c01025a9>] sysenter_past_esp+0x52/0x75
Code: c9 e9 03 e5 e5 ff 8d 76 00 5b 5e c9 c3 89 d0 e8 c5 f2 e5 ff eb
cf 89 f0 e8 0c ff ff ff 5b 8b 86 98 00 00 00 5e c9 e9 de e4 e5 ff <0f>
0b 57 01 ab c5 35 c0 eb a5 8d 74 26 00 55 89 e5 53 89 c3 e8
Thanks,
--alessandro
"There is no distance that I don't see
I do have a will - No limit to my reach"
(Wallflowers, "Empire In My Mind")
next reply other threads:[~2005-03-04 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 20:48 Alessandro Suardi [this message]
2005-03-04 23:39 ` Fwd: non-fatal oops with EIP at skb_release_data, available for debugging Alessandro Suardi
2005-04-06 22:30 ` Alessandro Suardi
2005-05-26 5:00 ` Andrew Morton
2005-05-29 1:11 ` Alessandro Suardi
2005-05-30 1:21 ` Andrew Morton
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=5a4c581d05030412482a596ee5@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--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.