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 68464C6FD1F for ; Thu, 16 Mar 2023 13:50:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229936AbjCPNuz (ORCPT ); Thu, 16 Mar 2023 09:50:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54222 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230325AbjCPNux (ORCPT ); Thu, 16 Mar 2023 09:50:53 -0400 Received: from smtp-relay-internal-0.canonical.com (smtp-relay-internal-0.canonical.com [185.125.188.122]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 14360B06C0 for ; Thu, 16 Mar 2023 06:50:47 -0700 (PDT) Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id BFF2A44605 for ; Thu, 16 Mar 2023 13:50:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1678974645; bh=pGYSqv8yaZjHwdWIWY499NZFPJpTqI2+kvxO3gPkHlQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=BtKq5q3wvvtdF86vyMcEOTFU8J4DPGdstxvWryjI2MzreeuGFP6Id/vHIWD9G732D D14AJufhRbJ5E80IMsh5PFQnDGu43SPE+39Oeg7a3IzPEh1Y6UmzVWH4IFRmla23pM 7a3phyAAAvlWvnof6hqo4QixSfQrz+JRTzsewQq0KnQtfRPiZLdI7J/jXGaH+Z7EiJ Je9jjga0VfihQAfCXpSc8npiRZmcWWswJhS0ayNDFlg0QyYtLO/qdU5h4XsWy2VTd/ 0TN+Dakci9+SYXyMwGG1SH8isKHHIKpE1btvorsFeKA0CXArxqzVZDIb9goYgJhukZ RtOC7jeeMd3aw== Received: by mail-ed1-f71.google.com with SMTP id t26-20020a50d71a000000b005003c5087caso1861002edi.1 for ; Thu, 16 Mar 2023 06:50:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678974645; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=pGYSqv8yaZjHwdWIWY499NZFPJpTqI2+kvxO3gPkHlQ=; b=g5NIqB4oPAYj+vLuf8CZUo7bVDoCulYXDy3peQeBJmy2A+zXxpY7l05AFrr0vI47pP McbqYhEEe1WnXe5JCt9Avp6F8sWAmA4Wl2j2oSLOSt+PiHn5Qz2DnbTS42vWgyrf2fL9 jIeqDoU7kzsrxRXUII+TUumYxc/cVazMhtGYIaQNKKoJCv3SRAM6VPQPuTB4OLBS+pkX bLtpYKfU2PpoziGoiT1PyIYIeNHT7dmvTswyHgu/t4qY929imyCcK6WFY+b1H+EzGTDK zC21kTAgcEimbKhEhfgiDi0k6UI5Z05fMofOc2PRnOdBtGvGgTMi/JYBOc+u/9jAqCM5 VE3A== X-Gm-Message-State: AO0yUKWv8c9e4hOW36CHpawA6ZCVgRMo87bZM5UoL2GoozVjkDGJHobT fdO39SlhQ+yIXNk+PO3n5WzGTV0wV7LCALpy+Rr58B5qi7PbF1g+1SexQL/9TRTaLkMaqhHnfXW B2Leao7v+60QfcQjGjHkci2bsbsOpyP5Uc1epNc6PusZjBTqBygzR X-Received: by 2002:a17:906:1cc9:b0:8b1:78b6:bbd7 with SMTP id i9-20020a1709061cc900b008b178b6bbd7mr10468119ejh.10.1678974645289; Thu, 16 Mar 2023 06:50:45 -0700 (PDT) X-Google-Smtp-Source: AK7set8rFj9CLfYMtKX4xu8yZAFbvxkkKoyzadeV3sP5cC/9RNyysGcLx9qP04sgCB1N4DVtpzc+Dw== X-Received: by 2002:a17:906:1cc9:b0:8b1:78b6:bbd7 with SMTP id i9-20020a1709061cc900b008b178b6bbd7mr10468099ejh.10.1678974645012; Thu, 16 Mar 2023 06:50:45 -0700 (PDT) Received: from localhost (host-79-53-23-214.retail.telecomitalia.it. [79.53.23.214]) by smtp.gmail.com with ESMTPSA id lm15-20020a170906980f00b0093034e71b94sm993133ejb.65.2023.03.16.06.50.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Mar 2023 06:50:44 -0700 (PDT) Date: Thu, 16 Mar 2023 14:50:43 +0100 From: Andrea Righi To: Ard Biesheuvel Cc: "Jason A. Donenfeld" , Paolo Pisati , linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, Darren Hart Subject: Re: kernel 6.2 stuck at boot (efi_call_rts) on arm64 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 16, 2023 at 02:45:49PM +0100, Ard Biesheuvel wrote: > 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) hm.. I don't have that in /sys/firmware/, this is what I have: # ls -l /sys/firmware/dmi/ total 0 drwxr-xr-x 2 root root 0 Mar 16 13:26 tables # ls -l /sys/firmware/dmi/tables/ total 0 -r-------- 1 root root 5004 Mar 16 13:26 DMI -r-------- 1 root root 24 Mar 16 13:26 smbios_entry_point -Andrea