From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 3 00:37:04 2005 Return-Path: X-Original-To: acpi@FreeBSD.ORG Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8184F16A423; Sun, 3 Jul 2005 00:37:04 +0000 (GMT) (envelope-from ps@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1DF643E66; Sun, 3 Jul 2005 00:20:17 +0000 (GMT) (envelope-from ps@mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id E3568623FB; Sat, 2 Jul 2005 17:19:56 -0700 (PDT) X-Original-To: ps@mu.org Delivered-To: ps@mu.org Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by elvis.mu.org (Postfix) with ESMTP id A65285C862; Thu, 24 Feb 2005 13:41:16 -0800 (PST) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id E6007575F2; Thu, 24 Feb 2005 21:41:14 +0000 (GMT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 36AD816A4F8; Thu, 24 Feb 2005 21:41:11 +0000 (GMT) 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 BE69816A4CE; Thu, 24 Feb 2005 21:41:06 +0000 (GMT) Received: from www.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4D6B43D46; Thu, 24 Feb 2005 21:41:05 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.0.128] ([192.168.2.2]) (authenticated bits=0) by www.portaone.com (8.12.11/8.12.11) with ESMTP id j1OLenEc084803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Feb 2005 22:40:50 +0100 (CET) (envelope-from sobomax@portaone.com) Message-ID: <421E49D9.60803@portaone.com> From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <20050224011924.992A65D07@ptavv.es.net> <421DA0B5.4060705@portaone.com> <421E42F2.6010105@root.org> In-Reply-To: <421E42F2.6010105@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.80/685/Wed Jan 26 10:08:24 2005 clamav-milter version 0.80j on www.portaone.com X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on elvis.mu.org X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL, BAYES_00, J_CHICKENPOX_13 autolearn=no version=3.0.2 X-Spam-Level: Cc: acpi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: patch: p4tcc and speedstep cpufreq drivers X-BeenThere: freebsd-acpi@freebsd.org List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Sun, 03 Jul 2005 00:37:04 -0000 X-Original-Date: Thu, 24 Feb 2005 23:40:41 +0200 X-List-Received-Date: Sun, 03 Jul 2005 00:37:04 -0000 Nate Lawson wrote: > Maxim Sobolev wrote: > >> Kevin Oberman wrote: >> >>> No joy. I set it to 262 and it was fine. The next step killed the system >>> again. >>> >>> I'm also concerned that taking TCC out of automatic mode might not be a >>> great idea, at least until things like _PSV are supported. When I do a >>> buildkernel, buildworld or any big compile job, I need to slow down the >>> CPU to keep the CPU form frying. It quickly jumps to 185 F. or higher if >>> I don't. If I understand automatic TCC, it should throttle the CPU all >>> by itself to prevent this. >> >> >> >> Taking TCC out of automatic mode doesn't disable thermal controlling >> circuitry completely, so that if the processor overheats it will shut >> down the machine anyway: >> >> --- >> Regardless of enabling of the automatic >> or On-Demand modes, in the event of a catastrophic cooling failure, >> the processor will >> automatically shut down when the silicon has reached a temperature of >> approximately >> 135 °C. At this point the system bus signal THERMTRIP# will go active >> and stay active >> until RESET# has been initiated. --- > > > Correct. Even more so, automatic mode continues to override On-Demand > mode if there is a more moderate thermal condition than THERMTRIP#: > > "On-Demand mode may be used at the same time Automatic mode is enabled, > however, if the system tries to enable the TCC via On-Demand mode at the > same time automatic mode is enabled AND a high temperature condition > exists, the duty cycle of the automatic mode will override the duty > cycle selected by the On-Demand mode." > > Since automatic mode is set by the BIOS before we even boot, things > should be fine. Well, this is quite tricky part of the spec. My reading is that the paragraph above applies only to situation if you are trying to set on-demand mode when both automatic mode is in effect *and* high temperature condition already exists, in that case automatic mode will win and override any manual settings. However, in the case when you have on-demand mode already on and high temperature condition emerges it will have no effect on duty cycle until THERMTRIP# kicks in. That's in my view explains why there is big AND in the text above. -Maxim _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"