From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 4 08:46:15 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AFC1493C for ; Mon, 4 Nov 2013 08:46:15 +0000 (UTC) (envelope-from lisen1001@gmail.com) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4EB6D24EB for ; Mon, 4 Nov 2013 08:46:15 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id b13so1507749wgh.0 for ; Mon, 04 Nov 2013 00:46:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Gup/Qu0spdXvQi7TXgCDfgky8kek/1UPNL6NHQXz4Co=; b=Rh8myK0KKQCAlhAZpMIKGgLkJSTqz07nI78i/YJX9BIuJ/rloktHhCT/Sb2UsQCEuu bmZ+6BUvsbskb1+h5c+ZO35QsigI8U77ZSFUvAdzYmaz4oCUrmBan04t932d1onmCwYU /Mc4I6UtpqFsYff0mgt9PAW5dMZRxgK2RC4h0kXFdd9MzbmGoFcPcxzc/pxg5v55o9D7 ywq5bOJK8rR1V84R8ef6PKigPx5jK2+ZkmWfi2H3tGKtG/O+14kb1ciudqhcdllWMiIW k1+JUlAFMp5T9+KzLv0EkUwxWzGvNgvYzmdrUDmQW+zhV/7QO3IEi9edY2+ZYfOIuV+o DHgw== MIME-Version: 1.0 X-Received: by 10.180.73.231 with SMTP id o7mr11301833wiv.21.1383554772201; Mon, 04 Nov 2013 00:46:12 -0800 (PST) Received: by 10.194.95.8 with HTTP; Mon, 4 Nov 2013 00:46:12 -0800 (PST) Date: Mon, 4 Nov 2013 16:46:12 +0800 Message-ID: Subject: Xeon E5 cpu work in low status From: =?GB2312?B?wO7JrQ==?= To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 08:46:15 -0000 hi,all: the cpu of my machine is : Intel(R) Xeon(R) CPU E5-2643 0 @ 3.30GHz. after a reboot. The cpu freq is : sysctl dev.cpu.0.freq dev.cpu.0.freq: 1200 i didn't set any power savings config in rc.conf. How can i fix this? From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 4 11:06:45 2013 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 099445B4 for ; Mon, 4 Nov 2013 11:06:45 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D1A292C25 for ; Mon, 4 Nov 2013 11:06:44 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rA4B6iqF048297 for ; Mon, 4 Nov 2013 11:06:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rA4B6iwx048295 for freebsd-acpi@FreeBSD.org; Mon, 4 Nov 2013 11:06:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Nov 2013 11:06:44 GMT Message-Id: <201311041106.rA4B6iwx048295@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 11:06:45 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/181665 acpi [acpi] System will not go into S3 state. o kern/180897 acpi [acpi] ACPI error with MB p8h67 v.1405 o kern/174766 acpi [acpi] Random acpi panic o kern/174504 acpi [ACPI] Suspend/resume broken on Lenovo x220 o kern/173408 acpi [acpi] [regression] ACPI Regression: battery does not o kern/171305 acpi [acpi] acpi_tz0: _CRT value is absurd, ignored (256.0C o kern/165381 acpi [cpufreq] powerd(8) eats CPUs for breakfast o kern/164329 acpi [acpi] hw.acpi.thermal.tz0.temperature shows strange v o kern/162859 acpi [acpi] ACPI battery/acline monitoring partialy working o kern/161715 acpi [acpi] Dell E6520 doesn't resume after ACPI suspend o kern/161713 acpi [acpi] Suspend on Dell E6520 o kern/160838 acpi [acpi] ACPI Battery Monitor Non-Functional o kern/160419 acpi [acpi_thermal] acpi_thermal kernel thread high CPU usa o kern/158689 acpi [acpi] value of sysctl hw.acpi.thermal.polling_rate ne o kern/154955 acpi [acpi] Keyboard or ACPI doesn't work on Lenovo S10-3 o kern/152098 acpi [acpi] Lenovo T61p does not resume o i386/146715 acpi [acpi] Suspend works, resume not on a HP Probook 4510s o kern/145306 acpi [acpi]: Can't change brightness on HP ProBook 4510s o i386/143798 acpi [acpi] shutdown problem with SiS K7S5A o kern/143420 acpi [acpi] ACPI issues with Toshiba o kern/142009 acpi [acpi] [panic] Panic in AcpiNsGetAttachedObject o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not a i386/122887 acpi [panic] [atkbdc] 7.0-RELEASE on IBM HS20 panics immed s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/73823 acpi [request] acpi / power-on by timer support 28 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 4 17:52:54 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 01926B39 for ; Mon, 4 Nov 2013 17:52:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CF19426DF for ; Mon, 4 Nov 2013 17:52:53 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id kp14so7228214pab.18 for ; Mon, 04 Nov 2013 09:52:53 -0800 (PST) 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=bFOfLm3JXAyf+skfKuvQVUKU6WIgU6aqaXU2moYAg8w=; b=CMrDCRI91QMwTrYdo/E8qPYwJ1uW4z5LO6ivRHohmUI5mTU2zcHqXst0+Hjjbh/2KO VF8odRbjTMvLw0/6jOI4b+YXFsQ2Vi7N780r57k7ts9cAOgJd0hDqdIz2UnXMa26vfe8 AzR+0pbdYjGtL2QRNV19p8MvYREgqic2yHfmNhzibfiUvMLSpiXzpCHP2PGi/zs4JZmq ThQk6egvzDDEBrpHHYlLuvjtngKSZwMyj5XfV7/qObpckvpfKg5rdb2iCt1s7yytUY68 zJ6Y2R4rpyM9MAMXTXF8Zhj48GiO8K36ZicN5y981YDTxvdcrcFtyk5Lo2jwJYXoX75k rL8Q== MIME-Version: 1.0 X-Received: by 10.66.144.102 with SMTP id sl6mr18589170pab.96.1383587573436; Mon, 04 Nov 2013 09:52:53 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Mon, 4 Nov 2013 09:52:53 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Nov 2013 09:52:53 -0800 X-Google-Sender-Auth: L56c-GX7f6wQQgPqY3P3SJAgNdQ Message-ID: Subject: Re: Xeon E5 cpu work in low status From: Kevin Oberman To: =?UTF-8?B?5p2O5qOu?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 17:52:54 -0000 On Mon, Nov 4, 2013 at 12:46 AM, =E6=9D=8E=E6=A3=AE w= rote: > hi,all: > the cpu of my machine is : Intel(R) Xeon(R) CPU E5-2643 0 @ > 3.30GHz. > > after a reboot. The cpu freq is : sysctl dev.cpu.0.freq > dev.cpu.0.freq: 1200 > > i didn't set any power savings config in rc.conf. > > How can i fix this? > It's not clear what is broken. Is the server busy? Is there some reason to expect it to be running at full clock-rate? What is the content of dev.cpu.0.freq_levels? By default, FreeBSD runs powerd and that will, by default, throttle back the clock when the system is not busy. I think that this is a bad thing., but it is not a bug. It's by design. I really think, based on my own testing, research and a major NSF computer center (SDSC), and work done by mav@ which can be found on the FreeBSD wiki ( https://wiki.freebsd.org/TuningPowerConsumption), those "power management" tools are broken by design a they are actually there for thermal control, not power management and are, at best, break-even, and in most cases are actually a loser in both power savings and system performance. (There are a very few edge cases where they can be beneficial, but as a side effect for very specific loads under fairly unusual circumstances.) To turn off these (mis)features, add the following to /boot/loader.conf: # Disable CPU throttling hint.p4tcc.0.disabled=3D1 hint.acpi_throttle.0.disabled=3D1 All real power management is through the use of EST and CPU sleep (CX) states. These can provide a big power win at minimal performance impact. Unfortunately CX states and throttling lay very badly together, probably because processor designers don't think that TCC and throttling are for power management, so are not an issue. For reasons that have always baffled me, rather than disable the inappropriate use of thermal management as power management, we disable the most effective power management tools by default. performance_cx_lowest=3D"HIGH" # Online CPU idle state economy_cx_lowest=3D"HIGH" # Offline CPU idle state Even the comments are confusing: what do "Online" and "Offline" mean? Offline means running on battery and online means AC power. In any case, it's not clear that there is any issue with your system other than that, by default, FreeBSD tries to really, really hard to manage power as badly as humanly possible. --=20 R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 4 18:00:49 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7DE7DC1D for ; Mon, 4 Nov 2013 18:00:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3F380272E for ; Mon, 4 Nov 2013 18:00:49 +0000 (UTC) Received: by mail-qa0-f44.google.com with SMTP id f11so425001qae.17 for ; Mon, 04 Nov 2013 10:00:48 -0800 (PST) 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:content-transfer-encoding; bh=R4jbOuGCuLO63nmIdRgQPoj5aWrFtogDwyJpQf4SsLM=; b=PHWj7akCUuhkD3I3MtfccLAl64PGxKz3w4DqDo8p3d5AlHFK5Ur/BEzNpk5T09r6pu QxI2alvqJYfORtaHJnqmtvVM7PYF1v0iosMmTNyKw2oyZH6bv0wjEK7RidC0ZCSNjpmN Z+lM0hxi24ByhcWjoGV2l/d0CvbQb+LmUd5Cmn00QBW0LzHB4Aj5db4gRAmNpCyUiTga pZWCeLxti3nnWAiPhCqGQ23dMUpXtAG7vLKzM5Wi6Tz0UbofBMkUk+E+v+8k/bk5wBgg 7Tq9LnSGB9Zd+LZTcxqJCEvQ7oUm/hhXSXmn5wdlzCQoowA+ASjXKfyC1VYbjjrYl1YQ v8JQ== MIME-Version: 1.0 X-Received: by 10.49.59.115 with SMTP id y19mr23851629qeq.8.1383588048455; Mon, 04 Nov 2013 10:00:48 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 4 Nov 2013 10:00:48 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Nov 2013 10:00:48 -0800 X-Google-Sender-Auth: HNOKVNMmQvx5zrl8GnCOHVdSm0I Message-ID: Subject: Re: Xeon E5 cpu work in low status From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-acpi@freebsd.org" , =?UTF-8?B?5p2O5qOu?= X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 18:00:49 -0000 A lot of us think this. The question is .. who's going to fix it? :-) -adrian On 4 November 2013 09:52, Kevin Oberman wrote: > On Mon, Nov 4, 2013 at 12:46 AM, =E6=9D=8E=E6=A3=AE = wrote: > >> hi,all: >> the cpu of my machine is : Intel(R) Xeon(R) CPU E5-2643 0 @ >> 3.30GHz. >> >> after a reboot. The cpu freq is : sysctl dev.cpu.0.freq >> dev.cpu.0.freq: 1200 >> >> i didn't set any power savings config in rc.conf. >> >> How can i fix this? >> > > It's not clear what is broken. Is the server busy? Is there some reason t= o > expect it to be running at full clock-rate? > > What is the content of dev.cpu.0.freq_levels? > > By default, FreeBSD runs powerd and that will, by default, throttle back > the clock when the system is not busy. I think that this is a bad thing., > but it is not a bug. It's by design. I really think, based on my own > testing, research and a major NSF computer center (SDSC), and work done b= y > mav@ which can be found on the FreeBSD wiki ( > https://wiki.freebsd.org/TuningPowerConsumption), those "power management= " > tools are broken by design a they are actually there for thermal control, > not power management and are, at best, break-even, and in most cases are > actually a loser in both power savings and system performance. (There are= a > very few edge cases where they can be beneficial, but as a side effect fo= r > very specific loads under fairly unusual circumstances.) > > To turn off these (mis)features, add the following to /boot/loader.conf: > # Disable CPU throttling > hint.p4tcc.0.disabled=3D1 > hint.acpi_throttle.0.disabled=3D1 > > > All real power management is through the use of EST and CPU sleep (CX) > states. These can provide a big power win at minimal performance impact. > Unfortunately CX states and throttling lay very badly together, probably > because processor designers don't think that TCC and throttling are for > power management, so are not an issue. > > For reasons that have always baffled me, rather than disable the > inappropriate use of thermal management as power management, we disable t= he > most effective power management tools by default. > performance_cx_lowest=3D"HIGH" # Online CPU idle state > economy_cx_lowest=3D"HIGH" # Offline CPU idle state > > Even the comments are confusing: what do "Online" and "Offline" mean? > Offline means running on battery and online means AC power. > > In any case, it's not clear that there is any issue with your system othe= r > than that, by default, FreeBSD tries to really, really hard to manage pow= er > as badly as humanly possible. > > > -- > R. Kevin Oberman, Network Engineer > E-mail: rkoberman@gmail.com > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 4 18:05:05 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 31A47D8F for ; Mon, 4 Nov 2013 18:05:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E66E32780 for ; Mon, 4 Nov 2013 18:05:04 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id l13so4183866qcy.32 for ; Mon, 04 Nov 2013 10:05:04 -0800 (PST) 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:content-transfer-encoding; bh=jqH1fIwWudUrwoDgcIlZH2hHPwt6upN08GV2FikxyA4=; b=Q1iHYLwyS2GgzCEcBPCBi30uQLQHD2I6saCPcrqgGzVX+bavQr7Jj5VCVV7HrhM73r go+ScF28Ydl70OX80h9zxRnX4zhml+BcCnZO7ryeWyRFcu/QiLh0GFFSXbVecAiQA8Ve b5ICOfZkRVEEdP9DByPasKH/Blqylu0+BUv0GMC+G9/nL6esJt5ua1EApv9dCFeSopbE /e4TEg3995H4w7NKGGQWXKY8YgB5A7Kn0PlN0Q21KasIELNUrjP3YSnYOpqrCJJCOvtp 681MhR1Colon1S8HdHwjJ35l3HYcrbbHDumT9BvEZZDDUR/VkG72QYbpNgtQfsL/aKob GV9w== MIME-Version: 1.0 X-Received: by 10.49.59.115 with SMTP id y19mr23883505qeq.8.1383588304083; Mon, 04 Nov 2013 10:05:04 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 4 Nov 2013 10:05:04 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Nov 2013 10:05:04 -0800 X-Google-Sender-Auth: sqEA5qnOfk1TD2TbvQh8ARWFdZY Message-ID: Subject: Re: Xeon E5 cpu work in low status From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-acpi@freebsd.org" , =?UTF-8?B?5p2O5qOu?= X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 18:05:05 -0000 .. and what I'd really like to see is some tools to inspect power consumption on the CPU side of things. I'd also like something for the GPU side of things too. I can't find anything in our DRM driver code that twiddles the clock PLL registers to slow things down. Thanks, -adrian On 4 November 2013 10:00, Adrian Chadd wrote: > A lot of us think this. The question is .. who's going to fix it? > > :-) > > > > -adrian > > > On 4 November 2013 09:52, Kevin Oberman wrote: >> On Mon, Nov 4, 2013 at 12:46 AM, =E6=9D=8E=E6=A3=AE wrote: >> >>> hi,all: >>> the cpu of my machine is : Intel(R) Xeon(R) CPU E5-2643 0 @ >>> 3.30GHz. >>> >>> after a reboot. The cpu freq is : sysctl dev.cpu.0.freq >>> dev.cpu.0.freq: 1200 >>> >>> i didn't set any power savings config in rc.conf. >>> >>> How can i fix this? >>> >> >> It's not clear what is broken. Is the server busy? Is there some reason = to >> expect it to be running at full clock-rate? >> >> What is the content of dev.cpu.0.freq_levels? >> >> By default, FreeBSD runs powerd and that will, by default, throttle back >> the clock when the system is not busy. I think that this is a bad thing.= , >> but it is not a bug. It's by design. I really think, based on my own >> testing, research and a major NSF computer center (SDSC), and work done = by >> mav@ which can be found on the FreeBSD wiki ( >> https://wiki.freebsd.org/TuningPowerConsumption), those "power managemen= t" >> tools are broken by design a they are actually there for thermal control= , >> not power management and are, at best, break-even, and in most cases are >> actually a loser in both power savings and system performance. (There ar= e a >> very few edge cases where they can be beneficial, but as a side effect f= or >> very specific loads under fairly unusual circumstances.) >> >> To turn off these (mis)features, add the following to /boot/loader.conf: >> # Disable CPU throttling >> hint.p4tcc.0.disabled=3D1 >> hint.acpi_throttle.0.disabled=3D1 >> >> >> All real power management is through the use of EST and CPU sleep (CX) >> states. These can provide a big power win at minimal performance impact= . >> Unfortunately CX states and throttling lay very badly together, probably >> because processor designers don't think that TCC and throttling are for >> power management, so are not an issue. >> >> For reasons that have always baffled me, rather than disable the >> inappropriate use of thermal management as power management, we disable = the >> most effective power management tools by default. >> performance_cx_lowest=3D"HIGH" # Online CPU idle state >> economy_cx_lowest=3D"HIGH" # Offline CPU idle state >> >> Even the comments are confusing: what do "Online" and "Offline" mean? >> Offline means running on battery and online means AC power. >> >> In any case, it's not clear that there is any issue with your system oth= er >> than that, by default, FreeBSD tries to really, really hard to manage po= wer >> as badly as humanly possible. >> >> >> -- >> R. Kevin Oberman, Network Engineer >> E-mail: rkoberman@gmail.com >> _______________________________________________ >> freebsd-acpi@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 4 22:03:48 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 88B2F90F for ; Mon, 4 Nov 2013 22:03:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 597012690 for ; Mon, 4 Nov 2013 22:03:48 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 09678B972; Mon, 4 Nov 2013 17:03:47 -0500 (EST) From: John Baldwin To: freebsd-acpi@freebsd.org Subject: Re: Xeon E5 cpu work in low status Date: Mon, 4 Nov 2013 14:53:03 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201311041453.03864.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 04 Nov 2013 17:03:47 -0500 (EST) Cc: Kevin Oberman , =?utf-8?q?=E6=9D=8E=E6=A3=AE?= X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 22:03:48 -0000 On Monday, November 04, 2013 12:52:53 pm Kevin Oberman wrote: > On Mon, Nov 4, 2013 at 12:46 AM, =E6=9D=8E=E6=A3=AE = wrote: >=20 > > hi,all: > > the cpu of my machine is : Intel(R) Xeon(R) CPU E5-2643 0 @ > > 3.30GHz. > > > > after a reboot. The cpu freq is : sysctl dev.cpu.0.freq > > dev.cpu.0.freq: 1200 > > > > i didn't set any power savings config in rc.conf. > > > > How can i fix this? > > >=20 > It's not clear what is broken. Is the server busy? Is there some reason to > expect it to be running at full clock-rate? >=20 > What is the content of dev.cpu.0.freq_levels? >=20 > By default, FreeBSD runs powerd and that will, by default, throttle back > the clock when the system is not busy. I think that this is a bad thing., > but it is not a bug. It's by design. I really think, based on my own > testing, research and a major NSF computer center (SDSC), and work done by > mav@ which can be found on the FreeBSD wiki ( > https://wiki.freebsd.org/TuningPowerConsumption), those "power management" > tools are broken by design a they are actually there for thermal control, > not power management and are, at best, break-even, and in most cases are > actually a loser in both power savings and system performance. (There are= a > very few edge cases where they can be beneficial, but as a side effect for > very specific loads under fairly unusual circumstances.) >=20 > To turn off these (mis)features, add the following to /boot/loader.conf: > # Disable CPU throttling > hint.p4tcc.0.disabled=3D1 > hint.acpi_throttle.0.disabled=3D1 >=20 > > All real power management is through the use of EST and CPU sleep (CX) > states. These can provide a big power win at minimal performance impact. > Unfortunately CX states and throttling lay very badly together, probably > because processor designers don't think that TCC and throttling are for > power management, so are not an issue. >=20 > For reasons that have always baffled me, rather than disable the > inappropriate use of thermal management as power management, we disable t= he > most effective power management tools by default. > performance_cx_lowest=3D"HIGH" # Online CPU idle state > economy_cx_lowest=3D"HIGH" # Offline CPU idle state >=20 > Even the comments are confusing: what do "Online" and "Offline" mean? > Offline means running on battery and online means AC power. >=20 > In any case, it's not clear that there is any issue with your system other > than that, by default, FreeBSD tries to really, really hard to manage pow= er > as badly as humanly possible. > The only thing is that powerd is not enabled by default, so it shouldn't be set to 1200 out of the box. I think there have been a few laptops=20 historically that would startup at a lower clock speed (EST) when booted on battery, but I've never heard of that for servers. In terms of thermal throttling vs EST: ideally powerd would only ever use E= ST, and the throttling would be driven by acpi_thermal. Most systems don't hav= e=20 the _TC1/_TC2 methods acpi_thermal needs (I think I've only seen it on olde= r=20 laptops), so that would effectively disable TCC on modern systems. This requires tearing cpufreq apart a bit. It's also not clear what we sho= uld display to the user. The simplest approach would be to only export "absolu= te" frequencies in freq_levels and the current "absolute" frequency as "freq". That would allow powerd to not need any changes. You could use a different sysctl node that is "throttling percent" or some such. If throttling kicked in on a system with TC1/TC2 then 'freq' wouldn't change when the CPU was=20 throttled, only the "throttling percent". =2D-=20 John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 4 22:25:00 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D6D3CFDE; Mon, 4 Nov 2013 22:25:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6D19B27D4; Mon, 4 Nov 2013 22:25:00 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id rA4MOsol075715; Tue, 5 Nov 2013 00:24:54 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua rA4MOsol075715 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id rA4MOsJJ075714; Tue, 5 Nov 2013 00:24:54 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 5 Nov 2013 00:24:54 +0200 From: Konstantin Belousov To: John Baldwin Subject: Re: Xeon E5 cpu work in low status Message-ID: <20131104222454.GU59496@kib.kiev.ua> References: <201311041453.03864.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3cvvRM8VcazWLkOB" Content-Disposition: inline In-Reply-To: <201311041453.03864.jhb@freebsd.org> User-Agent: Mutt/1.5.22 (2013-10-16) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: Kevin Oberman , freebsd-acpi@freebsd.org, ?????? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 22:25:01 -0000 --3cvvRM8VcazWLkOB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 04, 2013 at 02:53:03PM -0500, John Baldwin wrote: > On Monday, November 04, 2013 12:52:53 pm Kevin Oberman wrote: > > On Mon, Nov 4, 2013 at 12:46 AM, ?????? wrote: > >=20 > > > hi,all: > > > the cpu of my machine is : Intel(R) Xeon(R) CPU E5-2643 0 @ > > > 3.30GHz. > > > > > > after a reboot. The cpu freq is : sysctl dev.cpu.0.freq > > > dev.cpu.0.freq: 1200 > > > > > > i didn't set any power savings config in rc.conf. > > > > > > How can i fix this? > > > > >=20 > > It's not clear what is broken. Is the server busy? Is there some reason= to > > expect it to be running at full clock-rate? > >=20 > > What is the content of dev.cpu.0.freq_levels? > >=20 > > By default, FreeBSD runs powerd and that will, by default, throttle back > > the clock when the system is not busy. I think that this is a bad thing= =2E, > > but it is not a bug. It's by design. I really think, based on my own > > testing, research and a major NSF computer center (SDSC), and work done= by > > mav@ which can be found on the FreeBSD wiki ( > > https://wiki.freebsd.org/TuningPowerConsumption), those "power manageme= nt" > > tools are broken by design a they are actually there for thermal contro= l, > > not power management and are, at best, break-even, and in most cases are > > actually a loser in both power savings and system performance. (There a= re a > > very few edge cases where they can be beneficial, but as a side effect = for > > very specific loads under fairly unusual circumstances.) > >=20 > > To turn off these (mis)features, add the following to /boot/loader.conf: > > # Disable CPU throttling > > hint.p4tcc.0.disabled=3D1 > > hint.acpi_throttle.0.disabled=3D1 > >=20 > > > > All real power management is through the use of EST and CPU sleep (CX) > > states. These can provide a big power win at minimal performance impac= t. > > Unfortunately CX states and throttling lay very badly together, probably > > because processor designers don't think that TCC and throttling are for > > power management, so are not an issue. > >=20 > > For reasons that have always baffled me, rather than disable the > > inappropriate use of thermal management as power management, we disable= the > > most effective power management tools by default. > > performance_cx_lowest=3D"HIGH" # Online CPU idle state > > economy_cx_lowest=3D"HIGH" # Offline CPU idle state > >=20 > > Even the comments are confusing: what do "Online" and "Offline" mean? > > Offline means running on battery and online means AC power. > >=20 > > In any case, it's not clear that there is any issue with your system ot= her > > than that, by default, FreeBSD tries to really, really hard to manage p= ower > > as badly as humanly possible. > > >=20 > The only thing is that powerd is not enabled by default, so it shouldn't = be > set to 1200 out of the box. I think there have been a few laptops=20 > historically that would startup at a lower clock speed (EST) when booted = on > battery, but I've never heard of that for servers. >=20 > In terms of thermal throttling vs EST: ideally powerd would only ever use= EST, > and the throttling would be driven by acpi_thermal. Most systems don't h= ave=20 > the _TC1/_TC2 methods acpi_thermal needs (I think I've only seen it on ol= der=20 > laptops), so that would effectively disable TCC on modern systems. >=20 > This requires tearing cpufreq apart a bit. It's also not clear what we s= hould > display to the user. The simplest approach would be to only export "abso= lute" > frequencies in freq_levels and the current "absolute" frequency as "freq". > That would allow powerd to not need any changes. You could use a differe= nt > sysctl node that is "throttling percent" or some such. If throttling kic= ked > in on a system with TC1/TC2 then 'freq' wouldn't change when the CPU was= =20 > throttled, only the "throttling percent". My Intel board DQ67OW starts with the fixed CPU speed, which is configurable in BIOS. Unless OS starts managing the frequency with the cpufreq and powerd, CPU is locked to the pre-configured speed. It was not easy to understand why my single-user memory b/w benchmarks show half of the expected throughput for the cache, until I found the setting and found that Intel defaults to 1/2 of the marketing frequency. For my board, it is Performance->Processor Overrides->Maximum Non-Turbo Ratio. It was set to 17, normal CPU mode is 34, turbo is 38 max. --3cvvRM8VcazWLkOB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJSeB61AAoJEJDCuSvBvK1BJPEP/1Q66rM3MALpPgBvf6/09t2u RivLDccEcMAwbWp298bhrstj09svKC3/+47/idp2wwsk85R69rzIvQ+9CMNU56lC 9HUNuEl4qC6nsGprJJbbSRK/qh1R7u88XIgXbKiXsSGegJfRnPJNOZTKDdN+7VaZ I7hUeuxtyXBI2jUWIlG9AzvNg8DXALHO15wkdMllSf+/5pBRHYDjCzMr8NOh144v 3iiV4A5ONWiGo3W3ReYz+q38UEqNcL5GpohPlfY+prQjVjjeagV5eclPJX6m2oW8 rpu63Jz0ETy6R4LVeKOav/8DeBHYxkgD24CTmuho1CvOYRWxU93a+ww7RnEmXiBf Ht1FUT2kp933me7rixcWgv3tZVXZq9dPxzmhUwEpExIf2A0GmHwP1OljrfVmC/C9 CXfnRMNzogPEUpPPP+HYCvBOR35J+8CW1SZCwfTFtUCdPTlkGKynQ9EQzont13QL TySrB7oVmQ3fA4lyindTSvRtzFfg72red0IP6Dh1uSD71FrdYu9hHKl4412pYgnQ s5NsrRxfWyQGtz6mXQKoe6lRDwqlOStxNzyuvKys8qtEZvbUl3RS0sowMyVoMDiq 77+m3ySz01MuMqYcGhpYk0Ux7jQvTPtMEBZgyybwkFjytp8KFrZZPCvR82lfASXr qT9uWQCNvi5CIbw1Gtfu =ad6o -----END PGP SIGNATURE----- --3cvvRM8VcazWLkOB-- From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 4 22:28:25 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 79531FC; Mon, 4 Nov 2013 22:28:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A1CE27F0; Mon, 4 Nov 2013 22:28:25 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id k18so4365057qcv.10 for ; Mon, 04 Nov 2013 14:28:24 -0800 (PST) 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=jJ8t4pNyFsk63G98Zg0Vt5PtUeB2sxxsM80Pkz/B1sc=; b=iUsbXXml8XXK3Y26lTNIZkJ4quMkk9p0twMsaz573IV48/HN3I2lsED2t2ixd6UbeC yMD1mBhr/A04TqqBNVgJLzv/+87tQHJJsau3dRBd6wlEqAvu4f7/Cy51DFJk1/hasMXY mht6Kb2Hl78qTGmcMR5+qIZjuLkTgvQjA/nHLCldbHHyAGB4eEiXPZOjfp+WUAY6Ktlt cm1bYo4Hx/rbkigTVb7Sixk+beiJCb36w/3qBCQNQSLcCBnlkmnda55I80Usa+JfX5wz wxz70L9c5eHIzcz2owSI2JBlVVxm8gbIsXc4lHmyXnc4YNmcvcN13E7/mJtlNe+8FGe6 gL9Q== MIME-Version: 1.0 X-Received: by 10.49.62.3 with SMTP id u3mr25021938qer.6.1383604104430; Mon, 04 Nov 2013 14:28:24 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 4 Nov 2013 14:28:24 -0800 (PST) In-Reply-To: <20131104222454.GU59496@kib.kiev.ua> References: <201311041453.03864.jhb@freebsd.org> <20131104222454.GU59496@kib.kiev.ua> Date: Mon, 4 Nov 2013 14:28:24 -0800 X-Google-Sender-Auth: O8fZ6N1HOJRHKG1I1KY1N6ENG-Y Message-ID: Subject: Re: Xeon E5 cpu work in low status From: Adrian Chadd To: Konstantin Belousov Content-Type: text/plain; charset=ISO-8859-1 Cc: Kevin Oberman , "freebsd-acpi@freebsd.org" , ?????? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 22:28:25 -0000 On 4 November 2013 14:24, Konstantin Belousov wrote: > My Intel board DQ67OW starts with the fixed CPU speed, which is > configurable in BIOS. Unless OS starts managing the frequency with the > cpufreq and powerd, CPU is locked to the pre-configured speed. It was > not easy to understand why my single-user memory b/w benchmarks show > half of the expected throughput for the cache, until I found the setting > and found that Intel defaults to 1/2 of the marketing frequency. > > For my board, it is Performance->Processor Overrides->Maximum Non-Turbo > Ratio. It was set to 17, normal CPU mode is 34, turbo is 38 max. Does powerd throttle each individual core like this? I don't have anything laptop-y that's recent enough for that to matter. -adrian From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 5 02:09:47 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5150FEC3; Tue, 5 Nov 2013 02:09:47 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9BF30238A; Tue, 5 Nov 2013 02:09:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id rA529hPX029199; Tue, 5 Nov 2013 13:09:43 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 5 Nov 2013 13:09:43 +1100 (EST) From: Ian Smith To: Adrian Chadd Subject: Re: Xeon E5 cpu work in low status In-Reply-To: Message-ID: <20131105124254.U89530@sola.nimnet.asn.au> References: <201311041453.03864.jhb@freebsd.org> <20131104222454.GU59496@kib.kiev.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Kevin Oberman , "freebsd-acpi@freebsd.org" , ?????? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 02:09:47 -0000 On Mon, 4 Nov 2013, Adrian Chadd wrote: > On 4 November 2013 14:24, Konstantin Belousov wrote: > > > My Intel board DQ67OW starts with the fixed CPU speed, which is > > configurable in BIOS. Unless OS starts managing the frequency with the > > cpufreq and powerd, CPU is locked to the pre-configured speed. It was > > not easy to understand why my single-user memory b/w benchmarks show > > half of the expected throughput for the cache, until I found the setting > > and found that Intel defaults to 1/2 of the marketing frequency. > > > > For my board, it is Performance->Processor Overrides->Maximum Non-Turbo > > Ratio. It was set to 17, normal CPU mode is 34, turbo is 38 max. > > Does powerd throttle each individual core like this? I don't have > anything laptop-y that's recent enough for that to matter. Unless something's changed recently I've missed, no. My 9 box is still broken, so ref to 8.2 sources .. start with /sys/kern/kern_cpu.c, cpufreq(4) and results of find /sys/ -name "*freq*". Nate Lawson commented way back: /* * Only initialize one set of sysctls for all CPUs. In the future, * if multiple CPUs can have different settings, we can move these * sysctls to be under every CPU instead of just the first one. */ I recall that some CPUs had potential for individual settings (voltage, freq) but some only per-package rather than per-core, and then there's the thermal control settings as well. I believe Kevin's right, p4tcc and acpi_throttle should be disabled by default, on most CPUs anyway, and that at least is just a simple change to hints, as a start. It's quite a deep rabbit warren, and most docs are only in the code - eg still? no mans for most if not all of the absolute and relative cpufreq drivers mentioned in cpufreq(4), as I recall - and of course the moving targets with newer CPUs .. so have fun down there! cheers, Ian From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 5 04:22:08 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A2B8AE33; Tue, 5 Nov 2013 04:22:08 +0000 (UTC) (envelope-from lisen1001@gmail.com) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1605E29EB; Tue, 5 Nov 2013 04:22:07 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id ex4so1536092wid.15 for ; Mon, 04 Nov 2013 20:22:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BlUp7wEyL8tYH3NhoU4zWUF3HhExPJ0s86Ch//1duCo=; b=0L0CSPTffj+ewotMVGz5pjslG3R9V4ZFApqwrgYpyE+L+u2Kgqm2+QHcFJrs3IFNEn EFITpvV75tLAFYCugJdIoaQT4LfOQRkgnidLc3RtIpcjFguLeDT0jxwpTDrJOXKW5NMx 1LV9x04rcjt+M1OokjJn9BkVMrO8RdP6YS4roDmHLZ8Wv5JAVhA/Rsy0is+8EeSCVdPj x2ccmEGfZ6r3hvp66sGy3juB/DfP4kPo1OSzHPF/5oxr/krQj2xZiOvcwbVnojPFuZyq j9GYoQ3xvDvy0Fx6wBqL3tuXeXjj7FWW6LW+HpcCysA6SZzHzbpYEsqCMLZ71tYoq8v+ Ak/g== MIME-Version: 1.0 X-Received: by 10.180.98.2 with SMTP id ee2mr15128787wib.21.1383625326421; Mon, 04 Nov 2013 20:22:06 -0800 (PST) Received: by 10.194.95.8 with HTTP; Mon, 4 Nov 2013 20:22:06 -0800 (PST) In-Reply-To: <20131105124254.U89530@sola.nimnet.asn.au> References: <201311041453.03864.jhb@freebsd.org> <20131104222454.GU59496@kib.kiev.ua> <20131105124254.U89530@sola.nimnet.asn.au> Date: Tue, 5 Nov 2013 12:22:06 +0800 Message-ID: Subject: Re: Xeon E5 cpu work in low status From: Jason To: Ian Smith Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kevin Oberman , "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 04:22:08 -0000 Thanks for all the responses. my machine is ibm bladecenter hs23 server. As Konstantin Belousov said, i check my server BIOS, change the processor performacne from "Favor Performace" to "Max Performance" It seems ok now. From owner-freebsd-acpi@FreeBSD.ORG Sat Nov 9 12:30:03 2013 Return-Path: Delivered-To: freebsd-acpi@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 79F9B50F for ; Sat, 9 Nov 2013 12:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4E5AF2B12 for ; Sat, 9 Nov 2013 12:30:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rA9CU1EN097559 for ; Sat, 9 Nov 2013 12:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rA9CU16P097558; Sat, 9 Nov 2013 12:30:01 GMT (envelope-from gnats) Date: Sat, 9 Nov 2013 12:30:01 GMT Message-Id: <201311091230.rA9CU16P097558@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org Cc: From: joseph Subject: Re: kern/162859: [acpi] ACPI battery/acline monitoring partialy working (switching) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: joseph List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Nov 2013 12:30:03 -0000 The following reply was made to PR kern/162859; it has been noted by GNATS. From: joseph To: bug-followup@FreeBSD.org, msuszko@gmail.com Cc: Subject: Re: kern/162859: [acpi] ACPI battery/acline monitoring partialy working (switching) Date: Sat, 09 Nov 2013 13:25:26 +0100 Count one more. I updated from FreeBSD 8.2, where the acpi battery status worked, to 9.2 where it does not. The battery charging level and state won't be updatet, means if i start with or without cable the charging level and state remain unchanged up to the next reboot. I use an HP 625.