From owner-freebsd-bugs@freebsd.org Mon May 2 21:45:58 2016 Return-Path: Delivered-To: freebsd-bugs@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 EEB05B2B1C1 for ; Mon, 2 May 2016 21:45:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DEB7916A9 for ; Mon, 2 May 2016 21:45:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u42LjwHn088270 for ; Mon, 2 May 2016 21:45:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 209202] [PATCH] [powermac_thermal] In-Kernel PowerMac fan control does not effectively regulate some quad core models Date: Mon, 02 May 2016 21:45:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2016 21:45:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209202 --- Comment #4 from Mark Millard --- (In reply to gmbroome from comment #3) Do not interpret my notes as an attempt to block the changes. The notes are just general background. Keeping a failure-mode machine operational can be worth while in the right kind of context. I just did not want the performan= ce tradeoff and I did not want to ask Justin Hibbits to do more than he already had done. I have access to an example "quad core Powermac G5" of each type relative to one pump vs. two, where both work without overheating problems and always h= ave: # sysctl -a | grep pump dev.smu.0.fans.cpu_a_pump.rpm: 1716 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 (So only one pump.) $ sysctl -a | grep pump dev.smu.0.fans.cpu_b_pump.rpm: 1485 dev.smu.0.fans.cpu_b_pump.maxrpm: 3600 dev.smu.0.fans.cpu_b_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.rpm: 1480 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 (So two pumps.) I put the same kinds of loads on each, although one has 12 GBytes of RAM and the other has 16 GBytes. As far as I can tell if a PowerMac G5 Quad Core has an overheating problem = then something is in a failure mode, usually the cooling system. --=20 You are receiving this mail because: You are the assignee for the bug.=