Dmesg and panic infos saved by ramoops does not exist after reset

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
1

Hi,

im using Jetson 35.2.1 on orin agx 32gb.
I want to save panic info in ddr ram and read it out after reboot.
I checked the reserved memory areas after reboot, nothing was there.

I found in dts, there is reserved memory for ramoops.
ramoops_carveout {
compatible = “ramoops”;
size = < 0x00 0x200000 >;
record-size = < 0x10000 >;
console-size = < 0x80000 >;
alignment = < 0x00 0x10000 >;
alloc-ranges = < 0x00 0x00 0x01 0x00 >;
no-map;
status = “okay”;
phandle = < 0x311 >;
};
And “reg” is added in UEFI and values are
reg = <0x08 0x2e800000 0x00 0x200000>;

Thus i think, the ramoops function should be okay in your design.
But after reboot, there is nothing in
/sys/fs/pstore/ and /var/lib/systemd/pstore

And i found after , after sudo reboot, the boot-mode is always Coldboot

sudo reboot
[ 897.888194] watchdog: watchdog0: watchdog did not stop!
[ 898.244587] nvgpu: 17000000.ga10b ga10b_intr_log_pending_intrs:306 [ERR] Pending TOP[0]: 0x00000004, LEAF[4]: 0x11000000
[ 898.257659] arm-smmu 8000000.iommu: disabling translation
[ 898.263311] arm-smmu 10000000.iommu: disabling translation
[ 898.268982] arm-smmu 12000000.iommu: disabling translation
[ 898.274805] reboot: Restarting system
Shutdown state requested 1
Rebooting system …
[0000.063] I> MB1 (version: 0.28.0.0-t234-54845784-ec016368)
[0000.069] I> t234-A01-0-Silicon (0x12347) Prod
[0000.073] I> Boot-mode : Coldboot
[0000.076] I> Emulation:
[0000.078] I> Entry timestamp: 0x00000000
[0000.082] I> last_boot_error: 0x0

3

i did the same test using Jetson 35.3.1 with the origin bsp & sample rootfs downloaded here: Jetson Linux 35.3.1 | NVIDIA Developer without any modification

after manully trigger a crash
echo 1 > /proc/sys/kernel/panic
echo c > /proc/sysrq-trigger

i still find nothing in this directory: /sys/fs/pstore/

is there any suggestions ?

4

Again i did the same test on Jetson r35.1, also the downloaded original version

the ramoops works perfect

after a panic reboot, there is infos in /sys/fs/pstore

root@nvidia:/sys/fs/pstore# ll
total 0
drwxr-x— 2 root root 0 4月 21 2022 ./
drwxr-xr-x 9 root root 0 1月 1 1970 …/
-r–r–r-- 1 root root 4165 6月 30 22:03 console-ramoops-0
-r–r–r-- 1 root root 88419 6月 30 22:03 dmesg-ramoops-0
-r–r–r-- 1 root root 88745 6月 30 22:03 dmesg-ramoops-1
root@nvidia:/sys/fs/pstore#

What’s more, i noticed that the reserverd memory range for r35.1 and later version are differnet

for r35.1 it’s

82c200000-82c20ffff : ramoops:dmesg(0/23)
82c210000-82c21ffff : ramoops:dmesg(1/23)
82c220000-82c22ffff : ramoops:dmesg(2/23)
82c230000-82c23ffff : ramoops:dmesg(3/23)
82c240000-82c24ffff : ramoops:dmesg(4/23)
82c250000-82c25ffff : ramoops:dmesg(5/23)
82c260000-82c26ffff : ramoops:dmesg(6/23)
82c270000-82c27ffff : ramoops:dmesg(7/23)
82c280000-82c28ffff : ramoops:dmesg(8/23)
82c290000-82c29ffff : ramoops:dmesg(9/23)
82c2a0000-82c2affff : ramoops:dmesg(10/23)
82c2b0000-82c2bffff : ramoops:dmesg(11/23)
82c2c0000-82c2cffff : ramoops:dmesg(12/23)
82c2d0000-82c2dffff : ramoops:dmesg(13/23)
82c2e0000-82c2effff : ramoops:dmesg(14/23)
82c2f0000-82c2fffff : ramoops:dmesg(15/23)
82c300000-82c30ffff : ramoops:dmesg(16/23)
82c310000-82c31ffff : ramoops:dmesg(17/23)
82c320000-82c32ffff : ramoops:dmesg(18/23)
82c330000-82c33ffff : ramoops:dmesg(19/23)
82c340000-82c34ffff : ramoops:dmesg(20/23)
82c350000-82c35ffff : ramoops:dmesg(21/23)
82c360000-82c36ffff : ramoops:dmesg(22/23)
82c370000-82c37ffff : ramoops:dmesg(23/23)
82c380000-82c3fffff : ramoops:console

and for later version it’s

82e800000-82e80ffff : ramoops:dmesg(0/23)
82e810000-82e81ffff : ramoops:dmesg(1/23)
82e820000-82e82ffff : ramoops:dmesg(2/23)
82e830000-82e83ffff : ramoops:dmesg(3/23)
82e840000-82e84ffff : ramoops:dmesg(4/23)
82e850000-82e85ffff : ramoops:dmesg(5/23)
82e860000-82e86ffff : ramoops:dmesg(6/23)
82e870000-82e87ffff : ramoops:dmesg(7/23)
82e880000-82e88ffff : ramoops:dmesg(8/23)
82e890000-82e89ffff : ramoops:dmesg(9/23)
82e8a0000-82e8affff : ramoops:dmesg(10/23)
82e8b0000-82e8bffff : ramoops:dmesg(11/23)
82e8c0000-82e8cffff : ramoops:dmesg(12/23)
82e8d0000-82e8dffff : ramoops:dmesg(13/23)
82e8e0000-82e8effff : ramoops:dmesg(14/23)
82e8f0000-82e8fffff : ramoops:dmesg(15/23)
82e900000-82e90ffff : ramoops:dmesg(16/23)
82e910000-82e91ffff : ramoops:dmesg(17/23)
82e920000-82e92ffff : ramoops:dmesg(18/23)
82e930000-82e93ffff : ramoops:dmesg(19/23)
82e940000-82e94ffff : ramoops:dmesg(20/23)
82e950000-82e95ffff : ramoops:dmesg(21/23)
82e960000-82e96ffff : ramoops:dmesg(22/23)
82e970000-82e97ffff : ramoops:dmesg(23/23)
82e980000-82e9fffff : ramoops:console

this reserved range ( the ‘reg’ property) is added into device tree in UEFI

5

Have you tested the pstore/ramoops on Jetson version later than r35.1?

6

i find the same problom on Jetson version later than r35.2

7

我用35.31版本也碰到了這個問題，盼回復.

9

Hi,

This is a known issue and will be fixed in next release.

10

Hi,

by the way, where could i find the “known issues”, that will be fixed in the future release?

11

No such place to search this info. It is just a result from my internal search.