From: Thomas Gleixner <tglx@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Tony Rodriguez <unixpro1970@gmail.com>
Cc: Linux kernel regressions list <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: the stuttering regression in 7.0: should I have done something different
Date: Fri, 15 May 2026 21:57:27 +0200 [thread overview]
Message-ID: <87se7sxx7c.ffs@tglx> (raw)
In-Reply-To: <a0feba9667ac6760f82137cca89afac7da786f22.camel@physik.fu-berlin.de>
Hi!
On Fri, May 15 2026 at 19:51, John Paul Adrian Glaubitz wrote:
> On Fri, 2026-05-15 at 17:35 +0200, Thomas Gleixner wrote:
>> > Thank you again for the debugging guidance and for the feedback on my
>> > original patch addressing the timer starvation issue. It was a pleasure
>> > contributing to the resolution.
>>
>> Thank you for going through the hassle of chasing it down and providing
>> the debug data to analyze it.
>>
>> I'm still puzzled how this went unnoticed for almost two decades:
>>
>> 112f48716d9f ("[SPARC64]: Add clocksource/clockevents support.")
>
> My suspicion is that it was previously visible only in certain edge cases,
> in particular on machines with many cores and high load.
>
> Case in point: In the past, SPARC LDOMs with lots of virtual CPUs could
> crash in rares cases when building packages such as GCC or LLVM and running
> their testsuites.
I assume those occasional failures did not leave conclusive hints around.
> I don't know if Tony's patch fixes this long-time issue that we have observed
> in the past on Debian's buildds, but I think that the chances aren't too bad.
Good luck!
> Thanks to both of you for hunting this down!
For some stupid reasons I like such puzzles :)
prev parent reply other threads:[~2026-05-15 19:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 16:30 the stuttering regression in 7.0: should I have done something different? Thorsten Leemhuis
2026-04-26 21:16 ` Greg KH
2026-05-08 5:51 ` John Paul Adrian Glaubitz
2026-05-08 6:33 ` Thorsten Leemhuis
[not found] ` <D5D19776-C809-4284-9417-F9A860877B98@gmail.com>
2026-05-08 7:50 ` Thorsten Leemhuis
2026-05-08 20:15 ` Tony Rodriguez
2026-05-08 20:21 ` Tony Rodriguez
2026-05-10 21:29 ` Thomas Gleixner
2026-05-11 3:13 ` Tony Rodriguez
2026-05-12 5:03 ` the stuttering regression in 7.0: should I have done something different Tony Rodriguez
2026-05-12 8:17 ` Thomas Gleixner
2026-05-12 21:43 ` Tony Rodriguez
2026-05-13 20:28 ` Thomas Gleixner
2026-05-14 7:24 ` Tony Rodriguez
2026-05-14 10:24 ` Thomas Gleixner
2026-05-15 4:47 ` Tony Rodriguez
2026-05-15 15:35 ` Thomas Gleixner
2026-05-15 17:51 ` John Paul Adrian Glaubitz
2026-05-15 19:57 ` 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=87se7sxx7c.ffs@tglx \
--to=tglx@kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sparclinux@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=unixpro1970@gmail.com \
/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.