[Jfs-discussion] assertion in inode.c

[Bernhard M. E. <bm...@mi...>]

Hello

We have some trouble with jfs 1.0.24 (kernel 2.4.19, jfs as
module). Our backup that starts at night at 1 o'clock is usually what
triggers the bug (as in this case). Here is the log:

Nov 26 01:09:03 boston kernel: jfs_clear_inode, active_ag = 101
Nov 26 01:09:03 boston kernel: i_ino = 253958, i_mode = 100775
Nov 26 01:09:03 boston kernel: assert(list_empty(&ji->mp_list))
Nov 26 01:09:03 boston kernel: kernel BUG at inode.c:51!
Nov 26 01:09:03 boston kernel: invalid operand: 0000
Nov 26 01:09:03 boston kernel: CPU:    1
Nov 26 01:09:03 boston kernel: EIP:    0010:[eepro100:__insmod_eepro100_O/lib/modules/2.4.19/kernel/drivers/net/e+-680188/96]    Tainted: P 
Nov 26 01:09:03 boston kernel: EIP:    0010:[<e08e7f04>]    Tainted: P 
Nov 26 01:09:03 boston kernel: EFLAGS: 00010296
Nov 26 01:09:03 boston kernel: eax: 00000021   ebx: dc4f44c8   ecx: 00000001   edx: c026d228
Nov 26 01:09:03 boston kernel: esi: ce6b4a00   edi: d8461228   ebp: c1625f54   esp: c1625ef8
Nov 26 01:09:03 boston kernel: ds: 0018   es: 0018   ss: 0018
Nov 26 01:09:03 boston kernel: Process kswapd (pid: 5, stackpage=c1625000)
Nov 26 01:09:03 boston kernel: Stack: e0908c7a e0908c61 ce6b4a00 c1625f40 c015329a ce6b4a00 c0152605 c160d470 
Nov 26 01:09:03 boston kernel:        d07170a0 d07170a0 ce6b4a00 c0153318 ce6b4a00 d84615e8 d84615e0 c015356d 
Nov 26 01:09:03 boston kernel:        c1625f40 00003020 c4abce08 ce6154a8 0000001e 000001d0 00000006 00000006 
Nov 26 01:09:03 boston kernel: Call Trace:    [eepro100:__insmod_eepro100_O/lib/modules/2.4.19/kernel/drivers/net/e+-545670/96] [eepro100:__insmod_eepro100_O/lib/
modules/2.4.19/kernel/drivers/net/e+-545695/96] [clear_inode+218/288] [destroy_inode+37/48] [dispose_list+56/80]
Nov 26 01:09:03 boston kernel: Call Trace:    [<e0908c7a>] [<e0908c61>] [<c015329a>] [<c0152605>] [<c0153318>]
Nov 26 01:09:03 boston kernel:   [prune_icache+189/224] [shrink_icache_memory+32/48] [shrink_caches+110/144] [try_to_free_pages+60/96] [kswapd_balance_pgdat+81/16
0] [kswapd_balance+38/80]
Nov 26 01:09:03 boston kernel:   [<c015356d>] [<c01535b0>] [<c0135f2e>] [<c0135f8c>] [<c0136041>] [<c01360b6>]
Nov 26 01:09:03 boston kernel:   [kswapd+161/193] [kswapd+0/193] [_stext+0/80] [kernel_thread+38/48] [kswapd+0/193]
Nov 26 01:09:03 boston kernel:   [<c0136211>] [<c0136170>] [<c0105000>] [<c0107296>] [<c0136170>]
Nov 26 01:09:03 boston kernel: 
Nov 26 01:09:03 boston kernel: Code: 0f 0b 33 00 86 8c 90 e0 5a 59 8d 43 5c 39 43 5c 74 19 68 a0 

Prior to this bug, no kernel related output was produced in
/var/log/messages (well, except for the boot messages).

System: Dual P3-700, RedHat 7.1 (standard (non-redhat) kernel 2.4.19),
Mylex DAC960 Raid (5 disks->1 logical disk). System hardware
monitoring reports no hardware errors.

Suggestions?

regards,

Bernhard Ege