linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking #update (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Andrea Righi <andrea.righi@canonical.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Paolo Pisati <paolo.pisati@canonical.com>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: kernel 6.2 stuck at boot (efi_call_rts) on arm64
Date: Wed, 5 Apr 2023 14:50:36 +0200	[thread overview]
Message-ID: <fbe78d1a-b75c-3565-9a8d-2a9aecc1eed3@leemhuis.info> (raw)
In-Reply-To: <59064730-e731-d137-ae92-e19622a122d0@leemhuis.info>

[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]

On 16.03.23 10:45, Linux regression tracking #adding (Thorsten Leemhuis)
wrote:
> On 16.03.23 08:54, Andrea Righi wrote:
>> Hello,
>>
>> the latest v6.2.6 kernel fails to boot on some arm64 systems, the kernel
>> gets stuck and never completes the boot. On the console I see this:
>>
>> [   72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
>> [   72.049571] rcu:     22-...0: (30 GPs behind) idle=b10c/1/0x4000000000000000 softirq=164/164 fqs=6443
>> [   72.058520]     (detected by 28, t=15005 jiffies, g=449, q=174 ncpus=32)
>> [   72.064949] Task dump for CPU 22:
>> [   72.068251] task:kworker/u64:5   state:R  running task     stack:0     pid:447   ppid:2      flags:0x0000000a
>> [   72.078156] Workqueue: efi_rts_wq efi_call_rts
>> [   72.082595] Call trace:
>> [   72.085029]  __switch_to+0xbc/0x100
>> [   72.088508]  0xffff80000fe83d4c
>>
>> After that, as a consequence, I start to get a lot of hung task timeout traces.
>>
>> I tried to bisect the problem and I found that the offending commit is
>> this one:
>>
>>  e7b813b32a42 ("efi: random: refresh non-volatile random seed when RNG is initialized")
>>
>> I've reverted this commit for now and everything works just fine, but I
>> was wondering if the problem could be caused by a lack of entropy on
>> these arm64 boxes or something else.
> 
> Thanks for the report. To be sure the issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
> tracking bot:
> 
> #regzbot ^introduced e7b813b32a42
> #regzbot title efi: stuck at boot (efi_call_rts) on arm64
> #regzbot ignore-activity

#regzbot fix: eb684408f3ea4856
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.



      reply	other threads:[~2023-04-05 12:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16  7:54 kernel 6.2 stuck at boot (efi_call_rts) on arm64 Andrea Righi
2023-03-16  7:58 ` Ard Biesheuvel
2023-03-16  9:45   ` Andrea Righi
2023-03-16  9:55     ` Ard Biesheuvel
2023-03-16 10:03       ` Andrea Righi
2023-03-16 10:18         ` Ard Biesheuvel
2023-03-16 11:33           ` Andrea Righi
2023-03-16 12:21             ` Ard Biesheuvel
2023-03-16 12:38               ` Ard Biesheuvel
2023-03-16 12:41                 ` Andrea Righi
2023-03-16 12:43                   ` Ard Biesheuvel
2023-03-16 12:49                     ` Andrea Righi
2023-03-16 13:45                       ` Ard Biesheuvel
2023-03-16 13:46                         ` Ard Biesheuvel
2023-03-16 13:50                         ` Andrea Righi
2023-03-16 13:53                           ` Ard Biesheuvel
2023-03-16 13:59                             ` Andrea Righi
2023-03-16 14:06                               ` Ard Biesheuvel
2023-03-16 14:08                                 ` Ard Biesheuvel
2023-03-16 14:25                                   ` Andrea Righi
2023-03-16 17:52                                   ` Andrea Righi
2023-03-16 18:55                                     ` Ard Biesheuvel
2023-03-16 18:57                                       ` Andrea Righi
2023-03-16 22:28                                       ` Darren Hart
2023-03-18 10:35                                         ` Ard Biesheuvel
2023-03-20 18:00                                           ` Darren Hart
2023-04-13 20:24                                           ` Andrea Righi
2023-04-17 22:05                                             ` Darren Hart
2023-04-18  5:42                                               ` Andrea Righi
2023-03-16  9:45 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-04-05 12:50   ` Linux regression tracking #update (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=fbe78d1a-b75c-3565-9a8d-2a9aecc1eed3@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=Jason@zx2c4.com \
    --cc=andrea.righi@canonical.com \
    --cc=ardb@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.pisati@canonical.com \
    --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).