From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 27 10:59:53 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FABC1065675 for ; Mon, 27 Jun 2011 10:59:53 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C990F8FC18 for ; Mon, 27 Jun 2011 10:59:52 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA20822; Mon, 27 Jun 2011 13:59:50 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Qb9Xi-0001wS-0b; Mon, 27 Jun 2011 13:59:50 +0300 Message-ID: <4E0862A0.7060405@FreeBSD.org> Date: Mon, 27 Jun 2011 13:59:44 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Vitaly Magerya References: <4E05EB91.9090509@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2011 10:59:53 -0000 on 25/06/2011 18:47 Vitaly Magerya said the following: > Andriy Gapon wrote: >> on 24/06/2011 22:13 Vitaly Magerya said the following: >>> Right after I start the laptop I only see one supported power state: >>> >>> # sysctl dev.cpu.0.cx_supported >>> dev.cpu.0.cx_supported: C1/1 >>> >>> But after 4+ minutes of uptime more power states kick in: >>> >>> # sysctl dev.cpu.0.cx_supported >>> dev.cpu.0.cx_supported: C1/1 C2/20 C3/100 >>> >>> I'd like to have all Cx right after the boot. Is this possible? >>> >>> (The temporary solution I employ is to update hw.acpi.cpu.cx_lowest >>> every time devd gets ACPI CMBAT message; this appears to happen >>> right after cx_supported is updated). >> >> Hmm, strange... >> Can you check if FreeBSD thinks that the system is on AC power until that >> CMBAT message? (I see in dmesg that during that boot it detected AC as >> disconnected). > > AC was indeed disconnected during that boot (and hw.acpi.acline was > 0 as expected). If I boot with power on the problem is the same: > about 4 minutes there's only C1, after that there are C1 and C2 (C3 > kicks in too once I disable the power). This is quite unexpected for me. You can try to run devd in debug mode and capture its output in a file, so that ACPI events could be examined. > (I boot with power cord disconnected, since LCD brightness controls > on the laptop don't work with FreeBSD, so that's the only way to > turn the brightness down). > >>> Also, when I boot the same machine under Linux (latest Ubuntu), >>> powertop reports C1, C2 and C4 right away. Is it possible to get >>> C4 under FreeBSD as well? >> >> I believe that what FreeBSD reports as C3 is the same as what Linux reports >> as C4. > > The problem is that on Linux power consumption is 5.2W (without USB > suspension or any other things powertop suggests), while on FreeBSD > I'm seeing 6.8W with C3. I assumed this was due to C4/C3 difference, > but maybe Linux is doing something differently. Quite possible. >>> Other ACPI problems, which I have are: >>> 1. When the power cord is plugged in, C3 state disappears. >> >> Does the same happen with Linux? >> Many notebooks disable deep Cx states when on AC power for some reason. > > No. On Linux C4 is reported both with and without AC plugged in. It seems that possibly we present different OS capabilities to ACPI... Needs more investigation. Can you also send me two binary files produced as follows: 1. dd if=/dev/mem size=1 iseek=0x3F5B9B71 count=0x00000203 of=... 2. dd if=/dev/mem size=1 iseek=0x3F5B92DA count=0x00000708 of=... Or, if it's not too much trouble for you, you can send results of decompilation of those files using iasl -d >>> 2. When I plug (or unplug) the power cord I get these two messages: >>> >>> ACPI Error: [\\_SB_.VDRV] Namespace lookup failure, AE_NOT_FOUND >>> (20101013/psargs-464) ACPI Error: Method parse/execution failed >>> >>> [\\_SB_.PCI0.LPC0.H_EC._Q51] (Node 0xc42ac1e0), AE_NOT_FOUND >>> (20101013/psparse-633) >>> >>> (This appears to be harmless). >> >> Not sure about these, looks like some additional/external table is not >> loaded. You may check if the same happens with the latest ACPICA in FreeBSD >> CURRENT. > > I just tried it with CURRENT snapshot from 2011-05-12; it behaves > the same. > > (For the record, Linux reports similar messages). Ok, then this is most likely a mistake of BIOS writers, it seems. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 27 11:06:57 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEE721065675 for ; Mon, 27 Jun 2011 11:06:56 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CE5138FC1A for ; Mon, 27 Jun 2011 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p5RB6uOB071753 for ; Mon, 27 Jun 2011 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p5RB6uha071749 for freebsd-acpi@FreeBSD.org; Mon, 27 Jun 2011 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Jun 2011 11:06:56 GMT Message-Id: <201106271106.p5RB6uha071749@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 Cc: Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2011 11:06:57 -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/154955 acpi [acpi] Keyboard or ACPI doesn't work on Lenovo S10-3 o kern/152438 acpi [acpi]: patch to acpi_asus(4) to add extra sysctls for 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/144045 acpi [acpi] [panic] kernel trap with acpi enabled o i386/143798 acpi [acpi] shutdown problem with SiS K7S5A o kern/143420 acpi [acpi] ACPI issues with Toshiba o kern/142263 acpi [acpi] ACPI regression on Asus K8N7-E deluxe motherboa o kern/142009 acpi [acpi] [panic] Panic in AcpiNsGetAttachedObject o amd64/140751 acpi [acpi] BIOS resource allocation and FreeBSD ACPI in TO 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 bin/137053 acpi [hang] FreeBSD 8.0 BETA2Compaq Mini 700 locks on boot o kern/137042 acpi [acpi] hp laptop's lcd not wakes up after suspend to r o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o bin/135349 acpi [patch] teach acpidump(8) to disassemble arbitrary mem o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not o kern/130683 acpi [ACPI] shutdown hangs after syncing disks - ACPI race? o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D p kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/91594 acpi [acpi] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/ o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/73823 acpi [request] acpi / power-on by timer support o i386/69750 acpi Boot without ACPI failed on ASUS L5 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 41 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 27 18:04:13 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7118D1065673; Mon, 27 Jun 2011 18:04:13 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0D9DB8FC08; Mon, 27 Jun 2011 18:04:12 +0000 (UTC) Received: by vws18 with SMTP id 18so4978327vws.13 for ; Mon, 27 Jun 2011 11:04:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Y3qtMRMPX3uDEBo2iAxyZj2PUW2V5psGvQvyKBuVuiQ=; b=tFdbJof+v4xt766kBAQ9X4+NPoEPtcKWNpYVJF9ovD09Tznop3DUlQFFzZZIx06FiJ VnnGIUceQIMV/djqcS5mSnEOcCCOEu/AmrlY2HTiuDlpUtdKJ7ELjvPn0WhQWMM6kkpr AnFU+fdKD93nAA5GWFAnAdcommSMa7uF9v99A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YtWpN3PGX2stCw/FgEODgnuLpXYzPgv9rUpRFMgXLNPISmitPe5PrpuT86yrbIPHCL ukftWHrFivLAzMhG0VuIUXbc6kI7Mc8aZbeqbNI2kycvpLdOQGZlWC+jtG6eYreHNEZn 2z8ZRLr4gt3lkPS3zAmEScFx5u6FynV/yMEhM= MIME-Version: 1.0 Received: by 10.52.187.164 with SMTP id ft4mr8624270vdc.59.1309197852206; Mon, 27 Jun 2011 11:04:12 -0700 (PDT) Received: by 10.52.184.226 with HTTP; Mon, 27 Jun 2011 11:04:11 -0700 (PDT) In-Reply-To: <4E0862A0.7060405@FreeBSD.org> References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> Date: Mon, 27 Jun 2011 21:04:11 +0300 Message-ID: From: Vitaly Magerya To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-acpi@freebsd.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2011 18:04:13 -0000 Andriy Gapon wrote: > You can try to run devd in debug mode and capture its output in a file, so > that ACPI events could be examined. After 2+ minutes of uptime I get the first devd event: !system=ACPI subsystem=CMBAT type=\_SB_.PCI0.LPC0.H_EC.BAT1 notify=0x80 At this point cx_supported is still C1/1. After 4+ minutes of uptime (sometimes it's 3+) I get the same message once again, this time cx_supported is updated with C1, C2 and C3. The same event is reported aftewrads too; once in a few minutes. If power cord is plugged in, I get about 4 events like that before cx_supported is updated; they continue to arrive afterwards, once or twice per minute. (I can show the actual output of devd in debug mode, but aside from those events it's about parsing and other uninteresting stuff). > It seems that possibly we present different OS capabilities to ACPI... > Needs more investigation. > > Can you also send me two binary files produced as follows: > 1. dd if=/dev/mem size=1 iseek=0x3F5B9B71 count=0x00000203 of=... > 2. dd if=/dev/mem size=1 iseek=0x3F5B92DA count=0x00000708 of=... > > Or, if it's not too much trouble for you, you can send results of > decompilation of those files using iasl -d You can find them all at [1] and [2]. [1] http://tx97.net/~magv/n143-acpi/mem-3f5b9b71.dsl.txt [2] http://tx97.net/~magv/n143-acpi/mem-3f5b92da.dsl.txt From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 11:28:38 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EF631065670 for ; Tue, 28 Jun 2011 11:28:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A9A118FC08 for ; Tue, 28 Jun 2011 11:28:37 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA06852; Tue, 28 Jun 2011 14:28:35 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QbWT4-0005PF-Il; Tue, 28 Jun 2011 14:28:34 +0300 Message-ID: <4E09BADF.7050702@FreeBSD.org> Date: Tue, 28 Jun 2011 14:28:31 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Vitaly Magerya References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 11:28:38 -0000 on 27/06/2011 21:04 Vitaly Magerya said the following: >> It seems that possibly we present different OS capabilities to ACPI... >> Needs more investigation. >> >> Can you also send me two binary files produced as follows: >> 1. dd if=/dev/mem size=1 iseek=0x3F5B9B71 count=0x00000203 of=... >> 2. dd if=/dev/mem size=1 iseek=0x3F5B92DA count=0x00000708 of=... >> >> Or, if it's not too much trouble for you, you can send results of >> decompilation of those files using iasl -d > > You can find them all at [1] and [2]. > > [1] http://tx97.net/~magv/n143-acpi/mem-3f5b9b71.dsl.txt > [2] http://tx97.net/~magv/n143-acpi/mem-3f5b92da.dsl.txt OK, thank you, very interesting. I think that part (but not all) of the differences between FreeBSD and Linux can be explained by the fact that FreeBSD currently doesn't advertise itself as featuring ACPI_CAP_SMP_C1_NATIVE and ACPI_CAP_SMP_C3_NATIVE. I am not sure what it would take to actually support these features. I think that Linux does support (or at least advertise support) for these features. I see one repeated condition for providing advanced C states, it's: (\_SB.C1ON) and (LAnd (LOr (LNot (PWRS), \_SB.C4AC), \_SB.C3SU))). I think that PWRS is supposed to reflect current AC state (1 - connected, 0 - disconnected). All of C1ON, C4AC and C3SU are declared in a special memory region: OperationRegion (SNVS, SystemMemory, 0x3F5C0C7D, 0x000000FF) My guess is that SNVS stands for "System Non-Volatile Storage" or some such, which may serve similarly to CMOS NVRAM for BIOS settings. Further, I guess that C4AC is a configuration setting for whether to provide C4 state while on AC, and C3SU - is whether C3 state should be supported. C1ON - not really sure. I would be interested to see memory dumps of the above region both early after boot and later when you get additional C states. This can be done with: dd if=/dev/mem size=1 iseek=0x3F5C0C7D count=0x000000FF I am not sure if the values in SNVS can change during OS run-time, so I would like to check that. At least they are not modified via ACPI code as far as I can see. Then, PWRS is declared in GNVS region ("Global Non-Volatile Storage"?): OperationRegion (GNVS, SystemMemory, 0x3F5C0D7C, 0x0100) I would like to get two dumps for this region too. I see that PWRS value is being manipulated in a few of EC (embedded controller device) methods. So maybe we do not call something related as early as Linux does. And, I also see that there is an interesting variable MPEN which controls whether to send Processor notifications when PNOT ("processor notify"?) method is called; these notifications are what leads to re-evaluation of _CST (avialable C states). I hope that the additional data will shed some light. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 19:14:49 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 278701065670; Tue, 28 Jun 2011 19:14:49 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org Date: Tue, 28 Jun 2011 15:14:34 -0400 User-Agent: KMail/1.6.2 References: <4E09BADF.7050702@FreeBSD.org> In-Reply-To: <4E09BADF.7050702@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106281514.36324.jkim@FreeBSD.org> Cc: Vitaly Magerya , Andriy Gapon Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 19:14:49 -0000 On Tuesday 28 June 2011 07:28 am, Andriy Gapon wrote: > I think that part (but not all) of the differences between FreeBSD > and Linux can be explained by the fact that FreeBSD currently > doesn't advertise itself as featuring ACPI_CAP_SMP_C1_NATIVE and > ACPI_CAP_SMP_C3_NATIVE. I am not sure what it would take to > actually support these features. I think that Linux does support > (or at least advertise support) for these features. Yes, Linux supports this Intel-specific feature. I think it shouldn't be too hard for us, however. We just have to add support for Intel-specific _CST FFH (Functional Fixed Hardware) in sys/dev/acpica/acpi_cpu.c. You can find more information from "Intel Processor Vendor-Specific ACPI" (order number 302223-005) on Intel website. Also, arch/x86/kernel/acpi/cstate.c of Linux source may help. I believe Linux actually supports all Intel-specific FFHs, BTW. Jung-uk Kim From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 19:37:11 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06882106564A; Tue, 28 Jun 2011 19:37:11 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 98D0A8FC12; Tue, 28 Jun 2011 19:37:10 +0000 (UTC) Received: by vws18 with SMTP id 18so570454vws.13 for ; Tue, 28 Jun 2011 12:37:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YFovKwCOJfjh77a9Fr1fo5H5VOoB0+W0Gq6F+gFC/lI=; b=HqZt4VoKYoRmoaVqTAfGDP1Orc0dPAUxsWPTErYHlsfvyFgFLRLbhAHnAEsbvRtkWd KufcycJLXKhwtNSslivaPfTZSlsmXvQ8O2/SwAC8TLeWqm74W443KMPZW4RpparAvMgI W7YKPVupwFj532oVrJmmr+JxwwzR6rfZ8S5gM= MIME-Version: 1.0 Received: by 10.52.177.196 with SMTP id cs4mr10638454vdc.279.1309289828844; Tue, 28 Jun 2011 12:37:08 -0700 (PDT) Received: by 10.52.108.226 with HTTP; Tue, 28 Jun 2011 12:37:08 -0700 (PDT) In-Reply-To: <4E09BADF.7050702@FreeBSD.org> References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> <4E09BADF.7050702@FreeBSD.org> Date: Tue, 28 Jun 2011 22:37:08 +0300 Message-ID: From: Vitaly Magerya To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-acpi@freebsd.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 19:37:11 -0000 > I think that part (but not all) of the differences between FreeBSD and Linux > can be explained by the fact that FreeBSD currently doesn't advertise itself as > featuring ACPI_CAP_SMP_C1_NATIVE and ACPI_CAP_SMP_C3_NATIVE. I am not sure > what it would take to actually support these features. I think that Linux does > support (or at least advertise support) for these features. Is there some simple way of sending fake advertisement? Or will that lead to disaster? > I would be interested to see memory dumps of the above region both early > after boot and later when you get additional C states. > This can be done with: > dd if=/dev/mem size=1 iseek=0x3F5C0C7D count=0x000000FF > > [...] > > Then, PWRS is declared in GNVS region ("Global Non-Volatile Storage"?): > OperationRegion (GNVS, SystemMemory, 0x3F5C0D7C, 0x0100) > I would like to get two dumps for this region too. When I boot without power, I get these dumps [1,2]. For your convenience, the same dumps decoded are at [3,4]. After C2 and C3 become available, I get mostly the same dumps [5,6]: only C1ON changes from 0 to 1. If I now plug the power cord in, PWRS changes from 0 to 1 and P80D changes from 06:08:00:00 to 30:08:00:00. If I unplug it once again, P80D becomes 31:08:00:00. When I boot with power cord in, everything is the same, except for PWRS and P80D (the latter is 06:... initially, and then cycles between 31:... and 30:...). > I see that PWRS value is being manipulated in a few of EC (embedded controller > device) methods. So maybe we do not call something related as early as > Linux does. PWRS appears to reflect power cord status correctly. If someone will tell me how the hell do you dump memory in Linux, I'll submit the dumps for it too. Currently dd fails there with this error: $ sudo dd if=/dev/mem of=... bs=1 skip=0x3F5C0C7D count=0x000000FF dd: read /dev/mem: Bad address (Reproduced by memory). [1] http://tx97.net/~magv/n143-acpi/mem-3f5c0c7d-before.bin [2] http://tx97.net/~magv/n143-acpi/mem-3f5c0d7c-before.bin [3] http://tx97.net/~magv/n143-acpi/mem-3f5c0c7d-before.txt [4] http://tx97.net/~magv/n143-acpi/mem-3f5c0d7c-before.txt [5] http://tx97.net/~magv/n143-acpi/mem-3f5c0c7d-after.bin [6] http://tx97.net/~magv/n143-acpi/mem-3f5c0d7c-after.bin From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 21:04:14 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D5301065675 for ; Tue, 28 Jun 2011 21:04:14 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BD2558FC2B for ; Tue, 28 Jun 2011 21:04:13 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA12977; Wed, 29 Jun 2011 00:04:11 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QbfS6-0005sP-BS; Wed, 29 Jun 2011 00:04:10 +0300 Message-ID: <4E0A41C8.3000904@FreeBSD.org> Date: Wed, 29 Jun 2011 00:04:08 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Vitaly Magerya References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> <4E09BADF.7050702@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 21:04:14 -0000 on 28/06/2011 22:37 Vitaly Magerya said the following: >> I think that part (but not all) of the differences between FreeBSD and Linux >> can be explained by the fact that FreeBSD currently doesn't advertise itself as >> featuring ACPI_CAP_SMP_C1_NATIVE and ACPI_CAP_SMP_C3_NATIVE. I am not sure >> what it would take to actually support these features. I think that Linux does >> support (or at least advertise support) for these features. > > Is there some simple way of sending fake advertisement? Or will > that lead to disaster? It doesn't make sense without actual support. And maybe (just maybe) it won't change much anyway. >> I would be interested to see memory dumps of the above region both early >> after boot and later when you get additional C states. >> This can be done with: >> dd if=/dev/mem size=1 iseek=0x3F5C0C7D count=0x000000FF >> >> [...] >> >> Then, PWRS is declared in GNVS region ("Global Non-Volatile Storage"?): >> OperationRegion (GNVS, SystemMemory, 0x3F5C0D7C, 0x0100) >> I would like to get two dumps for this region too. > > When I boot without power, I get these dumps [1,2]. For your > convenience, the same dumps decoded are at [3,4]. After C2 and C3 > become available, I get mostly the same dumps [5,6]: only C1ON > changes from 0 to 1. Yep. Now the biggest question is what that C1ON is and what changes its value. And how do we (and Linux) trigger that change. [snip] > If someone will tell me how the hell do you dump memory in Linux, > I'll submit the dumps for it too. Currently dd fails there with > this error: > > $ sudo dd if=/dev/mem of=... bs=1 skip=0x3F5C0C7D count=0x000000FF > dd: read /dev/mem: Bad address > > (Reproduced by memory). No idea here. Maybe they don't allow to access memory reserved by kernel from userland, even to root. > [1] http://tx97.net/~magv/n143-acpi/mem-3f5c0c7d-before.bin > [2] http://tx97.net/~magv/n143-acpi/mem-3f5c0d7c-before.bin > [3] http://tx97.net/~magv/n143-acpi/mem-3f5c0c7d-before.txt > [4] http://tx97.net/~magv/n143-acpi/mem-3f5c0d7c-before.txt > [5] http://tx97.net/~magv/n143-acpi/mem-3f5c0c7d-after.bin > [6] http://tx97.net/~magv/n143-acpi/mem-3f5c0d7c-after.bin Since we are now dealing with black box/magic behind ACPI, may I try to suggest doing some DSDT hacks and seeing what changes? One thing to try would be replacing "\_SB.VDRV" with "VDRV" in _Q51 and _Q52 methods. That at least should rid you of those annoying ACPI errors, at best it could improve something. At the very worst it may fry your machine, though... -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 21:13:27 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 6D7E7106564A; Tue, 28 Jun 2011 21:13:26 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org Date: Tue, 28 Jun 2011 17:13:11 -0400 User-Agent: KMail/1.6.2 References: <4E09BADF.7050702@FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201106281713.20698.jkim@FreeBSD.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Vitaly Magerya , Andriy Gapon Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 21:13:27 -0000 On Tuesday 28 June 2011 03:37 pm, Vitaly Magerya wrote: > > I think that part (but not all) of the differences between > > FreeBSD and Linux can be explained by the fact that FreeBSD > > currently doesn't advertise itself as featuring > > ACPI_CAP_SMP_C1_NATIVE and ACPI_CAP_SMP_C3_NATIVE. I am not sure > > what it would take to actually support these features. I think > > that Linux does support (or at least advertise support) for these > > features. > > Is there some simple way of sending fake advertisement? Or will > that lead to disaster? Actually, ACPI_CAP_SMP_C1_NATIVE is kinda supported but without hints from ACPI _CST FFH. It sits in machdep.c as cpu_idle_mwait(). So, I think you can advertise them. The easist way is this (not tested): Index: sys/dev/acpica/acpi_cpu.c =================================================================== --- sys/dev/acpica/acpi_cpu.c (revision 223651) +++ sys/dev/acpica/acpi_cpu.c (working copy) @@ -339,6 +339,10 @@ acpi_cpu_attach(device_t dev) * SMP control where each CPU can have different settings. */ sc->cpu_features = ACPI_CAP_SMP_SAME | ACPI_CAP_SMP_SAME_C3; +#if defined(__amd64__) || defined(__i386__) + if ((cpu_feature2 & CPUID2_MON) != 0) + sc->cpu_features |= ACPI_CAP_SMP_C1_NATIVE; +#endif if (devclass_get_drivers(acpi_cpu_devclass, &drivers, &drv_count) == 0) { for (i = 0; i < drv_count; i++) { if (ACPI_GET_FEATURES(drivers[i], &features) == 0) ACPI_CAP_SMP_C3_NATIVE is also kinda supported without hints from the GAS. Jung-uk Kim From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 21:18:47 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EA45106564A; Tue, 28 Jun 2011 21:18:47 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B44758FC0A; Tue, 28 Jun 2011 21:18:46 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA13155; Wed, 29 Jun 2011 00:18:45 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QbfgC-0005tE-Us; Wed, 29 Jun 2011 00:18:44 +0300 Message-ID: <4E0A4534.30904@FreeBSD.org> Date: Wed, 29 Jun 2011 00:18:44 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Jung-uk Kim References: <4E09BADF.7050702@FreeBSD.org> <201106281713.20698.jkim@FreeBSD.org> In-Reply-To: <201106281713.20698.jkim@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, Vitaly Magerya Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 21:18:47 -0000 on 29/06/2011 00:13 Jung-uk Kim said the following: > On Tuesday 28 June 2011 03:37 pm, Vitaly Magerya wrote: >>> I think that part (but not all) of the differences between >>> FreeBSD and Linux can be explained by the fact that FreeBSD >>> currently doesn't advertise itself as featuring >>> ACPI_CAP_SMP_C1_NATIVE and ACPI_CAP_SMP_C3_NATIVE. I am not sure >>> what it would take to actually support these features. I think >>> that Linux does support (or at least advertise support) for these >>> features. >> >> Is there some simple way of sending fake advertisement? Or will >> that lead to disaster? > > Actually, ACPI_CAP_SMP_C1_NATIVE is kinda supported but without hints > from ACPI _CST FFH. It sits in machdep.c as cpu_idle_mwait(). So, > I think you can advertise them. The easist way is this (not tested): But don't we currently ignore FFH-type C state definitions? I am not sure that mwait that we use (its parameters) would be the same as the system would expect us to use unless we actually parse FFH data. Even for C1 sate. Also I am not sure if that would give much gain/difference. > Index: sys/dev/acpica/acpi_cpu.c > =================================================================== > --- sys/dev/acpica/acpi_cpu.c (revision 223651) > +++ sys/dev/acpica/acpi_cpu.c (working copy) > @@ -339,6 +339,10 @@ acpi_cpu_attach(device_t dev) > * SMP control where each CPU can have different settings. > */ > sc->cpu_features = ACPI_CAP_SMP_SAME | ACPI_CAP_SMP_SAME_C3; > +#if defined(__amd64__) || defined(__i386__) > + if ((cpu_feature2 & CPUID2_MON) != 0) > + sc->cpu_features |= ACPI_CAP_SMP_C1_NATIVE; > +#endif > if (devclass_get_drivers(acpi_cpu_devclass, &drivers, &drv_count) == 0) { > for (i = 0; i < drv_count; i++) { > if (ACPI_GET_FEATURES(drivers[i], &features) == 0) > > ACPI_CAP_SMP_C3_NATIVE is also kinda supported without hints from > the GAS. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 21:26:42 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBEB5106566B; Tue, 28 Jun 2011 21:26:42 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E6DF68FC14; Tue, 28 Jun 2011 21:26:41 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA13229; Wed, 29 Jun 2011 00:26:40 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Qbfns-0005te-B8; Wed, 29 Jun 2011 00:26:40 +0300 Message-ID: <4E0A470F.6090503@FreeBSD.org> Date: Wed, 29 Jun 2011 00:26:39 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Jung-uk Kim References: <4E09BADF.7050702@FreeBSD.org> <201106281514.36324.jkim@FreeBSD.org> In-Reply-To: <201106281514.36324.jkim@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, Vitaly Magerya Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 21:26:42 -0000 on 28/06/2011 22:14 Jung-uk Kim said the following: > On Tuesday 28 June 2011 07:28 am, Andriy Gapon wrote: >> I think that part (but not all) of the differences between FreeBSD >> and Linux can be explained by the fact that FreeBSD currently >> doesn't advertise itself as featuring ACPI_CAP_SMP_C1_NATIVE and >> ACPI_CAP_SMP_C3_NATIVE. I am not sure what it would take to >> actually support these features. I think that Linux does support >> (or at least advertise support) for these features. > > Yes, Linux supports this Intel-specific feature. I think it shouldn't > be too hard for us, however. We just have to add support for > Intel-specific _CST FFH (Functional Fixed Hardware) in > sys/dev/acpica/acpi_cpu.c. You can find more information from "Intel > Processor Vendor-Specific ACPI" (order number 302223-005) on Intel > website. Also, arch/x86/kernel/acpi/cstate.c of Linux source may > help. I believe Linux actually supports all Intel-specific FFHs, > BTW. Once upon a time there was a patch proposed for FreeBSD: http://thread.gmane.org/gmane.os.freebsd.current/127860/focus=6372 Unfortunately I have never really evaluated it. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 21:39:55 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 8A8661065670; Tue, 28 Jun 2011 21:39:54 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Andriy Gapon Date: Tue, 28 Jun 2011 17:39:45 -0400 User-Agent: KMail/1.6.2 References: <201106281713.20698.jkim@FreeBSD.org> <4E0A4534.30904@FreeBSD.org> In-Reply-To: <4E0A4534.30904@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106281739.47588.jkim@FreeBSD.org> Cc: freebsd-acpi@freebsd.org, Vitaly Magerya Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 21:39:55 -0000 On Tuesday 28 June 2011 05:18 pm, Andriy Gapon wrote: > on 29/06/2011 00:13 Jung-uk Kim said the following: > > On Tuesday 28 June 2011 03:37 pm, Vitaly Magerya wrote: > >>> I think that part (but not all) of the differences between > >>> FreeBSD and Linux can be explained by the fact that FreeBSD > >>> currently doesn't advertise itself as featuring > >>> ACPI_CAP_SMP_C1_NATIVE and ACPI_CAP_SMP_C3_NATIVE. I am not > >>> sure what it would take to actually support these features. I > >>> think that Linux does support (or at least advertise support) > >>> for these features. > >> > >> Is there some simple way of sending fake advertisement? Or will > >> that lead to disaster? > > > > Actually, ACPI_CAP_SMP_C1_NATIVE is kinda supported but without > > hints from ACPI _CST FFH. It sits in machdep.c as > > cpu_idle_mwait(). So, I think you can advertise them. The > > easist way is this (not tested): > > But don't we currently ignore FFH-type C state definitions? Correct. > I am not sure that mwait that we use (its parameters) would be the > same as the system would expect us to use unless we actually parse > FFH data. Even for C1 sate. It is unfortunate but you're correct. We don't have correct support code yet. > Also I am not sure if that would give much gain/difference. Just for the sake of testing your theory, nothing more, nothing less. Jung-uk Kim From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 21:40:59 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id B02BE106564A; Tue, 28 Jun 2011 21:40:54 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Andriy Gapon Date: Tue, 28 Jun 2011 17:40:47 -0400 User-Agent: KMail/1.6.2 References: <201106281514.36324.jkim@FreeBSD.org> <4E0A470F.6090503@FreeBSD.org> In-Reply-To: <4E0A470F.6090503@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106281740.49247.jkim@FreeBSD.org> Cc: freebsd-acpi@freebsd.org, Vitaly Magerya Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 21:40:59 -0000 On Tuesday 28 June 2011 05:26 pm, Andriy Gapon wrote: > on 28/06/2011 22:14 Jung-uk Kim said the following: > > On Tuesday 28 June 2011 07:28 am, Andriy Gapon wrote: > >> I think that part (but not all) of the differences between > >> FreeBSD and Linux can be explained by the fact that FreeBSD > >> currently doesn't advertise itself as featuring > >> ACPI_CAP_SMP_C1_NATIVE and ACPI_CAP_SMP_C3_NATIVE. I am not > >> sure what it would take to actually support these features. I > >> think that Linux does support (or at least advertise support) > >> for these features. > > > > Yes, Linux supports this Intel-specific feature. I think it > > shouldn't be too hard for us, however. We just have to add > > support for Intel-specific _CST FFH (Functional Fixed Hardware) > > in > > sys/dev/acpica/acpi_cpu.c. You can find more information from > > "Intel Processor Vendor-Specific ACPI" (order number 302223-005) > > on Intel website. Also, arch/x86/kernel/acpi/cstate.c of Linux > > source may help. I believe Linux actually supports all > > Intel-specific FFHs, BTW. > > Once upon a time there was a patch proposed for FreeBSD: > http://thread.gmane.org/gmane.os.freebsd.current/127860/focus=6372 > Unfortunately I have never really evaluated it. Hmm, interesting patch. I think he is in the right direction. Thanks for sharing, Jung-uk Kim From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 28 22:20:08 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 191C9106566B for ; Tue, 28 Jun 2011 22:20:08 +0000 (UTC) (envelope-from edv@agile.bc.ca) Received: from defout.telus.net (outbound04.telus.net [199.185.220.223]) by mx1.freebsd.org (Postfix) with ESMTP id 74EE68FC08 for ; Tue, 28 Jun 2011 22:20:07 +0000 (UTC) Received: from edmwcm02 ([204.209.205.13]) by priv-edmwes23.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20110628220743.HDW2283.priv-edmwes23.telusplanet.net@edmwcm02> for ; Tue, 28 Jun 2011 16:07:43 -0600 Received: from [192.168.0.253] ([75.155.136.54]) by edmwcm02 with bizsmtp id 1a7i1h0171Abl5F01a7iEq; Tue, 28 Jun 2011 16:07:43 -0600 X-Authority-Analysis: v=1.1 cv=5i6vPWBL4re/i438pBOyuTEsJek3JZfexb/71e7L7Zo= c=1 sm=2 a=00GrbmtOa5AA:10 a=bYfgUtIk2pwA:10 a=8nJEP1OIZ-IA:10 a=HUAmJIpXAAAA:8 a=wM33tHU_zF1LJWFup8AA:9 a=XQ9Yrmqor3KWeYdLP1kA:7 a=wPNLvfGTeEIA:10 X-Telus-Outbound-IP: 75.155.136.54 Message-ID: <4E0A50AA.5000003@agile.bc.ca> Date: Tue, 28 Jun 2011 15:07:38 -0700 From: Ed VanderPloeg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-acpi@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 28 Jun 2011 22:36:12 +0000 Cc: Subject: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 22:20:08 -0000 I'm using an Aaeon AEC-6831 embedded system based on an Intel Atom N270, which uses their GENE-9455 motherboard. After updating the BIOS to enable ACPI, I'm now getting the following (verbose) console message during boot and every 10 seconds thereafter: ACPI Error: [RTMP] Namespace lookup failure, AE_NOT_FOUND (20101013/psargs-464) ACPI Error: Method parse/execution failed [\_TZ_.THRM._TMP] (Node 0xc56b0760), AE_NOT_FOUND (20101013/psparse-633) acpi_tz0: error fetching current temperature -- AE_NOT_FOUND The unit seems to run very warm which makes me wonder if this problem is preventing lower power states, if such things are related. I've collected the outputs from a verbose dmesg, from sysctl hw.acpi, and from acpidump. They are zipped up over here: http://www.agilecontrols.com/post/aec6831_acpi.zip I've also included datasheets of the system and motherboard in case they are useful. I ran the asl file through iasl and noticed 3 errors and 1 warning seemingly unrelated to this problem. I fixed these problems good enough to get rid of the compiler messages and loaded the aml file for the next boot, but the behaviour didn't change. The system is on my bench for development right now, so I'm able to poke around and try things. For now I've simply reduced the ACPI messages to weekly with # sysctl hw.acpi.thermal.polling_rate = 604800 By the way, what happens with a polling_rate of 0? I tried this and the messages stopped, then changed it back to 10 seconds but the messages never came back again... Ed VanderPloeg From owner-freebsd-acpi@FreeBSD.ORG Wed Jun 29 09:38:10 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DF991065672 for ; Wed, 29 Jun 2011 09:38:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 684908FC0C for ; Wed, 29 Jun 2011 09:38:09 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA23442; Wed, 29 Jun 2011 12:38:05 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QbrDg-0008o3-P4; Wed, 29 Jun 2011 12:38:04 +0300 Message-ID: <4E0AF27B.3030600@FreeBSD.org> Date: Wed, 29 Jun 2011 12:38:03 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Ed VanderPloeg References: <4E0A50AA.5000003@agile.bc.ca> In-Reply-To: <4E0A50AA.5000003@agile.bc.ca> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2011 09:38:10 -0000 on 29/06/2011 01:07 Ed VanderPloeg said the following: > I'm using an Aaeon AEC-6831 embedded system based on an Intel Atom N270, which > uses their GENE-9455 motherboard. After updating the BIOS to enable ACPI, I'm > now getting the following (verbose) console message during boot and every 10 > seconds thereafter: > > ACPI Error: [RTMP] Namespace lookup failure, AE_NOT_FOUND (20101013/psargs-464) > ACPI Error: Method parse/execution failed [\_TZ_.THRM._TMP] (Node 0xc56b0760), > AE_NOT_FOUND (20101013/psparse-633) > acpi_tz0: error fetching current temperature -- AE_NOT_FOUND The problem is that RTMP is defined as an external object: External (RTMP, IntObj) so it's supposed to come from an additional table, but apparently either no additional table defines it or a necessary additional table is not loaded. This could be either a BIOS problem or... something else :) > The unit seems to run very warm which makes me wonder if this problem is > preventing lower power states, if such things are related. > > I've collected the outputs from a verbose dmesg, from sysctl hw.acpi, and from > acpidump. They are zipped up over here: > > http://www.agilecontrols.com/post/aec6831_acpi.zip Try either recent stable/8 or head (aka CURRENT) and see if it helps. They contain a change that may be a work-around for a BIOS (ACPI tables) like yours. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Wed Jun 29 18:01:38 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D06E106564A for ; Wed, 29 Jun 2011 18:01:38 +0000 (UTC) (envelope-from edv@agile.bc.ca) Received: from defout.telus.net (defout.telus.net [204.209.205.13]) by mx1.freebsd.org (Postfix) with ESMTP id B17E88FC15 for ; Wed, 29 Jun 2011 18:01:37 +0000 (UTC) Received: from edmwcm03 ([204.209.205.13]) by priv-edmwes48.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20110629180131.XLRJ9861.priv-edmwes48.telusplanet.net@edmwcm03> for ; Wed, 29 Jun 2011 12:01:31 -0600 Received: from [192.168.0.253] ([75.155.136.54]) by edmwcm03 with bizsmtp id 1u1W1h01d1Abl5F01u1WCq; Wed, 29 Jun 2011 12:01:31 -0600 X-Telus-Outbound-IP: 75.155.136.54 X-Authority-Analysis: v=1.1 cv=EF5+/2dZ0nDTVLCimDbxnkvLLSCcTT2SaZuFCfhwddE= c=1 sm=2 a=00GrbmtOa5AA:10 a=lp1F1aYoXqwA:10 a=8nJEP1OIZ-IA:10 a=HUAmJIpXAAAA:8 a=f2IHuidIA1t9rUqa8UMA:9 a=2WCOiVeKON6kwBDbJoIA:7 a=wPNLvfGTeEIA:10 Message-ID: <4E0B6873.6010901@agile.bc.ca> Date: Wed, 29 Jun 2011 11:01:23 -0700 From: Ed VanderPloeg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-acpi@FreeBSD.org References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> In-Reply-To: <4E0AF27B.3030600@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2011 18:01:38 -0000 On 2011-06-29 2:38 AM, Andriy Gapon wrote: > on 29/06/2011 01:07 Ed VanderPloeg said the following: >> I'm using an Aaeon AEC-6831 embedded system based on an Intel Atom N270, which >> uses their GENE-9455 motherboard. After updating the BIOS to enable ACPI, I'm >> now getting the following (verbose) console message during boot and every 10 >> seconds thereafter: >> >> ACPI Error: [RTMP] Namespace lookup failure, AE_NOT_FOUND (20101013/psargs-464) >> ACPI Error: Method parse/execution failed [\_TZ_.THRM._TMP] (Node 0xc56b0760), >> AE_NOT_FOUND (20101013/psparse-633) >> acpi_tz0: error fetching current temperature -- AE_NOT_FOUND > > The problem is that RTMP is defined as an external object: > External (RTMP, IntObj) > so it's supposed to come from an additional table, but apparently either no > additional table defines it or a necessary additional table is not loaded. > This could be either a BIOS problem or... something else :) Aaeon tech support has now stated that the errors are from a faulty BIOS, and that AWARD will eventually release an update to fix this. >> The unit seems to run very warm which makes me wonder if this problem is >> preventing lower power states, if such things are related. >> >> I've collected the outputs from a verbose dmesg, from sysctl hw.acpi, and from >> acpidump. They are zipped up over here: >> >> http://www.agilecontrols.com/post/aec6831_acpi.zip > > Try either recent stable/8 or head (aka CURRENT) and see if it helps. They > contain a change that may be a work-around for a BIOS (ACPI tables) like yours. I'll give stable/8 a try. Does this error indicate something potentially harmful, or if it is benign? I can silence the messages easy enough until a BIOS update comes out. Ed From owner-freebsd-acpi@FreeBSD.ORG Wed Jun 29 19:45:07 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9045D106566B for ; Wed, 29 Jun 2011 19:45:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id DE9218FC15 for ; Wed, 29 Jun 2011 19:45:06 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id WAA03024; Wed, 29 Jun 2011 22:45:03 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Qc0h5-0009IE-Bi; Wed, 29 Jun 2011 22:45:03 +0300 Message-ID: <4E0B80BE.6080605@FreeBSD.org> Date: Wed, 29 Jun 2011 22:45:02 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.18) Gecko/20110626 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Ed VanderPloeg References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> <4E0B6873.6010901@agile.bc.ca> In-Reply-To: <4E0B6873.6010901@agile.bc.ca> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2011 19:45:07 -0000 on 29/06/2011 21:01 Ed VanderPloeg said the following: > On 2011-06-29 2:38 AM, Andriy Gapon wrote: >> on 29/06/2011 01:07 Ed VanderPloeg said the following: >>> I'm using an Aaeon AEC-6831 embedded system based on an Intel Atom N270, which >>> uses their GENE-9455 motherboard. After updating the BIOS to enable ACPI, I'm >>> now getting the following (verbose) console message during boot and every 10 >>> seconds thereafter: >>> >>> ACPI Error: [RTMP] Namespace lookup failure, AE_NOT_FOUND (20101013/psargs-464) >>> ACPI Error: Method parse/execution failed [\_TZ_.THRM._TMP] (Node 0xc56b0760), >>> AE_NOT_FOUND (20101013/psparse-633) >>> acpi_tz0: error fetching current temperature -- AE_NOT_FOUND >> >> The problem is that RTMP is defined as an external object: >> External (RTMP, IntObj) >> so it's supposed to come from an additional table, but apparently either no >> additional table defines it or a necessary additional table is not loaded. >> This could be either a BIOS problem or... something else :) > > Aaeon tech support has now stated that the errors are from a faulty BIOS, and > that AWARD will eventually release an update to fix this. OK. >>> The unit seems to run very warm which makes me wonder if this problem is >>> preventing lower power states, if such things are related. >>> >>> I've collected the outputs from a verbose dmesg, from sysctl hw.acpi, and from >>> acpidump. They are zipped up over here: >>> >>> http://www.agilecontrols.com/post/aec6831_acpi.zip >> >> Try either recent stable/8 or head (aka CURRENT) and see if it helps. They >> contain a change that may be a work-around for a BIOS (ACPI tables) like yours. > > I'll give stable/8 a try. > > Does this error indicate something potentially harmful, or if it is benign? I > can silence the messages easy enough until a BIOS update comes out. Actually I was speaking about potentially making est driver attach on your system. I also suspected that RTMP might have gotten loaded from the same dynamic table that is related to est attachment issue, but apparently that was not going to happen. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 30 16:33:07 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DED6B1065675 for ; Thu, 30 Jun 2011 16:33:06 +0000 (UTC) (envelope-from edv@agile.bc.ca) Received: from defout.telus.net (defout.telus.net [204.209.205.13]) by mx1.freebsd.org (Postfix) with ESMTP id 640658FC1C for ; Thu, 30 Jun 2011 16:33:05 +0000 (UTC) Received: from edmwcm04 ([204.209.205.13]) by priv-edmwes04.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20110630163259.BAYT24872.priv-edmwes04.telusplanet.net@edmwcm04> for ; Thu, 30 Jun 2011 10:32:59 -0600 Received: from [192.168.0.253] ([75.155.136.54]) by edmwcm04 with bizsmtp id 2GYz1h00z1Abl5F01GYz7l; Thu, 30 Jun 2011 10:32:59 -0600 X-Telus-Outbound-IP: 75.155.136.54 X-Authority-Analysis: v=1.1 cv=QUfQBVzlX4/ya68PAJjJGj5hWUIyJvqu6OBFlX9+M7Y= c=1 sm=2 a=00GrbmtOa5AA:10 a=lp1F1aYoXqwA:10 a=8nJEP1OIZ-IA:10 a=HUAmJIpXAAAA:8 a=wVjY19UYuB-NpeheeoMA:9 a=wNmF7C-BXVrkVKAMYlUA:7 a=wPNLvfGTeEIA:10 Message-ID: <4E0CA533.5030104@agile.bc.ca> Date: Thu, 30 Jun 2011 09:32:51 -0700 From: Ed VanderPloeg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-acpi@FreeBSD.org References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> <4E0B6873.6010901@agile.bc.ca> <4E0B80BE.6080605@FreeBSD.org> In-Reply-To: <4E0B80BE.6080605@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 16:33:07 -0000 I updated to 8-stable but am still getting ACPI error messages to console every 10 seconds. What happens when sysctl hw.acpi.thermal.polling_rate=0? Does this disable polling? I noticed that when I set it to zero, the error messages seem to stop, but then setting it to a non-zero value never brings the messages back again. Ed On 2011-06-29 12:45 PM, Andriy Gapon wrote: > on 29/06/2011 21:01 Ed VanderPloeg said the following: >> On 2011-06-29 2:38 AM, Andriy Gapon wrote: >>> on 29/06/2011 01:07 Ed VanderPloeg said the following: >>>> I'm using an Aaeon AEC-6831 embedded system based on an Intel Atom N270, which >>>> uses their GENE-9455 motherboard. After updating the BIOS to enable ACPI, I'm >>>> now getting the following (verbose) console message during boot and every 10 >>>> seconds thereafter: >>>> >>>> ACPI Error: [RTMP] Namespace lookup failure, AE_NOT_FOUND (20101013/psargs-464) >>>> ACPI Error: Method parse/execution failed [\_TZ_.THRM._TMP] (Node 0xc56b0760), >>>> AE_NOT_FOUND (20101013/psparse-633) >>>> acpi_tz0: error fetching current temperature -- AE_NOT_FOUND >>> >>> The problem is that RTMP is defined as an external object: >>> External (RTMP, IntObj) >>> so it's supposed to come from an additional table, but apparently either no >>> additional table defines it or a necessary additional table is not loaded. >>> This could be either a BIOS problem or... something else :) >> >> Aaeon tech support has now stated that the errors are from a faulty BIOS, and >> that AWARD will eventually release an update to fix this. > > OK. > >>>> The unit seems to run very warm which makes me wonder if this problem is >>>> preventing lower power states, if such things are related. >>>> >>>> I've collected the outputs from a verbose dmesg, from sysctl hw.acpi, and from >>>> acpidump. They are zipped up over here: >>>> >>>> http://www.agilecontrols.com/post/aec6831_acpi.zip >>> >>> Try either recent stable/8 or head (aka CURRENT) and see if it helps. They >>> contain a change that may be a work-around for a BIOS (ACPI tables) like yours. >> >> I'll give stable/8 a try. >> >> Does this error indicate something potentially harmful, or if it is benign? I >> can silence the messages easy enough until a BIOS update comes out. > > > Actually I was speaking about potentially making est driver attach on your > system. I also suspected that RTMP might have gotten loaded from the same > dynamic table that is related to est attachment issue, but apparently that was > not going to happen. > From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 30 19:49:13 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BC9D106566C; Thu, 30 Jun 2011 19:49:13 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id E448A8FC18; Thu, 30 Jun 2011 19:49:12 +0000 (UTC) Received: by vxg33 with SMTP id 33so2636041vxg.13 for ; Thu, 30 Jun 2011 12:49:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MyG+zaPABZ8qZH4rH3H78oo0ALpAX51qGD2P9R7gNnA=; b=vdUEneBpjUIJoTPaaa/vAD2lQSup52HzOzG/HpzS+P0Hbg+FabooS6NwpePX8Dr5iQ b0HTXhAJ7mr97cMDGhA6Des1WenHsrtS4/cr2urF0NsAXL8I+ph7+TkUgw/0aLD5py1F as9t9k12jl+ozqc5Elw2aC16EskYlytYFr5co= MIME-Version: 1.0 Received: by 10.52.73.196 with SMTP id n4mr3604302vdv.39.1309463351920; Thu, 30 Jun 2011 12:49:11 -0700 (PDT) Received: by 10.52.108.226 with HTTP; Thu, 30 Jun 2011 12:49:11 -0700 (PDT) In-Reply-To: <4E0A41C8.3000904@FreeBSD.org> References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> <4E09BADF.7050702@FreeBSD.org> <4E0A41C8.3000904@FreeBSD.org> Date: Thu, 30 Jun 2011 22:49:11 +0300 Message-ID: From: Vitaly Magerya To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-acpi@freebsd.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 19:49:13 -0000 Andriy Gapon wrote: > on 28/06/2011 22:37 Vitaly Magerya said the following: >> Is there some simple way of sending fake advertisement? Or will >> that lead to disaster? > > It doesn't make sense without actual support. > And maybe (just maybe) it won't change much anyway. I see. Should I hold my breath for this code? > Since we are now dealing with black box/magic behind ACPI, may I try to suggest > doing some DSDT hacks and seeing what changes? One thing to try would be > replacing "\_SB.VDRV" with "VDRV" in _Q51 and _Q52 methods. > That at least should rid you of those annoying ACPI errors, at best it could > improve something. At the very worst it may fry your machine, though... Just tried this. Nothing seems fried; the visible effect is that now when I plug the power cord in backlight brightness turns all the way up, and then back down the I turn it off. No changes in SNVS or GNVS variables aside from the usual ones. From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 30 20:49:34 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D529106564A for ; Thu, 30 Jun 2011 20:49:34 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B471D8FC13 for ; Thu, 30 Jun 2011 20:49:33 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA24470; Thu, 30 Jun 2011 23:49:30 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QcOB0-000CQE-9b; Thu, 30 Jun 2011 23:49:30 +0300 Message-ID: <4E0CE158.6030804@FreeBSD.org> Date: Thu, 30 Jun 2011 23:49:28 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.18) Gecko/20110626 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Vitaly Magerya References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> <4E09BADF.7050702@FreeBSD.org> <4E0A41C8.3000904@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 20:49:34 -0000 on 30/06/2011 22:49 Vitaly Magerya said the following: > Andriy Gapon wrote: >> on 28/06/2011 22:37 Vitaly Magerya said the following: >>> Is there some simple way of sending fake advertisement? Or will >>> that lead to disaster? >> >> It doesn't make sense without actual support. >> And maybe (just maybe) it won't change much anyway. > > I see. Should I hold my breath for this code? Probably no. Here's what Intel docs say: The processor implements two software interfaces for requesting low power states, MWAIT instruction extensions with sub-state hints and P_LVLx reads to the ACPI P_BLK register block mapped in the processor’s I/O address space. The P_LVLx I/O reads are converted to equivalent MWAIT C-state requests inside the processor and do not directly result in I/O reads on the processor FSB. My interpretation is that both mechanism should work equally. >> Since we are now dealing with black box/magic behind ACPI, may I try to suggest >> doing some DSDT hacks and seeing what changes? One thing to try would be >> replacing "\_SB.VDRV" with "VDRV" in _Q51 and _Q52 methods. >> That at least should rid you of those annoying ACPI errors, at best it could >> improve something. At the very worst it may fry your machine, though... > > Just tried this. Nothing seems fried; the visible effect is that > now when I plug the power cord in backlight brightness turns all > the way up, and then back down the I turn it off. No changes in > SNVS or GNVS variables aside from the usual ones. At least some improvement (or just a difference)... Not sure how to proceed here further. Apparently we do something differently from Linux (and presumably Windows) here, but it's quite hard to tell what. The problem is that SNVS/GNVS (in particular C1ON) seem to be controlled by some firmware/hardware and that's a black box. And I am still puzzled about which exactly event triggers change in C1ON value on FreeBSD... Do you have powerd enabled? Can you check if anything changes with it disabled (just for the sake of testing). P.S. Just an idea, maybe the following script could be of some help if you have dtrace support in your kernel: $ dtrace -n 'fbt::AcpiEvaluateObject:entry { printf("%p->%s\n", args[0], (string)args[1]); }' I would like to get entries, if any, around the time that the C-states become available. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 30 20:55:32 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id BA05C10656D5; Thu, 30 Jun 2011 20:55:31 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org Date: Thu, 30 Jun 2011 16:55:14 -0400 User-Agent: KMail/1.6.2 References: <4E0A41C8.3000904@FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106301655.19258.jkim@FreeBSD.org> Cc: Vitaly Magerya , Andriy Gapon Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 20:55:32 -0000 On Thursday 30 June 2011 03:49 pm, Vitaly Magerya wrote: > Andriy Gapon wrote: > > on 28/06/2011 22:37 Vitaly Magerya said the following: > >> Is there some simple way of sending fake advertisement? Or will > >> that lead to disaster? > > > > It doesn't make sense without actual support. > > And maybe (just maybe) it won't change much anyway. > > I see. Should I hold my breath for this code? :-) I have written a very rough patch and it is available from here: http://people.freebsd.org/~jkim/acpi_cst.diff It compiles but wasn't tested at all, i.e., I have no hardware. Please be careful. Jung-uk Kim From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 30 20:59:14 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3E391065675 for ; Thu, 30 Jun 2011 20:59:14 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 117348FC1B for ; Thu, 30 Jun 2011 20:59:13 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA24589; Thu, 30 Jun 2011 23:59:09 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QcOKK-000CQf-PZ; Thu, 30 Jun 2011 23:59:08 +0300 Message-ID: <4E0CE39C.5050307@FreeBSD.org> Date: Thu, 30 Jun 2011 23:59:08 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.18) Gecko/20110626 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Ed VanderPloeg References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> <4E0B6873.6010901@agile.bc.ca> <4E0B80BE.6080605@FreeBSD.org> <4E0CA533.5030104@agile.bc.ca> In-Reply-To: <4E0CA533.5030104@agile.bc.ca> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 20:59:15 -0000 on 30/06/2011 19:32 Ed VanderPloeg said the following: > I updated to 8-stable but am still getting ACPI error messages to console every > 10 seconds. Just for my curiosity - has anything changed with respect to est driver attachment? > What happens when sysctl hw.acpi.thermal.polling_rate=0? Does this disable > polling? I noticed that when I set it to zero, the error messages seem to stop, > but then setting it to a non-zero value never brings the messages back again. I've just the code in acpi_thermal driver and it doesn't have any validation for polling_rate and thus no special treatment for the value of zero. So, it passes timeout of zero to msleep() function, which does have a special meaning for zero - it means sleep forever until wakeup event. Essentially when you did sysctl hw.acpi.thermal.polling_rate=0, you made the thermal zone handling thread to sleep "forever". This can be considered a bug in FreeBSD ACPI TZ driver. The only thing that seems to be able to wake up the thread after that is a change of power profile. So switching from AC to batter or vice versa could wake up the thread and make it use a new value of polling_rate. > On 2011-06-29 12:45 PM, Andriy Gapon wrote: >> on 29/06/2011 21:01 Ed VanderPloeg said the following: >>> On 2011-06-29 2:38 AM, Andriy Gapon wrote: >>>> on 29/06/2011 01:07 Ed VanderPloeg said the following: >>>>> I'm using an Aaeon AEC-6831 embedded system based on an Intel Atom N270, which >>>>> uses their GENE-9455 motherboard. After updating the BIOS to enable ACPI, I'm >>>>> now getting the following (verbose) console message during boot and every 10 >>>>> seconds thereafter: >>>>> >>>>> ACPI Error: [RTMP] Namespace lookup failure, AE_NOT_FOUND >>>>> (20101013/psargs-464) >>>>> ACPI Error: Method parse/execution failed [\_TZ_.THRM._TMP] (Node 0xc56b0760), >>>>> AE_NOT_FOUND (20101013/psparse-633) >>>>> acpi_tz0: error fetching current temperature -- AE_NOT_FOUND >>>> >>>> The problem is that RTMP is defined as an external object: >>>> External (RTMP, IntObj) >>>> so it's supposed to come from an additional table, but apparently either no >>>> additional table defines it or a necessary additional table is not loaded. >>>> This could be either a BIOS problem or... something else :) >>> >>> Aaeon tech support has now stated that the errors are from a faulty BIOS, and >>> that AWARD will eventually release an update to fix this. >> >> OK. >> >>>>> The unit seems to run very warm which makes me wonder if this problem is >>>>> preventing lower power states, if such things are related. >>>>> >>>>> I've collected the outputs from a verbose dmesg, from sysctl hw.acpi, and from >>>>> acpidump. They are zipped up over here: >>>>> >>>>> http://www.agilecontrols.com/post/aec6831_acpi.zip >>>> >>>> Try either recent stable/8 or head (aka CURRENT) and see if it helps. They >>>> contain a change that may be a work-around for a BIOS (ACPI tables) like yours. >>> >>> I'll give stable/8 a try. >>> >>> Does this error indicate something potentially harmful, or if it is benign? I >>> can silence the messages easy enough until a BIOS update comes out. >> >> >> Actually I was speaking about potentially making est driver attach on your >> system. I also suspected that RTMP might have gotten loaded from the same >> dynamic table that is related to est attachment issue, but apparently that was >> not going to happen. >> -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 30 22:52:38 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BD3D106566B; Thu, 30 Jun 2011 22:52:38 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id BB1698FC12; Thu, 30 Jun 2011 22:52:35 +0000 (UTC) Received: by vws18 with SMTP id 18so2764576vws.13 for ; Thu, 30 Jun 2011 15:52:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4ZJqLRb3N0ehF0ZgxJ3aK0gKTw+ZT9oerfHVuM9qoM8=; b=M6VlVSg70F5uZnstfSCmlwsleXZsHLfH80fw4Nrr+RCSdCpKwU1a4UOwQdD3yH5bTu zs2zQqxdhhf3hlDI7Ogu4GUkFRxA9DbttZtxm7yPzui9EkUxGfgLuTdtqkaep1yM27TA VT8OnuOMsKwBFMBJTDQqSWGhgX5qnLte1dyDo= MIME-Version: 1.0 Received: by 10.52.66.199 with SMTP id h7mr3607765vdt.119.1309474354284; Thu, 30 Jun 2011 15:52:34 -0700 (PDT) Received: by 10.52.108.226 with HTTP; Thu, 30 Jun 2011 15:52:34 -0700 (PDT) In-Reply-To: <4E0CE158.6030804@FreeBSD.org> References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> <4E09BADF.7050702@FreeBSD.org> <4E0A41C8.3000904@FreeBSD.org> <4E0CE158.6030804@FreeBSD.org> Date: Fri, 1 Jul 2011 01:52:34 +0300 Message-ID: From: Vitaly Magerya To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-acpi@freebsd.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 22:52:38 -0000 Andriy Gapon wrote: > Here's what Intel docs say: > > The processor implements two software interfaces for requesting low power > states, MWAIT instruction extensions with sub-state hints and P_LVLx reads to > the ACPI P_BLK register block mapped in the processor's I/O address space. The > P_LVLx I/O reads are converted to equivalent MWAIT C-state requests inside the > processor and do not directly result in I/O reads on the processor FSB. > > My interpretation is that both mechanism should work equally. I see. >> Just tried this. Nothing seems fried; the visible effect is that >> now when I plug the power cord in backlight brightness turns all >> the way up, and then back down the I turn it off. No changes in >> SNVS or GNVS variables aside from the usual ones. > > At least some improvement (or just a difference)... Since VDRV is always 0, you can't really say if it's a coincidence or the intended behavior. > Not sure how to proceed here further. Apparently we do something differently > from Linux (and presumably Windows) here, but it's quite hard to tell what. The > problem is that SNVS/GNVS (in particular C1ON) seem to be controlled by some > firmware/hardware and that's a black box. > And I am still puzzled about which exactly event triggers change in C1ON value > on FreeBSD... I got the dumps for Linux (it appears that you can't just read /dev/mem on there, you need to mmap it). The summary of differences between FreeBSD and Linux right after the boot: DB00: 01 -> 00 P80D: 06:08:00:00 -> 06:08:4C:00 PCP0: 1D -> BF PCP1: 1D -> BF BRTL: 00 -> 1E VDRV: 00 -> 01 (Note that C1ON is 0 just as with FreeBSD, and yet powertop does report C2 and C4). Then, after about 4 minutes of uptime, C1ON changes to 1 (and powertop still reports the same states). > Do you have powerd enabled? Can you check if anything changes > with it disabled (just for the sake of testing). I do; nothing changes if I don't. > P.S. Just an idea, maybe the following script could be of some help if you > have dtrace support in your kernel: > $ dtrace -n 'fbt::AcpiEvaluateObject:entry { printf("%p->%s\n", args[0], > (string)args[1]); }' > I would like to get entries, if any, around the time that the C-states > become available. I'll try to compile the kernel with dtrace and post the results back. From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 30 22:52:44 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7CE610656A8; Thu, 30 Jun 2011 22:52:44 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 662A28FC08; Thu, 30 Jun 2011 22:52:44 +0000 (UTC) Received: by mail-vw0-f54.google.com with SMTP id 18so2764576vws.13 for ; Thu, 30 Jun 2011 15:52:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AKy0UnxWeYJkpdhqZR8ipw8gKUjzWuJSg28c39C7Eq8=; b=fAIgE18Vb2083K9pPWf1Ouv1Q7vbBMRnJ/ZaPnYsqBAVfhl3ZHc42vc2j2WXDX8DVj xvwmSj518F6FHglmBtzbccOMusuXnMjbvCRhir+zCFMlaOdXwE2sSaVzisU5JuhWD9DF hnpyPs4HrmV874gRQ0k5ST2AYRo4SKqKpqH/w= MIME-Version: 1.0 Received: by 10.52.110.133 with SMTP id ia5mr3576959vdb.239.1309474362344; Thu, 30 Jun 2011 15:52:42 -0700 (PDT) Received: by 10.52.108.226 with HTTP; Thu, 30 Jun 2011 15:52:42 -0700 (PDT) In-Reply-To: <201106301655.19258.jkim@FreeBSD.org> References: <4E0A41C8.3000904@FreeBSD.org> <201106301655.19258.jkim@FreeBSD.org> Date: Fri, 1 Jul 2011 01:52:42 +0300 Message-ID: From: Vitaly Magerya To: Jung-uk Kim Content-Type: text/plain; charset=UTF-8 Cc: freebsd-acpi@freebsd.org, Andriy Gapon Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 22:52:44 -0000 Jung-uk Kim wrote: > I have written a very rough patch and it is available from here: > > http://people.freebsd.org/~jkim/acpi_cst.diff > > It compiles but wasn't tested at all, i.e., I have no hardware. > Please be careful. Cool. I'll try it. From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 1 04:16:36 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DABA8106566C for ; Fri, 1 Jul 2011 04:16:36 +0000 (UTC) (envelope-from edv@agile.bc.ca) Received: from defout.telus.net (defout.telus.net [204.209.205.13]) by mx1.freebsd.org (Postfix) with ESMTP id 780278FC0C for ; Fri, 1 Jul 2011 04:16:36 +0000 (UTC) Received: from edmwcm03 ([204.209.205.13]) by priv-edmwes34.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20110701041630.KASZ19410.priv-edmwes34.telusplanet.net@edmwcm03> for ; Thu, 30 Jun 2011 22:16:30 -0600 Received: from [192.168.0.253] ([75.155.136.54]) by edmwcm03 with bizsmtp id 2UGV1h01g1Abl5F01UGVVk; Thu, 30 Jun 2011 22:16:30 -0600 X-Telus-Outbound-IP: 75.155.136.54 X-Authority-Analysis: v=1.1 cv=cIiwr5sCMxG0B044PlTrl4zX/zgGkweVSaZCBOM7nCw= c=1 sm=2 a=00GrbmtOa5AA:10 a=lp1F1aYoXqwA:10 a=8nJEP1OIZ-IA:10 a=HUAmJIpXAAAA:8 a=VtG63zPMF9qiiiJZtlgA:9 a=WVFSnRx-lnb832Uo3eUA:7 a=wPNLvfGTeEIA:10 Message-ID: <4E0D4A15.6000904@agile.bc.ca> Date: Thu, 30 Jun 2011 21:16:21 -0700 From: Ed VanderPloeg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Andriy Gapon References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> <4E0B6873.6010901@agile.bc.ca> <4E0B80BE.6080605@FreeBSD.org> <4E0CA533.5030104@agile.bc.ca> <4E0CE39C.5050307@FreeBSD.org> In-Reply-To: <4E0CE39C.5050307@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 04:16:37 -0000 On 2011-06-30 1:59 PM, Andriy Gapon wrote: > on 30/06/2011 19:32 Ed VanderPloeg said the following: >> I updated to 8-stable but am still getting ACPI error messages to console every >> 10 seconds. > > Just for my curiosity - has anything changed with respect to est driver attachment? I'm not sure what you mean by "attachment". With 8-stable now installed: stanbud# kldstat -v | grep est 445 cpu/est Is there anything you would like me to check? >> What happens when sysctl hw.acpi.thermal.polling_rate=0? Does this disable >> polling? I noticed that when I set it to zero, the error messages seem to stop, >> but then setting it to a non-zero value never brings the messages back again. > > I've just the code in acpi_thermal driver and it doesn't have any validation for > polling_rate and thus no special treatment for the value of zero. So, it passes > timeout of zero to msleep() function, which does have a special meaning for zero > - it means sleep forever until wakeup event. Essentially when you did sysctl > hw.acpi.thermal.polling_rate=0, you made the thermal zone handling thread to > sleep "forever". This can be considered a bug in FreeBSD ACPI TZ driver. The > only thing that seems to be able to wake up the thread after that is a change of > power profile. So switching from AC to batter or vice versa could wake up the > thread and make it use a new value of polling_rate. > >> On 2011-06-29 12:45 PM, Andriy Gapon wrote: >>> on 29/06/2011 21:01 Ed VanderPloeg said the following: >>>> On 2011-06-29 2:38 AM, Andriy Gapon wrote: >>>>> on 29/06/2011 01:07 Ed VanderPloeg said the following: >>>>>> I'm using an Aaeon AEC-6831 embedded system based on an Intel Atom N270, which >>>>>> uses their GENE-9455 motherboard. After updating the BIOS to enable ACPI, I'm >>>>>> now getting the following (verbose) console message during boot and every 10 >>>>>> seconds thereafter: >>>>>> >>>>>> ACPI Error: [RTMP] Namespace lookup failure, AE_NOT_FOUND >>>>>> (20101013/psargs-464) >>>>>> ACPI Error: Method parse/execution failed [\_TZ_.THRM._TMP] (Node 0xc56b0760), >>>>>> AE_NOT_FOUND (20101013/psparse-633) >>>>>> acpi_tz0: error fetching current temperature -- AE_NOT_FOUND >>>>> >>>>> The problem is that RTMP is defined as an external object: >>>>> External (RTMP, IntObj) >>>>> so it's supposed to come from an additional table, but apparently either no >>>>> additional table defines it or a necessary additional table is not loaded. >>>>> This could be either a BIOS problem or... something else :) >>>> >>>> Aaeon tech support has now stated that the errors are from a faulty BIOS, and >>>> that AWARD will eventually release an update to fix this. >>> >>> OK. >>> >>>>>> The unit seems to run very warm which makes me wonder if this problem is >>>>>> preventing lower power states, if such things are related. >>>>>> >>>>>> I've collected the outputs from a verbose dmesg, from sysctl hw.acpi, and from >>>>>> acpidump. They are zipped up over here: >>>>>> >>>>>> http://www.agilecontrols.com/post/aec6831_acpi.zip >>>>> >>>>> Try either recent stable/8 or head (aka CURRENT) and see if it helps. They >>>>> contain a change that may be a work-around for a BIOS (ACPI tables) like yours. >>>> >>>> I'll give stable/8 a try. >>>> >>>> Does this error indicate something potentially harmful, or if it is benign? I >>>> can silence the messages easy enough until a BIOS update comes out. >>> >>> >>> Actually I was speaking about potentially making est driver attach on your >>> system. I also suspected that RTMP might have gotten loaded from the same >>> dynamic table that is related to est attachment issue, but apparently that was >>> not going to happen. >>> > > From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 1 05:44:07 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A813106566C for ; Fri, 1 Jul 2011 05:44:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B84B88FC18 for ; Fri, 1 Jul 2011 05:44:06 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id IAA29954; Fri, 01 Jul 2011 08:44:02 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QcWWI-000F2v-Km; Fri, 01 Jul 2011 08:44:02 +0300 Message-ID: <4E0D5EA0.1020704@FreeBSD.org> Date: Fri, 01 Jul 2011 08:44:00 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.18) Gecko/20110626 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Ed VanderPloeg References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> <4E0B6873.6010901@agile.bc.ca> <4E0B80BE.6080605@FreeBSD.org> <4E0CA533.5030104@agile.bc.ca> <4E0CE39C.5050307@FreeBSD.org> <4E0D4A15.6000904@agile.bc.ca> In-Reply-To: <4E0D4A15.6000904@agile.bc.ca> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 05:44:07 -0000 on 01/07/2011 07:16 Ed VanderPloeg said the following: > On 2011-06-30 1:59 PM, Andriy Gapon wrote: >> on 30/06/2011 19:32 Ed VanderPloeg said the following: >>> I updated to 8-stable but am still getting ACPI error messages to console every >>> 10 seconds. >> >> Just for my curiosity - has anything changed with respect to est driver >> attachment? > > I'm not sure what you mean by "attachment". With 8-stable now installed: > > stanbud# kldstat -v | grep est > 445 cpu/est > > Is there anything you would like me to check? Yes, your dmesg (search for "est"). -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 1 11:55:00 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D60BF106564A for ; Fri, 1 Jul 2011 11:55:00 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 21B4B8FC18 for ; Fri, 1 Jul 2011 11:54:59 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA05326; Fri, 01 Jul 2011 14:54:57 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QccJF-000FJB-46; Fri, 01 Jul 2011 14:54:57 +0300 Message-ID: <4E0DB58F.4070906@FreeBSD.org> Date: Fri, 01 Jul 2011 14:54:55 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.18) Gecko/20110626 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Vitaly Magerya References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> <4E09BADF.7050702@FreeBSD.org> <4E0A41C8.3000904@FreeBSD.org> <4E0CE158.6030804@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 11:55:00 -0000 on 01/07/2011 01:52 Vitaly Magerya said the following: > I got the dumps for Linux (it appears that you can't just read > /dev/mem on there, you need to mmap it). The summary of differences > between FreeBSD and Linux right after the boot: > > DB00: 01 -> 00 > P80D: 06:08:00:00 -> 06:08:4C:00 Not sure what these two are. > PCP0: 1D -> BF > PCP1: 1D -> BF These reflect advertised OS power-management capabilities and appear to be correct. > BRTL: 00 -> 1E This seems to be a variable holding current BRighTness Level. It seems to be ralated to _BCM/_BQC/etc methods used acpi_video driver. > VDRV: 00 -> 01 Looks like this variable should tell if OS has ACPI Video driver, to be precise if _BCL method was invoked at least once. Looks like in your case the driver doesn't attach for some reason?.. Unfortunately, I don't remember if or where you provided your dmesg. > > (Note that C1ON is 0 just as with FreeBSD, and yet powertop does > report C2 and C4). Hmm, this is the strangest thing. According to my analysis of all the ASL code that we extracted if C1ON is zero, then no deep C-states should be reported by _CST method. As such, I wonder where does Linux get C-states information from? Or what else could be going on here. Maybe they somehow query them directly from HW by-passing ACPI in this case... Actually, it seems that they have them simply hardcoded: http://lxr.linux.no/#linux+v2.6.39/drivers/idle/intel_idle.c#L171 I am not sure how to check on Linux which cpuidle driver is being used. If you know, could please check that? And if the driver is intel_idle, then there is no mystery, they use those hardcoded values. > Then, after about 4 minutes of uptime, C1ON changes to 1 (and > powertop still reports the same states). OK, no difference here. So it's probably done by firmware based on some unknown logic. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 1 13:25:16 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CCF81065676 for ; Fri, 1 Jul 2011 13:25:16 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 704FF8FC14 for ; Fri, 1 Jul 2011 13:25:15 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA06765; Fri, 01 Jul 2011 16:25:14 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E0DCAB9.4030904@FreeBSD.org> Date: Fri, 01 Jul 2011 16:25:13 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.18) Gecko/20110622 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-acpi@FreeBSD.org References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> <4E09BADF.7050702@FreeBSD.org> <4E0A41C8.3000904@FreeBSD.org> <4E0CE158.6030804@FreeBSD.org> <4E0DB58F.4070906@FreeBSD.org> In-Reply-To: <4E0DB58F.4070906@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Vitaly Magerya Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 13:25:16 -0000 on 01/07/2011 14:54 Andriy Gapon said the following: > Actually, it seems that they have them simply hardcoded: > http://lxr.linux.no/#linux+v2.6.39/drivers/idle/intel_idle.c#L171 Here is a presentation on intel_idle driver that describes reasons for its existence and some additional information. I am not convinced that we need to follow Linux example. Unless Intel provides and maintains the driver for us like it does for Linux :-) -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 1 13:31:12 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91F5B106564A for ; Fri, 1 Jul 2011 13:31:12 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D7D668FC0A for ; Fri, 1 Jul 2011 13:31:11 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA06870; Fri, 01 Jul 2011 16:31:10 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E0DCC1D.4020101@FreeBSD.org> Date: Fri, 01 Jul 2011 16:31:09 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.18) Gecko/20110622 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-acpi@FreeBSD.org References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> <4E09BADF.7050702@FreeBSD.org> <4E0A41C8.3000904@FreeBSD.org> <4E0CE158.6030804@FreeBSD.org> <4E0DB58F.4070906@FreeBSD.org> <4E0DCAB9.4030904@FreeBSD.org> In-Reply-To: <4E0DCAB9.4030904@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Vitaly Magerya Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 13:31:12 -0000 on 01/07/2011 16:25 Andriy Gapon said the following: > on 01/07/2011 14:54 Andriy Gapon said the following: >> Actually, it seems that they have them simply hardcoded: >> http://lxr.linux.no/#linux+v2.6.39/drivers/idle/intel_idle.c#L171 > > Here Yep, here :-) http://events.linuxfoundation.org/slides/2010/linuxcon2010_brown.pdf > is a presentation on intel_idle driver that describes reasons for its > existence and some additional information. I am not convinced that we need to > follow Linux example. Unless Intel provides and maintains the driver for us like > it does for Linux :-) > -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 2 02:17:01 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5FF81065672 for ; Sat, 2 Jul 2011 02:17:01 +0000 (UTC) (envelope-from edv@agile.bc.ca) Received: from defout.telus.net (defout.telus.net [199.185.220.80]) by mx1.freebsd.org (Postfix) with ESMTP id 121A78FC13 for ; Sat, 2 Jul 2011 02:17:00 +0000 (UTC) Received: from edtncm04 ([199.185.220.240]) by priv-edtnes28.telusplanet.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20110702021659.NEAG6613.priv-edtnes28.telusplanet.net@edtncm04> for ; Fri, 1 Jul 2011 20:16:59 -0600 Received: from [192.168.0.253] ([75.155.136.54]) by edtncm04 with bizsmtp id 2qGz1h00A1Abl5F01qGz0W; Fri, 01 Jul 2011 20:16:59 -0600 X-Telus-Outbound-IP: 75.155.136.54 X-Authority-Analysis: v=1.1 cv=ZTwfZDt+/MwiRvUtBx93qE2eneoRbj17DtNgIyec0i8= c=1 sm=2 a=00GrbmtOa5AA:10 a=lp1F1aYoXqwA:10 a=8nJEP1OIZ-IA:10 a=gmgNY01lnP_z__yLKQ8A:9 a=tMp1OG5FPx07Buioe9IA:7 a=wPNLvfGTeEIA:10 Message-ID: <4E0E7F91.2050408@agile.bc.ca> Date: Fri, 01 Jul 2011 19:16:49 -0700 From: Ed VanderPloeg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: Andriy Gapon References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> <4E0B6873.6010901@agile.bc.ca> <4E0B80BE.6080605@FreeBSD.org> <4E0CA533.5030104@agile.bc.ca> <4E0CE39C.5050307@FreeBSD.org> <4E0D4A15.6000904@agile.bc.ca> <4E0D5EA0.1020704@FreeBSD.org> In-Reply-To: <4E0D5EA0.1020704@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2011 02:17:01 -0000 On 2011-06-30 10:44 PM, Andriy Gapon wrote: > on 01/07/2011 07:16 Ed VanderPloeg said the following: >> On 2011-06-30 1:59 PM, Andriy Gapon wrote: >>> on 30/06/2011 19:32 Ed VanderPloeg said the following: >>>> I updated to 8-stable but am still getting ACPI error messages to console every >>>> 10 seconds. >>> >>> Just for my curiosity - has anything changed with respect to est driver >>> attachment? >> >> I'm not sure what you mean by "attachment". With 8-stable now installed: >> >> stanbud# kldstat -v | grep est >> 445 cpu/est >> >> Is there anything you would like me to check? > > Yes, your dmesg (search for "est"). > # egrep '(^| )est' dmesg.8-release est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 60f0c270600060f device_attach: est0 attach returned 6 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 60f0c270600060f device_attach: est1 attach returned 6 # egrep '(^| )est' dmesg.8-stable est0: on cpu0 est1: on cpu1 From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 2 20:30:25 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19CC0106566C; Sat, 2 Jul 2011 20:30:25 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id B29728FC1D; Sat, 2 Jul 2011 20:30:24 +0000 (UTC) Received: by vxg33 with SMTP id 33so4143762vxg.13 for ; Sat, 02 Jul 2011 13:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bJvdfZxRDQrnLbBGQupoq8N0cf8D4MiUdVJU2+/aVeQ=; b=Kqx2rsHpMCRRZ7GHc9W697Mem1NnmyebXJQdWXZ4+yr4UkgTklu1keX0hYiUYSUHvO RurM1tflpw32C0NJwaPWBIY6CR6uo+AniGghAIVymgAGRcsqSkzj3ftkchGUfi7Fq7eR rosGITApcxNycTv6NUfCqIJvc//yWkXTQ4A0s= MIME-Version: 1.0 Received: by 10.52.91.72 with SMTP id cc8mr2680737vdb.79.1309638621889; Sat, 02 Jul 2011 13:30:21 -0700 (PDT) Received: by 10.52.108.226 with HTTP; Sat, 2 Jul 2011 13:30:21 -0700 (PDT) In-Reply-To: <4E0DB58F.4070906@FreeBSD.org> References: <4E05EB91.9090509@FreeBSD.org> <4E0862A0.7060405@FreeBSD.org> <4E09BADF.7050702@FreeBSD.org> <4E0A41C8.3000904@FreeBSD.org> <4E0CE158.6030804@FreeBSD.org> <4E0DB58F.4070906@FreeBSD.org> Date: Sat, 2 Jul 2011 23:30:21 +0300 Message-ID: From: Vitaly Magerya To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-acpi@freebsd.org Subject: Re: (Missing) power states of an Atom N455-based netbook X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2011 20:30:25 -0000 Andriy Gapon wrote: >> VDRV: 00 -> 01 > > Looks like this variable should tell if OS has ACPI Video driver, to be precise > if _BCL method was invoked at least once. > Looks like in your case the driver doesn't attach for some reason?.. I don't have acpi_video loaded (it's not loaded by default). If I do load it, VDRV indeed becomes 1 (brightness controls that acpi_video exposes don't work though; this appears to be a known problem with Samsung laptops). > Unfortunately, I don't remember if or where you provided your dmesg. It's at [1]. >> (Note that C1ON is 0 just as with FreeBSD, and yet powertop does >> report C2 and C4). > > [...] > > Actually, it seems that they have them simply hardcoded: > http://lxr.linux.no/#linux+v2.6.39/drivers/idle/intel_idle.c#L171 > I am not sure how to check on Linux which cpuidle driver is being used. If you > know, could please check that? And if the driver is intel_idle, then there is > no mystery, they use those hardcoded values. I think the mystery is solved then: $ cat /sys/devices/system/cpu/cpuidle/current_driver intel_idle >> Then, after about 4 minutes of uptime, C1ON changes to 1 (and >> powertop still reports the same states). > > OK, no difference here. So it's probably done by firmware based on some unknown > logic. It seems that way. [1] http://tx97.net/~magv/dmesg-n143-verbose.82.txt