Hi,
I had a similar problem with a ZipSlack package. It turned out
to be a 'umsdos kernel bug'. Upgrading made this problem go
away.
Try what you will, but your kernel may be having problems with
your hardware, while your hardware may be fine. There could be a
bug in the kernel and you may have to upgrade your kernel to get
rid of it.
But of course, it could be practically anything. One other reason
that I've encountered for a Linux box crashing, was a
misconfigured swap partition. I had to manually re-format the
swap partition, and correct the entries made in
/etc/fstab. It was possible that RH6.1 failed to map the hard
drive correctly because I was making a triple-boot system between
Win95/WinNT/RH6.1.
One final reason that I can think of is the duration of time
between reboots. A Intel-based Linux box using 32-bit
architecture may have to be rebooted after a particular period of
time (ie 3 to 4 years). It was found that the low-level CPU
registers (cache) eventually overflowed and your kernel
became...insane. But this problem may be fixed in more recent
kernels, for 2.2.x kernels and above, for example. On a side
note, a system based on 64-bit architecture wouldn't need to be
rebooted for quite a few more years (ie Digital Alpha systems).
Best Regards,
L.G.
-- Generated Signature --
Nezvannyi gost'--khuzhe tatarina.
[An uninvited guest is worse than the
Mongol invasion]
-- Russian proverb
-- End Sig --
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
