2.5-bk Oops : kernel BUG at fs/dcache.c:765!

Andrew Walrond (andrew@walrond.org)
Mon, 07 Apr 2003 13:31:10 +0100


I have replicated this problem on both 2.4-bk and 2.5-bk. It occurs 50%
of boots during early boot script processing

kernel BUG at fs/dcache.c:765!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c016edb3>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010216
eax: f7a77e20 ebx: f7dc9300 ecx: 00000000 edx: 00000000
esi: f7a77e20 edi: f7a73a48 ebp: f7a73a20 esp: f7aade30
ds: 007b es: 007b ss: 0068
Stack: 00000001 f7dc9300 f7aac000 f7dd5ba0 f7a73a20 c01b7368 f7a73a20
f7a77e20
f7a73a20 f7ab1e10 f7fe28c0 00000000 f7ae52d0 c011bde0 00000000
00000000
f7ae0080 00000246 f7bb2940 00000000 f7ae52d0 c011bde0 00000000
00000000
Call Trace: [<c01b7368>] [<c011bde0>] [<c011bde0>] [<c01642ed>]
[<c0164867>] [<c011971c>] [<c01656ce>] [<c01550d3>] [<c01556db>]
[<c010950b>]
Code: 0f 0b fd 02 66 22 30 c0 bb 00 e0 ff ff 21 e3 ff 43 14 31 c0

>>EIP; c016edb3 <d_instantiate+23/b0> <=====

Trace; c01b7368 <devfs_d_revalidate_wait+d8/1d0>
Trace; c011bde0 <default_wake_function+0/20>
Trace; c011bde0 <default_wake_function+0/20>
Trace; c01642ed <do_lookup+6d/c0>
Trace; c0164867 <link_path_walk+527/9f0>
Trace; c011971c <do_page_fault+20c/43f>
Trace; c01656ce <open_namei+7e/460>
Trace; c01550d3 <filp_open+43/70>
Trace; c01556db <sys_open+5b/90>
Trace; c010950b <syscall_call+7/b>

Code; c016edb3 <d_instantiate+23/b0>
00000000 <_EIP>:
Code; c016edb3 <d_instantiate+23/b0> <=====
0: 0f 0b ud2a <=====
Code; c016edb5 <d_instantiate+25/b0>
2: fd std
Code; c016edb6 <d_instantiate+26/b0>
3: 02 66 22 add 0x22(%esi),%ah
Code; c016edb9 <d_instantiate+29/b0>
6: 30 c0 xor %al,%al
Code; c016edbb <d_instantiate+2b/b0>
8: bb 00 e0 ff ff mov $0xffffe000,%ebx
Code; c016edc0 <d_instantiate+30/b0>
d: 21 e3 and %esp,%ebx
Code; c016edc2 <d_instantiate+32/b0>
f: ff 43 14 incl 0x14(%ebx)
Code; c016edc5 <d_instantiate+35/b0>
12: 31 c0 xor %eax,%eax

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/