Re: platform/x86: thinkpad_acpi: unhandled HKEY 0x60b0 and 0x60b1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 18-01-09 22:16:10, Andy Shevchenko wrote:
> +Cc: Mattew, who is an author of the patch I posted link to which earlier.
> 
> On Tue, Jan 9, 2018 at 3:19 PM, David Herrmann <dh.herrmann@xxxxxxxxx> wrote:
> > Hi
> >
> > The thinkpad_acpi driver constantly reports about unhandled events on
> > my ThinkPad X1 5gen. The logs look like this:
> >
> > kernel: thinkpad_acpi: unknown possible thermal alarm or keyboard event received
> > kernel: thinkpad_acpi: unhandled HKEY event 0x60b1
> > kernel: thinkpad_acpi: please report the conditions when this event
> > happened to ibm-acpi-devel@...
> >
> > kernel: thinkpad_acpi: unknown possible thermal alarm or keyboard event received
> > kernel: thinkpad_acpi: unhandled HKEY event 0x60b0
> > kernel: thinkpad_acpi: please report the conditions when this event
> > happened to ibm-acpi-devel@...
> >
> > I have no clue what triggers them. However, the 0x60b1 event seems to
> > notify about some kind of action, and 0x60b0 seems to notify about its
> > end (like FAN-START, and FAN-STOP). The 0x60b0 follows 0x60b1 usually
> > in a timespan between 1s-10s.
> >
> > The event occurs even when the laptop is not moved/touched, but only
> > performs random computations. The first time this occurs is usually
> > during user-space startup, which might just be the time the module is
> > loaded. So far, I did not see any other event occurring before/after
> > it, which might give any hints.
> >
> > What is the recommended way to deal with that? I am having a hard-time
> > figuring out what triggers it, but at the same time it spams the
> > system-logs to a degree that after 1h of uptime, the vast majority of
> > the system log is cluttered with those messages.
> >
> > I can provide a patch to ignore these events in the driver? Or does
> > anyone have access to Lenovo developers to ask for help?
> >

I've been able to trigger it 'at will' on the X1C5.  If I hover my hand
just below the arrow keys I'll get the first signal, after I take it
away I get the second one.  There seems to be a delay in when I put (or
take away) my hand to prevent spamming the logs even more.  It could be
to sense lid close, but there's already another sensors for that I
thought.  The only remaining thing I can guess it that it's to detect
your hands to turn on the keyboard backlight or something.

I don't think it's related at all to the fingerprint sensor as I hover
my hand to the right of it.

-- 
Matthew Thode

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Kernel Development]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux