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