Ubuntu
linux package

Touchpad doesn't work in 4.17 or later

  1. Cosmic (18.10)
  2. Bug #1778323
Bug #1778323 reported by Patrik Kullman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned
Cosmic
Confirmed
Medium
Unassigned

Bug Description

Using the builds at http://kernel.ubuntu.com/~kernel-ppa/mainline/ I can successfully install and run 4.16.17 (Linux version 4.16.17-041617-generic (kernel@tangerine) (gcc version 7.3.0 (Ubuntu 7.3.0-23ubuntu2)) #201806201630 SMP Wed Jun 20 20:32:55 UTC 2018) but not 4.17.2 or 4.18-rc1.

In the later ones, the touchpad does not work after boot and rebooting stalls:

Jun 18 15:42:50 pkxps kernel: [ 242.366528] INFO: task systemd-udevd:309 blocked for more than 120 seconds.
Jun 18 15:42:50 pkxps kernel: [ 242.366540] Not tainted 4.17.2-041702-generic #201806160433
Jun 18 15:42:50 pkxps kernel: [ 242.366545] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 18 15:42:50 pkxps kernel: [ 242.366551] systemd-udevd D 0 309 273 0x80000104
Jun 18 15:42:50 pkxps kernel: [ 242.366558] Call Trace:
Jun 18 15:42:50 pkxps kernel: [ 242.366576] __schedule+0x291/0x870
Jun 18 15:42:50 pkxps kernel: [ 242.366582] ? __switch_to_asm+0x34/0x70
Jun 18 15:42:50 pkxps kernel: [ 242.366587] ? __switch_to_asm+0x40/0x70
Jun 18 15:42:50 pkxps kernel: [ 242.366596] ? get_work_pool+0x40/0x40
Jun 18 15:42:50 pkxps kernel: [ 242.366602] schedule+0x2c/0x80
Jun 18 15:42:50 pkxps kernel: [ 242.366609] schedule_timeout+0x1db/0x360
Jun 18 15:42:50 pkxps kernel: [ 242.366615] ? __schedule+0x299/0x870
Jun 18 15:42:50 pkxps kernel: [ 242.366623] ? get_work_pool+0x40/0x40
Jun 18 15:42:50 pkxps kernel: [ 242.366629] wait_for_completion+0xba/0x140
Jun 18 15:42:50 pkxps kernel: [ 242.366637] ? wake_up_q+0x80/0x80
Jun 18 15:42:50 pkxps kernel: [ 242.366645] flush_work+0x127/0x1e0
Jun 18 15:42:50 pkxps kernel: [ 242.366652] ? worker_detach_from_pool+0xa0/0xa0
Jun 18 15:42:50 pkxps kernel: [ 242.366661] __cancel_work_timer+0x131/0x1b0
Jun 18 15:42:50 pkxps kernel: [ 242.366669] cancel_delayed_work_sync+0x13/0x20
Jun 18 15:42:50 pkxps kernel: [ 242.366676] power_supply_unregister+0x37/0xb0
Jun 18 15:42:50 pkxps kernel: [ 242.366682] devm_power_supply_release+0x11/0x20
Jun 18 15:42:50 pkxps kernel: [ 242.366692] release_nodes+0x110/0x1f0
Jun 18 15:42:50 pkxps kernel: [ 242.366701] devres_release_group+0x7c/0xb0
Jun 18 15:42:50 pkxps kernel: [ 242.366718] wacom_remove+0xce/0x120 [wacom]
Jun 18 15:42:50 pkxps kernel: [ 242.366733] hid_device_remove+0x55/0xb0 [hid]
Jun 18 15:42:50 pkxps kernel: [ 242.366741] device_release_driver_internal+0x15b/0x220
Jun 18 15:42:50 pkxps kernel: [ 242.366751] ? __hid_bus_driver_added+0x40/0x40 [hid]
Jun 18 15:42:50 pkxps kernel: [ 242.366760] ? hid_destroy_device+0x60/0x60 [hid]
Jun 18 15:42:50 pkxps kernel: [ 242.366766] device_release_driver+0x12/0x20
Jun 18 15:42:50 pkxps kernel: [ 242.366771] device_reprobe+0x30/0x50
Jun 18 15:42:50 pkxps kernel: [ 242.366782] __hid_bus_reprobe_drivers+0x4b/0x60 [hid]
Jun 18 15:42:50 pkxps kernel: [ 242.366793] bus_for_each_dev+0x74/0xb0
Jun 18 15:42:50 pkxps kernel: [ 242.366803] __hid_bus_driver_added+0x2c/0x40 [hid]
--
Jun 18 15:42:50 pkxps kernel: [ 242.366859] ? __vunmap+0x81/0xb0
Jun 18 15:42:50 pkxps kernel: [ 242.366867] ? _cond_resched+0x19/0x40
Jun 18 15:42:50 pkxps kernel: [ 242.366874] ? kmem_cache_alloc_trace+0xb8/0x1c0
Jun 18 15:42:50 pkxps kernel: [ 242.366883] ? do_init_module+0x27/0x209
Jun 18 15:42:50 pkxps kernel: [ 242.366892] do_init_module+0x5f/0x209
Jun 18 15:42:50 pkxps kernel: [ 242.366900] load_module+0x1987/0x1f10
Jun 18 15:42:50 pkxps kernel: [ 242.366913] __do_sys_finit_module+0xfc/0x120
Jun 18 15:42:50 pkxps kernel: [ 242.366919] ? __do_sys_finit_module+0xfc/0x120
Jun 18 15:42:50 pkxps kernel: [ 242.366929] __x64_sys_finit_module+0x1a/0x20
Jun 18 15:42:50 pkxps kernel: [ 242.366936] do_syscall_64+0x5a/0x120
Jun 18 15:42:50 pkxps kernel: [ 242.366942] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 18 15:42:50 pkxps kernel: [ 242.366948] RIP: 0033:0x7f03e2729839
Jun 18 15:42:50 pkxps kernel: [ 242.366952] RSP: 002b:00007ffde9a0e588 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Jun 18 15:42:50 pkxps kernel: [ 242.366959] RAX: ffffffffffffffda RBX: 0000561aff969a00 RCX: 00007f03e2729839
Jun 18 15:42:50 pkxps kernel: [ 242.366963] RDX: 0000000000000000 RSI: 00007f03e24080e5 RDI: 0000000000000007
Jun 18 15:42:50 pkxps kernel: [ 242.366967] RBP: 00007f03e24080e5 R08: 0000000000000000 R09: 00007ffde9a0e6a0
Jun 18 15:42:50 pkxps kernel: [ 242.366970] R10: 0000000000000007 R11: 0000000000000246 R12: 0000000000000000
Jun 18 15:42:50 pkxps kernel: [ 242.366974] R13: 0000561aff95d850 R14: 0000000000020000 R15: 0000561aff969a00
Jun 18 15:42:50 pkxps kernel: [ 242.366987] INFO: task kworker/u8:3:394 blocked for more than 120 seconds.
Jun 18 15:42:50 pkxps kernel: [ 242.366996] Not tainted 4.17.2-041702-generic #201806160433
Jun 18 15:42:50 pkxps kernel: [ 242.367000] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 18 15:42:50 pkxps kernel: [ 242.367006] kworker/u8:3 D 0 394 2 0x80000000
Jun 18 15:42:50 pkxps kernel: [ 242.367021] Workqueue: events_power_efficient power_supply_deferred_register_work
Jun 18 15:42:50 pkxps kernel: [ 242.367024] Call Trace:
Jun 18 15:42:50 pkxps kernel: [ 242.367034] __schedule+0x291/0x870
Jun 18 15:42:50 pkxps kernel: [ 242.367040] ? __switch_to_asm+0x40/0x70
Jun 18 15:42:50 pkxps kernel: [ 242.367048] schedule+0x2c/0x80
Jun 18 15:42:50 pkxps kernel: [ 242.367056] schedule_preempt_disabled+0xe/0x10
Jun 18 15:42:50 pkxps kernel: [ 242.367063] __mutex_lock.isra.4+0x18c/0x4d0
Jun 18 15:42:50 pkxps kernel: [ 242.367069] ? __switch_to_asm+0x34/0x70
Jun 18 15:42:50 pkxps kernel: [ 242.367074] ? __switch_to_asm+0x34/0x70
Jun 18 15:42:50 pkxps kernel: [ 242.367083] __mutex_lock_slowpath+0x13/0x20
Jun 18 15:42:50 pkxps kernel: [ 242.367090] ? __mutex_lock_slowpath+0x13/0x20
Jun 18 15:42:50 pkxps kernel: [ 242.367097] mutex_lock+0x2f/0x40
Jun 18 15:42:50 pkxps kernel: [ 242.367104] power_supply_deferred_register_work+0x2b/0x50
Jun 18 15:42:50 pkxps kernel: [ 242.367112] process_one_work+0x1de/0x3e0
Jun 18 15:42:50 pkxps kernel: [ 242.367119] worker_thread+0x32/0x410
Jun 18 15:42:50 pkxps kernel: [ 242.367126] kthread+0x121/0x140
Jun 18 15:42:50 pkxps kernel: [ 242.367132] ? process_one_work+0x3e0/0x3e0
Jun 18 15:42:50 pkxps kernel: [ 242.367138] ? kthread_create_worker_on_cpu+0x70/0x70
Jun 18 15:42:50 pkxps kernel: [ 242.367144] ret_from_fork+0x35/0x40
Jun 18 15:43:18 pkxps kernel: [ 269.976729] rfkill: input handler enabled

Revision history for this message
Patrik Kullman (nomego) wrote :
Revision history for this message
Patrik Kullman (nomego) wrote :
Revision history for this message
Patrik Kullman (nomego) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
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.18 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.18-rc2

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: cosmic kernel-da-key
Changed in linux (Ubuntu Cosmic):
status: Confirmed → Incomplete
Revision history for this message
Patrik Kullman (nomego) wrote :
Changed in linux (Ubuntu Cosmic):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Patrik Kullman (nomego) wrote :

Not sure if you get these updates without a comment but I did try 4.18-rc2 and bug is still present.

Anything else I can do ?

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

Can you do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression.

Revision history for this message
Patrik Kullman (nomego) wrote :

Amazingly enough these issues seem resolved in 4.18-rc3! So 4.17 through 4.18-rc2 are affected, likely 4.17-rc? too.
Only weirdness in dmesg now is this, but I'm not sure of the implications:

[ 18.148559] pci_bus 0000:02: Allocating resources
[ 18.148627] pcieport 0000:02:01.0: bridge window [io 0x1000-0x0fff] to [bus 04-38] add_size 1000
[ 18.148650] pcieport 0000:02:02.0: bridge window [io 0x1000-0x0fff] to [bus 39] add_size 1000
[ 18.148658] pcieport 0000:02:02.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 39] add_size 200000 add_align 100000
[ 18.148681] pcieport 0000:01:00.0: bridge window [io 0x1000-0x0fff] to [bus 02-39] add_size 2000
[ 18.148693] pcieport 0000:01:00.0: BAR 13: no space for [io size 0x2000]
[ 18.148698] pcieport 0000:01:00.0: BAR 13: failed to assign [io size 0x2000]
[ 18.148707] pcieport 0000:01:00.0: BAR 13: no space for [io size 0x2000]
[ 18.148711] pcieport 0000:01:00.0: BAR 13: failed to assign [io size 0x2000]
[ 18.148731] pcieport 0000:02:02.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
[ 18.148736] pcieport 0000:02:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[ 18.148742] pcieport 0000:02:01.0: BAR 13: no space for [io size 0x1000]
[ 18.148746] pcieport 0000:02:01.0: BAR 13: failed to assign [io size 0x1000]
[ 18.148752] pcieport 0000:02:02.0: BAR 13: no space for [io size 0x1000]
[ 18.148756] pcieport 0000:02:02.0: BAR 13: failed to assign [io size 0x1000]
[ 18.148767] pcieport 0000:02:02.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
[ 18.148772] pcieport 0000:02:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[ 18.148777] pcieport 0000:02:02.0: BAR 13: no space for [io size 0x1000]
[ 18.148782] pcieport 0000:02:02.0: BAR 13: failed to assign [io size 0x1000]
[ 18.148787] pcieport 0000:02:01.0: BAR 13: no space for [io size 0x1000]
[ 18.148792] pcieport 0000:02:01.0: BAR 13: failed to assign [io size 0x1000]
[ 22.647320] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 22.647337] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 22.647355] pcieport 0000:00:1c.0: device [8086:9d10] error status/mask=00000001/00002000
[ 22.647386] pcieport 0000:00:1c.0: [ 0] Receiver Error (First)
[ 22.721810] pci_raw_set_power_state: 31 callbacks suppressed
[ 22.721812] pcieport 0000:02:00.0: Refused to change power state, currently in D3
[ 22.723448] pci_bus 0000:03: busn_res: [bus 03] is released
[ 22.723537] pci_bus 0000:04: busn_res: [bus 04-38] is released
[ 22.723601] pci_bus 0000:39: busn_res: [bus 39] is released
[ 22.724655] pci_bus 0000:02: busn_res: [bus 02-39] is released

Revision history for this message
Patrik Kullman (nomego) wrote :

Actually it didn't get solved with 4.18-rc3, but rather works on some boots.
Tried rc4 now and problem remains, I just haven't rebooted enough.

Hard to verify with a bisect as well.

Revision history for this message
Patrik Kullman (nomego) wrote :
Revision history for this message
Patrik Kullman (nomego) wrote :
Revision history for this message
Patrik Kullman (nomego) wrote :
Revision history for this message
Patrik Kullman (nomego) wrote :

Ok uploaded different dmesgs for the same kernel when the touchpad is working and not. (Two examples of when it's working)
When it's not working, the computer won't reboot/halt either.

Took me about 10-12 reboots to get one boot when it's working.

Revision history for this message
Patrik Kullman (nomego) wrote :

I haven't experienced this for a while now (since 4.19-rc1?), can be closed.

Kai-Heng Feng (kaihengfeng)
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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