From: sylvain.rochet@finsecur•com (Sylvain Rochet)
To: linux-arm-kernel@lists•infradead.org
Subject: at91sam9 Main crystal frequency problems
Date: Wed, 7 Oct 2015 11:33:52 +0200 [thread overview]
Message-ID: <20151007093352.GA15524@gradator.net> (raw)
In-Reply-To: <5613E822.2020004@overkiz.com>
Hi Antoine,
On Tue, Oct 06, 2015 at 05:26:26PM +0200, Antoine Aubert wrote:
> Le 06/10/2015 16:12, Boris Brezillon a ?crit :
> >
> > Any progress regarding this problem. I think Jiri (in Cc) has pretty
> > much the same problem (see this thread [1]).
> > IIRC, activating NO_HZ_IDLE solved the problem for you, but have you
> > find the root cause?
>
> I'm not sure that the same issue. Here I don't have slow xtal.
There was no issue, it was just a misunderstanding on how the watchdog
stack is working.
> What I found:
> * DTB was not up to date (build with an other kernel version)
> Since we start from kexec, we added --dtb option
> * slow_xtal wasn't disabled in our DTS
> * defconfig was outdated
>
> What i did first:
> * updated the dts, disabled slow xtal
> * Update DTB
> * activating NO_HZ_IDLE
>
> > 20d updtime without WRST
>
> Today what I did:
> * use LTS last kernel: 4.1.6
> * updated the dts, disabled slow xtal
> * generate config from scratch using "make ARCH=arm at91_dt_defconfig"
> (without NO_HZ_IDLE=
>
> 12h uptime, at this time no WRST
Great, no issue then, thank you !
Sylvain
prev parent reply other threads:[~2015-10-07 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 7:31 at91sam9 Main crystal frequency problems Antoine Aubert
2015-09-08 16:12 ` Boris Brezillon
2015-09-14 12:41 ` Antoine Aubert
2015-09-14 13:20 ` Boris Brezillon
2015-10-06 14:12 ` Boris Brezillon
2015-10-06 15:26 ` Antoine Aubert
2015-10-07 9:33 ` Sylvain Rochet [this message]
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=20151007093352.GA15524@gradator.net \
--to=sylvain.rochet@finsecur$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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