Date: Mon, 23 Nov 1998 23:36:33 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: John Polstra <jdp@polstra.com> Cc: rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Message-ID: <5830.911860593@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 23 Nov 1998 14:28:05 PST." <199811232228.OAA00715@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199811232228.OAA00715@vashon.polstra.com>, John Polstra writes: >> Well, I would, but I have been running this box >> overclocked for more than 6 months now, never had >> a glitch. Reboots only started back when other >> people reported such behaviour on the list as well. >> Im going to get a spare box and make a serial console >> off of it, see if I can get the panic message. > >It doesn't make any difference how long your box has appeared to work. >If you're overclocking it at all, we don't want to see your panic >messages. They are too likely to mislead. It's just that simple. I would actually argue that the longer the box has been overclocked the warmer the cpu runs. Think "dusty fans" to follow the drift. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5830.911860593>