My attempt at booting the MNT Reform with A311D CPU card this morning resulted in a blank screen. Attempting to enter my LUKS password blind, which has worked in the past, did not work. Hooking up an external screen via HDMI also did not show that being active.I think this is probably a kernel thing. Using the UART port (externally accessible mod for the win), I can see some kind of looping on this (it shows up before the LUKS password, but loops infinitely afterwards):
[ 131.292900] meson-dw-hdmi ff600000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)[ 131.297586] meson-dw-hdmi ff600000.hdmi-tx: registered DesignWare HDMI I2C bus driver[ 131.305741] meson-drm ff900000.vpu: bound ff600000.hdmi-tx (ops meson_dw_hdmi_ops [meson_dw_hdmi])[ 131.317722] meson-drm ff900000.vpu: Queued 2 outputs on vpu[ 131.320757] meson-drm ff900000.vpu: CVBS Output connector not available
I’ll try booting off SD card to see if this is something else, but I’m assuming a kernel incompatibility/regression at this point.
1 Like
As expected, using the most recent image off SD card boots fine, right into the setup wizard. I’ll dig into my notes to see if I can remember what I need to do to mount my system into the SD image and update it in place to a newer kernel.
1 Like
Okay, weird.
I’m not sure if this is actually the problem, but using the fresh system image (with kernel 6.16.3) things booted fine. I was able to mount the encrypted NVME drive and do a chroot and update packages and whatnot. But that wasn’t sufficient to get it booting. I don’t know which of the following things “fixed” it, but I:
re-flashed uboot to the emmc
removed linux-image-6.16.3 (causing me to currently be on 6.15.6).
Just updating packages and reflashing uboot to the emmc did not result in a clean boot, so it feels like my copy of 6.16.3 got horked up somehow. Dunno, but I’m back up and running.
Overall, still mysterious! But it’s working again, and so I’m pleased!
2 Likes
nocko
September 19, 2025, 10:43pm
4
Reporting in to say that I am also experiencing this with Trixie + trixie-backports kernel (6.16.1+reform20250823T232542Z).
1 Like
josch
September 20, 2025, 4:53am
5
Hi @nocko welcome to the forum!
We do not even know what “this” is because @UnlikelyLass never managed to figure out what the problem was nor what fixed it. If your problem is “blank screen on boot” then that can have a whole range of wildly different reasons. Could you open a new thread about your specific problem? It would be useful if you include whether a vanilla system image booted from sd-card works or not. It would be mega-useful if you had a usb uart adapter and could share the serial output you get during boot.
1 Like
For my situation, vanilla image on an SD card was fine. And downgrading the kernel to the 6.15 range seems to be the thing that fixed it, but I haven’t tried reinstalling it. Maybe I should do that? Current kernel:
Linux reform 6.15.6-mnt-reform-arm64 #1 SMP Debian 6.15.6-1~exp1+reform20250719T140750Z (2025-07-19) aarch64 GNU/Linux
packages:
ii linux-image-6.15.6-mnt-reform-arm64 6.15.6-1~exp1+reform20250719T140750Z arm64 Linux 6.15 for 64-bit ARMv8 machines (MNT Reform)
1 Like
nocko
September 20, 2025, 5:21pm
7
I was cosigning this experience. The screen was active every boot when 6.15.x kernels were the norm. 6.16.x the screen did not activate every boot. After several reboots it would randomly work.
I eventually noticed that if I removed the SD card and booted the system, waiting 3-4 minutes (booting from emmc uboot?), then reboot from the SD Card the screen would activate consistently. I’ve been rebooting this way for ~6 weeks. Feels like a GPU registers setup issue (race?).
I’ll break out the UART this afternoon. It’s such a hassle. I miss having uboot graphics support like the imx8 eventually had…
Just like UnlikelyLass, I’m seeing the same looping messages over UART and a blank screen when I boot. I thought it was a hardware issue with my DSI to eDP chip, but since other people are having the same problem I am not so sure any more. My post is here. Reform SN65DSIx6 DSI to eDP is NAK'ing On Boot
When you break out the UART adapter, maybe you can grep for this?
ti_sn65dsi86 1-002c: error -ENXIO: failed to read device id
I’ll try downgrading to a 6.15 kernel.
2 Likes
I wonder: do we all have the A311D CPU card in use?
I’m wondering if this is strictly the kernel itself, or some way the kernel and u-boot interact with one another. I was able to boot off an SD card with the “standard image”, which also has a 6.16 kernel, just fine. Could be a module, could have something to do with how the .scr file is assembled, maybe?
2 Likes
nocko
September 24, 2025, 12:07pm
10
I have the A311D as well. Sorry for the UART delay, life gets in the way sometimes.
1 Like
nocko
September 24, 2025, 5:21pm
11
Complete boot logs linked below.
TLDR:
6.15.6 activates the screen consistently when started via uboot menu. This suggest that boot.scr is fine.
ti_sn65dsi86 driver crashes after failing device id read. meson-drm fails to find CVBS connector in a loop. Consistent with @kaybarkbark and @UnlikelyLass
Failure:
[ 4.848383] ti_sn65dsi86 1-002c: error -ENXIO: failed to read device id
[ 4.849437] ------------[ cut here ]------------
[ 4.852402] nvme nvme0: pci function 0000:01:00.0
[ 4.853983] WARNING: CPU: 4 PID: 227 at drivers/regulator/core.c:2450 _regulator_put+0x58/0x68
[ 4.856155] meson-dw-hdmi ff600000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[ 4.858975] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[ 4.860670] meson-dw-hdmi ff600000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[ 4.861203] meson-drm ff900000.vpu: bound ff600000.hdmi-tx (ops meson_dw_hdmi_ops [meson_dw_hdmi])
[ 4.867242] Modules linked in: nvme snd_timer(+) pcs_xpcs(+) ghash_ce ti_sn65dsi86(+) mdio_mux meson_gxbb_wdt gf128mul phylink meson_vdec(C) panfrost(+) clk_pwm videobuf2_dma_contig snd meson_dw_mipi_dsi sha1_ce videobuf2_memops v4l2_mem2mem nvme_core
[ 4.879799] hwmon hwmon2: temp1_input not attached to any thermal zone
[ 4.882755] mdio_devres drm_shmem_helper rtc_pcf8523 soundcore dw_mipi_dsi of_mdio dwc3_meson_g12a gpu_sched videobuf2_v4l2 nvme_keyring fixed_phy usb_common spi_gpio videodev meson_dw_hdmi fwnode_mdio reset_meson_audio_arb videobuf2_common meson_drm mc ao_cec_g12a libphy spi_bitbang rtc_meson_vrtc nvme_auth mdio_bus meson_canvas panel_edp pwm_regulator gpio_regulator drm_dp_aux_bus nvmem_meson_efuse cpufreq_dt
[ 4.964572] CPU: 4 UID: 0 PID: 227 Comm: (udev-worker) Tainted: G C 6.16.3+1-mnt-reform-arm64 #1 PREEMPTLAZY Debian 6.16.3-1~bpo13+1+reform20250826T191649Z
[ 4.980083] Tainted: [C]=CRAP
[ 4.983029] Hardware name: MNT Reform 2 with BPI-CM4 Module (DT)
[ 4.989010] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 4.995943] pc : _regulator_put+0x58/0x68
[ 4.999929] lr : regulator_bulk_free+0x54/0x88
[ 5.004349] sp : ffff8000833f3410
[ 5.007642] x29: ffff8000833f3410 x28: ffff8000833f39a0 x27: 0000000000000000
[ 5.014749] x26: ffff8000833f39a0 x25: ffff800081821fd8 x24: ffff800081e3feb0
[ 5.021855] x23: ffff0000038ccd00 x22: ffff000004715730 x21: ffff0000037f89c0
[ 5.028962] x20: ffff80008218b0a0 x19: ffff0000047156e8 x18: 00000000d180b877
[ 5.036069] x17: 000000000d096b14 x16: 000000005c8b016b x15: 07640765076c0769
[ 5.043175] x14: 0000000000000000 x13: 6469206563697665 x12: 642064616572206f
[ 5.050282] x11: 742064656c696166 x10: 203a4f49584e452d x9 : ffff800080aee45c
[ 5.057389] x8 : ffff8000833f3420 x7 : 0000000000000000 x6 : fffffdffc00dfe20
[ 5.064495] x5 : 44a0b68b59af025d x4 : 0000000000000000 x3 : 0000000000000000
[ 5.071602] x2 : ffff0000038ccd00 x1 : 0000000000000001 x0 : ffff0000037f89c0
[ 5.078709] Call trace:
[ 5.081136] _regulator_put+0x58/0x68 (P)
[ 5.085122] regulator_bulk_free+0x54/0x88
[ 5.089195] devm_regulator_bulk_release+0x24/0x40
[ 5.093962] release_nodes+0x6c/0x108
[ 5.097602] devres_release_group+0x158/0x1a0
[ 5.101936] i2c_device_probe+0x3a4/0x440
[ 5.105922] really_probe+0xc8/0x3a0
[ 5.109476] __driver_probe_device+0x84/0x160
[ 5.113809] driver_probe_device+0x44/0x130
[ 5.117969] __driver_attach+0xcc/0x208
[ 5.121782] bus_for_each_dev+0x84/0x100
[ 5.125682] driver_attach+0x2c/0x40
[ 5.129236] bus_add_driver+0x118/0x250
[ 5.133049] driver_register+0x70/0x138
[ 5.136862] i2c_register_driver+0x50/0xf0
[ 5.140936] ti_sn65dsi86_init+0x3c/0xff8 [ti_sn65dsi86]
[ 5.146222] do_one_initcall+0x60/0x2f8
[ 5.150036] do_init_module+0x5c/0x268
[ 5.153762] load_module+0x201c/0x27f8
[ 5.157489] init_module_from_file+0x94/0xf8
[ 5.161736] __arm64_sys_finit_module+0x26c/0x368
[ 5.166415] invoke_syscall+0x6c/0x100
[ 5.170142] el0_svc_common.constprop.0+0x48/0xf0
[ 5.174822] do_el0_svc+0x24/0x38
[ 5.178115] el0_svc+0x3c/0x190
[ 5.181236] el0t_64_sync_handler+0x10c/0x138
[ 5.185569] el0t_64_sync+0x198/0x1a0
[ 5.189209] ---[ end trace 0000000000000000 ]---
[ 5.195198] ------------[ cut here ]------------
[ 5.198398] WARNING: CPU: 4 PID: 227 at drivers/regulator/core.c:2450 _regulator_put+0x58/0x68
[ 5.206976] Modules linked in: ulpi dw_hdmi_i2s_audio polyval_ce nvme snd_timer pcs_xpcs ghash_ce ti_sn65dsi86(+) mdio_mux meson_gxbb_wdt gf128mul phylink meson_vdec(C) panfrost(+) clk_pwm videobuf2_dma_contig snd meson_dw_mipi_dsi sha1_ce videobuf2_memops v4l2_mem2mem nvme_core mdio_devres drm_shmem_helper rtc_pcf8523 soundcore dw_mipi_dsi of_mdio dwc3_meson_g12a gpu_sched videobuf2_v4l2 nvme_keyring fixed_phy usb_common spi_gpio videodev meson_dw_hdmi fwnode_mdio reset_meson_audio_arb videobuf2_common meson_drm mc ao_cec_g12a libphy spi_bitbang rtc_meson_vrtc nvme_auth mdio_bus meson_canvas panel_edp pwm_regulator gpio_regulator drm_dp_aux_bus nvmem_meson_efuse cpufreq_dt
[ 5.266520] CPU: 4 UID: 0 PID: 227 Comm: (udev-worker) Tainted: G WC 6.16.3+1-mnt-reform-arm64 #1 PREEMPTLAZY Debian 6.16.3-1~bpo13+1+reform20250826T191649Z
[ 5.282032] Tainted: [W]=WARN, [C]=CRAP
[ 5.285843] Hardware name: MNT Reform 2 with BPI-CM4 Module (DT)
[ 5.291823] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 5.298756] pc : _regulator_put+0x58/0x68
[ 5.302747] lr : regulator_bulk_free+0x54/0x88
[ 5.307163] sp : ffff8000833f3410
[ 5.310456] x29: ffff8000833f3410 x28: ffff8000833f39a0 x27: 0000000000000000
[ 5.317562] x26: ffff8000833f39a0 x25: ffff800081821fd8 x24: ffff800081e3feb0
[ 5.324669] x23: ffff0000038ccd00 x22: ffff000004715730 x21: ffff0000037f8c00
[ 5.331776] x20: ffff80008218b0a0 x19: ffff000004715700 x18: 00000000d180b877
[ 5.338882] x17: 000000000d096b14 x16: 000000005c8b016b x15: 07640765076c0769
[ 5.345989] x14: 0000000000000000 x13: 6469206563697665 x12: 642064616572206f
[ 5.353096] x11: 742064656c696166 x10: fffffffffffffa70 x9 : ffff800080aee45c
[ 5.360202] x8 : ffff8000833f3380 x7 : 0000000000000000 x6 : fffffdffc00dfe20
[ 5.367309] x5 : ffff000003f3a0f8 x4 : 0000000000000000 x3 : 0000000000000000
[ 5.374416] x2 : ffff0000038ccd00 x1 : 0000000000000001 x0 : ffff0000037f8c00
[ 5.381523] Call trace:
[ 5.383950] _regulator_put+0x58/0x68 (P)
[ 5.387936] regulator_bulk_free+0x54/0x88
[ 5.392009] devm_regulator_bulk_release+0x24/0x40
[ 5.396776] release_nodes+0x6c/0x108
[ 5.400415] devres_release_group+0x158/0x1a0
[ 5.404749] i2c_device_probe+0x3a4/0x440
[ 5.408736] really_probe+0xc8/0x3a0
[ 5.412289] __driver_probe_device+0x84/0x160
[ 5.416622] driver_probe_device+0x44/0x130
[ 5.420782] __driver_attach+0xcc/0x208
[ 5.424596] bus_for_each_dev+0x84/0x100
[ 5.428496] driver_attach+0x2c/0x40
[ 5.432049] bus_add_driver+0x118/0x250
[ 5.435862] driver_register+0x70/0x138
[ 5.439676] i2c_register_driver+0x50/0xf0
[ 5.443749] ti_sn65dsi86_init+0x3c/0xff8 [ti_sn65dsi86]
[ 5.449036] do_one_initcall+0x60/0x2f8
[ 5.452849] do_init_module+0x5c/0x268
[ 5.456576] load_module+0x201c/0x27f8
[ 5.460302] init_module_from_file+0x94/0xf8
[ 5.464549] __arm64_sys_finit_module+0x26c/0x368
[ 5.469229] invoke_syscall+0x6c/0x100
[ 5.472956] el0_svc_common.constprop.0+0x48/0xf0
[ 5.477636] do_el0_svc+0x24/0x38
[ 5.480929] el0_svc+0x3c/0x190
[ 5.484049] el0t_64_sync_handler+0x10c/0x138
[ 5.488382] el0t_64_sync+0x198/0x1a0
[ 5.492023] ---[ end trace 0000000000000000 ]---
[ 5.500517] usbcore: registered new interface driver usbfs
[ 5.508218] ------------[ cut here ]------------
[ 5.508268] WARNING: CPU: 2 PID: 227 at drivers/regulator/core.c:2450 _regulator_put+0x58/0x68
[ 5.515795] Modules linked in: usbcore(+) ulpi dw_hdmi_i2s_audio polyval_ce mdio_mux_meson_g12a(+) nvme snd_timer pcs_xpcs ghash_ce ti_sn65dsi86(+) mdio_mux meson_gxbb_wdt gf128mul phylink meson_vdec(C) panfrost(+) clk_pwm videobuf2_dma_contig snd meson_dw_mipi_dsi sha1_ce videobuf2_memops v4l2_mem2mem nvme_core mdio_devres drm_shmem_helper rtc_pcf8523 soundcore dw_mipi_dsi of_mdio dwc3_meson_g12a gpu_sched videobuf2_v4l2 nvme_keyring fixed_phy usb_common spi_gpio videodev meson_dw_hdmi fwnode_mdio reset_meson_audio_arb videobuf2_common meson_drm mc ao_cec_g12a libphy spi_bitbang rtc_meson_vrtc nvme_auth mdio_bus meson_canvas panel_edp pwm_regulator gpio_regulator drm_dp_aux_bus nvmem_meson_efuse cpufreq_dt
[ 5.578285] CPU: 2 UID: 0 PID: 227 Comm: (udev-worker) Tainted: G WC 6.16.3+1-mnt-reform-arm64 #1 PREEMPTLAZY Debian 6.16.3-1~bpo13+1+reform20250826T191649Z
[ 5.593797] Tainted: [W]=WARN, [C]=CRAP
[ 5.597608] Hardware name: MNT Reform 2 with BPI-CM4 Module (DT)
[ 5.603589] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 5.608394] panfrost ffe40000.gpu: clock rate = 24000000
[ 5.610521] pc : _regulator_put+0x58/0x68
[ 5.619795] lr : regulator_bulk_free+0x54/0x88
[ 5.624216] sp : ffff8000833f3410
[ 5.627508] x29: ffff8000833f3410 x28: ffff8000833f39a0 x27: 0000000000000000
[ 5.634615] x26: ffff8000833f39a0 x25: ffff800081821fd8 x24: ffff800081e3feb0
[ 5.641722] x23: ffff0000038ccd00 x22: ffff000004715730 x21: ffff0000037f8d80
[ 5.648828] x20: ffff80008218b0a0 x19: ffff000004715718 x18: 0000000000000014
[ 5.655935] x17: ffff0000003e25c0 x16: 00000000000013b7 x15: 0000000000000d29
[ 5.663042] x14: ffff800081e3fff8 x13: 0000000000000001 x12: ffff8000629fb000
[ 5.670148] x11: 00000000000000c0 x10: fffffffffffff2b0 x9 : ffff800080aee45c
[ 5.677255] x8 : ffff8000833f3380 x7 : 0000000000000000 x6 : 0000000000000400
[ 5.684362] x5 : 0000000000000008 x4 : 0000000000000000 x3 : 0000000000000000
[ 5.691468] x2 : 0000000000000000 x1 : 0000000000000001 x0 : ffff0000037f8d80
[ 5.698576] Call trace:
[ 5.701003] _regulator_put+0x58/0x68 (P)
[ 5.704989] regulator_bulk_free+0x54/0x88
[ 5.709062] devm_regulator_bulk_release+0x24/0x40
[ 5.713828] release_nodes+0x6c/0x108
[ 5.717468] devres_release_group+0x158/0x1a0
[ 5.721802] i2c_device_probe+0x3a4/0x440
[ 5.725788] really_probe+0xc8/0x3a0
[ 5.729342] __driver_probe_device+0x84/0x160
[ 5.733675] driver_probe_device+0x44/0x130
[ 5.737835] __driver_attach+0xcc/0x208
[ 5.741648] bus_for_each_dev+0x84/0x100
[ 5.745548] driver_attach+0x2c/0x40
[ 5.749102] bus_add_driver+0x118/0x250
[ 5.752915] driver_register+0x70/0x138
[ 5.756728] i2c_register_driver+0x50/0xf0
[ 5.760802] ti_sn65dsi86_init+0x3c/0xff8 [ti_sn65dsi86]
[ 5.766088] do_one_initcall+0x60/0x2f8
[ 5.769902] do_init_module+0x5c/0x268
[ 5.773628] load_module+0x201c/0x27f8
[ 5.777355] init_module_from_file+0x94/0xf8
[ 5.781602] __arm64_sys_finit_module+0x26c/0x368
[ 5.786282] invoke_syscall+0x6c/0x100
[ 5.790008] el0_svc_common.constprop.0+0x48/0xf0
[ 5.794688] do_el0_svc+0x24/0x38
[ 5.797982] el0_svc+0x3c/0x190
[ 5.801102] el0t_64_sync_handler+0x10c/0x138
[ 5.805435] el0t_64_sync+0x198/0x1a0
[ 5.809076] ---[ end trace 0000000000000000 ]---
[ 5.813838] ------------[ cut here ]------------
[ 5.815155] usbcore: registered new interface driver hub
[ 5.818263] WARNING: CPU: 2 PID: 227 at drivers/regulator/core.c:2450 _regulator_put+0x58/0x68
[ 5.818277] Modules linked in: usbcore(+) ulpi dw_hdmi_i2s_audio polyval_ce mdio_mux_meson_g12a(+) nvme snd_timer pcs_xpcs ghash_ce ti_sn65dsi86(+) mdio_mux meson_gxbb_wdt gf128mul phylink meson_vdec(C) panfrost(+) clk_pwm videobuf2_dma_contig snd meson_dw_mipi_dsi sha1_ce videobuf2_memops v4l2_mem2mem nvme_core mdio_devres drm_shmem_helper rtc_pcf8523 soundcore dw_mipi_dsi of_mdio dwc3_meson_g12a gpu_sched videobuf2_v4l2 nvme_keyring fixed_phy usb_common spi_gpio videodev meson_dw_hdmi fwnode_mdio reset_meson_audio_arb videobuf2_common meson_drm mc ao_cec_g12a libphy spi_bitbang rtc_meson_vrtc nvme_auth mdio_bus meson_canvas panel_edp pwm_regulator gpio_regulator drm_dp_aux_bus nvmem_meson_efuse cpufreq_dt
[ 5.894618] CPU: 2 UID: 0 PID: 227 Comm: (udev-worker) Tainted: G WC 6.16.3+1-mnt-reform-arm64 #1 PREEMPTLAZY Debian 6.16.3-1~bpo13+1+reform20250826T191649Z
[ 5.910130] Tainted: [W]=WARN, [C]=CRAP
[ 5.913942] Hardware name: MNT Reform 2 with BPI-CM4 Module (DT)
[ 5.919922] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 5.926855] pc : _regulator_put+0x58/0x68
[ 5.930842] lr : regulator_bulk_free+0x54/0x88
[ 5.935262] sp : ffff8000833f3410
[ 5.938555] x29: ffff8000833f3410 x28: ffff8000833f39a0 x27: 0000000000000000
[ 5.945662] x26: ffff8000833f39a0 x25: ffff800081821fd8 x24: ffff800081e3feb0
[ 5.952768] x23: ffff0000038ccd00 x22: ffff000004715730 x21: ffff0000037f8300
[ 5.959875] x20: ffff80008218b0a0 x19: ffff000004715730 x18: 0000000000000014
[ 5.966982] x17: ffff0000003e25c0 x16: 00000000000013b7 x15: 0000000000000d29
[ 5.974088] x14: ffff800081e3fff8 x13: 0000000000000001 x12: ffff8000629fb000
[ 5.981195] x11: 00000000000000c0 x10: 0000000000000770 x9 : ffff800080aee45c
[ 5.988302] x8 : ffff8000833f3380 x7 : ffff00000089e948 x6 : 0000000000000000
[ 5.995408] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
[ 6.002515] x2 : 0000000000000000 x1 : 0000000000000001 x0 : ffff0000037f8300
[ 6.009622] Call trace:
[ 6.012050] _regulator_put+0x58/0x68 (P)
[ 6.016035] regulator_bulk_free+0x54/0x88
[ 6.020108] devm_regulator_bulk_release+0x24/0x40
[ 6.024875] release_nodes+0x6c/0x108
[ 6.028515] devres_release_group+0x158/0x1a0
[ 6.032848] i2c_device_probe+0x3a4/0x440
[ 6.036835] really_probe+0xc8/0x3a0
[ 6.040388] __driver_probe_device+0x84/0x160
[ 6.044722] driver_probe_device+0x44/0x130
[ 6.048882] __driver_attach+0xcc/0x208
[ 6.052695] bus_for_each_dev+0x84/0x100
[ 6.056595] driver_attach+0x2c/0x40
[ 6.060148] bus_add_driver+0x118/0x250
[ 6.063962] driver_register+0x70/0x138
[ 6.067775] i2c_register_driver+0x50/0xf0
[ 6.071848] ti_sn65dsi86_init+0x3c/0xff8 [ti_sn65dsi86]
[ 6.077135] do_one_initcall+0x60/0x2f8
[ 6.080948] do_init_module+0x5c/0x268
[ 6.084675] load_module+0x201c/0x27f8
[ 6.088402] init_module_from_file+0x94/0xf8
[ 6.092648] __arm64_sys_finit_module+0x26c/0x368
[ 6.097328] invoke_syscall+0x6c/0x100
[ 6.101055] el0_svc_common.constprop.0+0x48/0xf0
[ 6.105735] do_el0_svc+0x24/0x38
[ 6.109028] el0_svc+0x3c/0x190
[ 6.112148] el0t_64_sync_handler+0x10c/0x138
[ 6.116482] el0t_64_sync+0x198/0x1a0
[ 6.120122] ---[ end trace 0000000000000000 ]---
[ 6.125205] usbcore: registered new device driver usb
[ 6.127548] panfrost ffe40000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found
[ 6.135506] meson-gx-mmc ffe03000.mmc: allocated mmc-pwrseq
[ 6.138430] meson-drm ff900000.vpu: CVBS Output connector not available
[ 6.142842] panfrost ffe40000.gpu: mali-g52 id 0x7212 major 0x0 minor 0x0 status 0x0
[ 6.158505] panfrost ffe40000.gpu: features: 00000000,00000df7, issues: 00000000,00000400
[ 6.164035] meson-dw-hdmi ff600000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[ 6.166527] panfrost ffe40000.gpu: Features: L2:0x07110206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002830 AS:0xff JS:0x7
[ 6.176716] meson-dw-hdmi ff600000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[ 6.188117] panfrost ffe40000.gpu: shader_present=0x3 l2_present=0x1
[ 6.196467] meson-drm ff900000.vpu: bound ff600000.hdmi-tx (ops meson_dw_hdmi_ops [meson_dw_hdmi])
[ 6.203529] nvme nvme0: allocated 64 MiB host memory buffer (16 segments).
[ 6.208935] [drm] Initialized panfrost 1.3.0 for ffe40000.gpu on minor 0
[ 6.213891] meson-drm ff900000.vpu: CVBS Output connector not available
[ 6.244518] nvme nvme0: 6/0/0 default/read/poll queues
[ 6.251816] nvme nvme0: Ignoring bogus Namespace Identifiers
[ 6.256183] meson-dw-hdmi ff600000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[ 6.263791] meson-dw-hdmi ff600000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[ 6.269948] meson-drm ff900000.vpu: bound ff600000.hdmi-tx (ops meson_dw_hdmi_ops [meson_dw_hdmi])
[ 6.287595] meson-drm ff900000.vpu: CVBS Output connector not available
[ 6.312803] meson-dw-hdmi ff600000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[ 6.320547] meson-dw-hdmi ff600000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[ 6.325277] meson-drm ff900000.vpu: bound ff600000.hdmi-tx (ops meson_dw_hdmi_ops [meson_dw_hdmi])
[ 6.339328] meson-drm ff900000.vpu: CVBS Output connector not available
[ 6.364137] meson-dw-hdmi ff600000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[ 6.369388] meson-dw-hdmi ff600000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[ 6.376733] meson-drm ff900000.vpu: bound ff600000.hdmi-tx (ops meson_dw_hdmi_ops [meson_dw_hdmi])
[ 6.395997] meson-drm ff900000.vpu: CVBS Output connector not available
[ 6.420067] meson-dw-hdmi ff600000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[ 6.432624] meson-dw-hdmi ff600000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[ 6.436022] meson-gx-mmc ffe03000.mmc: card claims to support voltages below defined range
[ 6.436240] meson-drm ff900000.vpu: bound ff600000.hdmi-tx (ops meson_dw_hdmi_ops [meson_dw_hdmi])
6.16.3 - Failure (Complete boot log): https://bin.disroot.org/?a323a12f0ca76ee2#6cM3PHPPTqhRA2UeNbeZHRnwzUrY4UworWcj2u8pQFWK
6.16.3 - Intermittent Success (complete boot log):
https://bin.disroot.org/?e1c6bfa7f651b283#FcVABV7kBpSqv2JcZcJ7U1qCHTNsXTbqCzzqSnCvZbyf
6.15.6 - Consistent succuss (complete boot log):
https://bin.disroot.org/?ece83e087f2cc149#5Xwp7d8737Rr9FuDHnXbUxpck9ZqBq6Cqr5EXhHK4vpQ
2 Likes
Probably less useful for debugging, but my rk3588 cpu upgrade arrived today, so I decided to try reinstalling the 6.16.x kernel and see if the issue returned on the a311d before installing it. IT DID NOT.
So I’m baffled.
ETA: The update was to the 6.18.6 kernel, fwiw.
josch
September 25, 2025, 12:48pm
13
nocko:
6.16.3 - Failure
Could we maybe try to test the latest MNT kernel? I just did 10 successful boots with 6.16.8 on the a311d classic reform.
I mistyped:
Linux reform 6.16.8-mnt-reform-arm64 #1 SMP PREEMPT Debian 6.16.8-1+reform20250910T145641Z (2025-09-1 aarch64 GNU/Linux
Switching from the 6.15.x kernel to the 6.16.8 kernel on the a311d did not see a return of the issue for me.
1 Like
nocko
September 25, 2025, 2:22pm
15
I will try 6.16.8 when it shows up in reform trixie-backports. Even if it works… it would be nice to find the patch which fixes the issue to eliminate the possibility of this being a race condition that may reappear with any kernel upgrade.
nocko
September 25, 2025, 2:32pm
16
Seems like this is the fix. Included in 6.16.7:
committed 05:02PM - 09 Sep 25 UTC
[ Upstream commit bdd5a14e660062114bdebaef9ad52adf04970a89 ]
The bridge has thr… ee bootstrap pins which are sampled to determine the
frequency of the external reference clock. The driver will also
(over)write that setting. But it seems this is racy after the bridge is
enabled. It was observed that although the driver write the correct
value (by sniffing on the I2C bus), the register has the wrong value.
The datasheet states that the GPIO lines have to be stable for at least
5us after asserting the EN signal. Thus, there seems to be some logic
which samples the GPIO lines and this logic appears to overwrite the
register value which was set by the driver. Waiting 20us after
asserting the EN line resolves this issue.
Fixes: a095f15c00e2 ("drm/bridge: add support for sn65dsi86 bridge driver")
Signed-off-by: Michael Walle <mwalle@kernel.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Link: https://lore.kernel.org/r/20250821122341.1257286-1-mwalle@kernel.org
Signed-off-by: Sasha Levin <sashal@kernel.org>
josch
September 25, 2025, 3:23pm
17
Okay. This can still take a while though.
I’m playing around with mkimage.sh but I can’t figure out how to uprev the kernel to 6.16.8, can someone point me in the right direction?
josch
September 26, 2025, 6:26am
19
Do you want to create a system image with kernel 6.16.8 or do you want to upgrade the kernel on your existing system? Can you be more verbose about what you are trying to accomplish? Upgrading your kernel does not involve mkimage.sh
I did a sudo apt full-upgrade over UART and got my system to update to 6.16.8. I can confirm that after a day of use and several reboots, I have not seen this issue again. I am back to daily driving my reform!
To answer your question josch, I originally wanted to create a new system image with 6.16.8, not upgrade an existing system. I didn’t realize that 6.16.8 was already available through apt and thought building a full system image from source with a newer kernel was the only way to get it. I am still curious about the system image build process though, do you know how to point mkimage.sh at a custom kernel version?
1 Like
