-
Notifications
You must be signed in to change notification settings - Fork 66
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
Comments
Hi @spongy-deluxe is this still issue with 6.8.2? |
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). 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.0The 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:
Results for 6.8.2The problem persists also with the 6.8.2 kernel from the postmarket os repo.
|
Switch to dpu with |
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):
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).
Related discussions:
Kernel discussion
Issue related commits:
Collection of magical workarounds (mostly hiding the issues with some likelihood):
psmouse.synaptics_intertouch=0
to kernel boot cmdlinefw_devlink=on
to kernel boot cmdlineWorkaround for pmos:
The text was updated successfully, but these errors were encountered: