Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1480602 - Kernel fails to suspend due to rmi_smbus
Summary: Kernel fails to suspend due to rmi_smbus
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-11 13:04 UTC by David H. Gutteridge
Modified: 2021-05-11 02:13 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)
journalctl -k output (274.77 KB, text/plain)
2017-08-11 13:05 UTC, David H. Gutteridge 		no flags Details
View All

Description David H. Gutteridge 2017-08-11 13:04:21 UTC 
Description of problem:

After upgrading to kernel 4.12.5-200.fc25, my Lenovo E531 fails to suspend. It has suspended with no issues from kernel 3.11 to 4.9, after which there were intermittent issues which I worked around by setting /sys/power/pm_async to 0. That workaround no longer applies with 4.12, instead the machine consistently fails to suspend.

Version-Release number of selected component (if applicable):
4.12.5-200.fc25

How reproducible:
Always

Steps to Reproduce:
1. Close lid of laptop
2. Observe it fails to suspend
3. Observe various messages in dmesg that relate to the failure

Actual results:
Failure to suspend

Expected results:
Suspension

Additional info:
Snippet from kernel log:

[ 2418.216600] PM: Syncing filesystems ... done.
[ 2418.711550] PM: Preparing system for sleep (mem)
[ 2418.712437] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 2418.715259] OOM killer disabled.
[ 2418.715261] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2418.716757] PM: Suspending system (mem)
[ 2418.716790] Suspending console(s) (use no_console_suspend to debug)
[ 2418.742342] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[ 2418.742345] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[ 2418.742347] rmi4_physical rmi4-00: Failed to suspend functions: -6
[ 2418.742350] rmi4_smbus 8-002c: Failed to suspend device: -6
[ 2418.742358] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[ 2418.742360] PM: Device 8-002c failed to suspend: error -6
[ 2418.742363] PM: Some devices failed to suspend, or early wake event detected
[ 2418.748592] PM: resume of devices complete after 6.223 msecs
[ 2418.748916] PM: resume devices took 0.006 seconds
[ 2418.748983] PM: Finishing wakeup.
[ 2418.748984] OOM killer enabled.
[ 2418.748987] Restarting tasks ... done.
[ 2418.751321] PM: Syncing filesystems ... 
[ 2418.764380] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[ 2418.948815] done.
[ 2418.948826] PM: Preparing system for sleep (freeze)
[ 2418.949090] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 2418.951905] OOM killer disabled.
[ 2418.951907] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2418.953392] PM: Suspending system (freeze)
[ 2418.953394] Suspending console(s) (use no_console_suspend to debug)
[ 2418.978304] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[ 2418.978307] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[ 2418.978310] rmi4_physical rmi4-00: Failed to suspend functions: -6
[ 2418.978312] rmi4_smbus 8-002c: Failed to suspend device: -6
[ 2418.978321] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[ 2418.978323] PM: Device 8-002c failed to suspend: error -6
[ 2418.978325] PM: Some devices failed to suspend, or early wake event detected
[ 2418.984840] PM: resume of devices complete after 6.509 msecs
[ 2418.985195] PM: resume devices took 0.007 seconds
[ 2418.985241] PM: Finishing wakeup.
[ 2418.985242] OOM killer enabled.
[ 2418.985244] Restarting tasks ... done.
Comment 1 David H. Gutteridge 2017-08-11 13:05:11 UTC 
Created attachment 1312139 [details]
journalctl -k output
Comment 2 David H. Gutteridge 2017-08-11 13:38:36 UTC 
Possibly related to bug 1431375.
Comment 3 David H. Gutteridge 2017-08-16 13:30:26 UTC 
I can also duplicate this with 4.12.5-300.fc26, unsurprisingly I suppose (I didn't see any differences in downstream patches between it and the Fedora 25 version). I've moved this bug to Fedora 26.
Comment 4 David H. Gutteridge 2017-09-02 18:05:58 UTC 
Still an issue with 4.12.9-300.fc26.
Comment 5 David H. Gutteridge 2017-09-09 04:07:10 UTC 
Still an issue with 4.12.11-300.fc26.
Comment 6 Torsten Casselt 2017-09-14 20:50:37 UTC 
Same here with Lenovo E540. Problem lies in the kernel module rmi_smbus. You can make the system suspend again if you unload rmi_smbus. Touchpad won’t work (if you even use it, I don’t).

WORKAROUND:

sudo modprobe -r rmi_smbus

Suspend should work. Touchpad not.
To make it persistent on reboots, add rmi_smbus to /etc/modprobe.d/backlist-touchpad.conf and run dracut -f.
Comment 7 Torsten Casselt 2017-09-19 17:50:01 UTC 
Not an issue anymore with 4.12.13-300.fc26. Thanks for the fix!
Comment 8 David H. Gutteridge 2017-09-19 23:10:47 UTC 
Unfortunately, with 4.12.13-300.fc26, this is still an issue with my hardware. No change.

Sep 18 20:38:20 arcusix.nonus-porta.net kernel: PM: Suspending system (mem)
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: Suspending console(s) (use no_console_suspend to debug)
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: psmouse serio3: Failed to disable mouse on synaptics-rmi4-pt/serio1
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: rmi4_physical rmi4-00: Failed to suspend functions: -6
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: rmi4_smbus 8-002c: Failed to suspend device: -6
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: PM: Device 8-002c failed to suspend: error -6
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: PM: Some devices failed to suspend, or early wake event detected
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: PM: resume of devices complete after 3.488 msecs
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: PM: resume devices took 0.004 seconds
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: PM: Finishing wakeup.
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: OOM killer enabled.
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: Restarting tasks ... done.
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: PM: Syncing filesystems ... 
Sep 18 20:38:20 arcusix.nonus-porta.net kernel: rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: done.
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: PM: Preparing system for sleep (freeze)
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: OOM killer disabled.
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: PM: Suspending system (freeze)
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: Suspending console(s) (use no_console_suspend to debug)
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: rmi4_physical rmi4-00: Failed to suspend functions: -6
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: rmi4_smbus 8-002c: Failed to suspend device: -6
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: PM: Device 8-002c failed to suspend: error -6
Sep 18 20:38:21 arcusix.nonus-porta.net kernel: PM: Some devices failed to suspend, or early wake event detected
Comment 9 nikita.marchant 2017-10-04 21:44:56 UTC 
I also have the same problem on a Lenovo L440 running 4.12.14-300.fc26.x86_64.

Sometimes, after a suspend (with the lid) the trackpad refuses to work and the system refuses to sleep, either by closing the lid or with systemctl suspend (du the suspend command does not complain).
I don't know the version of the last kernel that didn't have the problem but it has already been present for a few versions (but always fedora 26)

Running sudo modprobe -r rmi_smbus && sudo modprobe rmi_smbus in a shell does work to re-enable my trackpad and be able to suspend again.

Here is the output of dmesg when i do a systemctl suspend :

[51649.195601] e1000e: enp0s25 NIC Link is Down
[51649.225066] wlp2s0: deauthenticating from 84:a1:d1:46:d9:8f by local choice (Reason: 3=DEAUTH_LEAVING)
[51649.241030] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[51649.455308] PM: Syncing filesystems ... done.
[51649.547391] PM: Preparing system for sleep (mem)
[51649.548292] Freezing user space processes ... (elapsed 0.003 seconds) done.
[51649.551666] OOM killer disabled.
[51649.551667] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[51649.553634] PM: Suspending system (mem)
[51649.553672] Suspending console(s) (use no_console_suspend to debug)
[51649.554368] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[51649.554370] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[51649.554372] rmi4_physical rmi4-00: Failed to suspend functions: -6
[51649.554375] rmi4_smbus 9-002c: Failed to suspend device: -6
[51649.554381] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[51649.554383] PM: Device 9-002c failed to suspend: error -6
[51649.554384] PM: Some devices failed to suspend, or early wake event detected
[51649.555014] PM: resume of devices complete after 0.627 msecs
[51649.555287] PM: resume devices took 0.001 seconds
[51649.555555] PM: Finishing wakeup.
[51649.555555] OOM killer enabled.
[51649.555556] Restarting tasks ... done.
[51649.558639] PM: Syncing filesystems ... 
[51649.566198] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[51649.569394] done.
[51649.569397] PM: Preparing system for sleep (freeze)
[51649.569586] Freezing user space processes ... (elapsed 0.002 seconds) done.
[51649.572224] OOM killer disabled.
[51649.572225] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[51649.573467] PM: Suspending system (freeze)
[51649.573468] Suspending console(s) (use no_console_suspend to debug)
[51649.574013] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[51649.574014] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[51649.574015] rmi4_physical rmi4-00: Failed to suspend functions: -6
[51649.574017] rmi4_smbus 9-002c: Failed to suspend device: -6
[51649.574021] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[51649.574022] PM: Device 9-002c failed to suspend: error -6
[51649.574023] PM: Some devices failed to suspend, or early wake event detected
[51649.574541] PM: resume of devices complete after 0.517 msecs
[51649.574759] PM: resume devices took 0.001 seconds
[51649.574777] PM: Finishing wakeup.
[51649.574778] OOM killer enabled.
[51649.574778] Restarting tasks ... done.
[51649.585795] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[51649.589488] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[51649.814440] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[51649.816481] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[51649.818198] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[51649.818500] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[51650.041295] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[51650.041580] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[51650.055524] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[51650.099479] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[51653.526858] wlp2s0: authenticate with 84:a1:d1:46:d9:8f
[51653.529285] wlp2s0: send auth to 84:a1:d1:46:d9:8f (try 1/3)
[51653.532374] wlp2s0: authenticated
[51653.533127] wlp2s0: associate with 84:a1:d1:46:d9:8f (try 1/3)
[51653.535616] wlp2s0: RX AssocResp from 84:a1:d1:46:d9:8f (capab=0x511 status=0 aid=42)
[51653.537191] wlp2s0: associated
[51653.537239] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[51653.573662] wlp2s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 84:a1:d1:46:d9:8f
Comment 10 David H. Gutteridge 2017-10-14 18:55:40 UTC 
Still an issue with kernel 4.13.6.
Comment 11 David H. Gutteridge 2017-10-30 23:44:02 UTC 
Still an issue with kernel 4.13.10. ("sudo modprobe -r rmi_smbus" is an effective workaround for me, but obviously not optimal...)
Comment 12 David H. Gutteridge 2017-12-05 14:02:08 UTC 
(Updating version to Fedora 27. Still an issue with kernel 4.14.3.)
Comment 13 David H. Gutteridge 2018-02-10 18:25:29 UTC 
Still an issue with kernel 4.15.2.
Comment 14 Dan Kenigsberg 2018-02-19 07:19:59 UTC 
Also with 4.15.3-300.fc27.x86_64
Comment 15 Aleksandar Kostadinov 2018-03-08 09:26:03 UTC 
On T460p with 4.14 things worked well for me. Now upgraded to 4.15.6-300.fc27.x86_64 and I needed to reload `rmi_smbus` module for suspend to start working.

Touchpad doesn't seem to work though before and after module reload. I need to try a reboot or something to be sure though.
Comment 16 Brad 2018-03-17 21:57:35 UTC 
(In reply to Aleksandar Kostadinov from comment #15)
> On T460p with 4.14 things worked well for me. Now upgraded to
> 4.15.6-300.fc27.x86_64 and I needed to reload `rmi_smbus` module for suspend
> to start working.
> 
> Touchpad doesn't seem to work through before and after the module reload. I need
> to try a reboot or something to be sure though.

I also own a T460p and have identical behavior on 4.15.9-300.fc27.x86_64. I just noticed it this week after restarting my computer for the first time in 2 months (over which several kernel upgrades took place). reloading `rmi_smbus` allows me to suspend again, but I was unable to get the trackpad and TrackPoint working again without a reboot.
Comment 17 David H. Gutteridge 2018-03-17 22:15:30 UTC 
(In reply to Brad from comment #16)
> (In reply to Aleksandar Kostadinov from comment #15)
> > On T460p with 4.14 things worked well for me. Now upgraded to
> > 4.15.6-300.fc27.x86_64 and I needed to reload `rmi_smbus` module for suspend
> > to start working.
> > 
> > Touchpad doesn't seem to work through before and after the module reload. I need
> > to try a reboot or something to be sure though.
> 
> I also own a T460p and have identical behavior on 4.15.9-300.fc27.x86_64. I
> just noticed it this week after restarting my computer for the first time in
> 2 months (over which several kernel upgrades took place). reloading
> `rmi_smbus` allows me to suspend again, but I was unable to get the trackpad
> and TrackPoint working again without a reboot.

The T460p issues -- only those -- should be resolved with kernel 4.15.10, which is now in testing. It has the following change applied:

commit 9f30ff6fa1a4b6075309163af33ca4d59ba8c9ae
Author: Arkadiusz Hiler <arkadiusz.hiler>
Date:   Wed Mar 7 15:40:28 2018 -0800

    Revert "Input: synaptics - Lenovo Thinkpad T460p devices should use RMI"
    
    commit 5444a992b4a73aa5246a432c482b20b89bce93a5 upstream.

The Fedora 27 update is here:

https://bodhi.fedoraproject.org/updates/FEDORA-2018-959aac67a3
Comment 18 David H. Gutteridge 2018-03-21 23:07:43 UTC 
I built a custom 4.15 kernel using Fedora's config-4.15.10-300.fc27.x86_64 as the basis, the only difference being I disabled the CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS option. That resolved the issue for me: my laptop now suspends and resumes consistently and the track pad works (such that I need it to) as before.
Comment 19 Aleksandar Kostadinov 2018-03-22 09:50:45 UTC 
Forgot to reply. T460p with 4.15.10 works fine here. With the older 4.15 I saw another driver have been used and input device name changed. Now things are back to how they worked in 4.14. So at least T460p is covered.
Comment 20 David H. Gutteridge 2018-06-06 00:50:22 UTC 
With kernel 4.16.14, the details in the output are a little different than I originally noted, e.g. "rmi_driver_clear_irq_bits: Failed to change enabled interrupts!".

[  858.876344] Suspending console(s) (use no_console_suspend to debug)
[  858.876996] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[  858.877008] psmouse serio3: Failed to disable mouse on rmi4-00.fn03/serio0
[  858.877377] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[  858.877724] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[  858.878189] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[  858.878192] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[  858.878195] rmi4_physical rmi4-00: Failed to suspend functions: -6
[  858.878201] rmi4_smbus 8-002c: Failed to suspend device: -6
[  858.878211] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[  858.878214] PM: Device 8-002c failed to suspend: error -6
[  858.878217] PM: Some devices failed to suspend, or early wake event detected
[  858.878596] PM: resume devices took 0.000 seconds
[  858.878634] OOM killer enabled.
[  858.878636] Restarting tasks ... done.
[  858.880161] PM: suspend exit
[  858.880273] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[  858.880377] PM: suspend entry (s2idle)
[  858.880379] PM: Syncing filesystems ... 
[  858.880626] rmi4_physical rmi4-00: rmi_driver_clear_irq_bits: Failed to change enabled interrupts!
[  858.894723] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts!
[  858.894734] psmouse: probe of serio3 failed with error -1
Comment 21 Jan Kratochvil 2018-06-09 20:24:13 UTC 
kernel-4.16.8-300.fc28.x86_64

rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
rmi4_physical rmi4-00: Failed to suspend functions: -6
rmi4_smbus 9-002c: Failed to suspend device: -6
dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
PM: Device 9-002c failed to suspend: error -6 
PM: Some devices failed to suspend, or early wake event detected
PM: resume devices took 0.000 seconds
OOM killer enabled.
Restarting tasks ... done.
rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts!
psmouse: probe of serio3 failed with error -1
PM: suspend exit

        Manufacturer: LENOVO
        Product Name: 37021K8
        Version: ThinkPad Helix
        SKU Number: LENOVO_MT_3702
        Family: ThinkPad Helix
Comment 22 Justin M. Forbes 2018-07-23 14:55:20 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 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.
Comment 23 David H. Gutteridge 2018-07-23 16:35:55 UTC 
This issue is still present in 4.17.7-200.fc28.
Comment 24 David H. Gutteridge 2018-09-12 04:23:37 UTC 
With kernel 4.18.5-200.fc28, the situation has changed. Now if I don't use "modprobe -r rmi_smbus", if I close the lid, not only does it fail to suspend, but the trackpad stops working regardless (whereas before, the trackpad still worked). If I use "modprobe -r rmi_smbus" and then "modprobe rmi_smbus", that doesn't bring the trackpad back. I now see these errors as well:

[ 9136.591215] rmi4_smbus 8-002c: failed to get SMBus version number!
Comment 25 Laura Abbott 2018-10-01 21:14:27 UTC 
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 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.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.
Comment 26 David H. Gutteridge 2018-10-02 14:32:20 UTC 
This is still an issue with 4.18.11-200.fc28.

[  200.234196] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[  200.234199] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[  200.234201] rmi4_physical rmi4-00: Failed to suspend functions: -6
[  200.234206] rmi4_smbus 8-002c: Failed to suspend device: -6
[  200.234215] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[  200.234217] PM: Device 8-002c failed to freeze: error -6
[  200.306391] PM: Basic memory bitmaps freed
[  200.306392] OOM killer enabled.
[  200.306394] Restarting tasks ... 
[  200.306418] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[  200.307591] rmi4_physical rmi4-00: rmi_driver_clear_irq_bits: Failed to change enabled interrupts!
[  200.309344] done.
[  200.327177] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts!
[  200.327191] psmouse: probe of serio3 failed with error -1
Comment 27 Justin M. Forbes 2019-01-29 16:24:17 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 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.
Comment 28 David H. Gutteridge 2019-02-05 02:52:30 UTC 
Bug still present with 4.20.6-200.fc29. Moving version to 29. Error basically the same output as before.

[  614.058930] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[  614.058932] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[  614.058935] rmi4_physical rmi4-00: Failed to suspend functions: -6
[  614.058940] rmi4_smbus 8-002c: Failed to suspend device: -6
[  614.058948] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[  614.058950] PM: Device 8-002c failed to freeze: error -6
[  614.169102] iwlwifi 0000:04:00.0: Radio type=0x2-0x0-0x0
[  614.437221] iwlwifi 0000:04:00.0: Radio type=0x2-0x0-0x0
[  614.514604] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[  614.514834] PM: Basic memory bitmaps freed
[  614.514835] OOM killer enabled.
[  614.514836] Restarting tasks ... 
[  614.514977] rmi4_physical rmi4-00: rmi_driver_clear_irq_bits: Failed to change enabled interrupts!
[  614.517599] done.
[  614.527662] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts!
[  614.527672] psmouse: probe of serio3 failed with error -1
Comment 29 Justin M. Forbes 2019-08-20 17:39:49 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 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.
Comment 30 David H. Gutteridge 2019-08-20 21:36:22 UTC 
Still an issue with 5.2.9-200.fc30.x86_64.

[  955.794352] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[  955.794355] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[  955.794358] rmi4_physical rmi4-00: Failed to suspend functions: -6
[  955.794361] rmi4_smbus 8-002c: Failed to suspend device: -6
[  955.794372] PM: dpm_run_callback(): rmi_smb_suspend+0x0/0x30 [rmi_smbus] returns -6
[  955.794400] PM: Device 8-002c failed to suspend: error -6
[  955.815728] PM: Some devices failed to suspend, or early wake event detected
[  956.156816] PM: resume devices took 0.341 seconds
[  956.156821] OOM killer enabled.
[  956.156822] Restarting tasks ... done.
[  956.161344] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts!
Comment 31 Justin M. Forbes 2020-03-03 16:25:55 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 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.
Comment 32 David H. Gutteridge 2020-03-04 23:01:42 UTC 
Still an issue with 5.5.7-200.fc31.x86_64.

[  213.129278] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[  213.129281] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[  213.129283] rmi4_physical rmi4-00: Failed to suspend functions: -6
[  213.129288] rmi4_smbus 8-002c: Failed to suspend device: -6
[  213.129294] PM: dpm_run_callback(): rmi_smb_suspend+0x0/0x30 [rmi_smbus] returns -6
[  213.129296] PM: Device 8-002c failed to freeze: error -6
[  213.244165] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[  213.244555] rmi4_physical rmi4-00: rmi_driver_clear_irq_bits: Failed to change enabled interrupts!
[  213.257192] iwlwifi 0000:04:00.0: Radio type=0x2-0x0-0x0
[  213.525566] iwlwifi 0000:04:00.0: Radio type=0x2-0x0-0x0
[  213.582559] PM: Basic memory bitmaps freed
[  213.582562] OOM killer enabled.
[  213.582563] Restarting tasks ... 
[  213.586058] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts!
[  213.586076] psmouse: probe of serio3 failed with error -1
[  213.593562] done.
Comment 33 Ben Cotton 2020-11-03 17:00:29 UTC 
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.
Comment 34 David H. Gutteridge 2020-11-24 04:10:55 UTC 
Still an issue with 5.9.9-200.fc33.x86_64.

[  161.501544] printk: Suspending console(s) (use no_console_suspend to debug)
[  161.502072] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[  161.502075] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[  161.502077] rmi4_physical rmi4-00: Failed to suspend functions: -6
[  161.502119] rmi4_smbus 8-002c: Failed to suspend device: -6
[  161.502123] PM: dpm_run_callback(): rmi_smb_suspend+0x0/0x30 [rmi_smbus] returns -6
[  161.502124] PM: Device 8-002c failed to freeze: error -6
[  161.589020] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[  161.589482] rmi4_physical rmi4-00: rmi_driver_clear_irq_bits: Failed to change enabled interrupts!
[  161.925628] PM: hibernation: Basic memory bitmaps freed
[  161.925629] OOM killer enabled.
[  161.925630] Restarting tasks ... done.
[  161.928651] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts!
[  161.928661] psmouse: probe of serio3 failed with error -1
[  162.179383] PM: hibernation: hibernation exit
Comment 35 David H. Gutteridge 2021-05-11 02:13:14 UTC 
I've found setting "psmouse.synaptics_intertouch=0" in grub's kernel command line resolves the issue for me. (I finally got around to reading the driver code.)

(Otherwise, still an issue with 5.11.18-300.fc34.x86_64.)
Note You need to log in before you can comment on or make changes to this bug.