From owner-freebsd-stable Wed May 29 7: 6:28 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtp016.mail.yahoo.com (smtp016.mail.yahoo.com [216.136.174.113]) by hub.freebsd.org (Postfix) with SMTP id 8A63537B410 for ; Wed, 29 May 2002 07:06:23 -0700 (PDT) Received: from unknown (HELO johncoop.MSHOME) (john?m?cooper@206.63.201.3 with plain) by smtp.mail.vip.sc5.yahoo.com with SMTP; 29 May 2002 14:06:22 -0000 Subject: Re: Problems with PC-Partner motherboards? From: John Merryweather Cooper Reply-To: john_m_cooper@yahoo.com To: Daniel O'Connor Cc: FreeBSD Stable In-Reply-To: <1022675050.45671.26.camel@chowder.dons.net.au> References: <1022574851.38850.59.camel@chowder.gsoft.com.au> <1022576621.1708.14.camel@johncoop.MSHOME> <1022675050.45671.26.camel@chowder.dons.net.au> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 29 May 2002 07:07:08 -0700 Message-Id: <1022681231.80006.4.camel@johncoop.MSHOME> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 2002-05-29 at 05:24, Daniel O'Connor wrote: > On Tue, 2002-05-28 at 18:33, John Merryweather Cooper wrote: > > Amanda appears to work the system pretty hard as the CPU spikes up about > > 20 deg. C (from 65 deg. C to 85 deg. C--still within the operating > > limits of 90 deg. C from the documentation--but a tad toasty). After > > amanda completed (takes about 2 hours on my system to back up a 60 Gig > > set of partitions), the CPU temperature settles down again. > > > > As you've observed, the freeze is "hard"--getting in with a debugger > > appears futile and I need to hit the reset switch to get things moving > > again--CTRL-ALT-DEL has no effect. > > > > I'm also wondering if this has anything to do with the tagged queing > > going south early in 4.5-STABLE (the tagged sysctl is currently disabled > > in my loader.conf with a comment). No real reason to think so, just a > > generalized feeling that all is not quite right. > > Hmmm.. I've tried it with a motherboard which uses an identical chipset > (Epox made) and they work fine. > > Maybe there is some issue with the CPU temp - I will have to see if I > can tell the temp on this mobo. > > My guaranteed killer is to run > > [ vty 1 ] > find -x /bigpart -type f -exec md5 {} \; > > [ vty 2 ] > cd /usr/src > while (1) > make buildkernel KERNCONF=GENERIC > end > > Which I would guess increase the CPU temp (like a lot of things :) > > I will try just md5'ing a small file in a loop which should just make > the CPU hot. > I think I've found the problem on mine. The BIOS thermal protection settings default to 60 deg. C. Since baseline operating temperature is at or above that temperature, I think the BIOS is deciding to kill the system under heavy load. I adjusted the BIOS thermal protection setting to 90 deg. C (the max it would go, AND the max normal operating temperature in the AMD documentation for my CPU), and things survived the nightly backup fine. Note that this required a BIOS upgrade, previously the max temp. wouldn't go above 70 deg. C. in the BIOS settings. I'm using xmbmon in ports to check on my temp. With the exception of the colors (which I've changed to be more readable, it works fine. > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 -- _ | |V| / ' || MacroHard -- \ \_| | | \_, || the perfection of form over | ----------------------------------|| substance, marketing over | Web: http://www.borgsdemons.com || performance, and greed over | AIM: johnmcooper || design . . . | =====================================================================/ Public Key: http://www.borgsdemons.com/Personal/pgpkey.asc | =====================================================================\ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message