2 ms·
> continuous hardware testing I have a non-thinkpad laptop, and it seems nearly every kernel release there is some regression. Touchpad not working.. Then GP
by londons_explore 3y ago
> continuous hardware testing
I have a non-thinkpad laptop, and it seems nearly every kernel release there is some regression. Touchpad not working.. Then GPU driver not working... Then suspend to disk broken... Regressions that, for a regular non-technical user would be a big headache.
I would like to 'lend' hardware to someone to prevent this. I'd happily leave my laptop/desktop/SBC overnight compiling a kernel, rebooting into it, running tests, and hopefully finding regressions before they get into a release.
Unfortunately, there doesn't seem to be any project to make this easy. I'd like to just "apt install volunteer-my-hardware-for-overnight-testing". A few thousand people doing that would soon find issues that only affect rare hardware.
- londons_explore 3y agoFor this kind of testing, you frequently want a 'watchdog' - which is hardware that can auto-reboot a computer if the software locks up or malfunctions. The way it works is that software 'pets' the watchdog every few minutes, and if the software malfunctions, then it doesn't pet the watchdog, and the system gets hard reset and boots a known good kernel. Unfortunately, while nearly all computer hardware has a watchdog, frequently the linux kernel doesn't implement support for it. That in turn means that testing buggy kernels on real hardware automatically frequently ends up with the hardware getting stuck and a human needs to reset stuff manually.
- rbanffy 3y ago> and a human needs to reset stuff manually. Unless it's so bad as it becomes unbootable and no safe boot option exists that can be engaged via, say, the serial console, being able to power cycle the board should be more or less enough. If the bootloader can be controlled via a serial console, then it can be automated. Of course, someone needs to build that infra.