Skip to contentSkip to conversation

oops Re: 2.5.63-mm2

DISCUSSION Con Kolivas 2 participants 2 messages Mar 4, 2003

lore
Share & tools
lore
#0 lore raw

oops running contest:

Unable to handle kernel paging request at virtual address 9acfdcf2
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0060:[<c016d525>]    Not tainted
EFLAGS: 00010246

EIP is at ext3_free_branches+0x1d/0x210
eax: 9acfdcf2 ebx: c6c8d610 ecx: cdf422c0 edx: c9120000
esi: c7ff6dc0 edi: 0001401f ebp: c2883eb4 esp: c2883e04
ds: 007b es: 007b ss: 0068
Process dbench (pid: 7379, threadinfo=c2882000 task=c1717900)

Stack: c6c8d610 c7ff6dc0 0001401f c2883eb4 c2883e14 c2883e14 c013f59c c6c8d610
       c2883eac c016d5d6 c7ff6dc0 cdf422c0 c6c8d610 c911f000 c9120000 00000000
       c2883eac 00000000 00000001 c7ff6dc0 00000400 cdf42240 00000001 c016d891
Call Trace:
 [<c013f59c>] __bread_slow+0x6c/0x94
 [<c016d5d6>] ext3_free_branches+0xce/0x210
 [<c016d891>] ext3_truncate+0x179/0x4b8
 [<c016da65>] ext3_truncate+0x34d/0x4b8
 [<c017b9a7>] __jbd_kmalloc+0x1b/0x6c
 [<c0175c13>] start_this_handle+0x157/0x1a0
 [<c0175d30>] journal_start+0x8c/0xb8
 [<c016b14f>] start_transaction+0x57/0x84
 [<c016b1e4>] ext3_delete_inode+0x0/0x190
 [<c016b2c3>] ext3_delete_inode+0xdf/0x190
 [<c016b1e4>] ext3_delete_inode+0x0/0x190
 [<c015284f>] generic_delete_inode+0x8b/0xb4
 [<c0152988>] generic_drop_inode+0x10/0x24
 [<c0152a02>] iput+0x66/0x6c
 [<c01500f6>] dput+0x16a/0x1a0
 [<c013e378>] __fput+0x94/0xb4
 [<c013e2e3>] fput+0x13/0x14
 [<c013cec5>] filp_close+0x99/0xa4
 [<c0116cb8>] put_files_struct+0x4c/0xb4
 [<c01176c7>] do_exit+0x1b7/0x354
 [<c011788a>] sys_exit+0xe/0x10
 [<c0108b17>] syscall_call+0x7/0xb

Code: f6 00 02 0f 85 e2 01 00 00 83 6c 24 3c 01 0f 82 b9 01 00 00

Con

#1 lore raw
Quoted 4 lines · Con Kolivas

oops running contest:

Unable to handle kernel paging request at virtual address 9acfdcf2

You had an ext3 handle which has a trashed ->journal pointer. I've seen that once, possibly twice before too.

I don't know what is causing it. It is just kmalloc'ed memory. It could be anywhere in the kernel :( Seems to have started around 2.5.63.