Aaron Lewis wrote: > > Any general troubleshooting advice? Are there logs or dumps to > analyze? I'm pretty green Linux-wise. the linux kernel and the various distributions are mature enough nowadays that they don't just flake out like that. in my experience 95% of the time something like this happened to me it was hardware. the other 5% it was buggy kernel modules (aka also hardware). Unfortunately it is probably the sort of hardware error that only creeps up randomly and any number of "test" utilities will not detect it. is there a monitor plugged into it? can you plug one and and switch to VT1 (Ctrl-Alt-F1) and wait for it to happen. there is a good chance something will get dumped to the console. if this is not an option, netconsole is an alternative, you will need to load netconsole using: modprobe netconsole netconsole=eth0,514@<your.syslog.server> modinfo netconsole gives you the proper syntax if you do not have a syslog server you can still capture the traffic using using netcat, on another box on that subnet use: nc -l -p 514 and wait for it to happen. once you have the kernel panic or Oops report (if you get one) it should have more info that an experienced eye can decipher. otherwise, start swapping hardware until it stops happening :)