Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1594323

Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1

Path csiph.com!weretis.net!feeder4.news.weretis.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod
From Romain Izard <romain.izard.pro@gmail.com>
Newsgroups linux.kernel
Subject Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1
Date Tue, 07 Mar 2017 16:10:01 +0100
Message-ID <tioUp-PI-9@gated-at.bofh.it> (permalink)
References <thYZY-7uY-17@gated-at.bofh.it>
X-Original-To linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, LKML <linux-kernel@vger.kernel.org>, Daniel Lezcano <daniel.lezcano@linaro.org>, Nicolas Ferre <nicolas.ferre@microchip.com>
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=mobile-devices-fr.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hxClTq9slvtWTVWsykA5ZRFdR3X2LvMgJ4DDJto6VK4=; b=hSFx0hAgei0ZijN6P7YXi68Yfe6pZ8L/TOntkHKZMA219ag/rfS0ggPtXABL6v1Sxo ZYBlx7JtEhxdBHzi9btyN//1FjXWHdGli6CKSlgF3NtQ4pHo2idZ3Edwfjo7Y2JyP5j/ Hby4PR5tWx1CM2LD5mn+P9ZcJkxWmQRXXcmiR9ZtFqCP5IYCI8Ih9Z21hOxgk51QG071 8yUwmVTevKhlFo9/YME9zlHW9iowuL0CqzAMBbg8gV6lmUNRLzngvMD03BvpnAjtL/PK z/AMPp07ZAjm8T/F19AGk06bErw6i+V5zSrRedBlM8qYbKfDZsNrik9nlu8px2Wcj4bF Gx2A==
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hxClTq9slvtWTVWsykA5ZRFdR3X2LvMgJ4DDJto6VK4=; b=GQHZLZB+4kd3ugFaXvJ21E82uPxv+AV15su8c6Avs5cstM8nsWCL1MtQbsp5+ormMY px7xJme6JfswpIK0rTiKee0bIGNIuGpSz05jIiaq/oR+eJLe77DnF91RO+NeT51daMQa v5RE4Es7FSzhefYpNtSVHiBG+3fZo/jMDXV/qe18UYGDlt5iF6eYPOlQfzA9487cpiJE qJU7jsB7PEwhXED2juXiiDaFmGQ+DNYsCbM4MSC4Inm29jhzv2CyvlXeUPUJNsrK6RRW eHaIo09jDCKRbq0GN8kQswLxTTr3nJeZMdbvH3eVyNRi6lvGDMXmgqyhcfxFbQ9j+h1L bPAQ==
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=hxClTq9slvtWTVWsykA5ZRFdR3X2LvMgJ4DDJto6VK4=; b=SaLnDCbraWP6KcTT1lUbr1KGCu3tQR1ifUTlwVe7k+obAMNxtFIRclwPYUTaIi4Noe l262XljgmPf6nJ4Y4KiuhiFVgQJX8cwamgCyrbgPTzH9d9Vdg3gqTUcoqYrJAyA/m88O H9HfL9fXFcGqhLyddKazC9dXOxF596UT1YqwmJ8bj8zpo2kVrUm3WGlfZHUud14hPCFk DxnL/uLgn2Ulz322XzxdFApr9y2PwP+OnwphJzsd7xSDZwvbPaGPQ0ejcL04XDQ3HRQO Tio/DPtvvNhOr6i0VnN8lVs0pS8ghZc5xQad4RWRT4cbemt6+R+5yeOjQOsEjyxUCWdE 2EYg==
X-Gm-Message-State AMke39nXkC725BTY8SEQyoesHdvIL4NhcQK3phOPBYqMRz+ozRW4Qc+tkPvrTYWxdnk6JCSyuqf6VYBHYEiTlhxq
X-Received by 10.237.42.194 with SMTP id t60mr895838qtd.269.1488899131119; Tue, 07 Mar 2017 07:05:31 -0800 (PST)
MIME-Version 1.0
X-Google-Sender-Auth hRE-niAXbLhgd9hP3EAFf4uuo7g
Content-Type text/plain; charset=UTF-8
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 46
Organization linux.* mail to news gateway
X-Original-Cc Thomas Gleixner <tglx@linutronix.de>, David Engraf <david.engraf@sysgo.com>
X-Original-Date Tue, 7 Mar 2017 16:05:10 +0100
X-Original-Message-ID <CAGkQfmMxame-m+Te59EnFACqmk9TU-3Mhi6BctQWDPKuy38FXg@mail.gmail.com>
X-Original-References <CAGkQfmPP7w09xutsK5OhfWzNfCyC3Bj8VmoFxDiB5eqAFnZBbQ@mail.gmail.com>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1594323

Show key headers only | View raw


2017-03-06 12:28 GMT+01:00 Romain Izard <romain.izard.pro@gmail.com>:
>
> While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained
> board. The boot log contains the following warning:
>
> [    0.100000] ------------[ cut here ]------------
> [    0.100000] WARNING: CPU: 0 PID: 1 at
> ../kernel/time/sched_clock.c:180 sched_clock_register+0x44/0x1e4
> [    0.100000] CPU: 0 PID: 1 Comm: swapper Not tainted 4.11.0-rc1+ #3
> [    0.100000] Hardware name: Atmel SAMA5
> [    0.100000] [<c010c494>] (unwind_backtrace) from [<c010a558>]
> (show_stack+0x10/0x14)
> [    0.100000] [<c010a558>] (show_stack) from [<c0115654>] (__warn+0xe0/0xf8)
> [    0.100000] [<c0115654>] (__warn) from [<c011571c>]
> (warn_slowpath_null+0x20/0x28)
> [    0.100000] [<c011571c>] (warn_slowpath_null) from [<c090b0d0>]
> (sched_clock_register+0x44/0x1e4)
> [    0.100000] [<c090b0d0>] (sched_clock_register) from [<c091fb98>]
> (tcb_clksrc_init+0x1ac/0x360)
> [    0.100000] [<c091fb98>] (tcb_clksrc_init) from [<c0900d8c>]
> (do_one_initcall+0xb4/0x15c)
> [    0.100000] [<c0900d8c>] (do_one_initcall) from [<c0900f68>]
> (kernel_init_freeable+0x134/0x1c4)
> [    0.100000] [<c0900f68>] (kernel_init_freeable) from [<c06bfc64>]
> (kernel_init+0x8/0x10c)
> [    0.100000] [<c06bfc64>] (kernel_init) from [<c0107318>]
> (ret_from_fork+0x14/0x3c)
> [    0.100000] ---[ end trace 7ce9be9d7cf6f800 ]---
> [    0.100012] sched_clock: 32 bits at 10MHz, resolution 96ns, wraps
> every 206986376143ns
>
> This is related to the following commit:
> 7b9f1d16e6d1 clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock
>
> When we call sched_clock_register from tcb_clksrc_init from
> arch_initcall, we are too late as sched expects all the candidates for
> its clock to be registered before interrupts are enabled. This warning
> does not prevent the tcb clock from being used.
>

After some more use with 4.11-rc1, I also noticed that the timestamp for
printk rolls over to 0 after only 413s. Reverting the aforementioned commit
fixes it.

-- 
Romain Izard

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Warning on boot on SAMA5D2 with Linux 4.11-rc1 Romain Izard <romain.izard.pro@gmail.com> - 2017-03-06 12:30 +0100
  Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1 Romain Izard <romain.izard.pro@gmail.com> - 2017-03-07 16:10 +0100
    Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1 David Engraf <david.engraf@sysgo.com> - 2017-03-07 16:20 +0100
      Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1 Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-03-07 18:40 +0100

csiph-web