Date: Sun, 18 Nov 2001 03:35:20 +0100 From: "Anthony Atkielski" <anthony@atkielski.com> To: "Greg Lehey" <grog@FreeBSD.org>, "FreeBSD Questions" <freebsd-questions@FreeBSD.org> Subject: Re: Mysterious boot during the night Message-ID: <034101c16fd9$aebc31c0$0a00000a@atkielski.com> References: <20011117130052.B7072@mars.thuis> <020e01c16f42$14885c10$0a00000a@atkielski.com> <20011117015632.B87944@xor.obsecurity.org> <02a001c16f53$215323b0$0a00000a@atkielski.com> <3BF63DB1.1070008@owt.com> <02a701c16f5e$a9cb0c70$0a00000a@atkielski.com> <020e01c16f42$14885c10$0a00000a@atkielski.com> <20011117015632.B87944@xor.obsecurity.org> <02a001c16f53$215323b0$0a00000a@atkielski.com> <3BF63DB1.1070008@owt.com> <20011118102106.C72712@monorchid.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg writes: > Considering he's running a different processor > and is keeping it 100% busy, this seems fine. I've been experimenting, and the processor seems to stabilize at around 48 degrees Celsius when it is 100% busy. When the system is idle, it cools off considerably. > The processor managed 54 hours or so of seti@home. > It crashed during> a cron job. I don't think I'd > blame seti@home. That is my assessment also. SETI is very repetitive, I believe. A code failure, or even a hardware failure exposed by the program, would show up in considerably less than 50 hours. Fifty hours of running time is around 270 trillion instructions executed. > The disks are the obvious thing to look at, since > seti@home keeps RAM busy as well. That also occurred to me. Both memory and processor--especially the latter--are well exercised by SETI, as far as I can tell. So the only thing that gets intermitted exercise is the disk. SETI doesn't seem to do a lot of disk I/O, except to take an occasional checkpoint. And then there is that mysterious coincidence of the cron job running at the moment of failure. > Now we're getting closer. There were problems > with IDE data corruption and the VT82C686B. sos > committed a fix to -CURRENT about 2 months ago: How can I tell if this fix is in my machine? I installed from a set of Wind River CDs, marked as FreeBSD 4.3 (without much additional information), and dated April 2001. > He doesn't appear to have MFCd to -STABLE. MFCd? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?034101c16fd9$aebc31c0$0a00000a>