From owner-freebsd-current Mon Nov 23 14:43:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27720 for freebsd-current-outgoing; Mon, 23 Nov 1998 14:43:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27602 for ; Mon, 23 Nov 1998 14:43:04 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id RAA31187; Mon, 23 Nov 1998 17:41:26 -0500 (EST) Date: Mon, 23 Nov 1998 17:41:26 -0500 (EST) From: Chuck Robey To: Steve Kargl cc: "Jordan K. Hubbard" , rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <199811232226.OAA24221@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Nov 1998, Steve Kargl wrote: > According to Jordan K. Hubbard: > > > I too have been experiencing random > > > reboots, with no apparent reason. > > > > I see an apparent reason. Keep reading. > > > > > My machine is a Pentium 200Mhz overclocked to 233Mhz, > > > > Stop that. At least until your system is 100% stable and does not > > exhibit any symptoms which can be clearly traced to software. > > > > Jordan, > > First, I agree he should stop overclocking. But, there really > is a *subtle* bug. I've 4 to 5 crashes, but I haven't been > able to get a dump. > > I've created and deleted 100's of MB of files (e.g., several > make worlds). Then, on a seeming idle system, simply reading > email can cause the problem. Jordan didn't mean that, but he was completely correct (and should go on being stubborn about it). There's nothing worse, in doing troubleshooting, than making an assumption and going off into a blind alley for weeks, and trying to find a software problem in a system that's being overclocked is simply asking for it. Part of the price you pay for overclocking is needing to dial back the clock for any serious troubleshooting. Overclocking is basically unreliable; if it works, that's just fine, but the guarantee runs 60 seconds, max. The problem's real, but no trouble reports if you're overclocking, no excuses accepted. It's not all that hard to dial the clock back (and no, I don't overclock, myself, even though I do have a system that could do that well). ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message