Bug 3937 - [beagleboard xM] Watchdog doesn't work
Summary: [beagleboard xM] Watchdog doesn't work
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-yocto (show other bugs)
Version: 1.4
Hardware: Beagleboard arm
: Medium normal
Target Milestone: 1.7 M3
Assignee: Kevin Hao
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-02-26 05:04 UTC by Yi Zhao
Modified: 2014-05-26 01:03 UTC (History)
10 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2013-02-26 05:04:44 UTC
Image location: http://autobuilder.yoctoproject.org/pub/nightly/20130220-2

Git rev:
master:7d22ef28e64de06b6238d0ef9b664c0bee6efa46

The watchdog doesn't work, it can not restart the system.

Steps:
#########
1. Boot up the system
2. echo 1 > /dev/watchdog
3. After some seconds, the system should restart.
#########
Comment 1 Bruce Ashfield 2013-02-26 20:45:24 UTC
Note: I have no hardware or cycles to look into the beagleboard issues. So they
are a stretch for 1.4.
Comment 2 Bruce Ashfield 2013-02-28 14:06:03 UTC
I'm putting my name down as a placeholder for this, but a resource to debug it needs
to be identified.
Comment 3 Simarpreet Singh 2013-05-15 20:24:01 UTC
Tested it out on kernels 3.4.26 and 3.4.36. Watchdog is working as expected. Couldn't reproduce the issue.
Comment 4 Ning Zhang 2013-06-03 03:33:07 UTC
(In reply to comment #3)
> Tested it out on kernels 3.4.26 and 3.4.36. Watchdog is working as expected.
> Couldn't reproduce the issue.

Hi Simarpreet,

This issue still exists on my side. My target is beagleboard xM.
I used "http://autobuilder.yoctoproject.org/pub/nightly/20130528-2" image, poky is master:676fd3f394a0c0576b63c77ed2184bf5f42c29b6.

When input "echo 1 > /dev/watchdog" from terminal, the board will hang in one minute, and input/output never work any more. This is not same as the expect behaviour(it should automated restart)

My test log from serial connection:


beagleboard login: 
Poky Next (Yocto Project Reference Distro) 1.4+snapshot-20130528 beagleboard ttyO2

beagleboard login: root
root@beagleboard:~# 
root@beagleboard:~# 
root@beagleboard:~# echo 1 > /dev/watchdog
omap_wdt: Unexpected close, not stopping!
root@beagleboard:~# uname -r
3.4.36-yocto-standard
root@beagleboard:~#     <-----it hangs here, no response any more
Comment 5 Kevin Cribbs 2014-03-20 00:49:08 UTC
I tested the specified scenario three times with 1.6 M3 on a Beagleboard xM rev C and it worked each time. If the problem remains, it is inconsistent.
...
root@beagleboard:~# echo 1 > /dev/watchdog
watchdog watchdog0: nowayout prevents watchdog being stopped!
watchdog watchdog0: watchdog did not stop!
root@beagleboard:~# 
U-Boot SPL 2013.07 (Feb 24 2014 - 21:19:25)
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
...
Comment 6 Stoicescu Cornel 2014-04-18 07:13:20 UTC
This issue is also present on beaglebone black.
Comment 7 Bruce Ashfield 2014-05-21 14:55:22 UTC
Kevin is looking after our reference boards, assigning to him, since this is being seen on the
beaglebone black as well.