From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 41641C4332D for ; Wed, 10 Feb 2021 13:03:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0C47664E7E for ; Wed, 10 Feb 2021 13:03:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229934AbhBJNDG (ORCPT ); Wed, 10 Feb 2021 08:03:06 -0500 Received: from mail.kernel.org ([198.145.29.99]:33736 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231543AbhBJNBg (ORCPT ); Wed, 10 Feb 2021 08:01:36 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 3D67D64E3B; Wed, 10 Feb 2021 13:00:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1612962053; bh=nrXu6xAPjOcZpDR/4duoPi3UpzdK1/f3kCdIhheWMhw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=TJKEKIxWT+Z3R8hf5yttBCH7MbYjeJYP2zckMhhhVQnHcjTxQ0TOmGSF0vBaT0fkX UYUlpyb9qmWxNMjzecLREgMUROavGJC5mTe9Kb671BFGqrhChBOIFGKw+Z8btbZz0B MO5tRF1VOBMLiY76vkC7sIzDgiO+6JfJADlKxvXE= Date: Wed, 10 Feb 2021 14:00:51 +0100 From: Greg KH To: Joerg Vehlow Cc: stable@vger.kernel.org, Ingo Molnar , Miroslav Lichvar , John Stultz Subject: Re: [4.14] Failing selftest timer/adjtick Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 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