All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joerg Vehlow <lkml@jv-coder.de>
Cc: stable@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Miroslav Lichvar <mlichvar@redhat.com>,
	John Stultz <john.stultz@linaro.org>
Subject: Re: [4.14] Failing selftest timer/adjtick
Date: Wed, 10 Feb 2021 14:00:51 +0100	[thread overview]
Message-ID: <YCPZA7nkGGDru3xw@kroah.com> (raw)
In-Reply-To: <e76744b3-342a-1f75-cba6-51fd8b01c5ce@jv-coder.de>

On Wed, Feb 10, 2021 at 01:43:10PM +0100, Joerg Vehlow wrote:
> Hi,
> 
> we found that on the selftest timer/adjtick fails on arm64 (tested on some
> renesas board and in qemu) quite frequently.
> By bisecting the kernel I found that it stopped failing after commit
> 78b98e3c5a66 (timekeeping/ntp: Determine the multiplier directly from NTP
> tick length).
> Should this patch be applied to 4.14 and is it even possible or could it
> break something else?

Have you tried applying it to that tree to see if it solves your problem
and works properly?  If so, please feel free to provide a working
backported copy, with your signed-off-by and we can consider it.

But, why not just use 4.19 or newer on that system?

thanks,

greg k-h

  reply	other threads:[~2021-02-10 13:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 12:43 [4.14] Failing selftest timer/adjtick Joerg Vehlow
2021-02-10 13:00 ` Greg KH [this message]
2021-02-10 13:07   ` Joerg Vehlow
2021-02-10 13:19     ` Miroslav Lichvar
2021-02-10 18:59       ` Naresh Kamboju
2021-02-11 10:34         ` Joerg Vehlow
2021-02-11 10:33       ` Joerg Vehlow
2021-02-11 10:45         ` Greg KH
2021-02-11 10:59         ` Miroslav Lichvar
2021-02-18  7:05           ` Joerg Vehlow
2021-03-01  7:04           ` Joerg Vehlow

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=YCPZA7nkGGDru3xw@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=lkml@jv-coder.de \
    --cc=mingo@kernel.org \
    --cc=mlichvar@redhat.com \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.