Image location: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.6.1/machines/beaglebone/ Git rev: daisy/a43dba8c2904f9c1ce0425c53c5a7f4718121e6b This issue had been fixed in master branch. But still exists in daisy branch.
Do you know what fixed it in the master branch for a backport?
(In reply to comment #1) > Do you know what fixed it in the master branch for a backport? It's a kernel config path. In meta branch for repo linux-yocto-3.14: commit 183622e8095545999a64bd72adedea2dffb6ec4b Author: Kevin Hao <kexin.hao@windriver.com> Date: Fri May 23 14:41:35 2014 +0800 beaglebone: enable the nowayout option for the watchdog The default watchdog behaviour is to stop the timer if the process managing it closes the file /dev/watchdog. The system would not reboot if watchdog daemon crashes due to a bug in it or get killed by other malicious code. So we prefer to enable nowayout option for the watchdong. With this enabled, there is no way of disabling the watchdog once it has been started. This option is also enabled in the predecessor of this BSP (beagleboard). Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> diff --git a/meta/cfg/kernel-cache/bsp/beaglebone/beaglebone.cfg b/meta/cfg/kernel-cache/bsp/beaglebone/beaglebone.cfg index 6b25636..81f97d6 100644 --- a/meta/cfg/kernel-cache/bsp/beaglebone/beaglebone.cfg +++ b/meta/cfg/kernel-cache/bsp/beaglebone/beaglebone.cfg @@ -195,6 +195,7 @@ CONFIG_POWER_SUPPLY=y # # Watchdog Device Drivers # +CONFIG_WATCHDOG_NOWAYOUT=y CONFIG_OMAP_WATCHDOG=y CONFIG_TWL4030_WATCHDOG=y
Information supplied
Did this get into any kernel branch such that it can be added to a kernel update for a 1.6.3?
I will talk with Bruce to get this fix merged into 1.6.3
The patch for this issue has been merged into daisy branch.
Verified with 1.6.3 rc2 git rev: daisy/6b8f7999c3e86d6e834af95ffe4c33d0d53db34a