From: Darren Hart <darren@os.amperecomputing.com>
To: Andrea Righi <andrea.righi@canonical.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Paolo Pisati <paolo.pisati@canonical.com>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kernel 6.2 stuck at boot (efi_call_rts) on arm64
Date: Mon, 17 Apr 2023 15:05:18 -0700 [thread overview]
Message-ID: <ZD3CniUzNXVJRthE@fedora> (raw)
In-Reply-To: <ZDhlBjbRGufpDm6u@righiandr-XPS-13-7390>
On Thu, Apr 13, 2023 at 10:24:38PM +0200, Andrea Righi wrote:
>
> Not sure if it's a similar issue, but I have found another Ampere box
> that is booting fine with your fixes, but the eifvars.sh kselftest is
> failing with some I/O errors, specifically:
Thanks for reporting. Can you confirm this worked reliably for you prior
to v6.1?
--
Darren
>
> $ sudo ./efivarfs.sh
> --------------------
> running test_create
> --------------------
> ./efivarfs.sh: line 58: printf: write error: Input/output error
> /sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27 has invalid size
> [FAIL]
> --------------------
> running test_create_empty
> --------------------
> [PASS]
> --------------------
> running test_create_read
> --------------------
> [PASS]
> --------------------
> running test_delete
> --------------------
> ./efivarfs.sh: line 103: printf: write error: Input/output error
> [PASS]
> --------------------
> running test_zero_size_delete
> --------------------
> ./efivarfs.sh: line 126: printf: write error: Input/output error
> ./efivarfs.sh: line 134: printf: write error: Input/output error
> /sys/firmware/efi/efivars/test_zero_size_delete-210be57c-9849-4fc7-a635-e6382d1aec27 should have been deleted
> [FAIL]
> --------------------
> running test_open_unlink
> --------------------
> open(O_WRONLY): Operation not permitted
> [FAIL]
> --------------------
> running test_valid_filenames
> --------------------
> ./efivarfs.sh: line 158: printf: write error: Input/output error
> ./efivarfs.sh: line 158: printf: write error: Input/output error
> ./efivarfs.sh: line 158: printf: write error: Input/output error
> ./efivarfs.sh: line 158: printf: write error: Input/output error
> [PASS]
> --------------------
> running test_invalid_filenames
> --------------------
> [PASS]
>
> If it helps:
>
> $ sudo hexdump -C /sys/firmware/dmi/entries/4-0/raw
> 00000000 04 30 04 00 01 03 fe 02 c1 d0 3f 41 00 00 00 00 |.0........?A....|
> 00000010 03 8a 72 06 b8 0b f0 0a 41 06 05 00 06 00 07 00 |..r.....A.......|
> 00000020 04 05 06 50 50 50 04 00 01 01 01 00 01 00 01 00 |...PPP..........|
> 00000030 43 50 55 20 31 00 41 6d 70 65 72 65 28 52 29 00 |CPU 1.Ampere(R).|
> 00000040 41 6d 70 65 72 65 28 52 29 20 41 6c 74 72 61 28 |Ampere(R) Altra(|
> 00000050 52 29 20 50 72 6f 63 65 73 73 6f 72 00 30 30 30 |R) Processor.000|
> 00000060 30 30 30 30 30 30 30 30 30 30 30 30 30 30 32 35 |0000000000000025|
> 00000070 35 30 32 30 39 30 33 33 38 36 35 42 34 00 30 30 |50209033865B4.00|
> 00000080 30 30 30 30 30 31 00 51 38 30 2d 33 30 00 00 |000001.Q80-30..|
> 0000008f
>
> I guess EFI is not very reliable here...
>
> -Andrea
--
Darren Hart
Ampere Computing / OS and Kernel
next prev parent reply other threads:[~2023-04-17 22:05 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 [this message]
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)
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=ZD3CniUzNXVJRthE@fedora \
--to=darren@os.amperecomputing.com \
--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 \
/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