Bootup Failure on Hamoa with 6.18.37

[sgaud-quic]

Bootup Failure on Hamoa with 6.18.37

Board : hamoa-iot-evk
Kernel version : 6.18.37
Lava Job : https://lava.infra.foundries.io/scheduler/job/397004

[    9.918294] pci 0006:00:00.0: PCI bridge to [bus 01-ff]
[    9.924553] pci_bus 0005:00: root bus resource [bus 00-ff]
[    9.929925] pci_bus 0006:00: resource 4 [io  0x200000-0x2fffff]
[    9.935562] pci_bus 0005:00: root bus resource [io  0x300000-0x3fffff] (bus address [0x0000-0xfffff])
[    9.941649] pci_bus 0006:00: resource 5 [mem 0x70300000-0x73ffffff]
[    9.951113] pci_bus 0005:00: root bus resource [mem 0x7e300000-0x7fffffff]
[    9.966629] pci 0005:00:00.0: [17cb:0111] type 01 class 0x060400 PCIe Root Port
[    9.974169] pci 0005:00:00.0: BAR 0 [mem 0x00000000-0x00000fff]
[    9.980264] pci 0005:00:00.0: PCI bridge to [bus 01-ff]
[    9.985636] pci 0005:00:00.0:   bridge window [io  0x300000-0x300fff]
[    9.992251] pci 0005:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[    9.999231] pci 0005:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   10.007222] pci 0005:00:00.0: PME# supported from D0 D3hot D3cold
[   10.015671] pci 0005:00:00.0: BAR 0 [mem 0x7e300000-0x7e300fff]: assigned
[   10.015874] pcieport 0003:00:00.0: PME: Signaling with IRQ 171
[   10.022673] pci 0005:00:00.0: PCI bridge to [bus 01-ff]
[   10.028936] pcieport 0003:00:00.0: AER: enabled with IRQ 171
[   10.034036] pci_bus 0005:00: resource 4 [io  0x300000-0x3fffff]
[   10.041294] pcieport 0006:00:00.0: PME: Signaling with IRQ 178
[   10.045932] pci_bus 0005:00: resource 5 [mem 0x7e300000-0x7fffffff]
[   10.058603] pcieport 0006:00:00.0: AER: enabled with IRQ 173
[   10.064891] pcieport 0005:00:00.0: PME: Signaling with IRQ 179
[   10.071302] pcieport 0005:00:00.0: AER: enabled with IRQ 179
root '/dev/disk/by-partlabel/rootfs' doesn't exist or does not contain a /dev.
[   39.911851] VREG_EDP_3P3: disabling
[   39.915458] VBL9: disabling
[   39.918439] VREG_RTMR0_1P15: disabling
[   39.922393] VREG_RTMR0_1P8: disabling
[   39.926261] VREG_RTMR1_1P15: disabling
[   39.930122] VREG_RTMR1_1P8: disabling
[   39.933895] VREG_RTMR1_3P3: disabling
[   39.937667] VREG_RTMR0_3P3: disabling
[   39.941535] VREG_RTMR2_1P15: disabling
[   39.945395] VREG_RTMR2_1P8: disabling
[   39.949174] VREG_RTMR2_3P3: disabling

[ziyuezhang-123]

From the boot log, I don't see any PCIe link training, enumeration, or AER failures.

The boot failure appears to be caused by:
root '/dev/disk/by-partlabel/rootfs' doesn't exist or does not contain a /dev.

As the device is boot from UFS not NVMe.
This looks more like a storage/UFS or boot configuration issue. Try to erase NVMe and UFS and then reflash the device may helping solve the issue

[Pradeep-pvk]

This appears to be similar to Launchpad Bug 2164906, which was resolved by https://orbit/CR/4649775. In that issue, the system became stuck in a TZ SCM call, as shown below, preventing the UFS probe from completing. As a result, the block devices were never created.

__switch_to+0x100/0x1e8 (T)
__schedule+0x2cc/0x748
schedule+0x40/0x110
schedule_timeout+0xf0/0x148
__wait_for_common+0xd0/0x238
wait_for_completion_state+0x2c/0x68
qcom_scm_wait_for_wq_completion+0x48/0xc0
__scm_smc_do.isra.0+0x100/0x198
__scm_smc_call+0xc8/0x330
qcom_scm_call+0x5c/0xd8
qcom_scm_ice_invalidate_key+0x7c/0xd0
qcom_ice_evict_key+0x48/0xa0
ufs_qcom_ice_keyslot_evict+0x50/0xa0 [ufs_qcom]
ufshcd_init_crypto+0x58/0xb8 [ufshcd_core]
ufshcd_init+0x61c/0x1040 [ufshcd_core]
ufshcd_pltfrm_init+0x14c/0x1230 [ufshcd_pltfrm]
ufs_qcom_probe+0x48/0xc8 [ufs_qcom]
platform_probe+0x70/0x128

Please ensure that the fix from CR 4649775 is included, as it addresses this issue and helps prevent the system from getting stuck during the TZ SCM call

[lumag]

I don't see this backtrace in the LAVA log, so I suppose that it's not related.