All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI failures on Dell Latitude E6220
Date: Sun, 25 Dec 2011 17:55:37 +0100	[thread overview]
Message-ID: <7iwr9k616e.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <20111224210300.GI25883@elie.Belkin> (Jonathan Nieder's message of "Sat, 24 Dec 2011 15:03:00 -0600")

>> I've tried 3.0.0-3, 3.1.1-1, 3.1.4-1, 3.1.5-1 and 3.2~rc4-1~experimental.1,
>> and the system enters PC7 and has decent battery life under all of them.

> What's weird is how gradually it got fixed on your system. :)  First
> v3.1.5 was fixed and 3.2-rc4 not fixed, and then everything fixed.

No mystery there.  I ran apt-get upgrade, removed 3.2-rc4, then switched
to the 3.1.5 kernel.  I never tested 3.2-rc4 after the upgrade.

(Note by the way that it's actually looking more complex than that -- it
looks like there are three levels of power consumption, the inital very
high one, a medium one, and the low one that I'm enjoying right now.
I believe that I can reproduce the medium one on the older kernels, but
I'm not 100% positive about it -- I'd need to do some more precise
measurements.  The only thing that I'm 100% positive about is that the
CPU is reliably entering PC7 under all kernels now.)

> Would you still be interested in tracking the ACPI method parse/execution
> failures?

I'll be glad to help if I can do that without having to understand too
much about ACPI.

-- Juliusz

  parent reply	other threads:[~2011-12-25 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  1:29 ACPI failures on Dell Latitude E6220 Juliusz Chroboczek
2011-12-21 16:40 ` Juliusz Chroboczek
2011-12-22 10:08   ` Jonathan Nieder
2011-12-22 13:23     ` Juliusz Chroboczek
2011-12-24 16:20       ` Juliusz Chroboczek
     [not found]         ` <20111224210300.GI25883@elie.Belkin>
2011-12-25 16:55           ` Juliusz Chroboczek [this message]
2011-12-28 16:29         ` Juliusz Chroboczek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7iwr9k616e.fsf@lanthane.pps.jussieu.fr \
    --to=jch@pps.jussieu.fr \
    --cc=jrnieder@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.