Skip to contentSkip to conversation

BUG in jfscode

DISCUSSION Tobias Bengtsson 2 participants 2 messages Feb 3, 2004 – Feb 5, 2004

lore
Share & tools
lore
#0 lore raw

Hi!

This output I got from a 2.6.2-rc3 compiled with the config attached

cheers, Tobias

PS. Please cc me the replies to this thread as I'm not subscribed.

------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_dmap.c:2686!
invalid operand: 0000 [#4]
CPU:    0
EIP:    0060:[<c02276d0>]    Not tainted
EFLAGS: 00210246

EIP is at dbBackSplit+0xe0/0x130
eax: 0000004b ebx: 00000400 ecx: c0478e90 edx: 00200246
esi: 00000000 edi: ee587166 ebp: d264b90c esp: d264b8e8
ds: 007b es: 007b ss: 0068
Process dpkg (pid: 22568, threadinfo=d264a000 task=ee623900)

Stack: c041d043 c041d031 00000a7e c041d400 0000000d 00000001 ee587001 0000000f 
       00000000 d264b960 c02274f0 ee587000 0000000f 0000000d 00000174 00000164 
       0000000f ee587000 ffffffff 09000000 efd1a904 0001e41a 00000000 00000000 
Call Trace:
 [<c02274f0>] dbAdjCtl+0x250/0x2c0
 [<c0226d02>] dbAllocDmap+0x42/0x70
 [<c0226ca0>] dbAllocDmapLev+0xa0/0xc0
 [<c02268b5>] dbAllocCtl+0x95/0x3e0
 [<c013be5b>] mempool_alloc+0x7b/0x170
 [<c013a63c>] read_cache_page+0x4c/0x240
 [<c011f790>] autoremove_wake_function+0x0/0x40
 [<c02265ca>] dbAllocAG+0x31a/0x390
 [<c013bfcd>] mempool_free+0x7d/0x90
 [<c02259ac>] dbAlloc+0x1dc/0x440
 [<c0230440>] extBalloc+0xe0/0x1e0
 [<c02341d5>] txLock+0x265/0x480
 [<c022ffe4>] extAlloc+0x144/0x340
 [<c0217116>] jfs_get_blocks+0x156/0x280
 [<c0155321>] __find_get_block_slow+0x31/0x130
 [<c0217256>] jfs_get_block+0x16/0x20
 [<c0157a79>] nobh_prepare_write+0xd9/0x410
 [<c02469c5>] radix_tree_node_alloc+0x15/0x60
 [<c0246af6>] radix_tree_extend+0x46/0x80
 [<c0138e5a>] add_to_page_cache+0x4a/0xf0
 [<c013acd6>] generic_file_aio_write_nolock+0x386/0xcc0
 [<c0217240>] jfs_get_block+0x0/0x20
 [<c011e28c>] __wake_up+0x1c/0x40
 [<c01469ef>] do_anonymous_page+0xff/0x210
 [<c0233e71>] txEnd+0x31/0x130
 [<c013b67a>] generic_file_write_nolock+0x6a/0x90
 [<c0147044>] handle_mm_fault+0x114/0x150
 [<c0147ef0>] vma_merge+0x90/0x2e0
 [<c011c42c>] do_page_fault+0x32c/0x558
 [<c0148605>] do_mmap_pgoff+0x4c5/0x5f0
 [<c013b779>] generic_file_write+0x49/0x60
 [<c0153c64>] vfs_write+0x84/0xe0
 [<c0110694>] sys_mmap2+0x54/0xa0
 [<c0153d3e>] sys_write+0x2e/0x50
 [<c010a20b>] syscall_call+0x7/0xb

Code: 0f 0b 7e 0a 31 d0 41 c0 83 c4 10 89 f2 31 da 80 3c 3a ff 75 

----8<----8<----
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(TM) XP 2600+
stepping : 0
cpu MHz : 1916.547
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips : 3776.51

Signature · 1 line
http://tobbe.nu/.sig
#1 lore raw
Quoted 1 line · Tobias Bengtsson

Hi!

Hi, Sorry it's taken me so long to respond.

Quoted 1 line

kernel BUG at fs/jfs/jfs_dmap.c:2686!

I've seen a similar bug reported before, but it occurs only rarely. I'm not sure what the cause is. My initial thought was the the block map got corrupted, but after digging through the code I don't know if it's that simple.

I would be interested if you can recreate the problem. If so, I may be able to put in some debug code to help determine where JFS is getting confused. Also, if it is block map corruption, running fsck -f against the volume should fix that.

Thanks,
Shaggy

Signature · 2 lines
David Kleikamp
IBM Linux Technology Center