linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: at91sam9: watchdog: period
Date: Fri, 15 May 2015 17:25:16 +0200	[thread overview]
Message-ID: <20150515172516.005e3a21@bbrezillon> (raw)
In-Reply-To: <55559D55.6020703@aksignal.cz>

Hi Jiri,

On Fri, 15 May 2015 09:16:37 +0200
Ji?? Prchal <jiri.prchal@aksignal.cz> wrote:

> Hi all,
> I'm trying to discover what's wrong with watchdog on my board. I didn't find anything about it on internet so I would 
> ask you for help.
> I have a board with sam9g25 and slow clock xtal 32768Hz with 10p capacitors to GND. Frequency seems to be good since 
> hwclock (RTC) runs pretty precisely powered from backup and main power too (no NTP). But watchdog time to reset is still 
> 61s regardless default (16s) or 4s heartbeat setting. No change to WDT_MR in bootstrap, so in Linux should work.
> Here is dump:
> [    0.000000] Booting Linux on physical CPU 0x0
> [    0.000000] Linux version 4.0.2_cpm9g25 (prchal at prchal) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-12ubuntu1) ) #10 
> PREEMPT Thu May 14 15:20:24 CEST 2015
> [    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=0005317f
> [    0.000000] CPU: VIVT data cache, VIVT instruction cache
> [    0.000000] Machine model: AKsignal CDU9G25_v6
> [    0.000000] Memory policy: Data cache writeback
> [    0.000000] AT91: Detected soc type: at91sam9x5
> [    0.000000] AT91: Detected soc subtype: at91sam9g25
> ...
> [    4.669669] AT91: Starting after watchdog reset
> [    4.675675] at91sam9_wdt: enabled (heartbeat=4 sec, nowayout=1)
> ...
> 
> / # killall watchdog
> [ 1821.114114] watchdog watchdog0: nowayout prevents watchdog being stopped!
> / # [ 1821.123123] watchdog watchdog0: watchdog did not stop!
> [ 1882.294294] at91sam9_wdt: I will reset your machine !

Is this file present on your board ?
/proc/device-tree/ahb/apb/watchdog at fffffe40/atmel,idle-halt

If it is then you should patch your DT to remove the property.

Best Regards,

Boris


-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2015-05-15 15:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  7:16 at91sam9: watchdog: period Jiří Prchal
2015-05-15 13:59 ` Bryan Evenson
2015-05-15 14:19   ` Nicolas Ferre
2015-05-18  6:25     ` Jiří Prchal
2015-05-15 15:25 ` Boris Brezillon [this message]
2015-05-18  6:27   ` Jiří Prchal
2015-05-18  7:27     ` Boris Brezillon
2015-05-18  8:17       ` Jiří Prchal
2015-05-19  3:07         ` Yang, Wenyou
2015-05-19  7:14           ` Boris Brezillon
2015-05-19  9:01             ` Jiří Prchal
2015-05-19  9:14               ` Boris Brezillon
2015-05-19  9:52                 ` Jiří Prchal
2015-05-19 10:04                   ` Boris Brezillon
2015-05-20 12:39                     ` Jiří Prchal
2015-05-21 12:41                     ` Jiří Prchal
2015-05-27  7:11                       ` Jiří Prchal
2015-05-19  7:12     ` Boris Brezillon
2015-05-19  9:00       ` Jiří Prchal
2015-10-06 13:07 ` Jiří Prchal
2015-10-06 18:03 ` Sylvain Rochet
2015-10-07  7:16   ` Jiří Prchal
2015-10-07  9:22   ` Sylvain Rochet

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=20150515172516.005e3a21@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).