Hi Alejandro, >>> I think that the internal timer can be useful in the following scenario: >>> If an user reboot the system, then the internal timer must ensure that >>> the watchdog didn't reset the system during the reboot process and it >>> send ticks to the wdt until the user/clean reboot process get finished. >>> Maybe a reboot notifier can be used to detect when the user reboot the >>> system manually. >> If a system is rebooted then the watchdog device is also resetted. >> So until you start the watchdog, it will not be activated... > > Yes, but I'm thinking in the following case: if the system was > restarting (clean reboot) and it take more than the watchdog timeout or > the timeleft was very small to do a clean reboot....then the wdt reset > the system and maybe it can be corrupt it. > Maybe this case is weird and uncommon, but it has a chance to occur. Don't forget that most watchdog drivers allready use a reboot_notifier or a platform shutdown method, to stop the watchdog before rebooting. And secondly, when watchdog devices are initialised the default behaviour is to stop the watchdog during initialisation (but it is allowed to have an option to manually change this behaviour so that the user can choose). Kind regards, Wim. -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
