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
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
On Sun, Sep 18, 2022 at 1:17 PM Thorsten Leemhuis
<[email protected]> wrote:
>
> Hi, this is your Linux kernel regression tracker speaking.
>
> I noticed a regression report in bugzilla.kernel.org. As many (most?)
I saw. I'll follow up there rather than splitting the thread to here.
[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