Jun 29 11:30:05 ns kernel: Assertion failure in __journal_file_buffer() at transaction.c:1935: "jh->b_jlist < 9" Jun 29 11:30:05 ns kernel: invalid operand: 0000 Jun 29 11:30:05 ns kernel: CPU: 0 Jun 29 11:30:05 ns kernel: EIP: 0010:[__journal_file_buffer+54/400] Not tainted Jun 29 11:30:05 ns kernel: EFLAGS: 00010282 Jun 29 11:30:05 ns kernel: eax: 00000059 ebx: c43b92e0 ecx: c47da000 edx: c5cf6140 Jun 29 11:30:05 ns kernel: esi: cbf7bcc0 edi: 00000000 ebp: 00000003 esp: c47dbe50 Jun 29 11:30:05 ns kernel: ds: 0018 es: 0018 ss: 0018 Jun 29 11:30:05 ns kernel: Process proftpd (pid: 9193, stackpage=c47db000) Jun 29 11:30:05 ns kernel: Stack: c020ebc0 c020f349 c020eba0 0000078f c020f1c6 c43b92e0 cbf7bcc0 cbfb9600 Jun 29 11:30:05 ns kernel: c70c2340 c01595ec c43b92e0 cbf7bcc0 00000003 c6ca9c64 c238d8a8 c6ca9b40 Jun 29 11:30:05 ns kernel: 00000498 c015368f c70c2340 c3ad95a0 c47dbefc 00000000 c70c2340 00000498 Jun 29 11:30:05 ns kernel: Call Trace: [journal_dirty_metadata+324/356] [ext3_do_update_inode+763/920] [ext3_mark_iloc_dirty+33/72] [ext3_mark_inode_dirty+41/52] [ext3_dirty_inode+134/196] Jun 29 11:30:05 ns kernel: [__mark_inode_dirty+46/120] [generic_file_write+808/1864] [do_getitimer+156/164] [ext3_file_write+70/76] [sys_write+146/224] [system_call+51/56] Jun 29 11:30:05 ns kernel: Jun 29 11:30:05 ns kernel: Code: 0f 0b 83 c4 14 90 8d 74 26 00 8b 43 14 39 f0 74 29 85 c0 74 this apeared in our log after that the load went up to 120 (is isposible?) then we had to reboot MB abit, chipset je intel BX440 we use soft-raid 1 any ideas? thanks for your help!! V Bilek
Hi, On Sat, Jun 29, 2002 at 01:24:16PM +0200, Vaclav Bilek wrote:> Jun 29 11:30:05 ns kernel: Assertion failure in __journal_file_buffer() at transaction.c:1935: "jh->b_jlist < 9"The last 3 times I've seen this reported, it turned out to be bad memory, or the use of a bust binary-only driver module. You don't seem to be doing the latter, so memtest86 is a good next step towards debugging this. Cheers, Stephen