Check the system event logs in the motherboard bios. Sometimes listed under SEL. Otherwise, I would stress test the machine. I used to run ctcs to burn in systems for a cluster I worked on for LLNL. It does memory, io, and cpu stress tests.
http://sourceforge.net/projects/va-ctcs/ You could also try lm-sensors to monitor the hardware. http://ubuntuforums.org/showthread.php?t=2780 brian On Wed, Dec 08, 2010 at 07:21:14AM -0800, Cam Ellison wrote: > Recently I upgraded to this MB, with an AMD Phenom II. The latest > Kubuntu (10.10) is loaded onto it. Twice it has halted suddenly: no > activity, no output, and has required a reboot. This is not an external > power problem: its power comes from an APC 3000. There is nothing in > the logs: everything runs normally and then suddenly nothing does. > > In both instances, the stoppage has occurred in the middle of a set of > cron.daily jobs (in the middle of the night), so I am exploring that > avenue. The problem is that the machine has been in place for 7 weeks, > and the two stoppages are about 5 weeks apart - there's not much to go on. > > I'm looking for any ideas about how to track this down: is there a > utility that might give me more insight? More to the point, does anyone > in the group have this combination and a comparable experience? > > TIA > > Cam Ellison > > > _______________________________________________ > vox-tech mailing list > vox-tech@lists.lugod.org > http://lists.lugod.org/mailman/listinfo/vox-tech -- Brian Lavender http://www.brie.com/brian/ "Program testing can be used to show the presence of bugs, but never to show their absence!" Professor Edsger Dijkstra 1972 Turing award recipient _______________________________________________ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech