View Single Post
Posts: 304 | Thanked: 160 times | Joined on Jul 2008
#12
Originally Posted by gravis86 View Post
This did not work for me. Bootreason is 32wd_to. I restarted the device, and typed in what you wrote. About 3 hours later, I got a reboot. Any other ideas?
My understanding from the bug thread (link in the first post), is that this work around disables the watchdog. With this work around in place, you will not get this reebot-issue anymore, simply because the whole chabang is disabled.

If you still get reboots, this is due to some other fault, or you havent done it right (it is easy to type something wrong), or you havent done a proper hard reboot (power on off) so your device is still unstable, or a combination.

Check /proc/bootreason after each reboot.