![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Bugz: solution
Jul. 13th, 2018 10:26 amYesterday I posted about a strange bug. I am still debugging, but I found the root cause of "linux kernel has memory between reboots".
The benchmark simply leaves /tmp/benchmarks.pid file with its PID. It works differently if same PID is already used or not. When rebooting with same kernel, PID is likely to stay the same, and when rebooting with different kernel, PID is more likely to change, because of different timings in the scheduler.
My bad, everything is simple. I wish the original bug was so simple to resolve too :(
The benchmark simply leaves /tmp/benchmarks.pid file with its PID. It works differently if same PID is already used or not. When rebooting with same kernel, PID is likely to stay the same, and when rebooting with different kernel, PID is more likely to change, because of different timings in the scheduler.
My bad, everything is simple. I wish the original bug was so simple to resolve too :(
