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 750E6C74A5B for ; Thu, 16 Mar 2023 14:00:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230354AbjCPN77 (ORCPT ); Thu, 16 Mar 2023 09:59:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40876 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229932AbjCPN7p (ORCPT ); Thu, 16 Mar 2023 09:59:45 -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 D60215B5D7 for ; Thu, 16 Mar 2023 06:59:42 -0700 (PDT) Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (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 A9BF73F48A for ; Thu, 16 Mar 2023 13:59:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1678975181; bh=s5o9DPzI1qYtz/YXjKH1gRwsqjy0KxEjU5/kQqTTsVg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=Wd7dvzCHQzcQNct8z3C2idEIVsLpQUn2OfTEyQX3PD1R15Jf3sLjd+mxYi5v5hTk8 467YMLkwPYMjLQd2Fg5h+ZCp9Vr5HICuoik0sntzk9J/nUpeT9cLR+YMTZKkxlfRgG q/fRtGqxW2SnZjpcygvIs9NpB5hNowfaXxbmoDy+BPijnYbWdTzsSu1uIhedvAazKJ fzjPG8OLKhnuVI04Bvad8nx1FSj5UWPzY4SQu5PGiQohutsSOmYf9jzOw3tqGd2G1/ aYlcj9gVuXA0i54HSBIPAGmYNNK3m/yxeofhoEHHpFuMMbUJuP44WFSYFkU/7N1DLP f8Op8G+kzoDLQ== Received: by mail-ed1-f69.google.com with SMTP id dn8-20020a05640222e800b004bd35dd76a9so3207579edb.13 for ; Thu, 16 Mar 2023 06:59:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678975181; 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=s5o9DPzI1qYtz/YXjKH1gRwsqjy0KxEjU5/kQqTTsVg=; b=p8N73+ccIcQuG1IL5fYoAFvEcVucIz+EE3WGoJL/dlAs+fwobIxs9thvpOUyd3JmTZ rFeAH9/VI5ewo7ZgJ0McHtJu2IhNGpFA1BMbt7kkkaV0n3seXl7mOniXftc6bXNgmzlP scCxXcf85QnVeVjjkHOY2nvReUbGRkprZqMYN8Hi5XxdXF8O2DowjBWPRc6gekw2nWSh 6mIQAb8vdI2rTyaOWP5ZHQPST9boHG2248NemPF3t4KXfpqVl5PYlhIgRaUPYbXl4DjS ruIl2W0pBxYALgwKyT2NK9rctWpxF0xfu/OHc3suji1d7zW5nGJrxdZhJBcSPxk20MAG Cd+w== X-Gm-Message-State: AO0yUKXsVhbJsefecFBswLhzVtI1JJ/UJZeMtpSZV8XGSxe0Mjyya2SI lr3xFD0hMUjZCO0onwHwuJ2vD7s7bCa/8lCxO3CZwrJGziZPmMDswKVHiM5hTrWNA20Ti/0Wuoj S7XCIEYoGNPGyfpRL852ImLFM1AbDW40ONBjlj5bBgA== X-Received: by 2002:a17:907:3fa6:b0:878:7189:a457 with SMTP id hr38-20020a1709073fa600b008787189a457mr12814467ejc.51.1678975181400; Thu, 16 Mar 2023 06:59:41 -0700 (PDT) X-Google-Smtp-Source: AK7set/WIv8P7aulh3CUCZ6bEKmlM7k4ERADum6gVWOgJy42nlzGzz7z4ZpPdO9IQIuQ3781APapJA== X-Received: by 2002:a17:907:3fa6:b0:878:7189:a457 with SMTP id hr38-20020a1709073fa600b008787189a457mr12814432ejc.51.1678975181045; Thu, 16 Mar 2023 06:59:41 -0700 (PDT) Received: from localhost (host-79-53-23-214.retail.telecomitalia.it. [79.53.23.214]) by smtp.gmail.com with ESMTPSA id i18-20020a1709064fd200b0092be390b51asm3834582ejw.113.2023.03.16.06.59.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Mar 2023 06:59:40 -0700 (PDT) Date: Thu, 16 Mar 2023 14:59:39 +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:53:24PM +0100, Ard Biesheuvel wrote: > On Thu, 16 Mar 2023 at 14:50, Andrea Righi wrote: > > > > 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 > > > > You'll need to load the dmi_sysfs module for that. But no big deal > otherwise, I'm pretty sure the word order is the correct on on your > system in any case (it decodes the value correctly in the next line) ok, much better after modprobe dmi_sysfs. :) $ sudo hexdump -C /sys/firmware/dmi/entries/4-0/raw 00000000 04 30 04 00 01 03 fe 02 02 00 3f 50 00 00 00 00 |.0........?P....| 00000010 03 89 b8 0b e4 0c b8 0b 41 06 05 00 06 00 07 00 |........A.......| 00000020 04 00 00 20 20 20 7c 00 01 01 00 00 00 00 00 00 |... |.........| 00000030 43 50 55 20 31 00 41 6d 70 65 72 65 28 54 4d 29 |CPU 1.Ampere(TM)| 00000040 00 65 4d 41 47 20 00 30 30 30 30 30 30 30 30 30 |.eMAG .000000000| 00000050 30 30 30 30 30 30 30 35 30 30 35 30 31 30 35 30 |0000000500501050| 00000060 32 46 42 30 39 38 38 00 55 6e 6b 6e 6f 77 6e 00 |2FB0988.Unknown.| 00000070 55 6e 6b 6e 6f 77 6e 00 00 |Unknown..| 00000079 -Andrea