Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xiaomi-vince: power management issues (supend transitions, i2c/smbus, synaptic rmi4) #167

Open
spongy-deluxe opened this issue Jan 31, 2024 · 2 comments

Comments

@spongy-deluxe
Copy link

spongy-deluxe commented Jan 31, 2024

Hi,

currently I am experiencing issues with postmarket OS on my Xiaomi Redmi 5 Plus. I am using a dual-boot configuration with lk2nd flashed to recovery and postmarket OS flashed on an external SD card.

The issues are most likely power management related. When they set in, the phone turns the screen on, shows the lockscreen and then turns off again after a while. The dmesg output (obtained via ssh) shows [ 8324.012680] ltrf216a 0-0053: failed to resume runtime PM: -22 repeatedly (with a frequency of 3 to 5 times per second). Finally the touchscreen becomes unresponsive and cannot be used anymore - hardware buttons still work.

I assume these issues occur because some problems with the power management. At first I suspected the bit banging of the I2C bus might be responsible but idk.

I have tested the kernels 6.6.10 and 6.7.0 (head) both yield the same behavior.

(I am not sure but the issue often occurred after I unplugged the phone from my computer's USB. Yet the issue also occurs after just setting the phone to standby.)

Do you have any clues what the underlying issue might be?

EDIT-1: Added dmesg log on linux 6.7.0. Pattern repeats at regular intervals. Only CPU failure differs.

postmarketos-xiaomi-vince-linux-6.7.0-86d576e1465a5216cb2f1bb420fa39d5f85cf52c.txt

EDIT-2: Added dmesg log on linux 6.7.0. Pattern occurs when standby button is pressed for a short time.

postmarketos-xiaomi-vince-linux-6.7.0-86d576e1465a5216cb2f1bb420fa39d5f85cf52c-short_power_button_press.txt

EDIT-3: I have verified that the problems persist in version 6.7.2-r0 (with modification CONFIG_RT_GROUP_SCHED=n).

The line [ 8324.012680] ltrf216a 0-0053: failed to resume runtime PM: -22 now only shows when the device is woken up. Pressing hardware buttons does not seem to result in errors anymore.

There is still the wake up behavior where the display randomly turns on and runs down the battery.

postmarketos-xiaomi-vince-linux-6.7.2-r0__standby_button_on_and_off.txt

EDIT-4: The issues usually start when the phone tries to go into power saving mode (as set up in the energy settings, for me after approx. 15 minutes on battery or connected to mains).

EDIT-5: In the following log the above described issue start [ 1752.862237] PM: suspend entry (s2idle).

xiaomi-6.7.2-r0_dmesg_when_auto_standby_kicks_in_after_15min.txt

The most important lines (before the suspend is stopped and then retried again):

[ 1752.899606] wcn36xx: ERROR SMD_EVENT (312) not supported
[ 1753.049071] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[ 1753.049095] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[ 1753.049106] rmi4_physical rmi4-00: Failed to suspend functions: -6
[ 1753.049128] rmi4_i2c 2-0020: Failed to resume device: -6
[ 1753.049147] rmi4_i2c 2-0020: PM: dpm_run_callback(): rmi_i2c_suspend+0x0/0x6c [rmi_i2c] returns -6
[ 1753.049192] rmi4_i2c 2-0020: PM: failed to suspend async: error -6
[ 1753.049494] PM: Some devices failed to suspend, or early wake event detected

Related:


EDIT-6: Okay, after digging through the kernel mailing list, this seems to be a long standing issue of the RMI4 driver. It seems not to model parent child relations properly, so that the power management suspends certain parts of the platform that are still needed (as far as I understood the child relationship to the I2C device is modeled properly but there are other undiscovered dependencies).

  • The asynchronous suspend mechanism might trigger this issue because RMI4 might be suspended earlier or later than defined by the hardware declaration order.
    • Disabling async suspend, might help if the declaration order was working before async suspend was enabled.

Related discussions:

Kernel discussion

Issue related commits:

  • 5b6164d ("driver core: Reorder devices on successful probe")
  • 172d931 ("i2c: enable async suspend/resume on i2c client devices")

Collection of magical workarounds (mostly hiding the issues with some likelihood):

  • Sometimes suggested but ineffective for vince (no psmouse module): Add psmouse.synaptics_intertouch=0 to kernel boot cmdline
  • Add fw_devlink=on to kernel boot cmdline
  • Revert ("driver core: Reorder devices on successful probe")
  • Revert ("i2c: enable async suspend/resume on i2c client devices")

Workaround for pmos:

  • Go to energy settings and disable "automatic suspend after x minutes" for both "on battery" and "connected to AC"
  • Locking the device via hardware button seems to work for vince (I guess only the screen is turned off and the screen locked)
@spongy-deluxe spongy-deluxe changed the title xiaomi-vince: I2C power management issues xiaomi-vince: power management issues (supend transmissions and I2C) Feb 2, 2024
@spongy-deluxe spongy-deluxe changed the title xiaomi-vince: power management issues (supend transmissions and I2C) xiaomi-vince: power management issues (supend transitions and I2C) Feb 2, 2024
@spongy-deluxe spongy-deluxe changed the title xiaomi-vince: power management issues (supend transitions and I2C) xiaomi-vince: power management issues (supend transitions, I2C/smbus, synaptic rmi4) Feb 3, 2024
@spongy-deluxe spongy-deluxe changed the title xiaomi-vince: power management issues (supend transitions, I2C/smbus, synaptic rmi4) xiaomi-vince: power management issues (supend transitions, i2c/smbus, synaptic rmi4) Feb 3, 2024
@barni2000
Copy link
Member

Hi @spongy-deluxe is this still issue with 6.8.2?

@spongy-deluxe
Copy link
Author

spongy-deluxe commented May 15, 2024

Hi @barni2000

yes, I still have this issue with a modified linux 6.8.2.

I have tested whether async suspend is the problem (okay, probably it was more of a "quick and dirty" test).
I just removed all calls to device_enable_async_suspend from the linux 6.8.2 codebase. However, this did not solve the issues (and perhaps caused even more issues in the dmesg output).

Next I'll try again with postmarket's vanilla 6.8.2-r1 and extend this answer. After that I am going to build and try the 6.9.0 kernel.


Results for 6.9.0

The problem still persists. Trying to enter suspend is aborted shortly after the screen turns off for a second.

After the failed suspend the touchscreen does not work anymore (until a reboot is done).

Remark: The kernel config was a custom migration from the current config

dmesg:

[   91.651428] PM: suspend entry (s2idle)
[   91.751057] Filesystems sync: 0.099 seconds
[   91.755845] Freezing user space processes
[   91.797027] Freezing user space processes completed (elapsed 0.041 seconds)
[   91.797057] OOM killer disabled.
[   91.797062] Freezing remaining freezable tasks
[   91.800319] Freezing remaining freezable tasks completed (elapsed 0.003 seconds)
[   91.800332] printk: Suspending console(s) (use no_console_suspend to debug)
[   92.002326] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
[   92.030103] wcn36xx: ERROR SMD_EVENT (312) not supported
[   92.163485] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[   92.163509] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[   92.163522] rmi4_physical rmi4-00: Failed to suspend functions: -6
[   92.163541] rmi4_i2c 2-0020: Failed to resume device: -6
[   92.163559] rmi4_i2c 2-0020: PM: dpm_run_callback(): rmi_i2c_suspend+0x0/0x6c [rmi_i2c] returns -6
[   92.163602] rmi4_i2c 2-0020: PM: failed to suspend async: error -6
[   92.164000] PM: Some devices failed to suspend, or early wake event detected
[   92.607080] OOM killer enabled.
[   92.607097] Restarting tasks ... done.
[   92.614662] random: crng reseeded on system resumption
[   92.614701] PM: suspend exit
[   92.614880] PM: suspend entry (s2idle)
[   92.719196] ------------[ cut here ]------------
[   92.719212] WARNING: CPU: 3 PID: 6928 at drivers/gpu/drm/msm/disp/mdp5/mdp5_pipe.c:138 mdp5_pipe_release+0xbc/0xcc [msm]
[   92.719351] Modules linked in: sch_ingress veth overlay nft_masq nft_chain_nat nf_nat bridge stp llc zram zsmalloc fuse wcn36xx mac80211 libarc4 cfg80211 btqcomsmd btqca nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bluetooth ecdh_generic ecc rfkill wcnss_ctrl q6asm_dai q6routing q6voice_dai q6afe_dai q6voice q6afe_clocks q6adm q6asm snd_q6dsp_common q6afe q6mvm q6cvp q6cvs q6voice_common q6core apr pdr_interface ipv6 qrtr_smd ledtrig_pattern crct10dif_ce qcom_q6v5_pas qcom_q6v5_mss qcom_wcnss_pil snd_soc_apq8016_sbc qcom_q6v5 qcom_pil_info snd_soc_msm8916_digital snd_soc_qcom_common ipa2_lite qcom_sysmon leds_aw2013 qcom_common venus_enc venus_dec videobuf2_dma_contig ov5675 qcom_camss st_lsm6dsx_spi venus_core videobuf2_dma_sg videobuf2_memops v4l2_mem2mem videobuf2_v4l2 qcom_spmi_vadc v4l2_fwnode qcom_spmi_temp_alarm rtc_pm8xxx qcom_vadc_common videobuf2_common v4l2_async qcom_pon reboot_mode snd_soc_msm8916_analog videodev mc i2c_qcom_cci bmi160_i2c
[   92.719531]  st_lsm6dsx_i2c ak8975 st_lsm6dsx bmi160_core qrtr industrialio_triggered_buffer socinfo rmtfs_mem kfifo_buf ltrf216a dm_crypt rmi_i2c rmi_core panel_xiaomi_td4310_fhdplus_e7_g55 panel_xiaomi_td4310_fhdplus_e7 panel_xiaomi_td4310_ebbg_fhdplus_e7 panel_xiaomi_nt36672_tianma_fhdplus_e7 panel_xiaomi_nt36672_csot_fhdplus_e7 nt36xxx msm gpu_sched drm_display_helper drm_kms_helper drm_exec drm drm_panel_orientation_quirks mdt_loader
[   92.719592] CPU: 3 PID: 6928 Comm: phoc Tainted: G        W          6.9.0-postmarketos-qcom-msm8953 #1-postmarketos-qcom-msm8953
[   92.719599] Hardware name: Xiaomi Redmi 5 Plus (DT)
[   92.719603] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   92.719609] pc : mdp5_pipe_release+0xbc/0xcc [msm]
[   92.719696] lr : mdp5_pipe_release+0x2c/0xcc [msm]
[   92.719778] sp : ffff80008498b920
[   92.719781] x29: ffff80008498b920 x28: ffff00001d8ae380 x27: 0000000000000005
[   92.719790] x26: 0000000000000038 x25: 0000000000000000 x24: ffff800079685c30
[   92.719798] x23: 0000000000000000 x22: ffff000013c65080 x21: ffff000018bf9c20
[   92.719807] x20: ffff000018bf9c00 x19: ffff000013c1d140 x18: 0000000000000000
[   92.719815] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
[   92.719824] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[   92.719832] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
[   92.719840] x8 : ffff8000794b2000 x7 : 0000000000000000 x6 : ffff00001d8ae380
[   92.719848] x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff8000794f7068
[   92.719857] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   92.719866] Call trace:
[   92.719869]  mdp5_pipe_release+0xbc/0xcc [msm]
[   92.719952]  mdp5_plane_atomic_check+0x354/0x478 [msm]
[   92.720036]  drm_atomic_helper_check_planes+0xd4/0x210 [drm_kms_helper]
[   92.720111]  drm_atomic_helper_check+0x50/0xa4 [drm_kms_helper]
[   92.720157]  msm_atomic_check+0x98/0xa4 [msm]
[   92.720244]  drm_atomic_check_only+0x4d4/0x914 [drm]
[   92.720420]  drm_mode_atomic_ioctl+0x9b8/0xd64 [drm]
[   92.720517]  drm_ioctl_kernel+0xbc/0x128 [drm]
[   92.720613]  drm_ioctl+0x20c/0x4b4 [drm]
[   92.720710]  __arm64_sys_ioctl+0xac/0xf0
[   92.720719]  invoke_syscall+0x48/0x114
[   92.720727]  el0_svc_common.constprop.0+0x40/0xe0
[   92.720734]  do_el0_svc+0x1c/0x28
[   92.720740]  el0_svc+0x34/0xd8
[   92.720747]  el0t_64_sync_handler+0x120/0x12c
[   92.720753]  el0t_64_sync+0x190/0x194
[   92.720759] ---[ end trace 0000000000000000 ]---
[   92.753588] Filesystems sync: 0.138 seconds
[   92.788619] Freezing user space processes
[   92.795508] Freezing user space processes completed (elapsed 0.006 seconds)
[   92.795527] OOM killer disabled.
[   92.795530] Freezing remaining freezable tasks
[   92.798186] Freezing remaining freezable tasks completed (elapsed 0.002 seconds)
[   92.798193] printk: Suspending console(s) (use no_console_suspend to debug)
[   92.798989] ------------[ cut here ]------------
[   92.798993] WARNING: CPU: 7 PID: 6361 at drivers/gpu/drm/msm/disp/mdp5/mdp5_pipe.c:138 mdp5_pipe_release+0xbc/0xcc [msm]
[   92.799129] Modules linked in: sch_ingress veth overlay nft_masq nft_chain_nat nf_nat bridge stp llc zram zsmalloc fuse wcn36xx mac80211 libarc4 cfg80211 btqcomsmd btqca nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bluetooth ecdh_generic ecc rfkill wcnss_ctrl q6asm_dai q6routing q6voice_dai q6afe_dai q6voice q6afe_clocks q6adm q6asm snd_q6dsp_common q6afe q6mvm q6cvp q6cvs q6voice_common q6core apr pdr_interface ipv6 qrtr_smd ledtrig_pattern crct10dif_ce qcom_q6v5_pas qcom_q6v5_mss qcom_wcnss_pil snd_soc_apq8016_sbc qcom_q6v5 qcom_pil_info snd_soc_msm8916_digital snd_soc_qcom_common ipa2_lite qcom_sysmon leds_aw2013 qcom_common venus_enc venus_dec videobuf2_dma_contig ov5675 qcom_camss st_lsm6dsx_spi venus_core videobuf2_dma_sg videobuf2_memops v4l2_mem2mem videobuf2_v4l2 qcom_spmi_vadc v4l2_fwnode qcom_spmi_temp_alarm rtc_pm8xxx qcom_vadc_common videobuf2_common v4l2_async qcom_pon reboot_mode snd_soc_msm8916_analog videodev mc i2c_qcom_cci bmi160_i2c
[   92.799270]  st_lsm6dsx_i2c ak8975 st_lsm6dsx bmi160_core qrtr industrialio_triggered_buffer socinfo rmtfs_mem kfifo_buf ltrf216a dm_crypt rmi_i2c rmi_core panel_xiaomi_td4310_fhdplus_e7_g55 panel_xiaomi_td4310_fhdplus_e7 panel_xiaomi_td4310_ebbg_fhdplus_e7 panel_xiaomi_nt36672_tianma_fhdplus_e7 panel_xiaomi_nt36672_csot_fhdplus_e7 nt36xxx msm gpu_sched drm_display_helper drm_kms_helper drm_exec drm drm_panel_orientation_quirks mdt_loader
[   92.799318] CPU: 7 PID: 6361 Comm: elogind Tainted: G        W          6.9.0-postmarketos-qcom-msm8953 #1-postmarketos-qcom-msm8953
[   92.799324] Hardware name: Xiaomi Redmi 5 Plus (DT)
[   92.799327] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   92.799332] pc : mdp5_pipe_release+0xbc/0xcc [msm]
[   92.799413] lr : mdp5_pipe_release+0x2c/0xcc [msm]
[   92.799494] sp : ffff8000845cb700
[   92.799496] x29: ffff8000845cb700 x28: ffff0000d5801200 x27: 0000000000000005
[   92.799503] x26: 0000000000000038 x25: 0000000000000000 x24: ffff800079685c30
[   92.799510] x23: 0000000000000000 x22: ffff000013c65080 x21: ffff0000ec561020
[   92.799516] x20: ffff0000ec561000 x19: ffff000013c1d140 x18: 0000000000000026
[   92.799523] x17: 6775626564206f74 x16: 0000000000000026 x15: 0000000000000000
[   92.799529] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[   92.799536] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
[   92.799542] x8 : ffff8000794b2000 x7 : 0000000000000000 x6 : ffff0000d5801200
[   92.799549] x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff8000794f7068
[   92.799555] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   92.799562] Call trace:
[   92.799565]  mdp5_pipe_release+0xbc/0xcc [msm]
[   92.799646]  mdp5_plane_atomic_check+0x354/0x478 [msm]
[   92.799727]  drm_atomic_helper_check_planes+0xd4/0x210 [drm_kms_helper]
[   92.799798]  drm_atomic_helper_check+0x50/0xa4 [drm_kms_helper]
[   92.799842]  msm_atomic_check+0x98/0xa4 [msm]
[   92.799924]  drm_atomic_check_only+0x4d4/0x914 [drm]
[   92.800081]  drm_atomic_commit+0x74/0xf0 [drm]
[   92.800174]  drm_atomic_helper_disable_all+0x200/0x214 [drm_kms_helper]
[   92.800218]  drm_atomic_helper_suspend+0xa8/0x224 [drm_kms_helper]
[   92.800262]  drm_mode_config_helper_suspend+0x34/0x94 [drm_kms_helper]
[   92.800306]  msm_kms_pm_prepare+0x28/0x40 [msm]
[   92.800388]  pm_generic_prepare+0x2c/0x44
[   92.800398]  genpd_prepare+0x6c/0x104
[   92.800404]  dpm_prepare+0xc4/0x2e8
[   92.800408]  dpm_suspend_start+0x20/0x6c
[   92.800412]  suspend_devices_and_enter+0x70/0x550
[   92.800419]  pm_suspend+0x164/0x1d0
[   92.800424]  state_store+0x80/0xec
[   92.800429]  kobj_attr_store+0x18/0x2c
[   92.800436]  sysfs_kf_write+0x44/0x54
[   92.800442]  kernfs_fop_write_iter+0x120/0x1cc
[   92.800446]  do_iter_readv_writev+0xd8/0x1b8
[   92.800451]  vfs_writev+0xf8/0x290
[   92.800456]  do_writev+0x7c/0x11c
[   92.800460]  __arm64_sys_writev+0x20/0x2c
[   92.800465]  invoke_syscall+0x48/0x114
[   92.800472]  el0_svc_common.constprop.0+0x40/0xe0
[   92.800477]  do_el0_svc+0x1c/0x28
[   92.800482]  el0_svc+0x34/0xd8
[   92.800488]  el0t_64_sync_handler+0x120/0x12c
[   92.800492]  el0t_64_sync+0x190/0x194
[   92.800497] ---[ end trace 0000000000000000 ]---
[   92.800537] msm_mdp 1a01000.display-controller: PM: device_prepare(): genpd_prepare+0x0/0x104 returns -22
[   92.800547] msm_mdp 1a01000.display-controller: PM: not prepared for power transition: code -22
[   92.800552] PM: Some devices failed to suspend, or early wake event detected
[   92.801312] OOM killer enabled.
[   92.801315] Restarting tasks ... done.
[   92.805792] random: crng reseeded on system resumption
[   92.805838] PM: suspend exit

Results for 6.8.2

The problem persists also with the 6.8.2 kernel from the postmarket os repo.

[   93.286900] PM: suspend entry (s2idle)
[   93.627554] Filesystems sync: 0.340 seconds
[   93.633775] Freezing user space processes
[   93.732853] Freezing user space processes completed (elapsed 0.099 seconds)
[   93.732873] OOM killer disabled.
[   93.732876] Freezing remaining freezable tasks
[   93.735500] Freezing remaining freezable tasks completed (elapsed 0.002 seconds)
[   93.735509] printk: Suspending console(s) (use no_console_suspend to debug)
[   93.739382] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
[   93.764492] wcn36xx: ERROR SMD_EVENT (312) not supported
[   93.894796] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[   93.894822] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[   93.894833] rmi4_physical rmi4-00: Failed to suspend functions: -6
[   93.894854] rmi4_i2c 2-0020: Failed to resume device: -6
[   93.894873] rmi4_i2c 2-0020: PM: dpm_run_callback(): rmi_i2c_suspend+0x0/0x6c [rmi_i2c] returns -6
[   93.894922] rmi4_i2c 2-0020: PM: failed to suspend async: error -6
[   93.895093] PM: Some devices failed to suspend, or early wake event detected
[   94.072237] OOM killer enabled.
[   94.072252] Restarting tasks ... done.
[   94.080955] random: crng reseeded on system resumption
[   94.081024] PM: suspend exit
[   94.081269] PM: suspend entry (s2idle)
[   94.244549] Filesystems sync: 0.163 seconds
[   94.308401] Freezing user space processes
[   94.314847] Freezing user space processes completed (elapsed 0.006 seconds)
[   94.314868] OOM killer disabled.
[   94.314871] Freezing remaining freezable tasks
[   94.317409] Freezing remaining freezable tasks completed (elapsed 0.002 seconds)
[   94.317417] printk: Suspending console(s) (use no_console_suspend to debug)
[   94.428095] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[   94.428124] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[   94.428137] rmi4_physical rmi4-00: Failed to suspend functions: -6
[   94.428149] rmi4_i2c 2-0020: Failed to resume device: -6
[   94.428165] ------------[ cut here ]------------
[   94.428170] unbalanced disables for l6
[   94.428238] WARNING: CPU: 5 PID: 58 at drivers/regulator/core.c:2999 _regulator_disable+0x130/0x25c
[   94.428273] Modules linked in: sch_ingress veth overlay nft_masq nft_chain_nat nf_nat bridge stp llc zram zsmalloc fuse wcn36xx mac80211 libarc4 cfg80211 btqcomsmd btqca nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bluetooth ecdh_generic ecc rfkill wcnss_ctrl ipv6 q6asm_dai q6routing q6voice_dai q6afe_dai q6afe_clocks q6voice q6adm q6asm q6cvs q6mvm q6afe snd_q6dsp_common q6cvp q6voice_common q6core apr pdr_interface qrtr_smd ledtrig_pattern crct10dif_ce snd_soc_apq8016_sbc snd_soc_qcom_common qcom_q6v5_pas snd_soc_msm8916_digital qcom_wcnss_pil leds_aw2013 qrtr qcom_q6v5_mss qcom_pil_info qcom_q6v5 ipa2_lite qcom_sysmon venus_dec venus_enc qcom_common qmi_helpers videobuf2_dma_contig st_lsm6dsx_spi qcom_camss ov5675 qcom_pon snd_soc_msm8916_analog qcom_spmi_vadc rtc_pm8xxx reboot_mode qcom_vadc_common videobuf2_dma_sg qcom_spmi_temp_alarm venus_core videobuf2_memops v4l2_mem2mem videobuf2_v4l2 v4l2_fwnode videobuf2_common v4l2_async videodev i2c_qcom_cci
[   94.428695]  mc bmi160_i2c st_lsm6dsx_i2c ak8975 bmi160_core st_lsm6dsx industrialio_triggered_buffer ltrf216a kfifo_buf rmtfs_mem socinfo dm_crypt rmi_i2c rmi_core panel_xiaomi_td4310_fhdplus_e7_g55 panel_xiaomi_td4310_fhdplus_e7 panel_xiaomi_td4310_ebbg_fhdplus_e7 panel_xiaomi_nt36672_tianma_fhdplus_e7 panel_xiaomi_nt36672_csot_fhdplus_e7 nt36xxx msm gpu_sched drm_display_helper drm_kms_helper drm_exec drm drm_panel_orientation_quirks mdt_loader
[   94.428838] CPU: 5 PID: 58 Comm: kworker/u18:1 Tainted: G        W          6.8.2-postmarketos-qcom-msm8953 #2-postmarketos-qcom-msm8953
[   94.428854] Hardware name: Xiaomi Redmi 5 Plus (DT)
[   94.428862] Workqueue: events_unbound async_run_entry_fn
[   94.428889] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   94.428903] pc : _regulator_disable+0x130/0x25c
[   94.428919] lr : _regulator_disable+0x130/0x25c
[   94.428934] sp : ffff80008163bc50
[   94.428939] x29: ffff80008163bc50 x28: 0000000000000000 x27: 0000000000000000
[   94.428960] x26: ffff000011710028 x25: ffff000011cfe040 x24: 0000000000000002
[   94.428980] x23: ffff000014129960 x22: 0000000000000001 x21: ffff000014129980
[   94.429001] x20: ffff000014171800 x19: ffff0000141facc0 x18: fffffffffffee3a8
[   94.429021] x17: 000000040044ffff x16: 00500072b5503510 x15: 0000000000000028
[   94.429041] x14: 0000000000000000 x13: ffff80008124fb68 x12: 00000000000009cc
[   94.429060] x11: 0000000000000344 x10: ffff8000812a7b68 x9 : ffff80008124fb68
[   94.429080] x8 : 00000000ffffefff x7 : ffff8000812a7b68 x6 : 80000000fffff000
[   94.429100] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 00000000ffffffff
[   94.429118] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000011d38000
[   94.429139] Call trace:
[   94.429144]  _regulator_disable+0x130/0x25c
[   94.429161]  regulator_bulk_disable+0x74/0x160
[   94.429177]  rmi_i2c_suspend+0x3c/0x6c [rmi_i2c]
[   94.429206]  __device_suspend+0x11c/0x3e0
[   94.429225]  async_suspend+0x28/0xac
[   94.429241]  async_run_entry_fn+0x34/0x14c
[   94.429258]  process_one_work+0x138/0x248
[   94.429276]  worker_thread+0x320/0x438
[   94.429290]  kthread+0x110/0x114
[   94.429304]  ret_from_fork+0x10/0x20
[   94.429319] ---[ end trace 0000000000000000 ]---
[   94.429364] Failed to disable vio: -EIO
[   94.429376] rmi4_i2c 2-0020: PM: dpm_run_callback(): rmi_i2c_suspend+0x0/0x6c [rmi_i2c] returns -6
[   94.429412] rmi4_i2c 2-0020: PM: failed to suspend async: error -6
[   94.429739] PM: Some devices failed to suspend, or early wake event detected
[   94.609673] OOM killer enabled.
[   94.609689] Restarting tasks ... done.
[   94.616564] random: crng reseeded on system resumption
[   94.616650] PM: suspend exit
[   94.748887] [drm:mdp5_irq_error_handler [msm]] *ERROR* errors: 04000000

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants