All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "Linux ARM" <linux-arm-kernel@lists.infradead.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	"Linux Regressions" <regressions@lists.linux.dev>,
	rcu <rcu@vger.kernel.org>, linux-clk <linux-clk@vger.kernel.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Dan Carpenter" <dan.carpenter@linaro.org>,
	"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Mark Brown" <broonie@kernel.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	"Anders Roxell" <anders.roxell@linaro.org>,
	"Aishwarya TCV" <aishwarya.tcv@arm.com>
Subject: Re: next-20241031: kernel/time/clockevents.c:455 clockevents_register_device
Date: Thu, 31 Oct 2024 10:56:23 +0100	[thread overview]
Message-ID: <ZyNUR4oi8TXeEpYi@lothringen> (raw)
In-Reply-To: <CA+G9fYtb5vAnEiHupwsnaeZ7uzdko_WAcjw9ZAFkHNXBVhi1EA@mail.gmail.com>

Hi,

On Thu, Oct 31, 2024 at 02:10:14PM +0530, Naresh Kamboju wrote:
> The QEMU-ARM64 boot has failed with the Linux next-20241031 tag.
> The boot log shows warnings at clockevents_register_device and followed
> by rcu_preempt detected stalls.
> 
> However, the system did not proceed far enough to reach the login prompt.
> The fvp-aemva, Qemu-arm64, Qemu-armv7 and Qemu-riscv64 boot failed.
> 
> Please find the incomplete boot log links below for your reference.
> The Qemu version is 9.0.2.
> 
> This is always reproducible.
> First seen on Linux next-20241031 tag.
>   Good: next-20241030
>   Good: next-20241031
> 
> qemu-arm64:
>   boot:
>     * clang-19-lkftconfig
>     * gcc-13-lkftconfig
>     * clang-nightly-lkftconfig
> 
> qemu-armv7:
>   boot:
>     * clang-19-lkftconfig
>     * gcc-13-lkftconfig
>     * clang-nightly-lkftconfig
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> Boot log:
> -------
> [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x000f0510]
>     0.000000] Linux version 6.12.0-rc5-next-20241031 (tuxmake@tuxmake)
> (aarch64-linux-gnu-gcc (Debian 13.3.0-5) 13.3.0, GNU ld (GNU Binutils
> for Debian) 2.43.1) #1 SMP PREEMPT @1730356841
> [    0.000000] KASLR enabled
> [    0.000000] random: crng init done
> [    0.000000] Machine model: linux,dummy-virt
> <trim>
> <6>[    0.216503] GICv3: CPU1: found redistributor 1 region 0:0x00000000080c0000
> <6>[    0.218511] GICv3: CPU1: using allocated LPI pending table
> @0x0000000100250000
> <4>[    0.220528] ------------[ cut here ]------------
> <4>[ 0.220657] WARNING: CPU: 1 PID: 0 at kernel/time/clockevents.c:455
> clockevents_register_device (kernel/time/clockevents.c:455

It's possible that I messed up something with clockevents.

Can you try to reproduce with:

git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
	timers/core

And if so it's possible that the bad commit is somewhere between:

    17a8945f369c (clockevents: Improve clockevents_notify_released() comment)

and

    bf9a001fb8e4 (clocksource/drivers/timer-tegra: Remove clockevents shutdown call on offlining)

I wish I could reproduce on my own but I don't have easy
access to such hardware.

Thanks.


  parent reply	other threads:[~2024-11-01 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31  8:40 next-20241031: kernel/time/clockevents.c:455 clockevents_register_device Naresh Kamboju
2024-10-31  9:42 ` Thomas Gleixner
2024-10-31  9:57   ` Frederic Weisbecker
2024-10-31  9:56 ` Frederic Weisbecker [this message]
2024-10-31 10:42   ` Thomas Gleixner

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=ZyNUR4oi8TXeEpYi@lothringen \
    --to=frederic@kernel.org \
    --cc=aishwarya.tcv@arm.com \
    --cc=alex.bennee@linaro.org \
    --cc=anders.roxell@linaro.org \
    --cc=anna-maria@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=paulmck@kernel.org \
    --cc=peter.maydell@linaro.org \
    --cc=rcu@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.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.