mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Renaud Barbier <Renaud.Barbier@ametek.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: NVME o nLS1046A-RDB
Date: Tue, 12 Nov 2024 08:57:06 +0100	[thread overview]
Message-ID: <ZzMKUugcLKGY4aq-@pengutronix.de> (raw)
In-Reply-To: <BYAPR07MB4358A74708FE72C8789667C0EC582@BYAPR07MB4358.namprd07.prod.outlook.com>

On Mon, Nov 11, 2024 at 11:15:46AM +0000, Renaud Barbier wrote:
> 
> From barebox:
> -------------------
> 
> The node /dev/nvme0n1p1 does not exists only /dev/nvme0n1.
> From barebox, I saw that below once. 
> It is not repeating at present whatever the command I use:
> ERROR: ext4 ext40: probe failed: Invalid argument
> 
> 
> 
> > 
> > does "md -s /dev/nvme0n1" work as expected?
> barebox@LS1046A RDB Board:/ md -s /dev/nvme0n1
> 00000000: 00000000 00000000 00000000 00000000                ................
> 00000010: 00000000 00000000 00000000 00000000                ................
> 00000020: 00000000 00000000 00000000 00000000                ................
> ....

Ok, 0x00000000 could be correct or not. Try md -s /dev/nvme0n1 0+512, it
should give you the protective MBR at the end. Or use some other
non-empty area and verify with Linux the data is correct.

DMA issues as Ahmad mentioned is a good guess.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2024-11-12  8:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 13:42 Renaud Barbier
2024-11-08 11:05 ` Sascha Hauer
2024-11-11 11:15   ` Renaud Barbier
2024-11-12  7:57     ` Sascha Hauer [this message]
2024-11-12 11:48       ` Renaud Barbier
2024-11-11 11:30 ` Ahmad Fatoum

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=ZzMKUugcLKGY4aq-@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=Renaud.Barbier@ametek.com \
    --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