Just as an observation, latest rpi-update kernel build (5.10.50) 64bit appears to cause a firmware timeout trace on boot up, but otherwise results in a working system. Out of the 3x test units (2x Pi4B2 and 1x Pi4B8) which are used for general upgrade and kernel/firmware upgrade testing, only the Pi4B2 units encountered this issue. All units are configured for headless operation.
Details of the crash report : -
Code: Select all
[ 3.389628] ------------[ cut here ]------------
[ 3.389639] Firmware transaction timeout
[ 3.389708] WARNING: CPU: 1 PID: 187 at drivers/firmware/raspberrypi.c:64 rpi_firmware_transaction+0xdc/0x108
[ 3.389710] Modules linked in: cfg80211 rfkill 8021q garp stp llc vc4(+) cec v3d drm_kms_helper gpu_sched drm drm_panel_orientation_quirks raspberrypi_hwmon i2c_brcmstb snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops backlight uio_pdrv_genirq uio nvmem_rmem i2c_dev aes_neon_bs sha256_generic aes_neon_blk crypto_simd cryptd ip_tables x_tables
[ 3.389793] CPU: 1 PID: 187 Comm: systemd-udevd Not tainted 5.10.50-v8+ #1438
[ 3.389796] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
[ 3.389800] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)
[ 3.389804] pc : rpi_firmware_transaction+0xdc/0x108
[ 3.389809] lr : rpi_firmware_transaction+0xdc/0x108
[ 3.389811] sp : ffffffc011f7b720
[ 3.389813] x29: ffffffc011f7b720 x28: ffffffc01132e010
[ 3.389819] x27: 0000000000000000 x26: ffffff804462fb00
[ 3.389824] x25: ffffff80408f4d80 x24: ffffffc011a11008
[ 3.389829] x23: 0000000000001000 x22: ffffff80408f4d80
[ 3.389835] x21: 00000000ffffff92 x20: ffffffc01140f6c8
[ 3.389840] x19: ffffffc011298948 x18: 0000000000000000
[ 3.389845] x17: 0000000000000000 x16: 0000000000000000
[ 3.389851] x15: 0000000000000000 x14: 0000000000000000
[ 3.389856] x13: 00000000fffede56 x12: ffffffc011325480
[ 3.389861] x11: 0000000000000003 x10: ffffffc01130d440
[ 3.389866] x9 : ffffffc0100e6500 x8 : 0000000000017fe8
[ 3.389871] x7 : c0000000ffffefff x6 : ffffffc011f7b380
[ 3.389876] x5 : 0000000000000001 x4 : 0000000000000000
[ 3.389881] x3 : 0000000000000001 x2 : 0000000000000000
[ 3.389886] x1 : 6a1f6cab7ab59000 x0 : 0000000000000000
[ 3.389892] Call trace:
[ 3.389897] rpi_firmware_transaction+0xdc/0x108
[ 3.389901] rpi_firmware_property_list+0xc0/0x180
[ 3.389905] rpi_firmware_property+0x78/0x110
[ 3.389942] vc4_drm_bind+0x298/0x2c0 [vc4]
[ 3.389946] try_to_bring_up_master+0x170/0x1d8
[ 3.389949] component_master_add_with_match+0xbc/0x108
[ 3.389965] vc4_platform_drm_probe+0xd0/0x108 [vc4]
[ 3.389969] platform_drv_probe+0x5c/0xb0
[ 3.389974] really_probe+0xec/0x3c0
[ 3.389977] driver_probe_device+0x60/0xc0
[ 3.389981] device_driver_attach+0x7c/0x88
[ 3.389984] __driver_attach+0x60/0xe8
[ 3.389988] bus_for_each_dev+0x7c/0xd0
[ 3.389991] driver_attach+0x2c/0x38
[ 3.389994] bus_add_driver+0x194/0x1f8
[ 3.389998] driver_register+0x6c/0x128
[ 3.390001] __platform_driver_register+0x50/0x60
[ 3.390016] vc4_drm_register+0x50/0x1000 [vc4]
[ 3.390021] do_one_initcall+0x54/0x2d0
[ 3.390026] do_init_module+0x60/0x248
[ 3.390029] load_module+0x1fd8/0x2238
[ 3.390032] __do_sys_finit_module+0xbc/0xf8
[ 3.390035] __arm64_sys_finit_module+0x28/0x38
[ 3.390040] el0_svc_common.constprop.2+0xac/0x1d0
[ 3.390044] do_el0_svc+0x2c/0x98
[ 3.390050] el0_svc+0x20/0x30
[ 3.390054] el0_sync_handler+0x90/0xb8
[ 3.390057] el0_sync+0x180/0x1c0
[ 3.390060] ---[ end trace e8f8b40ee759d27c ]---
All 3x test units run PiOS 64bit, 1x Pi4B2 runs Lite only, the other and the Pi4B8 run the desktop version. These units are used for development and upgrade testing as well as other fixed functionality - backup imaging is always conducted before testing both general and kernel/firmware upgrades so any issues found are easily and can quickly be negated/restored.
In initial testing, reverting the Pi4B2 units to kernel build 5.10.46, boot without any sign of firmware timeout trace reports within dmesg boot logs. I haven't had any further available testing time yet to try narrowing down to a specific kernel/firmware commit, between 5.10.46 and 5.10.50.
Edit: No longer an issue after the update to newer commit 5.10.52.