John McCabe-Dansted | 3 Jun 2011 11:02
Picon

Re: unknown thermal alarm received ... 0x6005

On Mon, May 30, 2011 at 10:17 PM, John McCabe-Dansted
<gmatht@...> wrote:
> THERMAL ALERT: unknown thermal alarm received
> unhandled HKEY event 0x6005

OK, this appears to occur exactly when I press the Fn key. I need to
press the Fn key when I switch to a VT to see the Oops message, and
that is why it is always appears when I see a kernel Oops. It appears
to be harmless in and of it self.

--

-- 
John C. McCabe-Dansted

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
Picon
Favicon

Re: unknown thermal alarm received ... 0x6005

On Fri, 03 Jun 2011, John McCabe-Dansted wrote:
> On Mon, May 30, 2011 at 10:17 PM, John McCabe-Dansted
<gmatht@...> wrote:
> > THERMAL ALERT: unknown thermal alarm received
> > unhandled HKEY event 0x6005
> 
> OK, this appears to occur exactly when I press the Fn key. I need to
> press the Fn key when I switch to a VT to see the Oops message, and
> that is why it is always appears when I see a kernel Oops. It appears
> to be harmless in and of it self.

John,

Thank you for your report.

Just to make sure I did understand it right:  if you press the Fn key
*alone*, with no other keys, your thinkpad issues event 0x6005.  Is that
correct?

Also, when you press Fn+<some other key>, does it issue event 0x6005 at all?

Does it issue the event when you press the key, when you release the key, or
both?

--

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

(Continue reading)

John McCabe-Dansted | 6 Jun 2011 09:09
Picon

Re: unknown thermal alarm received ... 0x6005

On Sun, Jun 5, 2011 at 4:47 AM, Henrique de Moraes Holschuh
<hmh@...> wrote:
> On Fri, 03 Jun 2011, John McCabe-Dansted wrote:
>> On Mon, May 30, 2011 at 10:17 PM, John McCabe-Dansted
<gmatht@...> wrote:
>> > THERMAL ALERT: unknown thermal alarm received
>> > unhandled HKEY event 0x6005
<snip>
> Just to make sure I did understand it right:  if you press the Fn key
> *alone*, with no other keys, your thinkpad issues event 0x6005.  Is that
> correct?
>
> Also, when you press Fn+<some other key>, does it issue event 0x6005 at all?
>
> Does it issue the event when you press the key, when you release the key, or
> both?

I get the 0x6005 event precisely when I release the Fn key, regardless
of whether I have also pressed (or am pressing) a function key or not.

Pressing and holding the key down does not cause the event (until I
release the key).

--

-- 
John C. McCabe-Dansted

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
(Continue reading)

John McCabe-Dansted | 6 Jun 2011 19:43
Picon

Re: unknown thermal alarm received ... 0x6005

On Mon, Jun 6, 2011 at 3:09 PM, John McCabe-Dansted <gmatht@...> wrote:
> I get the 0x6005 event precisely when I release the Fn key, regardless
> of whether I have also pressed (or am pressing) a function key or not.
>
> Pressing and holding the key down does not cause the event (until I
> release the key).

Also, I think I only get the 0x6005 event when I have the Fn key lock
function enabled in the BIOS (it is disabled by default).

--

-- 
John C. McCabe-Dansted

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
Picon
Favicon

Re: unknown thermal alarm received ... 0x6005

On Tue, 07 Jun 2011, John McCabe-Dansted wrote:
> On Mon, Jun 6, 2011 at 3:09 PM, John McCabe-Dansted
<gmatht@...> wrote:
> > I get the 0x6005 event precisely when I release the Fn key, regardless
> > of whether I have also pressed (or am pressing) a function key or not.
> >
> > Pressing and holding the key down does not cause the event (until I
> > release the key).
> 
> Also, I think I only get the 0x6005 event when I have the Fn key lock
> function enabled in the BIOS (it is disabled by default).

Hmm, that's very interesting, and it brings to mind a few other
questions:

What is the intended effect of the "Fn key lock" function?  (I can infer
it, but since you can actually experience it...)

What really changes when it is enabled in Linux?

Do you know how it is supposed to behave in Windows (if it doesn't match
what happens in Linux) ?

--

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

------------------------------------------------------------------------------
(Continue reading)

John McCabe-Dansted | 7 Jun 2011 06:13
Picon

Re: unknown thermal alarm received ... 0x6005

On Tue, Jun 7, 2011 at 5:11 AM, Henrique de Moraes Holschuh
<hmh@...> wrote:
> On Tue, 07 Jun 2011, John McCabe-Dansted wrote:
>> On Mon, Jun 6, 2011 at 3:09 PM, John McCabe-Dansted
<gmatht@...> wrote:
>> > I get the 0x6005 event precisely when I release the Fn key, regardless
>> > of whether I have also pressed (or am pressing) a function key or not.
>> >
>> > Pressing and holding the key down does not cause the event (until I
>> > release the key).
>>
>> Also, I think I only get the 0x6005 event when I have the Fn key lock
>> function enabled in the BIOS (it is disabled by default).
>
> Hmm, that's very interesting, and it brings to mind a few other
> questions:
>
> What is the intended effect of the "Fn key lock" function?  (I can infer
> it, but since you can actually experience it...)

When the Fn Key Lock is enabled in the bios:
  1) pressing Fn once will cause the the next key to be interpreted as
a Function key (i.e. F1..F10, the E420 does not have dedicated F1..F10
keys, but shares them with e.g. volume control). In Linux it also
causes e.g. the S key to be interpreted as "Take a screenshot"
  2) pressing Fn twice will cause all keys to be interpreted as
Function keys until Fn is pressed again.

> What really changes when it is enabled in Linux?

(Continue reading)

Picon
Favicon

Re: unknown thermal alarm received ... 0x6005

On Tue, 07 Jun 2011, John McCabe-Dansted wrote:
> The 0x6005 appears to indicate that the Fn Key Lock status has
> changed. It is possible for 0x6005 to be emitted when a key other than
> Fn is pressed, if the the Fn Key Lock status is next key is next key
> only then pressing any key will change the FKL status (to unlocked,
> unless it is the Fn key being pressed a second time, which will change
> the FKL status to permanently locked, but either way the FKL status
> changes and 0x6005 will be emitted).
> 
> 
> y: 0x6005 warning emitted
> n: 0x6005 warning *not* emitted
> 
> Key, ?, Fn Key Lock status
>    ,  , Unlocked
> Fn , y, Next key locked only
> Fn , y, Permanently locked
> Z  , n, Permanently locked
> F1 , n, Permanently locked
> 
> Fn , y, Unlocked
> 
> Fn , y, Next key locked only
> F1 , y, Unlocked
> 
> Fn , y, Next key locked only
> Z  , y, Unlocked

Thanks.  So, it works out-of-the-box without help, that's good.

(Continue reading)

John McCabe-Dansted | 7 Jun 2011 19:46
Picon

Re: unknown thermal alarm received ... 0x6005

On Tue, Jun 7, 2011 at 9:16 PM, Henrique de Moraes Holschuh
<hmh@...> wrote:
> Maybe userspace might want to show a "Fn" indicator in the taskbar or
> something, but that's about it.  It looks like something that will remain
> vendor-specific, too.

Yes, that is what the Windows 7 install Lenovo bundles does. It
displays the same "Fn" overlay when changing to next key or permanent
Fn lock mode (though the overlay is not permanent even in permanent
lock mode.)

> However, the event is missing some in-band information about the final state
> (next use, lock, unlock) which would be required to write a GUI hint.  It is
> likely available elsewhere (in the ACPI DSDT or in an ACPI SSDT, most
> likely).
>
> Can you send me the (gzipped) output of dmidecode and acpidump for your
> thinkpad?  Please cross-out UUIDs and serial numbers.

Sent off-list as requested

--

-- 
John C. McCabe-Dansted

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
(Continue reading)


Gmane