Do you see the same behavior?
No I see the full logs for each boot with persistent logging enabled:
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Linux version 6.6.84-7.2.0-g87bfb710b6f1 (oe-user@oe-host) (aarch64-tdx-linux-gcc (GCC) 13.3.0, GNU ld (GNU Binutils) 2.42.0.20240723) #1-Torizon SMP PREEMPT Mon Mar 31 08:47:48 UTC 2025
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: KASLR disabled due to lack of seed
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Machine model: Toradex Verdin iMX8M Plus WB on Verdin Development Board
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: efi: UEFI not found.
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Reserved memory: created CMA memory pool at 0x00000000a0000000, size 512 MiB
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: OF: reserved mem: 0x00000000a0000000..0x00000000bfffffff (524288 KiB) map reusable linux,cma
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: OF: reserved mem: 0x0000000000900000..0x000000000096ffff (448 KiB) nomap non-reusable ocram@900000
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Zone ranges:
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: DMA [mem 0x0000000040000000-0x00000000ffffffff]
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: DMA32 empty
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Normal [mem 0x0000000100000000-0x000000013fffffff]
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Movable zone start for each node
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Early memory node ranges
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: node 0: [mem 0x0000000040000000-0x000000013fffffff]
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Initmem setup node 0 [mem 0x0000000040000000-0x000000013fffffff]
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: psci: probing for conduit method from DT.
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: psci: PSCIv1.1 detected in firmware.
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: psci: Using standard PSCI v0.2 function IDs
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: psci: MIGRATE_INFO_TYPE not supported.
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: psci: SMC Calling Convention v1.4
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: percpu: Embedded 29 pages/cpu s80040 r8192 d30552 u118784
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: pcpu-alloc: s80040 r8192 d30552 u118784 alloc=29*4096
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Detected VIPT I-cache on CPU0
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: CPU features: detected: GIC system register CPU interface
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: alternatives: applying boot alternatives
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/157a467dd3b97eaebfbf6e17d0c8859fdd0abc1d397c637c6ecd808f79dc0260/0
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Unknown kernel command line parameters "splash ostree=/ostree/boot.1/torizon/157a467dd3b97eaebfbf6e17d0c8859fdd0abc1d397c637c6ecd808f79dc0260/0", will be passed to user space.
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: Built 1 zonelists, mobility grouping on. Total pages: 1032192
Jan 08 18:22:58 verdin-imx8mp-06849059 kernel: mem auto-init: stack:all(zero), heap alloc:off, heap free:off
....<2000+ lines of logs>
I don’t know why yours would be cut off. Did you modify anything else? I’m just on a standard 7.2.0 release image. The only modification was the persistent logging related changes. Or at least I assume you have other modifications I can see from your logs you at least modified stuff like the device hostname.
Try to enable persistent logging on a standard 7.2.0 image with no other modifications. Then compare and see if the behavior is the same. If it’s not then there must be some other modification that is affecting the logging.
Best Regards,
Jeremias