From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Eta Zhou <stephen.eta.zhou@gmail.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Guenter Roeck <groeck7@gmail.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] clocksource: timer-sp804: Fix an Oops when read_current_timer is called on ARM32 platforms where the SP804 is not registered as the sched_clock.
Date: Tue, 28 Apr 2026 09:16:06 -0700 [thread overview]
Message-ID: <d64aa3ce-7da9-48c5-b45c-c9d2d4a801f8@roeck-us.net> (raw)
In-Reply-To: <ae7afpmHlfDelyPi@stephen.localdomain>
Hi Stephen,
On Mon, Apr 27, 2026 at 11:39:42AM +0800, Stephen Eta Zhou wrote:
> On 26/04/26 20:25, Guenter Roeck wrote:
> > I found that the integratorcp qemu emulation still hangs unpredictably
> > with this and the preceding patch in the tree.
>
> Hi Guenter,
>
> Thanks for the report.
>
> Could you share the QEMU command line, kernel config, and the detailed
> steps you used to reproduce the hang?
>
> I will try to reproduce it locally and debug it from my side.
>
No worries. As I said, this was purely informational. Ever since 6.18
Linux started to break on more and more platforms in my tests. I can not
keep up with testing or analyzing the problems, so as I find issues I
report it and stop testing if the problem persists over a couple of
releases. As in this case, it is obvious that no either one cares, that
it is a problem with qemu, or a problem with my setup. Given all that,
even if the problem is not related to my setup, it would be a waste of time
trying to track it down or to keep testing.
Thanks,
Guenter
prev parent reply other threads:[~2026-04-28 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 8:16 Stephen Eta Zhou
2026-01-29 21:32 ` [tip: timers/clocksource] clocksource/drivers/timer-sp804: " tip-bot2 for Stephen Eta Zhou
2026-04-27 3:25 ` [PATCH v2] clocksource: timer-sp804: " Guenter Roeck
2026-04-27 3:39 ` Stephen Eta Zhou
2026-04-28 16:16 ` Guenter Roeck [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=d64aa3ce-7da9-48c5-b45c-c9d2d4a801f8@roeck-us.net \
--to=linux@roeck-us.net \
--cc=daniel.lezcano@linaro.org \
--cc=groeck7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=stephen.eta.zhou@gmail.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®