rmkit
rmkit copied to clipboard
remux eats 40% of the CPU after a while on 3.8.2.1965
Following tests on that discussion to install 3.8.2.1965, I tried to use remux instead of rocket.
While the manipulation worked and remux is always displaying on swipe, at some point it starts to eat 40% of the CPU and never ends eating eat.
systemctl restart is putting it back on rails for a moment, but it's nor a fix or a solution.
Where should I look / do you have something I can try for you to help identify the problem ?
https://github.com/rmkit-dev/rmkit/blob/master/docs/PERF.md
good luck
I will try to profile it tonight
Happens after a sleep long enough to cut the WIFI, and a wake up. At wake up, remux burns 50% of the CPU looping on this like a crazy:
pselect6(10, [5 6 7 9], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [6], left {tv_sec=0, tv_nsec=999991376})
pselect6(10, [5 6 7 9], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [6], left {tv_sec=0, tv_nsec=999990126})
pselect6(10, [5 6 7 9], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [6], left {tv_sec=0, tv_nsec=999991376})
pselect6(10, [5 6 7 9], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [6], left {tv_sec=0, tv_nsec=999991126})
pselect6(10, [5 6 7 9], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [6], left {tv_sec=0, tv_nsec=999990875})
pselect6(10, [5 6 7 9], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [6], left {tv_sec=0, tv_nsec=999992375})
pselect6(10, [5 6 7 9], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [6], left {tv_sec=0, tv_nsec=999990876})
Might be worth looking at some of the high-CPU reports on other Linux-based systems to see if the issues discovered there apply to this hardware.
I haven't dug into this at all, if you have had progress, awesome! otherwise, I will have to find time to download and play with 3.8. is the keyboard plugged in, btw?
again, thanks for flagging the perf issue!
Hello, I didn't dug that much after my last post here. I went back on 3.3.2/toltec/remux and 3.8 classic for the other partition. No bad perfs anymore and I only have to reboot to get what I need.
is the keyboard plugged in, btw?
I remember seeing the problem when not using the keyboard. I can't say if using it would have changed something, sorry.
I admit I didn't have the faith to continue to tweak/grind more, since I yet have to build myself a pogo pin connector for a proper recovery in case things goes wrong.
Happens after a sleep long enough to cut the WIFI, and a wake up. ...
@gullradriel I'm a little confused by this statement. By default in toltec, wifi is disabled on every suspend with the rm2-suspend-fix package. Do you mean that this is due to the automatic suspend that xochitl does? Or the automatic suspend remux starts? Or can you replicate this by suspending with the power button?
I'm trying to replicate right now with some experimental changes to add 3.5.2 and 3.8.2 support to toltec. So far I've been unable to replicate.
In my tests when I was going too quick to lock and unlock, then it was not cutting the wifi or triggering the cpu eating.
I've been unable to replicate with manual suspend or waiting for both xochitl or remux to automatically suspend after inactivity.