On 28 May, Matt M wrote: > Try testing the memory in the system -- use memtest86. Run through all the > tests (takes about 24 hours on your average system), and see what it shows > up. Memory's always the first thing I test when I start seeing `random' > instability in a system.
Okay, I'll reserve some time on the weekend to try that. I've downloaded, compiled and installed version 3.0 and added it in as a boot image in lilo. The system rebooted this morning at 4:02 am, just as it did the day before, give or take a few seconds. At 4:05am there's a scheduled backup, but nothing else nearby that I'm aware of. What time does the RH cron.daily script get run? There was also a system lock-up around noon by my wife, and just now by me, while I was reading Matt's message. We were both logged in, so memory use would have been moderately high. These system lock-ups are different to the unattended ones - for those the system reboots, but when it locks up while we're using it, the system just stays hung. I guess the new monitor is turned on at those times, turned off when it's unattended. Jan Schmidt wrote: > As I said, I was using the cpuburn package, which runs tight assembler loops > to heat CPUs up. With the dodgy PSU and the standard CPU core voltage, it > would just hard lock within 10 seconds. After the PSU upgrade, I ran it for > 8 hours and got the CPU up to 55C > > Other symptoms were programs randomly segfaulting, particularly video > encoding and other such CPU intensive apps. Hmm. All very strange. I guess I have a few avenues to explore, anyway. I'll let you all know how I get on. luke -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
