From owner-freebsd-ppc@freebsd.org Tue Jul 14 03:06:41 2015 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CAEEE99BFDC for ; Tue, 14 Jul 2015 03:06:41 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8DB641B06 for ; Tue, 14 Jul 2015 03:06:41 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by iecuq6 with SMTP id uq6so2747483iec.2 for ; Mon, 13 Jul 2015 20:06:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=EK57cF6rT37ApjgSH5UBeIk3DKY7sxIL17STnFTjNnM=; b=0PWd5u44/BXf/yoVrQCS5KFyDAKeB3jf40ByrC5FXmO8HiaZWtGdS/anhg05QI8LV7 skL5zfbc5akBerOb20AMgc8Ban8CKsT88S9JtL3b9mwH5ru2EwKeP0l5UtmfWcMSjmps i9Rhq/xyY21FvRcgeJ6FQdXbeeMcCLyQoSKZfX5GdA31eqY1fjMqC/jyM7T/wxD6qmsj IsVkbmVrjxkJ6LNlf8D0xcLORknY3AbJOUwVjgTxfU2xDogfguG3Jhs5j+ciaCXz1uo+ CDse6nB2K2WS4gtKwfkZnqDgth8s1O9SL2o89fqqqLc+YFwIBO+N0gPNDfkT2YU0bggB Mrxw== MIME-Version: 1.0 X-Received: by 10.107.149.14 with SMTP id x14mr45707811iod.87.1436843201015; Mon, 13 Jul 2015 20:06:41 -0700 (PDT) Sender: chmeeedalf@gmail.com Received: by 10.36.121.149 with HTTP; Mon, 13 Jul 2015 20:06:40 -0700 (PDT) In-Reply-To: References: Date: Mon, 13 Jul 2015 20:06:40 -0700 X-Google-Sender-Auth: tgeoJShmgUTOGqDTP8F6J8gN57w Message-ID: Subject: Re: CPU Temp Warnings From: Justin Hibbits To: Matthias Schojohann Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 03:06:42 -0000 Hi Matt, Yes, it would require an svn up to head and buildworld+buildkernel. Alternatively, there are snapshots available on the FTP server that include the change. Yet another alternative, for now, if you're feeling adventurous enough to cherry-pick the patch, the relevant patch is r277314, or a simple drop-in of the sys/dev/iicbus/adt746x.c from head would work (still have to compile from source, but everything is 10 except this file). I'm in the process of creating a patch to be included in 10.2, which you could upgrade to at release time as well. - Justin On Thu, Jul 9, 2015 at 1:38 AM, Matthias Schojohann wrote: > Hey Justin, > i'm not quite sure what you mean with "can you try with head"? > Like svn head and make buildworld etc.?! > After my disastrous upgrade to 11.0 i don't know if i want to again :D > > Cheers, Matt > > 2015-07-09 5:35 GMT+02:00 Justin Hibbits : >> >> On Wed, Jul 8, 2015 at 8:12 PM, Justin Hibbits >> wrote: >> > On Wed, Jul 8, 2015 at 7:13 AM, Matthias Schojohann >> > wrote: >> >> Hey all, >> >> i have a FreeBSD10.1-RELEASE on my iBook G4 1,41GHz and every once in a >> >> while i get an error on the terminal that says: >> >> WARNING: Current temperature (CPU BOTTOMSIDE: 255.0 C) exceeds critical >> >> temperature (80.0 C); count = 1 >> >> >> >> sysctl dev.adt746x.0.sensors.cpu_bottomside.temp however gives me temps >> >> like 50.0 C so where does my system get the 255 from? Apart from the >> >> fact >> >> that i don't want to see my CPU on that temperature, it's pretty >> >> annoying >> >> when i have systat running on that machine. >> >> >> >> Cheers, Matt >> > >> > Hi Matt, >> > >> > 255 is (char)-1 on PowerPC, so it indicates an error reading from the >> > device. I'll take a look at it, and try to silence the error. Could >> > you file a bug so it doesn't get lost? >> > >> > - Justin >> >> Hi Matt, >> >> Can you try with head? I made some changes back in January correcting >> the type signs for temperature reading, because of that same problem. >> I still see some temperature warnings on my Aluminum PowerBook (127C), >> but I think that's a glitch in the sensor, not necessarily the driver, >> but I'm not certain. Any time I see all 1's in a reading, I'm >> suspicious of the reading itself, not of the environment, without >> other data. >> >> - Justin > >