From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D693EC6FD19 for ; Thu, 16 Mar 2023 13:46:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229796AbjCPNqn (ORCPT ); Thu, 16 Mar 2023 09:46:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47430 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229687AbjCPNqi (ORCPT ); Thu, 16 Mar 2023 09:46:38 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 640FECB046; Thu, 16 Mar 2023 06:46:06 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 8C5F162035; Thu, 16 Mar 2023 13:46:03 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EDF3CC4339E; Thu, 16 Mar 2023 13:46:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1678974363; bh=F113rtx7fosIYjNGw0x4G5PNjBcnLmKibxBii2Azr5E=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=aa4x4cU8c6w9Jj4ftot6l/fHGmyBWuXWV0DiiWWDDjxq/RZKdCYzEnjJSp6iJo3R/ ihywjhfdftQ4mUJUFWOD4PxwS8tb+S1jlZ+IkfqF2tcDBVcVAyLI6HNXoU2FAQIaGJ oKoi+HvHsn8pKB1OWr1wBqUr0Yy2sSNA5xX6NS2OmAiX3cUb1/zj9/Vbxj2GKyYM/b 7ci3XwJc/julq9/Ks3ykLKNNd8Td2DggLaEmPrVeSOfIjYNi1yHxoWwpi4VDcVERXb 9xiSoT4HF9KTOQT2gmEUP5c0EP08o9w8uXdqAdQ3kS/sK9iL4IMIT/Fz4xpv4ZE8YL bEex2arl/uryg== Received: by mail-lf1-f47.google.com with SMTP id bp27so2437659lfb.6; Thu, 16 Mar 2023 06:46:02 -0700 (PDT) X-Gm-Message-State: AO0yUKWQPn76ZlnkoEcG3QD/zz9l1dnpYZtzISvR7befeyWeRFORndCP OZLkSSUCnflXsr/bqHQ0iWXtHWt2OFXvEQNp3jw= X-Google-Smtp-Source: AK7set/hZhTTxx+ba6zxHqxrpeCE/1sHTHvt3oX9fqbiHRhfQAqdyaDGgH984DnvhJrTQFobGwjsQdBYa9VSsh6Kk1Q= X-Received: by 2002:ac2:5519:0:b0:4e8:4b7a:6b73 with SMTP id j25-20020ac25519000000b004e84b7a6b73mr3249249lfk.4.1678974360920; Thu, 16 Mar 2023 06:46:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ard Biesheuvel Date: Thu, 16 Mar 2023 14:45:49 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: kernel 6.2 stuck at boot (efi_call_rts) on arm64 To: Andrea Righi Cc: "Jason A. Donenfeld" , Paolo Pisati , linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, Darren Hart Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 16 Mar 2023 at 13:50, Andrea Righi wrote: > > On Thu, Mar 16, 2023 at 01:43:32PM +0100, Ard Biesheuvel wrote: > > On Thu, 16 Mar 2023 at 13:41, Andrea Righi wrote: > > > > > > On Thu, Mar 16, 2023 at 01:38:30PM +0100, Ard Biesheuvel wrote: > > > > On Thu, 16 Mar 2023 at 13:21, Ard Biesheuvel wrote: > > > > > > > > > > On Thu, 16 Mar 2023 at 12:34, Andrea Righi wrote: > > > > > > > > > > > > On Thu, Mar 16, 2023 at 11:18:21AM +0100, Ard Biesheuvel wrote: > > > > > > > On Thu, 16 Mar 2023 at 11:03, Andrea Righi wrote: > > > > > > > > > > > > > > > > On Thu, Mar 16, 2023 at 10:55:58AM +0100, Ard Biesheuvel wrote: > > > > > > > > > (cc Darren) > > > > > > > > > > > > > > > > > > On Thu, 16 Mar 2023 at 10:45, Andrea Righi wrote: > > > > > > > > > > > > > > > > > > > > On Thu, Mar 16, 2023 at 08:58:20AM +0100, Ard Biesheuvel wrote: > > > > > > > > > > > Hello Andrea, > > > > > > > > > > > > > > > > > > > > > > On Thu, 16 Mar 2023 at 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. > > > > > > > > > > > > > > > > > > > > > > > > Any suggestion? Let me know if you want me to do any specific test. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks for the report. > > > > > > > > > > > > > > > > > > > > > > This is most likely the EFI SetVariable() call going off into the > > > > > > > > > > > weeds and never returning. > > > > > > > > > > > > > > > > > > > > > > Is this an Ampere Altra system by any chance? Do you see it on > > > > > > > > > > > different types of hardware? > > > > > > > > > > > > > > > > > > > > This is: Ampere eMAG / Lenovo ThinkSystem HR330a. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Could you check whether SetVariable works on this system? E.g. by > > > > > > > > > > > updating the EFI boot timeout (sudo efibootmgr -t )? > > > > > > > > > > > > > > > > > > > > ubuntu@kuzzle:~$ sudo efibootmgr -t 10 > > > > > > > > > > ^C^C^C^C > > > > > > > > > > > > > > > > > > > > ^ Stuck there, so it really looks like SetVariable is the problem. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Could you please share the output of > > > > > > > > > > > > > > > > > > dmidecode -s bios > > > > > > > > > dmidecode -s system-family > > > > > > > > > > > > > > > > $ sudo dmidecode -s bios-vendor > > > > > > > > LENOVO > > > > > > > > $ sudo dmidecode -s bios-version > > > > > > > > hve104r-1.15 > > > > > > > > $ sudo dmidecode -s bios-release-date > > > > > > > > 02/26/2021 > > > > > > > > $ sudo dmidecode -s bios-revision > > > > > > > > 1.15 > > > > > > > > $ sudo dmidecode -s system-family > > > > > > > > Lenovo ThinkSystem HR330A/HR350A > > > > > > > > > > > > > > > > > > > > > > Thanks > > > > > > > > > > > > > > Mind checking if this patch fixes your issue as well? > > > > > > > > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/commit/?h=altra-fix&id=77fa99dd4741456da85049c13ec31a148f5f5ac0 > > > > > > > > > > > > Unfortunately this doesn't seem to be enough, I'm still getting the same > > > > > > problem also with this patch applied. > > > > > > > > > > > > > > > > Thanks for trying. > > > > > > > > > > How about the last 3 patches on this branch? > > > > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-smbios-altra-fix > > > > > > > > Actually, that may not match your hardware. > > > > > > > > Does your kernel log have a line like > > > > > > > > SMCCC: SOC_ID: ID = jep106:036b:0019 Revision = 0x00000102 > > > > > > > > ? > > > > > > $ sudo dmesg | grep "SMCCC: SOC_ID" > > > [ 5.320782] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... > > > > > > > Thanks. Could you share the entire dmidecode output somewhere? Or at > > least the type 4 record(s)? > > Sure, here's the full output of dmidecode: > https://pastebin.ubuntu.com/p/4ZmKmP2xTm/ > Thanks. I have updated my SMBIOS patches to take the processor version 'eMAG' into account, which appears to be what these boxes are using. I have updated the efi/urgent branch here with the latest versions. Mind giving them a spin? In the mean time, just for the record - could you please run this as well? hexdump -C /sys/firmware/dmi/entries/4-0/raw (as root) There seem to be eMAG boxes that put the type 4 ID in the wrong word order, so I'd like to make sure we have a record of the binary representation. Thanks a lot for spending time on this.