All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Juliusz Chroboczek <jch@pps.jussieu.fr>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI failures on Dell Latitude E6220
Date: Thu, 22 Dec 2011 04:08:49 -0600	[thread overview]
Message-ID: <20111222100849.GA6548@elie.Belkin> (raw)
In-Reply-To: <87vcp998us.fsf@pirx.pps.jussieu.fr>

Juliusz Chroboczek wrote:

>>> [  227.525937] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20110623/evregion-478)
>>> [  227.525946] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV.ECR1] (Node ffff880128e7a3d0), AE_TIME (20110623/psparse-536)
>>> [  227.525957] ACPI Error: Method parse/execution failed [\ECRB] (Node ffff880128e7a268), AE_TIME (20110623/psparse-536)
>
> This appears to be fixed, or at least worked around, by Debian's kernel
> 3.1.5-1.  My idle battery time doubled (yay!).  Turbostat indicates that
> the CPU is now entering the higher-numbered "PC" states, which it wasn't
> doing beforehand.

Thanks for the update.  Am I right in guessing that 3.1.4-1 is broken,
too, and that with 3.1.5-1 the ACPI exceptions are gone?  Could you
attach "dmesg" output from booting a fixed kernel for reference?

>From a quick glance, none of the fixes introduced by 3.1.5-1 seems to
explain this change in an obvious way.  Glad to hear the new kernel is
working well, though.

Curious,
Jonathan

  reply	other threads:[~2011-12-22 10:08 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 [this message]
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
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=20111222100849.GA6548@elie.Belkin \
    --to=jrnieder@gmail.com \
    --cc=jch@pps.jussieu.fr \
    --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.