> On Jul 12, 2017, at 12:24 PM, Matthias Schiffer > <mschif...@universe-factory.net> wrote: > > On 07/12/2017 08:02 PM, Philip Prindeville wrote: >> >>> On Jul 11, 2017, at 3:19 AM, Hans Dedecker <dedec...@gmail.com> wrote: >>> >>> Hi, >>> >>> I would like to cherry-pick the start/stop kernel watchdog support to >>> the lede-17.01 procd branch : >>> >>> e5e99c4 watchdog: add support for starting/stopping kernel watchdog >>> >>> It allows to gracefully stop the kernel watchdog via ubus which was >>> before not possible as only the user space watchdog kicking could be >>> stopped. >>> >>> If nobody objects within the next few days I will take it as a passive >>> consensus and update the procd lede-17.01 branch and the procd package >>> Makefile in the lede-17.01 branch. >>> >>> Thx, >>> Hans >> >> >> Hi Hans! >> >> I’ve not been following this too closely, so forgive me if the question is a >> bit naive. >> >> Since the sysupgrade process involves replacing procd now, would the >> watchdog need to be stopped as procd exits so that the hardware doesn’t >> reset itself during a particularly length update? Let’s say you have a >> large FLASH with slow write times… that could take a long time and I don’t >> want a hardware watchdog thinking that the system has hung… >> >> Thanks, >> >> -Philip >> > > Hi, > the watchdog file descriptor is passed from procd to upgraded, which will > continue to trigger the watchdog during the upgrade. > > Matthias
Awesome, thank you! _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
