From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-crypto@vger.kernel.org
Subject: Re: [REGESSION] Bug 216502 - slow crng initialization on Rockchip 3399 (Friendyarm NanoPi M4) #forregzbot
Date: Thu, 8 Dec 2022 16:32:37 +0100 [thread overview]
Message-ID: <8bcbbce3-13ce-9b5e-38c2-235a93bd18e2@leemhuis.info> (raw)
In-Reply-To: <4deaa04b-f103-9cc4-7946-9ea69afd94d0@leemhuis.info>
[Note: this mail contains only information for Linux kernel regression
tracking. Mails like these contain '#forregzbot' in the subject to make
then easy to spot and filter out. The author also tried to remove most
or all individuals from the list of recipients to spare them the hassle.]
On 18.09.22 14:17, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker speaking.
>
> I noticed a regression report in bugzilla.kernel.org. As many (most?)
> kernel developer don't keep an eye on it, I decided to forward it my
> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216502 :
>
>> Crng initialization time has significantly increased on Rockchip
>> 3399-based Friendyarm NanoPi M4 in v6.0.0-rc5 compared to v5.18.0 (from
>> 2.36s since rootfs mounted to 8.55s since rootfs mounted). Bisection
>> points at 78c768e619fb ("random: vary jitter iterations based on cycle
>> counter speed"). Manually reverting that commit on top of v6.0.0-rc5
>> fixes the issue. Attached dmesg logs correspond to vanilla v6.0.0-rc5
>> ("bad") and v6.0.0-rc5 with 78c768e619fb reverted ("good").
> See the ticket for more details. Apologies if I forwarded it to the
> wrong folks, I cover a lot of ground and thus sometimes get things
> wrong. :-/
>
> BTW, I'd also like to add the report to the list of tracked regressions
> to ensure it's doesn't fall through the cracks in the end:
>
> #regzbot introduced: 78c768e619fb
> https://bugzilla.kernel.org/show_bug.cgi?id=216502
> #regzbot ignore-activity
#regzbot inconclusive: a proper RNG driver for the soc afaics should fix
this, which apparently satisfies the reporter
prev parent reply other threads:[~2022-12-08 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 12:17 [REGESSION] Bug 216502 - slow crng initialization on Rockchip 3399 (Friendyarm NanoPi M4) Thorsten Leemhuis
2022-09-19 9:15 ` Jason A. Donenfeld
2022-12-08 15:32 ` Thorsten Leemhuis [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=8bcbbce3-13ce-9b5e-38c2-235a93bd18e2@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).