Beaglebone watchdog spamming dmesg

This forum is for supported devices using an ARMv7 Texas Instruments (TI) SoC.

Beaglebone watchdog spamming dmesg

Postby relghuar » Fri Mar 01, 2013 11:32 am

Hello, I tried to activate watchdog on my beaglebone. It's working fine (restarts the board after 60 seconds of inactivity), problem is it fills dmesg log with lots of annoying messages:

$this->bbcode_second_pass_code('', '
[ 1158.610382] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1158.613769] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1163.617462] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1163.620849] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1163.624420] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1163.629943] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1163.633361] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1163.636932] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1163.640441] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1163.643981] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1163.647583] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1168.651275] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1168.654663] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1168.660034] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1168.663482] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1168.669189] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1168.672760] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1168.676208] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1168.681091] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1168.684478] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1173.689147] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 1173.692565] omap_hwmod: wd_timer2: _wait_target_disable failed
')

There's always 9 of them every 5 seconds (I have 10 second tick interval in watchdog.conf), so the kernel log output is fairly useless and it fills system logs very quickly.
I found very little recent info about this other than it should have been fixed long time ago. Best fix a came across is the patch at the end of this thread http://e2e.ti.com/support/arm/sitara_arm/f/791/t/194467.aspx, though I haven't tried it yet. If I can confirm it works with current core/linux-am33x from archlinuxarm github repo (or come up with something that works), would it be possible to patch it there?
Regards,
rel
relghuar
 
Posts: 18
Joined: Sun Nov 18, 2012 3:51 pm

Re: Beaglebone watchdog spamming dmesg

Postby relghuar » Sat Mar 02, 2013 10:20 am

Hi again,
I can confirm the patch I've linked to yesterday really works. When it's applied as the last patch in linux-am33x PKGBUILD kernel package can be built automatically, resulting watchdog still reboots the machine correctly and the annoying spam in dmesg is gone.
Would it be possible to include this patch in github repo? I can provide a full diff against current repository if it helps...
Regards,
rel
relghuar
 
Posts: 18
Joined: Sun Nov 18, 2012 3:51 pm

Re: Beaglebone watchdog spamming dmesg

Postby pepedog » Sat Mar 02, 2013 10:29 am

You don't need to do that,
https://github.com/archlinuxarm/PKGBUILDs
pull it (whole repo), modify your bits on your github, commit, push it.
Don't forget to do md5 and package release
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK


Return to Texas Instruments (TI)

Who is online

Users browsing this forum: No registered users and 2 guests