search

Miouyouyou / RockMyy

Build scripts and patches used to cross-compile 5.6-rcX kernels for RK3288 boards
MIT License
32 stars 9 forks source link

Asus C100P switching off randomly on charged battery usage #16

Closed UralZima closed 4 years ago

UralZima commented 4 years ago

Hello. I have Asus C100P (veyron_minnie), a RK3288 chromebook. Actually the problem exists not only with this kernel, also with PrawnOS's kernel and Arch's kernel (5.x)

The issue is, my chromebook is turning off on battery usage randomly. Battery is charged. I did some tests to identify the issue. so:

So, it may be video-related, some kernel voltage guard related, some powersaving mode, or something like this. Please help me resolve this issue.

Miouyouyou commented 4 years ago

Are you using Rockchip Mali OpenGL accelerated drivers or not ?

Anyway, a simple test to check whether it's just the whole thing overheating and behaving in a very weird manner is to try shutting down Xorg/Wayland/Whatever graphics system you're using and then fire some CPU intensive benchmarks :

sudo apt install p7zip
while true; do 7zr b; sleep 2s; done

And see if the same issue occurs. That should remove a lot of potential culprits (GPU, VPU, drivers, ...)

UralZima commented 4 years ago

No I am not using mali drivers. Using standard fbdev driver. Will try with benchmarks

Miouyouyou commented 4 years ago

Ok

UralZima commented 4 years ago

I tried the benchmarks. I disabled sddm, boot into console and run the tests without xorg and left fully charged c100p for the whole night. Morning it was off, the battery level was at 25%. Better results, but anyway it turned off. It worked many hours with full cpu load. Now I am running same tests with AC plugged in for hours - it works, so it is not soc overheat problem. Any ideas? I will continue tests with video playback

Miouyouyou commented 4 years ago

Well, it seems that my response through mail didn't get through, so I'll repost it :

Hmm... So, the next culprit might be either the RAM or the hard drive, since the issues can happen when decrypting the disk on bootup.

I don't know any good memory tester for ARM systems. @ThomasKaiser uses https://github.com/ssvb/tinymembench for memory banchmarks. You can also try his sbc-bench project ( https://github.com/ThomasKaiser/sbc-bench ) for a complete benchmark of your system. If the system were to crash on the same benchmark every time, you might have a very good idea on what's going on, since he tests every part of the hardware one by one.

iozone could do the trick for testing the hard drive... Run it a few times, but don't do it too much as that could fairly reduce the lifespan of the underlying storage hardware (If it's a MMC for example).

sudo apt install iozone3
iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2

If you get an "Invalid argument" error, that means that your kernel does not support Direct I/O. In which case, try this :

iozone -e -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2

I will continue tests with video playback

If you can install glmark2, try running it (install it from git to avoid various issues) :


sudo apt install libjpeg-dev libpng-dev pkg-config libudev-dev libdrm-dev libegl1-mesa-dev libgles2-mesa-dev libgbm-dev
git clone --depth 1 https://github.com/glmark2/glmark2
cd glmark2
./waf configure --with-flavors=drm-glesv2
./waf
sudo ./waf install
glmark2-es2-drm
Miouyouyou commented 4 years ago

If you still have these issues, feel free to reopen this ticket. Meanwhile, I'm closing it due to no activity.