On 08/09/2013 03:20 PM, Harald Hoyer wrote: > On 08/05/2013 12:19 PM, Baoquan He wrote: >> Hi Harald, >> >> Since some drivers do the soft kicking. That is if BIOS has enabled >> watchdog, then kernel driver kicks the hardware till user space watchdog >> daemon comes along. This can help sove the problem in kdump which kdump >> kernel reboot before vmcore saving is finished. That problem is >> triggered because watchdog started in 1st kernel and timeout because of >> stopping being kicked. >> >> I noticed in 04watchdog the watchdog.sh will start watchdog if >> /dev/watchdog exists. I am just wondering if it's needed to start >> watchdog by accessing /dev/watchdog. If starting watchdog is not needed, >> I want to make some code change of watchdog.sh. >> >> What's your suggestion? >> >> Baoquan >> Thanks a lot > > Basically the 04watchdog module was used only in the testsuite. You might > consider to use the systemd watchdog feature instead. > > http://0pointer.de/blog/projects/watchdog.html > > or, if 0pointer is down again: > > http://webcache.googleusercontent.com/search?q=cache:jYfJU_fFZy8J:0pointer.de/blog/projects/watchdog.html Hi, I tried your suggestion, systemd can't help. In /etc/systemd/system.conf, there are 2 options to control watchdog, however it need watchdog hardware to be present. That means watchdog driver need be loaded during startup. Baoquan Thanks > -- > To unsubscribe from this list: send the line "unsubscribe initramfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
