Date: Fri, 13 Mar 1998 04:36:20 -0800 (PST) From: Chris Timmons <skynyrd@opus.cts.cwu.edu> To: freebsd-stable@FreeBSD.ORG Subject: Re: panic at getnewbuf+0x21f Message-ID: <Pine.BSF.3.96.980313043050.24670B-100000@opus.cts.cwu.edu> In-Reply-To: <Pine.BSF.3.96.980311082432.21355C-100000@opus.cts.cwu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
removing NO_F00F_HACK seems to relieve this condition, although running with that option set in kernels pre-2/28 doesn't seem to present a problem. perhaps some of you with thrashable p5 boxes can see how well your systems run with the F00F hack disabled these days? I've checked my CPU fan, enabled my summer-only "leaf blower" case fan, relaxed the memory timing, etc. The panics I get are NOT random, they occur at the same place every time. Alas, I'm beginning to wonder myself... -Chris On Wed, 11 Mar 1998, Chris Timmons wrote: > > I still haven't figured out what's going on, but I get reliable panics > during CVSup and other high volume disk activity in this environment: > > -stable as of 0445 pst today, full build/installworld > genuine intel p5 > NO_F00F_HACK > CLK_USE_I586_CALIBRATION > > aha-3940 > de-500 100/mb ether > > /home with CVS repository on 2 disk ccd which is > NFS exported to a -current machine that has it mounted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980313043050.24670B-100000>