Chad Leigh -- Shire.Net LLC wrote: > > I have the following thing that started in the last day or two > (machine has been running fine forever) > > May 16 11:25:26 woodhall BUG at jfs_imap.c:964 assert(le32_to_cpu > (iagp->wmap[extno]) & mask) > May 16 11:25:26 woodhall kernel BUG at jfs_imap.c:964! > May 16 11:25:26 woodhall invalid operand: 0000 2.4.22-aa1 #1 SMP Wed > Nov 5 21:33:40 MST 2003 > May 16 11:25:26 woodhall CPU: 0 > May 16 11:25:26 woodhall EIP: 0010:[<c02072a5>] Tainted: GF > May 16 11:25:26 woodhall EFLAGS: 00010282 > May 16 11:25:26 woodhall eax: 00000047 ebx: 00000000 ecx: > f390a02c edx: 00000001 > May 16 11:25:26 woodhall esi: 00000001 edi: 40000000 ebp: > c4756000 esp: f390bea4 > May 16 11:25:26 woodhall ds: 0018 es: 0018 ss: 0018 > May 16 11:25:26 woodhall Process jfsCommit (pid: 9, stackpage=f390b000) > May 16 11:25:26 woodhall Stack: c0356e61 c0356f3e 000003c4 c03681c0 > c4767e00 c014ed8f c4767e00 c1160be0 > May 16 11:25:26 woodhall 00000029 00000000 00000036 00000000 00000000 > 00000000 00000000 c7594000 > May 16 11:25:26 woodhall 00000000 00000020 00000000 f358f330 f8800690 > c0217034 f358f330 f358f330 > May 16 11:25:26 woodhall Call Trace: [<c014ed8f>] [<c0217034>] > [<c0217772>] [<c01fba40>] [<c01fba61>] > May 16 11:25:26 woodhall [<c0165120>] [<c021c89b>] [<c021d07d>] > [<c021d2ad>] [<c010915e>] [<c0105000>] > May 16 11:25:26 woodhall [<c0105000>] [<c010743e>] [<c021d130>] > May 16 11:25:26 woodhall Code: 0f 0b c4 03 3e 6f 35 c0 e9 9d f5 ff ff > ba ff ff fe ff 89 c8 >
Combined with your networking problems, I would guess you have a hardware fault. Check your fans, make sure they are still spinning. If it isn't that simple, my guess is you need to replace your motherboard or memory. You could also try under-clocking your FSB and CPU as a temporary fix, if your PC BIOS will let you do that. > > bash-2.05b# uname -a > Linux woodhall 2.4.22-aa1 #1 SMP Wed Nov 5 21:33:40 MST 2003 i686 AMD > Athlon(tm) MP 2800+ AuthenticAMD GNU/Linux > bash-2.05b# > > The machine exists on private networks only (it does have a public > address but nothing at all listening on it -- mainly to be able to go > out to the net to emerge) > > > I think my earlier eth0 problems were from this as well -- the FS was > screwed up after this happened. Ouch. Make sure you do not have write-caching enabled on the hard disks, as journalled filesystems and write-caching do not mix. -Richard -- gentoo-user@gentoo.org mailing list
