Tracy R Reed wrote:
[snip]
RedHat has looked into this and used our kickstart config in a virtual
machine machine with 256M of RAM and 2 80G disks and the install worked
perfectly. So I'm guessing it has something to do with the hardware.
Anyone interested in all of the details can read the notes from our
RedHat support ticket which I have pasted here:
http://pastebin.ca/927325
Any ideas why I would be getting this strange error? I'm rather bummed
that even RedHat hasn't been able to figure this out in a month. If I
don't get this sorted in the next few days I am just going to set up the
machines without RAID. The plan is to run the two of them in HA mode
anyway. Was just hoping to have the extra protection.
The EPIA Eden processor is almost, but not quite exactly x86 instruction
identical to modern Intel and AMD. In particular, it doesn't have some
of the SSE/3DNow extensions which might be used inadvertently by the kernel.
Have you tried several different kernels?
Also, the ATA drives might have some sort of bad DMA interaction. Older
VIA chipsets were notorious for those problems. Since you state in your
report that you can do an install on a single disk, try that and then
with the second disk in the system pound the system with I/O requests to
both disks to see if you can generate a failure. If you can't make it
fail, then do a single disk install and mirror it after the fact.
You might also try reducing the RAM to 512MB. When you go over about
896MB, the kernel has to do weird things with memory on 32-bit systems,
which you can see at the very beginning of dmesg. DMA takes place in
lower memory, so maybe limiting memory will force everything to behave.
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
