After reinstalling slack 9.1 I have been getting this error. the computer will boot, and I can log in, but after a few minutes of working on the system, it will freeze for about 2 minutes then return the following error.

journal-601, buffer write failed
kernel BUG at print.c:341!
invalid operand: 0000
cpu: 0
eip: 00010:[<c01b22da>] Not tainted
EFlags: 00010282
eax: 00000038 ebx: c116b400 ecx: c116b400 edx: c314e000
esi: 00000000 edi: c08678b0 ebp: c116b400 esp: c11ffec0
ds: 0018 es: 0018 ss: 0018
Process kupdated (pid: 6, stackpage=c11f000)
Stack: c02d8a79 c038dfa0 c038a3e0 c02e6b40 c11ffee4
c02e6b40 0000001a c11ffef8 00000018 00000000
c08678b0 c116b400 00000030 00000004 00000002
c01c1146 c116b400 c480fd9c 00000001 c01bfaca
Call Trace: [<c01bce65>] [<c01c1146>] [<c01bfaca>] [<c01c03f5>]
[<c01aac60>] [<c01af5c8>] [<c013c5e4>] [<c013bb1e>]
[<c013bdbf>] [<c0105000>] [<c0107416>] [<c013bcf0>]
Code: 0f 0b 55 01 8c 8a 2d c0 85 db 68 a0 df 38 c0 74 15 66 8b 43

This is the series of errors and codes that prints on the screen after the 1-2 minutes of inactivity when the system hangs.

It looks to me like my kernel has become corrupted. When I reinstalled I had the system use the same kernel as the boot disk.

Any help will be greatly appreciated.

Does anyone know anything about these errors and/or codes?

Can anyone help me with this problem?

Hi,

i'm not so expert, but the message "journal-601, buffer write failed" may be due to a corrupted filesystem, try to run reiserfsck, BUT be careful and read the man page

man reiserfsck

before run the check program.

Another reason of this error may be an hd damaged...

Thanks, I'll try that. It may be the hd, the whole system is fairly old. pentium 133 proc., mobo with simm memory modules and such. If the HD is going bad, that could also explain why only half of it shows up to the bios and to fdisk. It is a 4.3 GB hd, but only 2.1 GB shows up to the system. When I change the specs to what they are supposed to be, the install program can't format the drive. I'll post another reply and let you know what the fscheck turns up.

I would have to agree that the drive may be going bad.

it may not be a bad drive, its happening on my linux system when i try to enable dma on the main harddisk. both harddrives new and bios not showing any failures - i am running
reiserfsck --rebuild-tree --logfile check.log
on the secondary hdd at the mo to see what could be wrong

Okay, Post a reply and let me know what you got back. I'm thinking that it may also be a conflict between my bios(quite old) and the hard disk (still old, but not nearly as old as the bios). The Mobo manufacturer no longer exsists and I can't find an updated bios that I might be able to use. I would try a new mobo, but then I have to buy new ram and everything too. (really old mobo) Well, I have just move recently and haven't set up the linux box yet and don't have net at home right now, so it may be a week or two before I check here again.

thanks for any help that I can get.

nothing happened, i think my disk is failing cos its going extremely slow for everything now
the mobo is a via kt xxx for an AMD, i have had nothing but hassel with installing linux on this mobo, i would recommend against it for AMD chips

I got my main hard drive problem fixed. bad file system support in the kernel. I had to switch to ext3 instead of reiserfs. now it works fine. I just need a newer mobo that will recognize all of my hard drive instead of only half of it. I have reconpiled the 2.4.22 kernel that came with my slack distro, but I haven't been able to upgrade to the 2.6.5 kernel. when I run any make comands on it it starts returning errors. I'll have to copy them down so maybe someone can help me get them resolved. thamks for all the help so far!!