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: Sat, 24 Dec 2011 17:20:39 +0100 [thread overview]
Message-ID: <8739cavt48.fsf@pirx.pps.jussieu.fr> (raw)
In-Reply-To: <7iipl8d9kk.fsf@lanthane.pps.jussieu.fr> (Juliusz Chroboczek's message of "Thu, 22 Dec 2011 14:23:23 +0100")
>> Thanks for the update. Am I right in guessing that 3.1.4-1 is broken,
>> too,
> I'll try, but not right now (I'm in just a wee bit of a rush).
I'm completely unable to reproduce the issue now.
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.
So it looks like the differences in ACPI log messages were a red her-
ring, and that something else changed on my system that was preventing
PC7 from being entered.
- it's not a BIOS change (I'm still running A03);
- it's not the iwlwifi firmware (that was last upgraded on 6 November);
- it could be the X server or the user-space DRI components, which were
upgraded a number of times since then.
I'm really at a loss; please let me know if you have any ideas.
-- Juliusz
next prev parent reply other threads:[~2011-12-24 16:20 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 [this message]
[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=8739cavt48.fsf@pirx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox