[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87r07wwo2x.ffs@tglx>
Date: Thu, 31 Oct 2024 11:42:30 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Frederic Weisbecker <frederic@...nel.org>, Naresh Kamboju
<naresh.kamboju@...aro.org>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>, open list
<linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org, Linux
Regressions <regressions@...ts.linux.dev>, rcu <rcu@...r.kernel.org>,
linux-clk <linux-clk@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>, Dan
Carpenter <dan.carpenter@...aro.org>, Anna-Maria Behnsen
<anna-maria@...utronix.de>, Mark Brown <broonie@...nel.org>, Alex
Bennée
<alex.bennee@...aro.org>, Peter Maydell <peter.maydell@...aro.org>, "Paul
E. McKenney" <paulmck@...nel.org>, Vincent Guittot
<vincent.guittot@...aro.org>, Anders Roxell <anders.roxell@...aro.org>,
Aishwarya TCV <aishwarya.tcv@....com>
Subject: Re: next-20241031: kernel/time/clockevents.c:455
clockevents_register_device
On Thu, Oct 31 2024 at 10:56, Frederic Weisbecker wrote:
> On Thu, Oct 31, 2024 at 02:10:14PM +0530, Naresh Kamboju wrote:
>> <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.
Yes. You added the warning :)
> Can you try to reproduce with:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> timers/core
I force pushed the branch with the warning removed.
> I wish I could reproduce on my own but I don't have easy
> access to such hardware.
apt-get install qemu-system
gives you access to all supported architectures :)
Powered by blists - more mailing lists