From: Joshua Hudson <joshudson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: How to interpret a kernel bug output from dmesg?
Date: Fri, 7 Oct 2005 17:53:34 -0700 [thread overview]
Message-ID: <bda6d13a0510071753h80ed0fdoa35f3b39a3079ef1@mail.gmail.com> (raw)
I got this. Probably I caused it. Kernel is 2.6.13, slightly modified
(weird new psuedo filesystem).
Problem is I don't know how to read it. I wouldn't recommend looking
for it yourself: I doubt
you will find anything.
Yes, I compiled with DEBUG_DCACHE (or something similar, uncommented the
debug define at the top of dcache.c). I ran dmesg -c just before the ls that
crashed, and dmesg right afterwards. Nothing else present.
------------[ cut here ]------------
kernel BUG at include/linux/dcache.h:294!
invalid operand: 0000 [#1]
PREEMPT
Modules linked in:
CPU: 0
EIP: 0060:[<c0160723>] Not tainted VLI
EFLAGS: 00010246 (2.6.13c1)
EIP is at __link_path_walk+0xd03/0xe60
eax: 00000000 ebx: ce054014 ecx: 00000001 edx: cdd392fc
esi: ce1b7000 edi: ce1ffecc ebp: ce1b7f10 esp: ce1b7e24
ds: 007b es: 007b ss: 0068
Process ls (pid: 258, threadinfo=ce1b7000 task=ce2eaae0)
Stack: 00000001 ce1b7e50 ce1b7e48 cdd392fc ce1b7e5c ce1b7e54 c02ac704 00000000
00000000 cfee48c0 ce1ffecc 00017c88 00000002 ce054012 c0169a73 ce1b7f10
ce1b7f50 ce1b7ebc ce1b7e7c c01608c7 ce00b294 ce054000 ce00b294 cfee48c0
Call Trace:
[<c0169a73>] dput+0x33/0x280
[<c01608c7>] link_path_walk+0x47/0xe0
[<c0160c1c>] path_lookup+0x8c/0x160
[<c0160eb3>] __user_walk+0x33/0x60
[<c015ae9c>] vfs_lstat+0x1c/0x60
[<c015b5cb>] sys_lstat64+0x1b/0x40
[<c016416d>] sys_fcntl+0x2d/0x60
[<c0102ab5>] syscall_call+0x7/0xb
Code: 2a ff 02 89 55 00 b8 01 00 00 00 e8 78 de fa ff 8b 46 08 a8 08
75 0d 89 3c 24 e8 29 93 00 00 e9 75 ff ff ff e8 8f 22 11 00 eb ec <0f>
0b 26 01 8e e6 27 c0 eb cc e8 7e 22 11 00 e9 97 fe ff ff 8b
<6>note: ls[258] exited with preempt_count 1
next reply other threads:[~2005-10-08 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 0:53 Joshua Hudson [this message]
2005-10-08 3:04 ` Randy.Dunlap
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=bda6d13a0510071753h80ed0fdoa35f3b39a3079ef1@mail.gmail.com \
--to=joshudson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®