New comment by Depau on void-packages repository

https://github.com/void-linux/void-packages/pull/28007#issuecomment-762416773

Comment:
> I'm running benchmarks over benchmarks right now, and, if I can say something, the pinebook seems more responsive and stable than before.

**Your** Pinebook.

Again, the device clearly has many other issues and crashes, and until every issue has been bisected and identified you can't be 100% sure that the problems aren't caused by overclocking.

RK3399 chips are real life objects, and as such no chip is made equal and not all chips will run stably at the same high frequencies. Since users will most likely NOT be aware that their device is being overclocked/undervolted/overvolted/anything unless they read the DTS, they will most likely blame it on faulty hardware rather than faulty settings.

Devices crash with tsys' kernel too. If yours doesn't, then you won the silicon lottery, good for you.

I suggest to stick with what rockchip does *for mainstream RK3399* - not for Chromebooks - and with whatever Rockchip has tested and guarantees when they sell the chips to their customers.

But most importantly - and I can't stress this enough - I do not think it is a good idea to imply that since it runs smoothly on **your particular device** it will run smoothly on everyone else's device. Run it on 100 devices, stress test them continuously with a synthetic workload for 24h and see if any of them crashes. I seriously doubt they will all pass the test.

Yes, it is fair to stress test them with a synthetic workload because you want devices to **never** crash, not to not crash when you're "just compiling Linux".

If it runs fine on your machine you can always add an overlay, it's free open-source software.