Description of problem: The device will freeze. Version-Release number of selected component (if applicable): kernel-4.12.8-300.fc26.x86_64 How reproducible: Every time. Steps to Reproduce: 1. wait for suspend 2. let it wake up Actual results: The touchpad is frozen. Expected results: Working touchpad Additional info: Device: Lenovo T440p Journal: Aug 24 22:00:02 foo kernel: rmi4_smbus 21-002c: failed to get SMBus version number! Aug 24 22:00:02 foo kernel: rmi4_physical rmi4-00: rmi_driver_reset_handler: Failed to read current IRQ mask. Aug 24 22:00:02 foo kernel: rmi4_f01 rmi4-00.fn01: Failed to restore normal operation: -6. Aug 24 22:00:02 foo kernel: rmi4_f01 rmi4-00.fn01: Resume failed with code -6. Aug 24 22:00:02 foo kernel: rmi4_physical rmi4-00: Failed to suspend functions: -6 Aug 24 22:00:02 foo kernel: rmi4_smbus 21-002c: Failed to resume device: -6 Aug 24 22:00:02 foo kernel: rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6). Aug 24 22:00:02 foo kernel: rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
Workaround: modprobe -r rmi_smbus;modprobe rmi_smbus after wake up
I confirm that I'm experiencing the same bug with same messages on a Thinkpad L540 running Arch Linux with the same kernel 4.12.8. Must have appeared after some of the recent (kernel?) updates.
Same on a Lenovo X1 Carbon (20A7 series), but happens randomly on wakeup, not every time.
Also affected by this on Lenovo X1 Carbon. Both touchpad + trackpoint. Also happens randomly. Fedora 27.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. 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 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those.
On 4.14.18-200 it will happens not so often more. But some times only the reload of of the modules will work. The 4.15 tree can't tested at this time, because the power management for this device it broken. So I market it as an blocker bug for this problem.
I have the same issue. After any sleep, touchpad is not working and workaround does not work to me. # uname -a Linux rstancel-rht.rstancel 4.15.8-300.fc27.x86_64 #1 SMP Fri Mar 9 18:11:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux My laptop is Lenovo ThinkPad T460
still happens on 4.15.10-300.fc27.x86_64. 'rmmod rmi_smbus ; insmod rmi_smbus' works, though.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Kernel 4.17.2 will have the same problem. So reopen it.
It looks better with 4.18rc1
*********** 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 28 kernel bugs. Fedora 28 has now been rebased to 4.17.7-200.fc28. 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 experience different issues, please open a new bug report for those.
The Problem still exits with 4.17
Created attachment 1469990 [details] Journal log after wake up
Problem is worse with 4.17 than with 4.16. uname -r 4.17.12-200.fc28.x86_64 kernel: PM: suspend entry (s2idle) kernel: PM: Syncing filesystems ... done. kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. kernel: OOM killer disabled. kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. kernel: Suspending console(s) (use no_console_suspend to debug) kernel: rmi4_f01 rmi4-01.fn01: Failed to write sleep mode: -6. kernel: rmi4_f01 rmi4-01.fn01: Suspend failed with code -6. kernel: rmi4_physical rmi4-01: Failed to suspend functions: -6 kernel: rmi4_smbus 10-002c: Failed to suspend device: -6 kernel: dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 kernel: PM: Device 10-002c failed to suspend: error -6 kernel: PM: Some devices failed to suspend, or early wake event detected kernel: PM: resume devices took 0.001 seconds kernel: OOM killer enabled. kernel: Restarting tasks ... done. kernel: rmi4_physical rmi4-01: rmi_driver_set_irq_bits: Failed to change enabled interrupts! kernel: psmouse: probe of serio4 failed with error -1 kernel: PM: suspend exit
Can you try it with 4.18? On my system it looks much better.
On 4.18 I got the same error today. But I noticed it has been quite some time from the last time it occoured
On 4.18 I got the same error today. But I noticed it has been quite some time from the last time it occurred
It feels like it's getting worse with 4.18.11-200.fc28.x86_64 :\ [92747.719271] usb 1-1.5: reset full-speed USB device number 3 using ehci-pci [92747.811564] rmi4_smbus 10-002c: failed to get SMBus version number! [92747.811969] rmi4_physical rmi4-04: rmi_driver_reset_handler: Failed to read current IRQ mask. [92747.812391] rmi4_f01 rmi4-04.fn01: Failed to restore normal operation: -6. [92747.812394] rmi4_f01 rmi4-04.fn01: Resume failed with code -6. [92747.812397] rmi4_physical rmi4-04: Failed to suspend functions: -6 [92747.812400] rmi4_smbus 10-002c: Failed to resume device: -6 [92747.816963] rmi4_f03 rmi4-04.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6). [92747.817352] rmi4_physical rmi4-04: rmi_driver_clear_irq_bits: Failed to change enabled interrupts! [92747.832939] rmi4_physical rmi4-04: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [92747.832949] psmouse: probe of serio7 failed with error -1
Hi, I don't get this error when I suspend my Thinkpad Yoga 260 (Fedora 28 and 4.18.16), but I have the problem that the trackpoint freezes around 1-3 time per week and I can fix it by restarting the whole machine or by entering this command: sudo sh -c 'echo -n "elantech" > /sys/bus/serio/devices/serio1/protocol' afterwards everything is back to normal. Hope I can help with this info. Greetings, albflo
I just started to see the same issue with fedora 29 on Thinkpad T540p. Strange is that that issue is affecting keyboard as well - I can not log in after suspend as the after suspend splash screen can not be closed by mouse nor keyboard. At the same time I can switch to virtual console and run "sudo modprobe -r rmi_smbus;sudo modprobe rmi_smbus" there. Switching back to log in screen does let me carry on as usual. For me I see it more as a Gnome issue, because I tested it with even f28 kernels - all are affected. gnome-session-3.30.1-2.fc29.x86_64
*********** 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 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. 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 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
Set to F29, because it will also happens on it. (kernel-4.20.10-200.fc29.x86_64) It looks like it will only happens when the device will run in battery mode.
*********** 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 29 kernel bugs. Fedora 29 has now been rebased to 5.2.9-100.fc29. 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 30, and are still experiencing this issue, please change the version to Fedora 30. If you experience different issues, please open a new bug report for those.
It will still happens randomly. :(
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still happens on F30. Can we please change the 'version' to 30? Thanks.
Still happens on F31 :)
Again happens on: Fedora 31 - HP elitebook 840 G6
*********** 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 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. 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 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
It will some times happens using the last kernel of Fedora 31 also. But only when it runs on battery.
Still happens randomly on F31 on battery and on power supply. Interestingly sometimes the problem doesn't occur at all for days and tons of suspend/resumes, but then, after a reboot, it happens again on every suspend/resume. Might have something to do with whether or not the laptop has been on power supply while booting. Not sure, need to confirm.
Still happens on F32 using kernel 5.6.8-300.fc32.x86_64.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
It will happens also on F32 sometimes, when the device will run on battery.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Please change the version to at least 33. Thanks!
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The same will happens on F33. But only when the device is running on battery and then goes to deep sleep. Then when it wakes up sometimes the touchepad will fails until the kernel module rmi_smbus will be reloaded.
Please reopen. This bug is still not fixed in F36 kernel 5.19.14-200.fc36.x86_64. > kernel: rmi4_f03 rmi4-05.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6). > kernel: rmi4_physical rmi4-05: rmi_driver_clear_irq_bits: Failed to change enabled interrupts! > kernel: rmi4_physical rmi4-05: rmi_driver_set_irq_bits: Failed to change enabled interrupts! > kernel: psmouse: probe of serio8 failed with error -1 > kernel: PM: suspend exit
Issue still exists on F37, kernel 6.1.7-200.fc37.x86_64 Workaround: # modprobe -r rmi_smbus # modprobe rmi_smbus Works for me.
(In reply to Marek Salwerowicz from comment #41) > Issue still exists on F37, kernel 6.1.7-200.fc37.x86_64 > > Workaround: > > # modprobe -r rmi_smbus > # modprobe rmi_smbus > > > Works for me. Thanks, I just upgraded my Thinkpad T540p to Fedora 37 (kernel 6.2.15-200.fc37.x86_64) and this workaround also works for me.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.