Any key pressed opens shutdown dialog (Asus X205TA)

Bug #1656618 reported by Joshua Clements
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

After a fresh install of 16.10 on my Asus X205TA, any key pressed on the built-in keyboard brings up the shutdown dialog. The system works fine with a USB keyboard.

The installed kernel was 4.8.0-34-generic. Booting with 4.8.0-22-generic, the keyboard works fine.

Other users have confirmed the bug in Fedora and Tails (https://ubuntuforums.org/showthread.php?t=2254322&p=13594241#post13594241) and in 16.10 MATE (https://ubuntuforums.org/showthread.php?t=2254322&p=13594617#post13594617).
---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
Lsusb:
 Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 8087:07e6 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X205TA
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=05a20fbf-3084-4535-bae3-bed719df662c ro quiet splash intel_max.idle_cstate=1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-22-generic N/A
 linux-backports-modules-4.8.0-22-generic N/A
 linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.8.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/04/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X205TA.212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X205TA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X205TA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=94efdbb7-8cb5-442c-8a16-5fbe6fbf4959
InstallationDate: Installed on 2017-01-16 (0 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard
 Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 8087:07e6 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X205TA
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=/dev/mmcblk1p2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-34-generic N/A
 linux-backports-modules-4.8.0-34-generic N/A
 linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.8.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/04/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X205TA.212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X205TA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X205TA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Joshua Clements (whirlynerd) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1656618

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joshua Clements (whirlynerd) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected yakkety
description: updated
Revision history for this message
Joshua Clements (whirlynerd) wrote : CRDA.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : IwConfig.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : JournalErrors.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : Lspci.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : ProcEnviron.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : ProcModules.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : PulseList.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : RfKill.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : UdevDb.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joshua Clements (whirlynerd) wrote :

I performed a fresh install of Xubuntu 16.10 and can confirm that this bug also exists in that installation. It is also using linux-image-4.8.0-34 as its default kernel package.

I wasn't able to perform the apport-collect as request on the previous installation, so another follows this comment using my Xubuntu 16.10 install and -34 kernel.

description: updated
Revision history for this message
Joshua Clements (whirlynerd) wrote : AlsaInfo.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : CRDA.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : IwConfig.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : JournalErrors.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : Lspci.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : ProcModules.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : RfKill.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : UdevDb.txt

apport information

Revision history for this message
Joshua Clements (whirlynerd) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc4

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Taddeo Manzi (sinistristradali) wrote :

Bug still present in upstream kernel.
"On a sidenode, touchpad and built-in keyboard do not work with 4.10-rc3. on boot dmesg shows the i2c_hid module "failed to reset device". When the laptop is finished booting, pressing one key on the built-in keyboard instantly powers off the laptop."

https://bugzilla.kernel.org/show_bug.cgi?id=95681#c183

Revision history for this message
Joshua Clements (whirlynerd) wrote :

Some of the folks working on getting the sound to work also noticed that something in kernel 4.9 is also preventing the keyboard and touchpad from working as well.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Taddeo Manzi (sinistristradali) wrote :

Wait, as harryharryharry, I can confirm that mainline kernel 4.9.0-040900.201612111631 works without problems. So the problem is only present in 4.8 ubuntu line and 4.10, so maybe the problem is caused by some backported code from mainstream, maybe security patch.
So, could be this change reported in
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-edge/linux-hwe-edge_4.8.0-34.36~16.04.1/changelog

 - HID: i2c-hid: fix OOB write in i2c_hid_set_or_send_report()

Revision history for this message
harry (vaaghoofdharry) wrote :

the OOB write fix was submitted in march 2016, so I doubt that has anything to do with it.

I tried debugging the module i2c_hid (which I'm not accustomed to) and dug op the following while loading the module and reading /proc/kmsg simultaneously (on kernel 4.10-rc1):

<3>[ 299.249790] i2c_hid i2c-PDEC3393:00: failed to reset device.
<3>[ 305.439747] i2c_hid i2c-PDEC3393:00: failed to reset device.
<3>[ 318.832237] i2c_hid i2c-PDEC3393:00: can't add hid device: -61

Revision history for this message
harry (vaaghoofdharry) wrote :

and with dyndbg==pmf enabled while loading the module:
<7>[ 857.237099] i2c_hid:i2c_hid_init_irq: i2c_hid i2c-PDEC3393:00: Requesting IRQ: 195
<3>[ 868.461393] i2c_hid i2c-PDEC3393:00: failed to reset device.
<3>[ 880.840464] i2c_hid i2c-PDEC3393:00: failed to reset device.
<4>[ 881.884430] i2c_hid: probe of i2c-PDEC3393:00 failed with error -61

Revision history for this message
harry (vaaghoofdharry) wrote :

adding i2c_hid.debug=1 as a boot parameter gives the following output:
[ 4.572059] i2c_hid i2c-PDEC3393:00: Fetching the HID descriptor
[ 4.572065] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f1 00
[ 4.575576] i2c_hid i2c-PDEC3393:00: HID Descriptor: 1e 00 00 01 b4 00 f2 00 f3 00 0e 00 f4 00 04 00 f5 00 f6 00 05 0b 85 85 01 00 00 00 00 00
[ 4.575685] i2c_hid i2c-PDEC3393:00: entering i2c_hid_parse
[ 4.575689] i2c_hid i2c-PDEC3393:00: i2c_hid_hwreset
[ 4.575692] i2c_hid i2c-PDEC3393:00: i2c_hid_set_power
[ 4.575695] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 08
[ 4.581210] i2c_hid i2c-PDEC3393:00: resetting...
[ 4.581214] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 01
[ 4.581660] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: waiting...
[ 9.701087] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: finished.
[ 9.701099] i2c_hid i2c-PDEC3393:00: failed to reset device.
[ 9.708842] i2c_hid i2c-PDEC3393:00: i2c_hid_set_power
[ 9.708854] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 01 08
[ 10.714178] i2c_hid i2c-PDEC3393:00: i2c_hid_hwreset
[ 10.714190] i2c_hid i2c-PDEC3393:00: i2c_hid_set_power
[ 10.714201] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 08
[ 10.714821] i2c_hid i2c-PDEC3393:00: resetting...
[ 10.714833] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 01
[ 10.718836] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: waiting...
[ 15.887586] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: finished.
[ 15.887597] i2c_hid i2c-PDEC3393:00: failed to reset device.
..............
..............
[ 29.294255] i2c_hid: probe of i2c-PDEC3393:00 failed with error -61
[ 29.465100] i2c_hid i2c-ELAN0100:00: Fetching the HID descriptor
[ 29.465104] i2c_hid i2c-ELAN0100:00: __i2c_hid_command: cmd=01 00
[ 29.468290] i2c_hid i2c-ELAN0100:00: HID Descriptor: 1e 00 00 01 6a 00 02 00 03 00 1e 00 04 00 00 00 05 00 06 00 f3 04 01 04 0a 00 00 00 00 00
[ 29.596520] i2c_designware 80860F41:04: I2C bus managed by PUNIT
[ 29.772290] elan_i2c i2c-ELAN0100:00: Elan Touchpad: Module ID: 0x0026, Firmware: 0x000a, Sample: 0x0001, IAP: 0x0000
[ 29.773767] input: Elan Touchpad as /devices/platform/80860F41:03/i2c-11/i2c-ELAN0100:00/input/input7
[ 31.145688] elan_i2c i2c-ELAN0100:00: Elan Touchpad: Module ID: 0x0026, Firmware: 0x000a, Sample: 0x0001, IAP: 0x0000
[ 31.145966] input: Elan Touchpad as /devices/platform/80860F41:03/i2c-11/i2c-ELAN0100:00/input/input11

Revision history for this message
harry (vaaghoofdharry) wrote :

I found the patch that causes the keyboard to malfunction !:
https://www.spinics.net/lists/linux-gpio/msg18340.html

reverse patching this patch 'solves' the issue (specifically reverse patching pinctrl-baytrail, reverse patching pinctrl-intel is not really necessary)

Revision history for this message
Zanna (rose-anna-bleasdale) wrote :

Last working kernel for me was 4.8.0-32 (still using it). In addition to any key triggering the shutdown dialog, the system is unstable. Various buttons on onboard causes the cursor to freeze (and keys to repeat indefinitely). I can unfreeze it by pressing something on the keyboard, which brings up the dialog and unfreezes the cursor so I can click cancel on the dialog and resume.

Planning to install zesty...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Does blacklist 'i2c-hid' make the issue gone?

Revision history for this message
Joshua Clements (whirlynerd) wrote :

Blacklisting 'i2c-hid' does not resolve the issue.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Looks like there is a keyboard related patch but not upstreamed yet:
https://bugzilla.kernel.org/show_bug.cgi?id=95681#c223

Norbert (nrbrtx)
tags: removed: yakkety
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.