From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 10:41:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 087BF16A4CE for ; Thu, 8 Jan 2004 10:41:36 -0800 (PST) Received: from cmsrelay02.mx.net (cmsrelay02.mx.net [165.212.11.111]) by mx1.FreeBSD.org (Postfix) with SMTP id 694E143D45 for ; Thu, 8 Jan 2004 10:41:31 -0800 (PST) (envelope-from noackjr@compgeek.com) Received: from uadvg131.cms.usa.net (165.212.11.131) by cmsoutbound.mx.net with SMTP; 8 Jan 2004 18:41:30 -0000 Received: from optimator.noacks.org [65.69.2.105] by uadvg131.cms.usa.net (ASMTP/noackjr@usa.net) via mtad (C8.MAIN.3.11E) with ESMTP id 078iaHspb0129M31; Thu, 08 Jan 2004 18:41:27 GMT X-USANET-Auth: 65.69.2.105 AUTH noackjr@usa.net optimator.noacks.org Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id DAE01191; Thu, 8 Jan 2004 12:41:26 -0600 (CST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 83712-03; Thu, 8 Jan 2004 12:41:16 -0600 (CST) Received: from www.noacks.org (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with SMTP id 164FD15D; Thu, 8 Jan 2004 12:41:16 -0600 (CST) Received: from 64.1.99.131 (SquirrelMail authenticated user noackjr) by www.noacks.org with HTTP; Thu, 8 Jan 2004 12:41:16 -0600 (CST) Message-ID: <10984.64.1.99.131.1073587276.squirrel@www.noacks.org> In-Reply-To: <20040108171214.33CAE5D08@ptavv.es.net> References: Message from Alexandre "Sunny" Kovalenko <20040107221254.74570411.Alex.Kovalenko@verizon.net> <20040108171214.33CAE5D08@ptavv.es.net> Date: Thu, 8 Jan 2004 12:41:16 -0600 (CST) From: "Jon Noack" To: "Kevin Oberman" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at noacks.org Content-Transfer-Encoding: quoted-printable cc: freebsd-current@freebsd.org cc: Alexandre Sunny Kovalenko Subject: Re: FreeBSD 5.2-CURRENT on HP Omnibook 6000 - ACPI problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@compgeek.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 18:41:36 -0000 Kevin Oberman wrote: > This is not even ACPI. Many motherboards for modern P4 and K7 chips do = a > very low-level BIOS shutdown on over-temp. See ASUS, ABIT, or most any > other mobo for a fairly useless blurb on this. > > From ABIT: > "ABIT ThermalGuard Technology is a special designed for ABIT MB prevent= s > CPU burning down by hardware cooling malfunction. With unique ABIT > Hardware Monitoring chip and CPU thermal detector, ThermalGuard > Technology can protect the better safety of all CPUs and customers' ABI= T > motherboards. When the temperature of CPU is over the default threshold > degree, system immediately shut down by ABIT ThermalGuard It's > great for preventing the lost of customers' investment. Unlike > other manufactories, which use BIOS or software to delivery same > feature. ABIT ThermalGuard Technology is much more reliable because it > is hardware-controlled and uninterruptible." > > So, if the fan fails to turn on, it is perfectly possible that the > system will power off regardless of ACPI. While ABIT makes it sound > exclusive, it looks pretty much the same as ASUS "CPU Overtemp Protecti= on > System (COPS)" and Gigabyte calls it "Anti-Burn" IMHO, this all stems from a Tom's Hardware article: http://www20.tomshardware.com/cpu/20010917/index.html Further coverage: http://www20.tomshardware.com/column/20011029/index.html A respected hardware review site publishes a spectacular video of an Athlon literally vaporizing itself (when the heatsink/fan is taken off during a Quake III timedemo) and suddenly everyone gets all worked up about it (while the P4 throttles itself back and just strolls along at ~1= 2 fps). In any case, it was extraordinarily public coverage, and manufacturers (especially their marketing people) have been in overdrive on it ever since. Jon Noack