From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: memtest failed for rk3588
Date: Tue, 10 Dec 2024 12:47:33 +0100 [thread overview]
Message-ID: <Z1gqVVWyhdjB-u9w@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvSEpZ_==v4o0Om_vCBoN3iuGGu8Qr1SxGxRy4NqCzOB4A@mail.gmail.com>
On Tue, Dec 10, 2024 at 02:29:59PM +0300, Alexander Shiyan wrote:
> Hello.
>
> The dump does not cause a crash, but the output is very strange:
>
> barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000100
> 3fc000100: 940033fd b0000060 39477ea1 91274c00 .3..`....~G9.L'.
> 3fc000110: 17ffffe2 91404001 b9428020 37f80180 .....@@. .B....7
> 3fc000120: b9428020 32010000 b9028020 52800020 .B....2 ... ..R
> 3fc000130: b9420822 32000042 b9020822 b9420822 ".B.B..2"...".B.
> 3fc000140: 521c0042 b9020822 d65f03c0 52800000 B..R"....._....R
> 3fc000150: 17fffff8 91404000 34000081 b9428001 .....@@....4..B.
> 3fc000160: 12007821 b9028001 b9420801 121f7821 !x........B.!x..
> 3fc000170: b9020801 b9420801 521c0021 b9020801 ......B.!..R....
> 3fc000180: d65f03c0 d37b7c21 71000c5f 8b010000 .._.!|{._..q....
> 3fc000190: 528aaaa1 72bdddc1 f9400400 b900ac01 ...R...r..@.....
> 3fc0001a0: 529dddc1 72aaaaa1 b90a7c01 b94a2401 ...R...r.|...$J.
> 3fc0001b0: 321c0021 b90a2401 b94a2403 12147463 !..2.$...$J.ct..
> 3fc0001c0: 54000300 52808001 1ac22022 2a030042 ...T...R" ..B..*
> 3fc0001d0: b90a2402 b94a2401 32000021 b90a2401 .$...$J.!..2.$..
> 3fc0001e0: b94a2401 360fffe1 b94a2401 121f7821 .$J....6.$J.!x..
> 3fc0001f0: b90a2401 b94a2401 12147421 b90a2401 .$...$J.!t...$..
> barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000200
> 3fc000200: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc000210: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc000220: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc000230: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc000240: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc000250: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc000260: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc000270: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc000280: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc000290: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc0002a0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc0002b0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc0002c0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc0002d0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc0002e0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
> 3fc0002f0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................
See:
| commit d8a6e1c2662aad2f5d9b4050a276b8e6b9fbb3b1
| Author: Jan Luebbe <jlu@pengutronix.de>
| Date: Sun Aug 3 17:51:38 2014 +0200
|
| ARM/mem: handle data aborts gracefully for md
|
| Sometimes memory ranges contain inaccessible registers which trigger a
| data abort when accessed. To handle this gracefully, we extend the data
| abort exception handler to ignore the exception when configured to do
| so.
|
| This allows detecting inaccessible memory from the md command. It will
| show XX for unreadable bytes instead.
I don't know why you get a data abort here. The answer is probably
somewhere in the DMC section of the RK3588 reference manual.
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 |
next prev parent reply other threads:[~2024-12-10 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 13:10 Alexander Shiyan
2024-12-06 14:25 ` Sascha Hauer
2024-12-10 11:29 ` Alexander Shiyan
2024-12-10 11:47 ` Sascha Hauer [this message]
2024-12-11 15:52 ` Alexander Shiyan
2024-12-13 12:15 ` Alexander Shiyan
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=Z1gqVVWyhdjB-u9w@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.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