From: Renaud Barbier <Renaud.Barbier@ametek.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Barebox List <barebox@lists.infradead.org>
Subject: RE: parted crash on NVME storage on LS1046A-RDB
Date: Fri, 10 Jan 2025 15:48:28 +0000 [thread overview]
Message-ID: <DM5PR07MB3532C9D58C2D8848C7F08136EC1C2@DM5PR07MB3532.namprd07.prod.outlook.com> (raw)
In-Reply-To: <2aa13c0d-1820-4f9a-a52e-95917f19f632@pengutronix.de>
>
> ***NOTICE*** This came from an external source. Use caution when
> replying, clicking links, or opening attachments.
>
> On 09.01.25 10:32, Renaud Barbier wrote:
> > We are investigating the use of NVME storage using a NXP LS1046A CPU.
> > I have a RDB eval board on which I installed NVME storage whose ext4
> partition was created from Linux.
> > The commit from which the boot loader is built is:
> > 2024.12.0-00214-ge3de867716e9-dirty from Tue Dec 17 2024
> >
> > The device is probed:
> > `-- pci-1957:81c0.1
> > `-- pci-126f:2263.0
> > `-- 0x00000000-0x6fc86d5fff ( 447.1 GiB): /dev/nvme0n1
> > `-- 0x00100000-0x401001ff ( 1 GiB): /dev/nvme0n1.0, nvme0n1.Linux
> filesystem
> >
> > nvme pci-126f:2263.0: serial: A012410180629000000 nvme
> > pci-126f:2263.0: model: SM681GEF AGS nvme pci-126f:2263.0: firmware:
> > TFX7GB
After using the nvme sanitize command from Linux, I tried to recreate the partition from barebox.
A crash happened.
I did notice a call to efi_partition_free below while when the partition table was created Linux it was dos_partition_free.
barebox@LS1046A RDB Board:/ parted /dev/nvme0n1 mklabel gpt
Created new disk label with GUID 00dc0465-aa1f-ad4d-9ada-e5ac1b1e5f13
NULL pointer dereference: DABT (current EL) exception (ESR 0x9600000b) at 0x0000000000000008
elr: 00000000fbd6a450 lr : 00000000fbd0f68c
x0 : 0000000000000000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 00000000bded2e18
x4 : 00000000bded2dd0 x5 : 00000000bdef5060
x6 : 0000000037e43680 x7 : 000000000000002e
x8 : 00000000bded2dd0 x9 : 0000000000000200
x10: 0000000000001000 x11: 0000000000001000
x12: 00000000fbff7681 x13: 00000000fbff7a79
x14: 00000000ffffffff x15: 00000000ffffffff
x16: 0000000000000000 x17: 00000000fbff74a8
x18: 00000000fbff7a40 x19: 0000000000000000
x20: 00000000bdfc61b8 x21: 00000000bded2e38
x22: 00000000bded2dd0 x23: 00000000fbde90c0
x24: 00000000fbe1f000 x25: 00000000fbdb54a8
x26: 00000000fbe1f000 x27: 00000000bdfc3de8
x28: 00000000fbde90f0 x29: 00000000fbff7ae0
Call trace:
[<fbd6a450>] (dev_remove_param+0x18/0x5c) from [<fbd0f68c>] (efi_partition_free+0x30/0x68)
[<fbd0f68c>] (efi_partition_free+0x30/0x68) from [<fbd0df38>] (partition_table_free+0x14/0x1c)
[<fbd0df38>] (partition_table_free+0x14/0x1c) from [<fbd66b14>] (do_parted+0x148/0x154)
[<fbd66b14>] (do_parted+0x148/0x154) from [<fbd07bd8>] (execute_command+0x44/0x8c)
[<fbd07bd8>] (execute_command+0x44/0x8c) from [<fbd0421c>] (execute_binfmt+0x68/0xa0)
[<fbd0421c>] (execute_binfmt+0x68/0xa0) from [<fbd124f8>] (run_list_real+0x8cc/0x978)
[<fbd124f8>] (run_list_real+0x8cc/0x978) from [<fbd11a80>] (parse_stream_outer+0x144/0x1f0)
[<fbd11a80>] (parse_stream_outer+0x144/0x1f0) from [<fbd128d8>] (run_shell+0x64/0xac)
[<fbd128d8>] (run_shell+0x64/0xac) from [<fbd01bd8>] (run_init+0x148/0x264)
[<fbd01bd8>] (run_init+0x148/0x264) from [<fbd01a38>] (start_barebox+0x50/0x8c)
[<fbd01a38>] (start_barebox+0x50/0x8c) from [<fbd93748>] (psci_driver_register+0x0/0x1c)
[<fbd93748>] (psci_driver_register+0x0/0x1c) from [<fbd0000c>] (__bare_init_start+0x0/0x14)
[<fbd0000c>] (__bare_init_start+0x0/0x14) from [<80028800>] (0x80028800)
[<80028800>] (0x80028800) from [<800280c4>] (0x800280c4)
next prev parent reply other threads:[~2025-01-10 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 9:32 Renaud Barbier
2025-01-09 11:20 ` Ahmad Fatoum
2025-01-10 15:48 ` Renaud Barbier [this message]
2025-01-10 15:52 ` Ahmad Fatoum
2025-01-10 16:29 ` Renaud Barbier
2025-01-10 16:50 ` Renaud Barbier
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=DM5PR07MB3532C9D58C2D8848C7F08136EC1C2@DM5PR07MB3532.namprd07.prod.outlook.com \
--to=renaud.barbier@ametek.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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