From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: at91sam9: watchdog: period
Date: Fri, 15 May 2015 16:19:25 +0200 [thread overview]
Message-ID: <5556006D.30306@atmel.com> (raw)
In-Reply-To: <BN3PR0501MB109030A3B29685D9188F6B71BBC70@BN3PR0501MB1090.namprd05.prod.outlook.com>
Le 15/05/2015 15:59, Bryan Evenson a ?crit :
> Jiri,
>
>> -----Original Message-----
>> From: linux-arm-kernel [mailto:linux-arm-kernel-
>> bounces at lists.infradead.org] On Behalf Of Jir? Prchal
>> Sent: Friday, May 15, 2015 3:17 AM
>> To: linux-arm-kernel at lists.infradead.org
>> Cc: Boris Brezillon; Jean-Christophe Plagniol-Villard; Nicolas Ferre
>> Subject: at91sam9: watchdog: period
>>
>> 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.
>
> I have the same hardware setup and the watchdog timeout is 15
> seconds for me. For my kernel, I am using the Atmel fork at
> github.com/linux4sam/linux-at91, master branch at commit
> 5d5b332821753d616e65da6237f0a3330e59b98f.
FYI, I've just moved the master branch of our github to the newer
3.18-based branch: linux-3.18-at91.
Bye,
> Even though this is based upon
> the 3.10 kernel, there isn't much that has changed with regard to the
> RTC or watchdog between 3.10 and 4.03; Atmel has been good on
> backporting their changes to their fork. Maybe try an older kernel and
> see if the problem goes away?
>
>
> Regards,
> Bryan
>
>> 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 !
>>
>> Thanks for any help.
>> Jiri
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
>
--
Nicolas Ferre
next prev parent reply other threads:[~2015-05-15 14:19 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 [this message]
2015-05-18 6:25 ` Jiří Prchal
2015-05-15 15:25 ` Boris Brezillon
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=5556006D.30306@atmel.com \
--to=nicolas.ferre@atmel.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).