From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core <openembedded-core@lists.openembedded.org>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Subject: Re: [OE-core] Dilemma on changes - merge or not to merge (e.g. 6.4)
Date: Thu, 17 Aug 2023 23:22:11 -0400 [thread overview]
Message-ID: <ZN7j425iXGBPbS5i@windriver.com> (raw)
In-Reply-To: <15f7e67b-afd7-7504-aa23-41a4c3cb62a1@prevas.dk>
[Re: [OE-core] Dilemma on changes - merge or not to merge (e.g. 6.4)] On 16/08/2023 (Wed 09:55) Rasmus Villemoes wrote:
> On 15/08/2023 15.08, Paul Gortmaker via lists.openembedded.org wrote:
> > [Dilemma on changes - merge or not to merge (e.g. 6.4)] On 14/08/2023 (Mon 10:54) Richard Purdie wrote:
> >
> >> Remaining are:
> >> * an error upon boot on preempt-rt on qemux86-64
> >> (e.g. https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/7616/steps/36/logs/stdio)
> >> We'll probably just have to ignore it in parselogs as it has been??
> >> around for a while and nobody seems interested in fixing it upstream.
> >
> > Just back from vacation and I see an internal report of 10-ish at boot
>
> it seems to be rate-limited to 10 per boot, so it should never appear
> more than those 10ish times:
>
> static bool report_idle_softirq(void)
> {
> ...
> if (ratelimit >= 10)
> return false;
> ...
> ratelimit++;
> ...
Amusingly enough - you were looking right at the problem. Just a few
stable kernels ago, it was inadvertently ratelimited to zero. :-P
https://lists.openembedded.org/g/openembedded-core/message/186343
Paul.
--
> }
>
> (it's all non-atomic/lockfree, so ofc it could just happen to get
> emitted 11 or 12 times if the stars align just right...)
>
> >
> > NOHZ tick-stop error: local softirq work is pending, handler #80!!!
> >
> > ..on the 6.1.43-rt10-yocto-preempt-rt kernel, on real hardware. So it
> > seems we can't blame that one entirely on v6.4 kernel (or qemu).
> >
> > We used to get (late 3.x and 4.x era) pretty common "NOHZ: local softirq
> > pending" messages even on common/popular distro kernels. But I haven't
> > seen those for a long time and they didn't scream "error" or have the
> > alarmist three exclamation marks either.
>
> FWIW, we're also seeing exactly that "NOHZ tick-stop error" message on
> 6.4.6-rt8 running on a couple of different imx8mp based boards.
>
> Rasmus
>
next prev parent reply other threads:[~2023-08-18 3:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 9:54 Dilemma on changes - merge or not to merge (e.g. 6.4) Richard Purdie
2023-08-15 13:08 ` Paul Gortmaker
2023-08-15 13:38 ` Richard Purdie
2023-08-16 7:55 ` [OE-core] " Rasmus Villemoes
2023-08-18 3:22 ` Paul Gortmaker [this message]
2023-08-22 9:31 ` Richard Purdie
[not found] ` <177DAAB2E4C3384A.4797@lists.openembedded.org>
2023-08-22 11:07 ` Richard Purdie
[not found] ` <177DAFEBFB5EB0D2.24073@lists.openembedded.org>
2023-08-22 11:47 ` Richard Purdie
2023-08-22 12:20 ` Mikko Rapeli
2023-08-22 12:28 ` Richard Purdie
2023-08-22 12:31 ` Alexander Kanavin
[not found] ` <177DB4530EBE3FA3.24073@lists.openembedded.org>
2023-08-22 14:49 ` Richard Purdie
[not found] ` <177DBC07E94591CC.4797@lists.openembedded.org>
2023-08-22 21:08 ` Richard Purdie
[not found] ` <177DD0B30D8FEDF8.27837@lists.openembedded.org>
2023-08-22 22:01 ` Richard Purdie
[not found] ` <177DD39B5534099F.27837@lists.openembedded.org>
2023-08-23 21:16 ` Richard Purdie
[not found] ` <177E1FB73F514F09.8058@lists.openembedded.org>
2023-08-24 14:04 ` Richard Purdie
[not found] ` <177E56C1DFAB4DFC.13053@lists.openembedded.org>
2023-08-24 20:18 ` Richard Purdie
2023-08-25 5:04 ` Frédéric Martinsons
2023-08-25 6:27 ` Mikko Rapeli
2023-08-25 6:34 ` Richard Purdie
2023-08-25 7:26 ` Mikko Rapeli
[not found] ` <177E8CC0D944344B.23833@lists.openembedded.org>
2023-08-30 10:43 ` Richard Purdie
[not found] ` <178023427EE7BA0B.20206@lists.openembedded.org>
2023-08-30 13:03 ` Richard Purdie
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=ZN7j425iXGBPbS5i@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rasmus.villemoes@prevas.dk \
--cc=richard.purdie@linuxfoundation.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.