From: Thomas Gleixner <tglx@linutronix.de>
To: Frederic Weisbecker <frederic@kernel.org>,
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>,
"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 11:42:30 +0100 [thread overview]
Message-ID: <87r07wwo2x.ffs@tglx> (raw)
In-Reply-To: <ZyNUR4oi8TXeEpYi@lothringen>
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 :)
prev parent reply other threads:[~2024-10-31 10:44 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
2024-10-31 10:42 ` Thomas Gleixner [this message]
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=87r07wwo2x.ffs@tglx \
--to=tglx@linutronix.de \
--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=frederic@kernel.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=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.