Bug 1558493 - Mouse on Thinkpad t460p non-responsive after resuming from suspend with 4.15.x kernels
Summary: Mouse on Thinkpad t460p non-responsive after resuming from suspend with 4.15....
Keywords:
Status: CLOSED DUPLICATE of bug 1548867
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-20 10:45 UTC by Daniel Berrangé
Modified: 2018-03-20 17:21 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-20 17:21:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg showing 4.15.9-300.fc27.x86_64 boot, suspend, resume sequence with errors on resume (117.86 KB, text/plain)
2018-03-20 10:45 UTC, Daniel Berrangé
no flags Details

Description Daniel Berrangé 2018-03-20 10:45:47 UTC
Created attachment 1410414 [details]
dmesg showing 4.15.9-300.fc27.x86_64 boot, suspend, resume sequence with errors on resume

Description of problem:
Since upgrading my Fedora 27 kernel to 4.15.7, the mouse pointer on my Thinkpad t460p laptop is always non-responsive after resuming from suspend. I also tried 4.15.9 with same results.

NB I am using the TrackPoint, and have the TrackPad disabled.

This a regression from 4.14.x series of kernels, where the mouse worked fine after suspend, so I have dropped back to using kernel-4.14.18-300.fc27.x86_64 to avoid the problem.

There are various suspicious looking errors in kernel dmesg when resuming from suspend  - I will attach the full dmesg log to this bug

Mar 20 09:22:19 localhost.localdomain kernel: rmi4_smbus 11-002c: failed to get SMBus version number!
Mar 20 09:22:19 localhost.localdomain kernel: rmi4_physical rmi4-00: rmi_driver_reset_handler: Failed to read current IRQ mask.
Mar 20 09:22:19 localhost.localdomain kernel: rmi4_f01 rmi4-00.fn01: Failed to restore normal operation: -16.
Mar 20 09:22:19 localhost.localdomain kernel: rmi4_f01 rmi4-00.fn01: Resume failed with code -16.
Mar 20 09:22:19 localhost.localdomain kernel: rmi4_physical rmi4-00: Failed to suspend functions: -16
Mar 20 09:22:19 localhost.localdomain kernel: rmi4_smbus 11-002c: Failed to resume device: -16
Mar 20 09:22:19 localhost.localdomain kernel: rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-16).
Mar 20 09:22:19 localhost.localdomain kernel: rmi4_physical rmi4-00: rmi_driver_clear_irq_bits: Failed to change enabled interrupts!
Mar 20 09:22:19 localhost.localdomain kernel: usb 1-3.4: reset high-speed USB device number 4 using xhci_hcd
Mar 20 09:22:19 localhost.localdomain kernel: usb 1-7:1.0: rebind failed: -517
Mar 20 09:22:19 localhost.localdomain kernel: usb 1-7:1.1: rebind failed: -517
Mar 20 09:22:19 localhost.localdomain kernel: PM: resume devices took 1.614 seconds
Mar 20 09:22:19 localhost.localdomain kernel: rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts!
Mar 20 09:22:19 localhost.localdomain kernel: psmouse: probe of serio3 failed with error -1


Version-Release number of selected component (if applicable):
kernel-4.15.7-300.fc27.x86_64
kernel-4.15.9-300.fc27.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Boot 4.15.7 kernel until GDM login screen is ready
2. Press power button to trigger suspend to RAM
3. Wait for suspend to fully complete
4. Press power button again to trigger wakeup from suspend
5. Try to mouse the mouse using the TrackPoint

Actual results:
The mouse pointer will not move, button presses have no effect

Expected results:
Normal mouse operation

Additional info:

Comment 1 Jeremy Cline 2018-03-20 17:21:52 UTC
Hi,

This should be fixed in 4.15.10.

*** This bug has been marked as a duplicate of bug 1548867 ***


Note You need to log in before you can comment on or make changes to this bug.