From owner-cvs-src@FreeBSD.ORG  Mon Feb  7 11:35:24 2005
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id D389F16A4CE; Mon,  7 Feb 2005 11:35:24 +0000 (GMT)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A86D543D1D; Mon,  7 Feb 2005 11:35:24 +0000 (GMT)
	(envelope-from sobomax@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.13.1/8.13.1) with ESMTP id j17BZOFV002250;
	Mon, 7 Feb 2005 11:35:24 GMT
	(envelope-from sobomax@repoman.freebsd.org)
Received: (from sobomax@localhost)
	by repoman.freebsd.org (8.13.1/8.13.1/Submit) id j17BZOpp002249;
	Mon, 7 Feb 2005 11:35:24 GMT
	(envelope-from sobomax)
Message-Id: <200502071135.j17BZOpp002249@repoman.freebsd.org>
From: Maxim Sobolev <sobomax@FreeBSD.org>
Date: Mon, 7 Feb 2005 11:35:24 +0000 (UTC)
To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org,
	cvs-all@FreeBSD.org
X-FreeBSD-CVS-Branch: HEAD
Subject: cvs commit: src/sys/i386/i386 p4tcc.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2005 11:35:25 -0000

sobomax     2005-02-07 11:35:24 UTC

  FreeBSD src repository

  Modified files:
    sys/i386/i386        p4tcc.c 
  Log:
  Fix the problem with incorrect throttling level reported immediately after
  reboot. Safter the reboot the TCC is usually in the Automatic mode, in which
  reading current performance level is likely to produce bogus results make sure
  to switch it to the On-Demand mode and set to some known performance level.
  Unfortunately there is no reliable way to check that TCC is in the Automatic
  mode. Reading bit 4 of ACPI Thermal Monitor Control Register produces 0
  regardless of the current mode.
  
  MFC after:      1 week
  
  Revision  Changes    Path
  1.7       +11 -0     src/sys/i386/i386/p4tcc.c