Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> wrote in news:ee89e9f9-7ddf-ef42-0ad6-5881c74ebb48@xxxxxxxxxxxxxx: > As described in the linked documentation, it's useless for monitoring > Linux boot, because it's a boot service and these are terminated very > early in the Linux boot process. > > Only usable x86 watchdog we have at the moment is the Fintek Super I/O > watchdog. If you have another Super I/O, but your BIOS exports a WDAT > ACPI table, barebox v2019.01.0 will come with ACPI driver support, so > you could write an ACPI driver on top. Alternatively, you could turn on > the watchdog in the BIOS and leave barebox out of it altogether. Just to be clear about what I'm doing. I have an embedded Linux device whose CPU is 64-Bit quad-core. Once the device has successfully booted up, there is a watchdog timer that makes sure everything keeps running smoothly. So if my device freezes AFTER it boots up successfully, then this eventuality is dealt with. What I have NOT dealt with though, is the case of the device freezing mid- boot. So let's say that Barebox tries to load the Linux kernel, and let's say the kernel get 15% loaded and then it freezes. If this happens, I need the device to reboot. How would you go about this? Would you use the watchdog timer in the BIOS, or would you use the one in Barebox? _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
