Linux RTC
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Gabriel Beddingfield <gabe@nestlabs.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	John Stultz <john.stultz@linaro.org>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	linux-rtc@vger.kernel.org, Guy Erb <guy@nestlabs.com>,
	Howard Harte <hharte@nestlabs.com>
Subject: Re: Extreme time jitter with suspend/resume cycles
Date: Thu, 5 Oct 2017 23:33:55 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1710052331310.2398@nanos> (raw)
In-Reply-To: <alpine.DEB.2.20.1710052302440.2398@nanos>

On Thu, 5 Oct 2017, Thomas Gleixner wrote:
> On Thu, 5 Oct 2017, Gabriel Beddingfield wrote:
> 
> > Hi Thomas,
> > 
> > On Thu, Oct 5, 2017 at 11:01 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > >> > Which SoC/clocksource driver are you talking about?
> > >>
> > >> NXP i.MX 6SoloX
> > >> drivers/clocksource/timer-imx-gpt.c
> > >
> > > So that clocksource driver looks correct. Do you have an idea in which
> > > context this time jump happens? Does it happen when you exercise your high
> > > frequency suspend/resume dance or is that happening just when you let the
> > > machine run forever as well?
> > 
> > We couldn't devise any reproduction steps. We observed it happening at
> > unexpected times in a fleet of devices -- and we couldn't find any
> > patterns to clue us in.
> 
> Ok. Did you talk to NXP about that? Or did you try to exercise reads in a
> loop to detect the wreckage and maybe a pattern in there?

The reason I'm asking is to exclude any weird issue in the timekeeping
code, which is still a possibility, despite the fact that I went through it
with a fine comb after stumbling over that check in the resume path.

Thanks,

	tglx

  parent reply	other threads:[~2017-10-05 21:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 16:11 Extreme time jitter with suspend/resume cycles Gabriel Beddingfield
2017-10-04 18:22 ` Thomas Gleixner
2017-10-04 23:10   ` Gabriel Beddingfield
2017-10-05  0:20     ` John Stultz
2017-10-05 16:46       ` Gabriel Beddingfield
2017-10-05 11:01     ` Thomas Gleixner
2017-10-05 16:47       ` Gabriel Beddingfield
2017-10-05 18:01         ` Thomas Gleixner
2017-10-05 20:51           ` Gabriel Beddingfield
2017-10-05 21:04             ` Thomas Gleixner
2017-10-05 21:12               ` Gabriel Beddingfield
2017-10-05 21:33               ` Thomas Gleixner [this message]
2017-10-05  0:16 ` John Stultz
2017-10-05 11:05   ` Thomas Gleixner
2017-10-05 14:11     ` Thomas Gleixner
2017-10-05 11:08   ` Miroslav Lichvar
2017-10-05 20:14   ` Gabriel Beddingfield
2017-10-05 21:31     ` Thomas Gleixner
2017-10-15  6:39 ` Introduce clock precision to help time travelers was " Pavel Machek
2017-10-18 20:34   ` Alan Cox
2017-10-18 21:08     ` Pavel Machek
2017-10-18 21:26       ` Alexandre Belloni
2017-10-18 21:56         ` Pavel Machek
2017-11-04 15:34           ` Alexandre Belloni

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=alpine.DEB.2.20.1710052331310.2398@nanos \
    --to=tglx@linutronix.de \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=gabe@nestlabs.com \
    --cc=guy@nestlabs.com \
    --cc=hharte@nestlabs.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=sboyd@codeaurora.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