kernel bug!

[Hugo van der Merwe <hugo@adept.co.za>]

Every day my server "dies", presumably doing cron job stuff. So I went 
through the cron.daily items, and ran into:


baboon:/etc/cron.daily# ./modutils
Assertion failure in journal_forget() at transaction.c:1217: "!jh->b_committed_data"
kernel BUG at transaction.c:1217!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c0157436>]    Not tainted
EFLAGS: 00010282
eax: 00000058   ebx: c25c3dc0   ecx: c2dea000   edx: 00000000
esi: cb4df000   edi: c1612380   ebp: c9291b40   esp: c2debd6c
ds: 0018   es: 0018   ss: 0018
Process rm (pid: 2456, stackpage=c2deb000)
Stack: c01ff160 c01ff6e1 c01ff140 000004c1 c01ff6f0 00000000 c0fbef20 c8af87e0
       c8af87e0 cb4df094 c014e9db c0fbef20 c1612380 00000003 c41d1000 c0fbef20
       00290413 00000003 c41d1000 c0fbef20 c015061f c0fbef20 00000000 c8af87e0
Call Trace:    [<c014e9db>] [<c015061f>] [<c0156de4>] [<c015070c>] [<c01509a8>]
  [<c0150874>] [<c0150a80>] [<c0150c41>] [<c0156449>] [<c014eaad>] [<c014eb4c>]
  [<c014ebf3>] [<c014eb4c>] [<c01418dc>] [<c01400d8>] [<c0139ad9>] [<c0139bb4>]
  [<c010856f>]

Code: 0f 0b c1 04 40 f1 1f c0 83 c4 14 53 e8 bd 02 00 00 c7 43 14
 find: rm terminated by signal 11




baboon:/etc/cron.daily# mount
/dev/hda1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
/dev/hda5 on /var type ext3 (rw)
/dev/hda7 on /tmp type reiserfs (rw)
/dev/hda8 on /usr type ext3 (rw)
/dev/hda9 on /home type ext3 (rw)


I'm surprised I only have one reiserfs, I thought I converted all the 
smaller partitions. Oh well.

This is definately what's killing my server. (It's still half alive, I 
could continue working in an ssh session, but cannot create new 
sessions, cannot access apache, can access dictd... if I run ps ax in 
the ssh session, it "freezes" here:

<SNIP>
 2423 tts/0    S      0:00 /bin/sh ./modutils
 2424 tts/0    S      0:00 /bin/sh /sbin/insmod_ksymoops_clean
 2428 tts/0    D      0:00 find /var/log/ksymoops -type f -atime +2 -exec rm {}

which is clearly related to the processes going balistic. I will try 
running an fsck. Any ideas? What should I do, what should I investigate?

hugo@baboon[1]:~$ uname -a
Linux baboon 2.4.19 #1 Thu Oct 17 14:05:10 SAST 2002 i686 unknown

Thanks,
Hugo van der Merwe

Please CC...