I've been seeing system freezes and spontaneous reboots while compiling
kernels since folks started messing around with the vm code (2.1.89?).
Sometimes I get "lucky" and the compiler merely dies on a signal 11,
and still other times gcc dies on a signal 4. 64 MB RAM, Cyrix 6x86L
P200+ (150 MHz), Buslogic SCSI controller. Sometimes this happens
while X is running, but most of the time I'm accessing the machine
remotely over a network connection. On a couple of occasions, the
compiler died because the input files "didn't make any sense". Upon
further examination, the contents of the files were garbage but every-
thing was fine after forcing a reboot and running fsck on the involved
filesystems (no errors found): sure smacks of corrupted cache to me.
Hardware *can* suddenly go bad, but...
For what it's worth, I'm currently up and running on 2.1.92 with the
"spam syslog" code disabled per a patch posted to this list.
-- Bob Tracy | "They couldn't hit an elephant at this dist- " Firewall Security Corp. | - Last words of Union General John Sedgwick, rct@frus.com | Battle of Spotsylvania Court House, U.S. Civil War- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu