From: Andy Isaacson <adi@hexapodia.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: ibm-acpi-devel@lists.sourceforge.net, linux-acpi@vger.kernel.org
Subject: Re: [ibm-acpi-devel] t420s: unhandled HKEY
Date: Sat, 16 Jun 2012 21:51:33 -0700 [thread overview]
Message-ID: <20120617045133.GL11306@hexapodia.org> (raw)
In-Reply-To: <20120616201735.GH15543@khazad-dum.debian.net>
On Sat, Jun 16, 2012 at 05:17:35PM -0300, Henrique de Moraes Holschuh wrote:
> Andy, as an early follow up, does it make any difference whether you
> plug/unplug AC power directly on the notebook, or on a docking
> station/port replicator?
>
> Do you have more than one power brick with different power ratings (e.g.
> 65W and 90W)?
>
> Because AFAIK you really should get a 0x6040 every time the AC power
> adapter state changes.
I do use two or three different PSUs, they may have different ratings.
The one I have in front of me is 65W, and I do get 0x6040 when I plug or
unplug it today. The other one is at the office and I'll check on
Monday.
Looking through syslog, I do have a lot of pairs of "unhandled HKEY
event 0x6040" followed immediately by "EC reports that Thermal Table has
changed", but there are also a few Thermal Table changed without a
preceding HKEY event. Perhaps 90% of "Thermal Table has changed" have a
HKEY before them. There don't appear to be any HKEY 0x6040 without a
"Thermal Table has changed" immediately after.
-andy
prev parent reply other threads:[~2012-06-17 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120606222804.GA6931@cloudera.com>
2012-06-08 8:08 ` t420s: unhandled HKEY Andy Isaacson
2012-06-16 20:11 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
[not found] ` <20120608080824.GS25324-3HqRAUrWAWyGglJvpFV4uA@public.gmane.org>
2012-06-16 20:17 ` Henrique de Moraes Holschuh
2012-06-17 4:51 ` Andy Isaacson [this message]
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=20120617045133.GL11306@hexapodia.org \
--to=adi@hexapodia.org \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--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