> - it could be a memory problem, but if it were, lots of kernel
> oops were expected, right?
This certainly sounds like a memory problem. I experienced almost the same
behaviour with a box some years ago, and it turned out to be memory. The
kernel didn't oops, and I actually had to run several kernel compiles at
the same time to have gcc die.
Try memtest86 on the suspect box.
--André Dahlqvist <andre.dahlqvist@telia.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/