From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 13 15:03:43 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D899E106566B for ; Mon, 13 Feb 2012 15:03:43 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from adsum.doit.wisc.edu (adsum.doit.wisc.edu [144.92.197.210]) by mx1.freebsd.org (Postfix) with ESMTP id AD8AB8FC0C for ; Mon, 13 Feb 2012 15:03:41 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed; delsp=yes Received: from avs-daemon.smtpauth1.wiscmail.wisc.edu by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LZC00012765JK00@smtpauth1.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Mon, 13 Feb 2012 09:03:41 -0600 (CST) Received: from [10.0.2.93] ([unknown] [76.210.60.16]) by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LZC00AR6761P840@smtpauth1.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Mon, 13 Feb 2012 09:03:38 -0600 (CST) Date: Mon, 13 Feb 2012 09:03:39 -0600 From: Nathan Whitehorn In-reply-to: To: Rob Ballantyne Message-id: <5F9EB093-EF0A-463A-83F2-05B20956D530@freebsd.org> X-Mailer: Apple Mail (2.936) X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.60.16 X-Spam-PmxInfo: Server=avs-14, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.2.13.145414, SenderIP=76.210.60.16 References: Cc: freebsd-ppc@freebsd.org Subject: Re: G5 Quad halting after 'over temp' X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 15:03:43 -0000 On Feb 11, 2012, at 8:15 PM, Rob Ballantyne wrote: > Hi All, > > I've just purchased G5 Quad to run FreeBSD PPC. During install the > machine would throw a couple of errors (I couldn't capture them -- > only on the screen) complaining about a lock reversal. Shortly after > this the machine to complain that a couple of diode temps were too > high (~1000 C, I'm sure this can't possibly be true). > > I found some advice about an Xserve behaving similarly and the > suggest was to use sysctl to set machdep.manage_fans=0 (disable that > feature I presume). I tried this and was able to install. I do have > a question about the safety of this. I presume this disables kernel > management of the fans. If the kernel is not managing the fan speed > does this fall to the firmware? Will the firmware keep the temps > within reason? The thing it does on earlier G5s is that the firmware runs all cooling devices at maximum if they aren't set, which is probably not what you want but is unlikely to set your machine on fire. Could you send the output of dmesg and the output of sysctl for the various sensors, dev.smusat, and dev.smu? -Nathan