Bug 1275280

Summary:	HP Spectre x360 keyboard intermittently disabled
Product:	[Fedora] Fedora	Reporter:	Nick Coghlan <ncoghlan>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	27	CC:	bugzilla, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, mstuff
Target Milestone:	---	Keywords:	Reopened
Target Release:	---	Flags:	jforbes: needinfo?
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-29 15:10:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nick Coghlan 2015-10-26 12:56:33 UTC

Description of problem:

The HP Spectre 360 is a convertible laptop that disables the keyboard when switched to touchscreen mode. While upgrading to the F23 beta appeared to fix some other problems (e.g. suspending now works), the recent 4.2.3 kernel is regularly disabling the keyboard during normal use.


Version-Release number of selected component (if applicable):

kernel-4.2.3-300.fc23.x86_64

How reproducible:

Consistently on the 4.2.3 kernel, very occasionally on the 4.2.1 kernel. 

Steps to Reproduce:
1. Run Fedora 23 on a HP Spectre x360
2. Watch for the backlight activation light under the F5 key to turn off
3.

Actual results:

The F5 "Enable backlight" key regularly goes dark, and stays dark for extended periods (up to tens of seconds). During this time, the keyboard is disabled as if the computer was in touch screen mode.

When using the 4.2.1 kernel instead, this still happens occasionally, but significantly less often, and the keyboard only stays disabled for a couple of seconds at most (unless actually flipped into tablet mode).

Prior to upgrading to the F23 beta (from F22), I don't recall this particular problem ever happening at all - the keyboard worked reliably.

Expected results:

The keyboard stays enabled unless the machinely is physically flipped into tablet mode.

Additional info:

I haven't double checked since booting back into 4.2.1, but I think when I tried switching to tablet mode while running 4.2.3, it *didn't* disable the keyboard.

Comment 1 Nick Coghlan 2016-06-13 16:04:11 UTC

Version bump as the problem still exists in F24 beta

Comment 2 morgan read 2016-08-06 08:30:53 UTC

I can add that this has occurred recently at boot - meaning that I'm unable to enter luks password, unable to enter rescue, unable to access the HP boot tools - all I'm able to do is press the power button for a few seconds, go away, pray and come back sometime latter and hope it works...  Sometimes it doesn't...

Comment 3 morgan read 2016-08-06 09:14:18 UTC

Re Comment 2
$ uname -r
4.6.4-301.fc24.x86_64

Comment 4 Laura Abbott 2016-09-23 19:08:04 UTC

*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.
 
Fedora 24 has now been rebased to 4.7.4-200.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25.
 
If you experience different issues, please open a new bug report for those.

Comment 5 Nick Coghlan 2016-09-28 08:49:52 UTC

Morgan, if it's staying disabled for more than 5-10 seconds, that's a different symptom and likely a different bug entirely, especially if it's only happening at startup (this one was about the keyboard being intermittently disabled during normal operation, and then coming back a few seconds later).

Laura, I haven't noticed the keyboard disabling itself since the upgrade to 4.7.4, so I'm going to mark this as "CLOSED CURRENTRELEASE" for now.

It's easy for me to miss when working on an external keyboard though (I have to notice the backlight switch turning itself off), so if I do see it happen again, I'll reopen the BZ.

Comment 6 Nick Coghlan 2016-10-06 01:30:12 UTC

I'm working directly on the laptop today (no external keyboard), and am seeing symptoms similar to those I saw with the 4.2.1 kernel: the internal keyboard will be intermittently disabled for a few seconds, before resuming normal operation.

It's rare enough that the system is still usable, but frequent enough that I saw the problem within 15-20 minutes of using the device without an external keyboard attached.

$ uname -r
4.7.5-200.fc24.x86_64

Comment 7 Nick Coghlan 2016-10-06 01:36:27 UTC

Following up on the "Additional Info" section in my initial bug report: flipping the device into tablet mode *does* disable the keyboard exactly as it should, so the only anomalous behaviour I'm seeing is that the keyboard sometimes gets disabled while in laptop mode.

Comment 8 Justin M. Forbes 2017-04-11 14:51:35 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 9 Justin M. Forbes 2017-04-28 17:09:09 UTC

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 10 Nick Coghlan 2017-11-19 03:48:03 UTC

I'm still seeing this behaviour in Fedora 26 with kernel-4.13.12-200.fc26.x86_64  - even though I almost always use an external keyboard now, I can see the backlight key occasionally turning itself off and on again.


Noting a few likely relevant points:

* according to https://answers.launchpad.net/magick-rotation/+faq/1346, one of the purposes of the hp_wmi kernel module is to report swivel hinge events from the laptop hardware
* one of the key functions of the swivel hinge notification is to turn off the laptop keyboard when in tablet mode
* according to https://bugs.freedesktop.org/show_bug.cgi?id=102765#c13 the ACPI errors seen in dmesg when booting the HP Spectre x360 are coming from the hp_wmi module

Quoting those errors (from kernel-4.12.13-300.fc26.x86_64 as reported in https://bugzilla.kernel.org/show_bug.cgi?id=197007, but ultimately determined to be unrelated to the monitor issues):

==============
[   14.459261] ACPI Error: Field [D128] at 1152 exceeds Buffer [NULL] size 160 (bits) (20170303/dsopcode-236)
[   14.459268] ACPI Error: Method parse/execution failed [\HWMC] (Node ffff8edcc61507f8), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
[   14.459279] ACPI Error: Method parse/execution failed [\_SB.WMID.WMAA] (Node ffff8edcc61523c0), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
[   14.459338] ACPI Error: Field [D128] at 1152 exceeds Buffer [NULL] size 160 (bits) (20170303/dsopcode-236)
[   14.459342] ACPI Error: Method parse/execution failed [\HWMC] (Node ffff8edcc61507f8), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
[   14.459349] ACPI Error: Method parse/execution failed [\_SB.WMID.WMAA] (Node ffff8edcc61523c0), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
[   14.459404] ACPI Error: Field [D128] at 1152 exceeds Buffer [NULL] size 160 (bits) (20170303/dsopcode-236)
[   14.459408] ACPI Error: Method parse/execution failed [\HWMC] (Node ffff8edcc61507f8), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
[   14.459415] ACPI Error: Method parse/execution failed [\_SB.WMID.WMAA] (Node ffff8edcc61523c0), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
[   14.459474] input: HP WMI hotkeys as /devices/virtual/input/input27
[   14.459637] ACPI Error: Field [D128] at 1152 exceeds Buffer [NULL] size 160 (bits) (20170303/dsopcode-236)
[   14.459642] ACPI Error: Method parse/execution failed [\HWMC] (Node ffff8edcc61507f8), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
[   14.459650] ACPI Error: Method parse/execution failed [\_SB.WMID.WMAA] (Node ffff8edcc61523c0), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
[   14.459692] ACPI Error: Field [D128] at 1152 exceeds Buffer [NULL] size 160 (bits) (20170303/dsopcode-236)
[   14.459695] ACPI Error: Method parse/execution failed [\HWMC] (Node ffff8edcc61507f8), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
[   14.459702] ACPI Error: Method parse/execution failed [\_SB.WMID.WMAA] (Node ffff8edcc61523c0), AE_AML_BUFFER_LIMIT (20170303/psparse-543)
==============

Comment 11 Jan Kurik 2018-05-31 09:07:56 UTC

This bug is currently reported against a Fedora version which is already unsuported.
I am changing the version to '27', the latest supported release.

Please check whether this bug is still an issue on the '27' release.
If you find this bug not being applicable on this release, please close it.

Comment 12 Justin M. Forbes 2018-07-23 15:15:58 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.

Comment 13 Justin M. Forbes 2018-08-29 15:10:57 UTC

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.