From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 20:20:12 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2A90106564A for ; Wed, 14 Dec 2011 20:20:12 +0000 (UTC) (envelope-from tomdean@speakeasy.org) Received: from asbnvacz-mailrelay01.megapath.net (asbnvacz-mailrelay01.megapath.net [207.145.128.243]) by mx1.freebsd.org (Postfix) with ESMTP id A38D78FC16 for ; Wed, 14 Dec 2011 20:20:12 +0000 (UTC) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.41]) by asbnvacz-mailrelay01.megapath.net (Postfix) with ESMTP id 96E25A7169F for ; Wed, 14 Dec 2011 15:20:11 -0500 (EST) Received: (qmail 16005 invoked from network); 14 Dec 2011 20:20:11 -0000 Received: by simscan 1.4.0 ppid: 23689, pid: 26388, t: 0.3136s scanners: clamav: 0.88.2/m:52/d:10739 spam: 3.0.4 Received: from 24-113-112-30.wavecable.com (HELO [192.168.2.2]) (tomdean@[24.113.112.30]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Dec 2011 20:20:10 -0000 From: "Thomas D. Dean" To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset="UTF-8" Organization: Home Date: Wed, 14 Dec 2011 12:20:10 -0800 Message-ID: <1323894010.3799.87.camel@asus> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail2.sea5 X-Spam-Level: * X-Spam-Status: No, score=1.6 required=8.0 tests=BAYES_50 autolearn=disabled version=3.0.4 Subject: FreeBSD 9.0 (RC2) Causes BIOS Message on Reboot X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tomdean@speakeasy.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2011 20:20:12 -0000 I know, this sounds strange. I have an ASUS P9X79 motherboard, Intel i7-3930K CPU. The motherboard TPU switch is on. This overclocks the CPU to 4.162GHz. Calculated from the TSC, with code from Intel. The details of doing this are in the CPUID datasheet. sysctl dev.cpu.0 always shows freq as 3.201GHz no matter what the clock actually is. Often, when rebooting from FreeBSD, I get a message from BIOS that overclocking has failed - press F1 to enter setup. I press F1, exit from setup, discarding changes, and the calculated CPU clock is 3.201GHz. Overclocking has failed. I shutdown, cycle power, boot, and overclocking works, calculated CPU clock is 4.162GHz. If I save changes when exiting from setup, overclocking works. A bus reset is issued? I have a tripple boot, Windows 7 for possible warranty issues, Linux and FreeBSD 9.0(RC2). I never see this message when rebooting from either of the other two OS's, only FreeBSD. I booted all three 5 times and saw 3 instances of overclocking failed when rebooting from FreeBSD. Here is the question: How may I find out what is causing this? I have an HP Envy 17 3D notebook that always has side effects of booting FreeBSD 8.2 AMD64 where Windows 7 and Linux do not. An over temperature message 0090D. The machine is not actually over temperature, just something tweeked that BIOS sees. Two machines doing strange things on reboot - it is not hardware or BIOS, both different. tomdean