From owner-freebsd-current@FreeBSD.ORG Fri Aug 13 15:52:04 2004 Return-Path: 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 5EFFC16A4CE; Fri, 13 Aug 2004 15:52:04 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D90043D39; Fri, 13 Aug 2004 15:52:04 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Fri, 13 Aug 2004 08:52:04 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 3B45F5D04; Fri, 13 Aug 2004 08:52:03 -0700 (PDT) To: Nate Lawson In-reply-to: Your message of "Thu, 12 Aug 2004 23:35:48 PDT." <411C6144.6060100@root.org> Date: Fri, 13 Aug 2004 08:52:03 -0700 From: "Kevin Oberman" Message-Id: <20040813155203.3B45F5D04@ptavv.es.net> cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: HEADSUP: acpi mpsafe committed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2004 15:52:04 -0000 > Date: Thu, 12 Aug 2004 23:35:48 -0700 > From: Nate Lawson > Sender: owner-freebsd-acpi@freebsd.org > > Let me know if there are any problems. > > Thanks for testing: Rong-En Fan , Kevin Oberman > , marcel. > > (And now the same to you! :) Why do I see things right AFTER the commit? (O.K. I actually saw them late last night, but was too tired to do any testing and am still in the process of building kernels to do some real testing.) Since I installed a kernel/modules with the mpsafe patches I have found that P4_TCC and throttling no longer work. They worked with an unpatched kernel/modules built on Wednesday and failed with the patched kernel/modules I am now running. I have not updated the sources between the two kernel builds, so I think it has to be the patches. Now the admission of not knowing what I am doing. The P4 TCC stuff appears to be very similar to the ACPI throttling capability. I suspect that the latter simply controls the former, but I really don't know. I guess that I really should have removed it when I was able to use ACPI throttling, but I never removed it and it continued to work until last night. When I went to battery, hw.p4tcc.cpuperf remained at 100 instead of dropping to hw.p4tcc.cpuperf_economy. Similarly, hw.acpi.cpu.thottle_state remains at 8 and hw.acpi.cw_lowest is at C1 instead of C2 or C3. economy_throttle_state is set to 4 and economy_cx_lowest is at default (LOW). Really takes down the old battery quickly! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634