From: Arthur LAMBERT <lambertarthur22@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] reboot freeze due to wachdog
Date: Tue, 15 Nov 2016 11:02:29 +0100 [thread overview]
Message-ID: <20161115100229.GA25612@arthur-bzh> (raw)
I have an issue with reboot on a imx6ul board + the watchdog hardware from uboot.
Most of the times the reboot freeze. Not all the time. I already post the issue
on freescale community. But uboot from freescale does not use the hardware
watchdog. That's why they ask me to post my issue here..
logs of the issue :
...
reboot
imx2-wdt 20bc000.wdog: Unexpected close: Expect reboot!
ALSA: Storing mixer settings...
Stopping network...Saving random seed... done.
Stopping dropbear sshd: OK
Stopping system message bus: done
Stopping logging: OK
OK
OK
umount: devtmpfs busy - remounted read-only
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
imx2-wdt 20bc000.wdog: Device shutdown: Expect reboot!
reboot: Restarting system
mxc_restart: Watchdog reset failed to assert reset
...
I am using the hardware watchdog in uboot like this :
...
#define CONFIG_HW_WATCHDOG
#define CONFIG_IMX_WATCHDOG
#define CONFIG_WATCHDOG_TIMEOUT_MSECS 20000 // 20s
...
In the board late init :
...
#ifdef CONFIG_HW_WATCHDOG
hw_watchdog_init();
#endif
...
I have of course a piece of code to feed the watchdog every 5 seconds.
The reboot was working perfectly before enabling the watchdog feature on the uboot.
Any reason that the hardware watchdog broke the reboot feature ?
I found a similar issue : https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.variscite.com%2Fsupport-forum%2Fviewtopic.php%3Ft%3D282
By checking their patch on the kernel, I was not able to find a solution for me.
They just remove a wdog node in their device tree. Do I need to add something
to my device tree ?
Thanks,
Arthur.
reply other threads:[~2016-11-15 10:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161115100229.GA25612@arthur-bzh \
--to=lambertarthur22@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox