Prepare qcom-next based on tag 'Linux 7.0' of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

[sgaud-quic]

Name SHA Commits

tech/bsp/clk 0f5a318 14
tech/bsp/interconnect ec1ab95 7
tech/security/firmware-smc a50984a 2
tech/bsp/soc-infra c793ce5 5
tech/bsp/pinctrl 28c2b80 1
tech/bsp/remoteproc abb91ae 5
tech/bus/peripherals 0849a10 6
tech/bus/pci/all 6a697f8 6
tech/bus/pci/mhi fb9c163 1
tech/bus/pci/phy aaf8ef1 4
tech/bus/usb/dwc 49ac8e0 2
tech/bus/usb/phy 8c7f91d 35
tech/debug/hwtracing 87ae82d 31
tech/pmic/misc e6525e3 9
tech/pmic/regulator 81fc8fb 6
tech/mem/iommu e31b170 5
tech/mm/audio/all 06f5706 16
tech/mm/camss 7c584e4 29
tech/mm/drm fa2d11c 15
tech/mm/fastrpc c29b2a8 5
tech/mm/video 72e188f 29
tech/mm/gpu 9c8e55d 2
tech/net/ath 0fa4871 3
tech/net/eth 49b156f 1
tech/net/qrtr 64d75f7 1
tech/net/phy a3602e9 1
tech/net/bluetooth 229e73e 3
tech/pm/power 2c0fae8 10
tech/pm/thermal d174ed3 6
tech/security/crypto a6ce790 12
tech/security/ice 7a9d8eb 26
tech/storage/phy cf1667f 1
tech/storage/all e254dae 1
tech/all/dt/qcs6490 5df38ca 19
tech/all/dt/qcs9100 c98cdc0 22
tech/all/dt/qcs8300 a32d843 27
tech/all/dt/qcs615 cdbdac6 27
tech/all/dt/agatti c828f10 1
tech/all/dt/hamoa 0c8d1c1 38
tech/all/dt/glymur ac7a496 32
tech/all/dt/kaanapali 710775e 28
tech/all/dt/pakala f6b63a0 7
tech/all/config b31ed76 57
tech/overlay/dt 2d3b16a 34
tech/all/workaround c3f9d3b 13
tech/mproc/all b204da4 5
tech/noup/debug/all a8695a4 19
tech/hwe/unoq ce06e26 16

[qcomlnxci]

Test jobs on 3ab29d9

• Job 76364 on kaanapali-mtp
• Job 76366 on lemans-evk
• Job 76361 on monaco-evk
• Job 76359 on qcs615-ride
• Job 76365 on qcs6490-rb3gen2
• Job 76360 on qcs8300-ride
• Job 76363 on qcs9100-ride-r3
• Job 76362 on sm8750-mtp
• Job 76358 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
BT_FW_KMD_Service	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_ON_OFF	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_SCAN	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPUFreq_Validation	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPU_affinity	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
DSP_AudioPD	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Ethernet	◻️	◻️	✅ Pass	◻️	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
Freq_Scaling	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
GIC	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
IPA	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Interrupts	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
OpenCV	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
PCIe	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Probe_Failure_Check	◻️	◻️	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	◻️
RMNET	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
UFS_Validation	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
USBHost	◻️	◻️	❌ Fail	◻️	❌ Fail	✅ Pass	✅ Pass	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
WiFi_OnOff	◻️	◻️	⚠️ skip	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
cdsp_remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
hotplug	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
irq	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
kaslr	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
pinctrl	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
qcom_hwrng	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
rngtest	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
shmbridge	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail	◻️	◻️
smmu	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
watchdog	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
wpss_remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️

[qcomlnxci]

Test jobs on 3ab29d9

• Job 76369 on kaanapali-mtp
• Job 76376 on lemans-evk
• Job 76372 on monaco-evk
• Job 76371 on qcs615-ride
• Job 76373 on qcs6490-rb3gen2
• Job 76370 on qcs8300-ride
• Job 76374 on qcs9100-ride-r3
• Job 76368 on sm8750-mtp
• Job 76367 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
BT_FW_KMD_Service	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
BT_ON_OFF	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
BT_SCAN	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
CPUFreq_Validation	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
CPU_affinity	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
DSP_AudioPD	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
Ethernet	◻️	◻️	✅ Pass	◻️	⚠️ skip	❌ Fail	◻️	◻️	◻️
Freq_Scaling	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
GIC	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
IPA	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
Interrupts	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
OpenCV	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	◻️	◻️	◻️
PCIe	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
Probe_Failure_Check	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
RMNET	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
UFS_Validation	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
USBHost	◻️	◻️	❌ Fail	◻️	❌ Fail	✅ Pass	◻️	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	◻️	◻️	◻️
WiFi_OnOff	◻️	◻️	⚠️ skip	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
cdsp_remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
hotplug	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
irq	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
kaslr	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
pinctrl	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
qcom_hwrng	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
rngtest	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
shmbridge	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
smmu	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
watchdog	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
wpss_remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️

[qcomlnxci]

Test jobs on 3ab29d9

• Job 77207 on kaanapali-mtp
• Job 76376 on lemans-evk
• Job 76372 on monaco-evk
• Job 76371 on qcs615-ride
• Job 76373 on qcs6490-rb3gen2
• Job 76370 on qcs8300-ride
• Job 76374 on qcs9100-ride-r3
• Job 76368 on sm8750-mtp
• Job 76367 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
BT_FW_KMD_Service	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
BT_ON_OFF	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
BT_SCAN	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
CPUFreq_Validation	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
CPU_affinity	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
DSP_AudioPD	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
Ethernet	◻️	◻️	✅ Pass	◻️	⚠️ skip	❌ Fail	◻️	◻️	◻️
Freq_Scaling	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
GIC	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
IPA	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
Interrupts	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
OpenCV	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	◻️	◻️	◻️
PCIe	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
Probe_Failure_Check	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
RMNET	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
UFS_Validation	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
USBHost	◻️	◻️	❌ Fail	◻️	❌ Fail	✅ Pass	◻️	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	◻️	◻️	◻️
WiFi_OnOff	◻️	◻️	⚠️ skip	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
cdsp_remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
hotplug	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
irq	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
kaslr	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
pinctrl	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
qcom_hwrng	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
rngtest	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
shmbridge	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
smmu	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
watchdog	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️
wpss_remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️

[qcomlnxci]

Test jobs on 5ff8a42

• Job 77466 on kaanapali-mtp
• Job 77461 on lemans-evk
• Job 77460 on monaco-evk
• Job 77469 on qcs615-ride
• Job 77465 on qcs6490-rb3gen2
• Job 77463 on qcs8300-ride
• Job 77464 on qcs9100-ride-r3
• Job 77467 on sm8750-mtp
• Job 77462 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
BT_FW_KMD_Service	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_ON_OFF	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_SCAN	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPUFreq_Validation	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPU_affinity	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
DSP_AudioPD	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Ethernet	◻️	◻️	✅ Pass	◻️	⚠️ skip	❌ Fail	⚠️ skip	◻️	◻️
Freq_Scaling	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
GIC	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
IPA	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Interrupts	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
OpenCV	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
PCIe	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Probe_Failure_Check	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	❌ Fail	◻️	◻️
RMNET	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
UFS_Validation	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
USBHost	◻️	◻️	❌ Fail	◻️	❌ Fail	✅ Pass	✅ Pass	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
WiFi_OnOff	◻️	◻️	⚠️ skip	◻️	⚠️ skip	✅ Pass	✅ Pass	◻️	◻️
cdsp_remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
hotplug	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
irq	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
kaslr	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
pinctrl	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
qcom_hwrng	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
rngtest	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
shmbridge	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail	◻️	◻️
smmu	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
watchdog	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
wpss_remoteproc	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️

[qcomlnxci]

Test jobs on 159f17d

• Job 78412 on glymur-crd
• Job 78415 on kaanapali-mtp
• Job 78416 on lemans-evk
• Job 78418 on monaco-evk
• Job 78420 on qcs615-ride
• Job 78410 on qcs6490-rb3gen2
• Job 78411 on qcs8300-ride
• Job 78413 on qcs9100-ride-r3
• Job 78419 on sm8750-mtp
• Job 78417 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	glymur-crd	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
0_qcom-next-ci-premerge-tests	◻️	◻️	◻️	◻️	◻️	◻️	◻️	❌ Fail	◻️	◻️
BT_FW_KMD_Service	◻️	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_ON_OFF	◻️	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_SCAN	◻️	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPUFreq_Validation	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPU_affinity	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
DSP_AudioPD	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Ethernet	◻️	◻️	◻️	✅ Pass	◻️	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
Freq_Scaling	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
GIC	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	❌ Fail	✅ Pass	◻️	◻️
IPA	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Interrupts	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
OpenCV	◻️	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
PCIe	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Probe_Failure_Check	◻️	◻️	◻️	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	◻️
RMNET	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
UFS_Validation	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
USBHost	◻️	◻️	◻️	❌ Fail	◻️	❌ Fail	❌ Fail	✅ Pass	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	◻️	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
WiFi_OnOff	◻️	◻️	◻️	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
cdsp_remoteproc	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
hotplug	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
irq	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
kaslr	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
pinctrl	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
qcom_hwrng	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
remoteproc	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
rngtest	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
shmbridge	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail	◻️	◻️
smmu	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
watchdog	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
wpss_remoteproc	◻️	◻️	◻️	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	◻️

[qcomlnxci]

Test jobs on 5ff8a42

• Job 80087 on kaanapali-mtp
• Job 80091 on lemans-evk
• Job 80090 on monaco-evk
• Job 80094 on qcs615-ride
• Job 80092 on qcs6490-rb3gen2
• Job 80095 on qcs8300-ride
• Job 80093 on qcs9100-ride-r3
• Job 80088 on sm8750-mtp
• Job 80089 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
BT_FW_KMD_Service	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_ON_OFF	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_SCAN	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPUFreq_Validation	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPU_affinity	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
DSP_AudioPD	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Ethernet	◻️	◻️	✅ Pass	⚠️ skip	⚠️ skip	❌ Fail	⚠️ skip	◻️	◻️
Freq_Scaling	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
GIC	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
IPA	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Interrupts	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
OpenCV	◻️	◻️	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
PCIe	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Probe_Failure_Check	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️	◻️
RMNET	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
UFS_Validation	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
USBHost	◻️	◻️	❌ Fail	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
WiFi_OnOff	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
cdsp_remoteproc	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
hotplug	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
irq	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
kaslr	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
pinctrl	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
qcom_hwrng	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
remoteproc	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
rngtest	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
shmbridge	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️	◻️
smmu	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
watchdog	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
wpss_remoteproc	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️

[qcomlnxci]

Test jobs on 5ff8a42

• Job 80566 on glymur-crd
• Job 80087 on kaanapali-mtp
• Job 80091 on lemans-evk
• Job 80090 on monaco-evk
• Job 80094 on qcs615-ride
• Job 80092 on qcs6490-rb3gen2
• Job 80095 on qcs8300-ride
• Job 80093 on qcs9100-ride-r3
• Job 80088 on sm8750-mtp
• Job 80089 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	glymur-crd	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
BT_FW_KMD_Service	◻️	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_ON_OFF	◻️	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
BT_SCAN	◻️	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPUFreq_Validation	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
CPU_affinity	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
DSP_AudioPD	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Ethernet	◻️	◻️	◻️	✅ Pass	⚠️ skip	⚠️ skip	❌ Fail	⚠️ skip	◻️	◻️
Freq_Scaling	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
GIC	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
IPA	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Interrupts	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
OpenCV	◻️	◻️	◻️	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
PCIe	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
Probe_Failure_Check	◻️	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️	◻️
RMNET	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
UFS_Validation	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
USBHost	◻️	◻️	◻️	❌ Fail	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	◻️	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	◻️	◻️
WiFi_OnOff	◻️	◻️	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
cdsp_remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
hotplug	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
irq	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
kaslr	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
pinctrl	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
qcom_hwrng	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
rngtest	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
shmbridge	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️	◻️
smmu	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
watchdog	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️
wpss_remoteproc	◻️	◻️	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️

[qcomlnxci]

Test Matrix

Test Case	glymur-crd	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
BT_FW_KMD_Service	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
BT_ON_OFF	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
BT_SCAN	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
CPUFreq_Validation	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
CPU_affinity	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
DSP_AudioPD	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
Ethernet	◻️	◻️	⚠️ skip	✅ Pass	◻️	◻️	⚠️ skip	⚠️ skip	◻️	◻️
Freq_Scaling	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
GIC	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
IPA	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
Interrupts	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
OpenCV	◻️	◻️	⚠️ skip	⚠️ skip	◻️	◻️	⚠️ skip	⚠️ skip	◻️	◻️
PCIe	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
Probe_Failure_Check	◻️	◻️	❌ Fail	❌ Fail	◻️	◻️	❌ Fail	❌ Fail	◻️	◻️
RMNET	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
UFS_Validation	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
USBHost	◻️	◻️	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	✅ Pass	◻️	◻️
WiFi_Firmware_Driver	◻️	◻️	⚠️ skip	⚠️ skip	◻️	◻️	⚠️ skip	⚠️ skip	◻️	◻️
WiFi_OnOff	◻️	◻️	✅ Pass	❌ Fail	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
cdsp_remoteproc	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
hotplug	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
irq	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
kaslr	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
pinctrl	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
qcom_hwrng	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
remoteproc	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
rngtest	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
shmbridge	◻️	◻️	❌ Fail	✅ Pass	◻️	◻️	✅ Pass	❌ Fail	◻️	◻️
smmu	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
watchdog	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️
wpss_remoteproc	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️	◻️

[qcomlnxci]

Test jobs on 740314b

• Job 80592 on glymur-crd
• Job 80593 on kaanapali-mtp
• Job 80589 on lemans-evk
• Job 80588 on monaco-evk
• Job 80594 on qcs615-ride
• Job 80591 on qcs6490-rb3gen2
• Job 80587 on qcs8300-ride
• Job 80595 on qcs9100-ride-r3
• Job 80590 on sm8750-mtp
• Job 80597 on x1e80100-crd

[rahujosh]

LAVA Failed Case Triage Summary

PR: #495

Job 80592 | SoC glymur-crd

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/80592

Failed test cases in LAVA job 80592 (SoC: glymur-crd).

  Case 1: auto-login-action

1. Failed case: auto-login-action
2. Root cause: On glymur-crd, the device never reaches kernel boot and falls back to USB Sahara (ENUM success -> Sahara Open) after reset, so LAVA’s auto-login-action waiting for Linux version times out due to board boot-flow/media state (SPI->NVMe path) rather than a kernel runtime crash.
3. Possible fix: Update the glymur-crd LAVA flow to force Normal boot mode after EDL flashing and gate auto-login-action on verified post-flash boot-media readiness (NVMe path visible) before starting prompt wait.
4. Detail analysis attachment: failed_case_job80592_1_detailed.md

  Case 2: minimal-boot

1. Failed case: minimal-boot
2. Root cause: On glymur-crd, the LAVA deploy path sets TAC debugboard boot mode to EDL and never switches it back, so the board reboots into USB Sahara (ENUM success/Sahara Init) instead of continuing SPI boot to Linux, causing auto-login-action timeout.
3. Possible fix: Update the LAVA worker flow for glymur-crd to explicitly set TAC boot mode back to Normal (or clear EDL latch) after flashing and before minimal-boot reset, then rerun case 2.
4. Detail analysis attachment: failed_case_job80592_2_detailed.md

  Case 3: job

1. Failed case: job
2. Root cause: On glymur-crd, the PR boot artifact never reaches the expected Linux boot banner because the SoC resets around the XBL/UEFI handoff (PM: Entering UEFI threshold) and drops into RamDump/Sahara mode, so minimal-boot times out and the wrapper job case fails.
3. Possible fix: On glymur-crd, fix the early-boot regression in the flashed kernel/DT boot path (validate boot.img+DTB compatibility and recent glymur-specific changes), and as immediate mitigation increase minimal-boot block timeout so retries are not exhausted by a single long boot failure.
4. Detail analysis attachment: failed_case_job80592_3_detailed.md

Job 80589 | SoC lemans-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/80589

Failed test cases in LAVA job 80589 (SoC: lemans-evk).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: On lemans-evk, the testcase hard-fails on three boot-time log matches that are platform-expected optional-device conditions (missing QCA BT firmware files and SPI TPM probe timeout) rather than a kernel crash/regression.
3. Possible fix: Make Probe_Failure_Check SoC-aware for lemans-evk by allowlisting/gating qca/*hpbtfw21*.tlv -ENOENT and tpm_tis_spi spi0.0 -110 unless BT firmware/TPM hardware is explicitly required in that lab profile.
4. Detail analysis attachment: failed_case_job80589_1_detailed.md

  Case 2: shmbridge

1. Failed case: shmbridge
2. Root cause: On lemans-evk (SA8775P), the qcom-iris video codec probe emits qcom_scm_mem_protect_video_var failed: -5 during boot, and the shmbridge testcase fails because it treats these non-shmbridge SCM video-protection errors as a shmbridge failure.
3. Possible fix: Gate/disable Iris secure video memory-protect calls on lemans-evk unless the required TZ/secure video memory setup is present, and update shmbridge log filtering to only fail on actual shmbridge/QCOM_SCM bridge API errors.
4. Detail analysis attachment: failed_case_job80589_2_detailed.md

  Case 3: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: On the lemans-evk run, the test runner sent LAVA_SIGNAL_STARTRUN but never sent LAVA_SIGNAL_ENDRUN, so LAVA marked the run unfinished and failed it despite normal TAC debugboard power control and successful board execution.
3. Possible fix: Update the qcom-next-ci-premerge runner (run.sh/result_parse.sh) to always emit LAVA_SIGNAL_ENDRUN in a trap/finally path on lemans-evk (including when subtests fail/skip), then re-run job 80589 flow.
4. Detail analysis attachment: failed_case_job80589_3_detailed.md

Job 80588 | SoC monaco-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/80588

Failed test cases in LAVA job 80588 (SoC: monaco-evk).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: On monaco-evk (QCS8300), Probe_Failure_Check is a false-positive failure caused by generic dmesg pattern matching of boot-time benign/optional probe events (cpufreq-dt -17, missing optional BT firmware fallback files, and tpm_tis_spi -110 on likely-unpopulated TPM SPI path) after DT changes in PR495.
3. Possible fix: Make the check SoC-aware by allowlisting these known monaco-evk benign signatures (or gating them on DT/hardware presence) and keep only actionable probe failures as fail criteria.
4. Detail analysis attachment: failed_case_job80588_1_detailed.md

  Case 2: USBHost

1. Failed case: USBHost
2. Root cause: On monaco-evk, USBHost fails because the PR’s later DT refactor moved board USB settings into monaco-evk-common.dtsi with &usb_1 { dr_mode = "peripheral"; }, which regresses the EVK’s primary GL3590-backed host path and leaves no host-enumerated USB devices for the test.
3. Possible fix: Restore monaco-evk primary USB DT to host configuration (dr_mode = "host" plus its Type-C/hub routing in the common/board DTS) and rerun USBHost with a known attached USB device on the EVK host path.
4. Detail analysis attachment: failed_case_job80588_2_detailed.md

  Case 3: WiFi_OnOff

1. Failed case: WiFi_OnOff
2. Root cause: On monaco-evk (SocMonacoLAA), the LAVA test image exposes ath11k modules but does not provide usable WiFi firmware/board data for the WCN6855/QCA6698 path, so no ieee80211 phy or WLAN netdev is created and WiFi_OnOff times out.
3. Possible fix: Update monaco-evk LAVA artifact provisioning to include/validate required ath11k firmware+BDF files before running WiFi_OnOff, and make the testcase SKIP (not FAIL) when those SoC-specific firmware prerequisites are absent.
4. Detail analysis attachment: failed_case_job80588_3_detailed.md

  Case 4: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: On monaco-evk, the premerge runner sends STARTRUN and per-test TESTCASE signals but never sends LAVA_SIGNAL_ENDRUN, so lava-dispatcher marks the test run unfinished/failed, with additional bench-dependent Monaco connectivity checks (USBHost/WiFi_OnOff) also failing.
3. Possible fix: Update the Monaco premerge runner flow (run.sh/result_parse.sh) to always emit LAVA_SIGNAL_ENDRUN with final aggregated status and make USB/WiFi checks conditional on detected Monaco lab peripherals/firmware readiness.
4. Detail analysis attachment: failed_case_job80588_4_detailed.md

Job 80594 | SoC qcs615-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/80594

Failed test cases in LAVA job 80594 (SoC: qcs615-ride).

  Case 1: login-action

1. Failed case: login-action
2. Root cause: On qcs615-ride, after fastboot boot the DUT never reached stable userspace because stray/corrupted fastboot getvar:product traffic appeared during login wait and the boot chain hit a watchdog reset, so LAVA never saw a shell prompt.
3. Possible fix: On the qcs615-ride worker, enforce exclusive TAC/USB ownership and normal-boot state after fastboot boot (reset/lock fastboot channel so no extra getvar reaches the DUT), then rerun the job.
4. Detail analysis attachment: failed_case_job80594_1_detailed.md

  Case 2: auto-login-action

1. Failed case: auto-login-action
2. Root cause: On qcs615-ride, the DUT unexpectedly reset/re-entered the PBL/SBL/UEFI boot path during fastboot boot (UART jumps from kernel output back to Format: Log Type boot banners), so LAVA never reached the expected root shell prompt.
3. Possible fix: Add qcs615-ride-specific recovery in LAVA fastboot-boot/auto-login-action to detect bootloader banner reappearance and immediately re-power-cycle + re-run fastboot boot (instead of waiting for login timeout), while checking board power/reset stability on TAC/PDU.
4. Detail analysis attachment: failed_case_job80594_2_detailed.md

  Case 3: fastboot-boot

1. Failed case: fastboot-boot
2. Root cause: On qcs615-ride, fastboot boot reported OKAY but the DUT stayed/re-entered the Qualcomm bootloader/UEFI fastboot path (repeated bootloader logs and Unhandled command: getvar:product) instead of reaching Linux console, so login-action timed out.
3. Possible fix: In the qcs615-ride LAVA fastboot path, add a post-boot state check that confirms exit from fastboot and Linux-console arrival, and on failure force a TAC debugboard normal-boot/power-cycle recovery with a longer fastboot-boot timeout.
4. Detail analysis attachment: failed_case_job80594_3_detailed.md

  Case 4: job

1. Failed case: job
2. Root cause: On the qcs615-ride (IQ-615 EVK), the DUT reboots back into PBL/SBL during fastboot-boot auto-login, so LAVA never reaches a stable Linux shell prompt and login-action times out.
3. Possible fix: Add a qcs615-ride boot-stability guard in LAVA (detect unexpected PBL/SBL banners after Starting kernel, force TAC debugboard power-cycle + fastboot retry) and increase fastboot-boot block timeout so retries can complete.
4. Detail analysis attachment: failed_case_job80594_4_detailed.md

Job 80591 | SoC qcs6490

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/80591

Failed test cases in LAVA job 80591 (SoC: qcs6490).

  Case 1: auto-login-action

1. Failed case: auto-login-action
2. Root cause: On qcs6490 (RB3gen2), fastboot boot succeeds but the DUT falls into a pre-OS XBL/UEFI reboot loop (including watchdog reset) and never reaches a Linux console prompt, so auto-login-action times out.
3. Possible fix: Force the RB3gen2 into confirmed normal boot state (not forced USB/dload), perform a hard power-cycle and firmware-slot sanity recovery on this board, then rerun with slightly larger fastboot-boot block timeout so retries are available if one boot loop recurs.
4. Detail analysis attachment: failed_case_job80591_1_detailed.md

  Case 2: fastboot-boot

1. Failed case: fastboot-boot
2. Root cause: On qcs6490 RB3gen2, fastboot boot succeeds but the board never reaches a stable Linux console (it repeatedly returns to UEFI/Gunyah and watchdog-resets), so LAVA auto-login-action times out and the case fails due block-time exhaustion.
3. Possible fix: For qcs6490 fastboot jobs, align boot artifacts/firmware expectations (boot.img + rb3gen2 DT/firmware compatibility) and adjust the LAVA fastboot-boot timeout/retry budget so one failed auto-login attempt does not consume the whole block.
4. Detail analysis attachment: failed_case_job80591_2_detailed.md

  Case 3: job

1. Failed case: job
2. Root cause: On qcs6490 RB3gen2, fastboot boot succeeds but the DUT never reaches the expected Linux console banner (Linux version [0-9]) and repeatedly falls back to early boot firmware, so auto-login-action times out and fastboot-boot exhausts the 10-minute block budget.
3. Possible fix: Update the qcs6490 LAVA boot flow to ensure kernel console comes up (verify boot.img+DTB/initramfs+cmdline for RB3gen2) and raise fastboot-boot block timeout (or reduce per-attempt timeout) so retries are actually possible.
4. Detail analysis attachment: failed_case_job80591_3_detailed.md

Job 80587 | SoC qcs8300-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/80587

Failed test cases in LAVA job 80587 (SoC: qcs8300-ride).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: On qcs8300-ride, Probe_Failure_Check is failing on three boot-time probe signatures (cpufreq-dt -17, AQR115C -22, xhci-hcd -110) that are currently treated as fatal by a generic log matcher even though they are platform bring-up/optional-path issues rather than a core kernel crash.
3. Possible fix: Make Probe_Failure_Check SoC-aware by allowlisting these known qcs8300-ride non-fatal probe patterns (or downgrading them to WARN) and keep USB/Ethernet health validated in their dedicated testcases, while separately fixing DT/board config if those peripherals are required.
4. Detail analysis attachment: failed_case_job80587_1_detailed.md

  Case 2: USBHost

1. Failed case: USBHost
2. Root cause: On qcs8300-ride, the USB host controller fails to initialize (xhci-hcd ... can't setup: -110 / probe failed), so the USBHost test cannot enumerate any USB devices.
3. Possible fix: Fix qcs8300-ride USB host bring-up by correcting DT/boot-time USB host wiring (host mode, VBUS regulator/GPIO enable, and HS/SS PHY clock-power dependencies) until xhci-hcd probes successfully.
4. Detail analysis attachment: failed_case_job80587_2_detailed.md

  Case 3: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: On the qcs8300-ride bench, required lab dependencies (notably USB host fixture/peripheral, and likely associated probe/firmware expectations) were missing, causing suite-level FAILs and the runner to exit without sending an end-of-run signal so LAVA marked the run unfinished.
3. Possible fix: Ensure qcs8300-ride LAVA worker provisioning includes the expected USBHost fixture and board-specific firmware/dependency set, and update the test runner to always emit ENDRUN/finalize signaling even when subtests fail.
4. Detail analysis attachment: failed_case_job80587_3_detailed.md

Job 80595 | SoC qcs9100-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/80595

Failed test cases in LAVA job 80595 (SoC: qcs9100-ride).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: On qcs9100-ride (Lemans Ride Rev3), Probe_Failure_Check fails because boot dmesg contains one Aquantia PHY probe error (AQR115C stmmac-0:08 ... error -22), indicating an invalid/unused MDIO PHY entry or missing PHY firmware property for an optional Ethernet path rather than a system crash.
3. Possible fix: Update qcs9100-ride/Lemans Ethernet DT to disable the unused Aquantia PHY path at stmmac-0:08 (or provide its required firmware/property data), and temporarily filter this known benign signature in Probe_Failure_Check until DT is corrected.
4. Detail analysis attachment: failed_case_job80595_1_detailed.md

  Case 2: shmbridge

1. Failed case: shmbridge
2. Root cause: On qcs9100-ride (Lemans Ride Rev3), boot-time IRIS (aa00000.video-codec) secure memory setup fails in TrustZone (qcom_scm_mem_protect_video_var failed: -5), and the shmbridge test fails because it flags these generic qcom_scm errors from current-boot dmesg.
3. Possible fix: Fix the qcs9100 IRIS secure PAS/CP memory configuration path (DT video-firmware/tz_cp_config and SCM sequencing) and tighten the shmbridge testcase grep to qcom_scm_shm_bridge*-specific failures instead of any qcom_scm error.
4. Detail analysis attachment: failed_case_job80595_2_detailed.md

  Case 3: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: On qcs9100-ride (Lemans Ride Rev3), the test runner started 0_qcom-next-ci-premerge-tests but never emitted LAVA_SIGNAL_ENDRUN, so lava-dispatcher marked the run unfinished and failed after collecting subtest results (including Probe_Failure_Check and shmbridge as FAIL).
3. Possible fix: Update the qcom-next-ci-premerge runner/result parser to always send LAVA_SIGNAL_ENDRUN on qcs9100-ride regardless of subtest failures, then rerun job 80595 to confirm clean run closure and expected per-test fail/pass reporting.
4. Detail analysis attachment: failed_case_job80595_3_detailed.md

Job 80590 | SoC sm8750-mtp

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/80590

Failed test cases in LAVA job 80590 (SoC: sm8750-mtp).

  Case 1: auto-login-action

1. Failed case: auto-login-action
2. Root cause: On sm8750-mtp, the device never reaches kernel console because XBL/AVB reports dtbo_a hash mismatch (Hash of data does not match digest) and stays in bootloader/mission-mode flow, so auto-login-action times out waiting for Linux version.
3. Possible fix: Re-provision the sm8750-mtp DUT boot-chain partitions as a matched set (at minimum dtbo_a with corresponding vbmeta* baseline, and verify fastboot boot artifacts align with that baseline) before rerunning the LAVA job.
4. Detail analysis attachment: failed_case_job80590_1_detailed.md

  Case 2: fastboot-boot

1. Failed case: fastboot-boot
2. Root cause: On sm8750-mtp the fastboot flow booted a boot.img that was not artifact-matched with the board’s dtbo_a/vbmeta_a chain, triggering dtbo_a AVB hash mismatch and bootloader DTB-corruption path so Linux never reached console prompt.
3. Possible fix: Regenerate and deploy a single matched sm8750-mtp boot set (boot.img + dtbo + vbmeta) or flash matching dtbo_a/vbmeta_a before fastboot boot, then rerun the LAVA fastboot-boot block.
4. Detail analysis attachment: failed_case_job80590_2_detailed.md

  Case 3: job

1. Failed case: job
2. Root cause: On sm8750-mtp, the fastboot boot chain never reaches kernel handoff because UEFI/AVB reports dtbo_a digest mismatch and DTB/runtime-image integrity warnings, so LAVA times out waiting for Linux version.
3. Possible fix: Regenerate and deploy a coherent SM8750 boot artifact set (boot.img + matching dtbo/vbmeta expectations for this firmware) and re-run with the same board firmware/slot to confirm kernel banner appears before auto-login-action timeout.
4. Detail analysis attachment: failed_case_job80590_3_detailed.md

[qcomlnxci]

Test jobs on c02129c

• Job 81079 on glymur-crd
• Job 81082 on kaanapali-mtp
• Job 81085 on lemans-evk
• Job 81083 on monaco-evk
• Job 81084 on qcs615-ride
• Job 81086 on qcs6490-rb3gen2
• Job 81080 on qcs8300-ride
• Job 81078 on qcs9100-ride-r3
• Job 81081 on sm8750-mtp
• Job 81087 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	glymur-crd	kaanapali-mtp	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	sm8750-mtp	x1e80100-crd
0_qcom-next-ci-premerge-tests	❌ Fail	◻️	◻️	◻️	◻️	◻️	◻️	◻️	◻️	◻️
BT_FW_KMD_Service	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
BT_ON_OFF	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
BT_SCAN	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
CPUFreq_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
CPU_affinity	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
DSP_AudioPD	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
Ethernet	⚠️ skip	◻️	⚠️ skip	✅ Pass	◻️	⚠️ skip	◻️	⚠️ skip	◻️	◻️
Freq_Scaling	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
GIC	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
IPA	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
Interrupts	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
OpenCV	◻️	◻️	⚠️ skip	⚠️ skip	◻️	⚠️ skip	◻️	⚠️ skip	◻️	◻️
PCIe	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
Probe_Failure_Check	❌ Fail	◻️	❌ Fail	❌ Fail	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
RMNET	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
UFS_Validation	⚠️ skip	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
USBHost	✅ Pass	◻️	✅ Pass	❌ Fail	◻️	❌ Fail	◻️	✅ Pass	◻️	◻️
WiFi_Firmware_Driver	❌ Fail	◻️	⚠️ skip	⚠️ skip	◻️	⚠️ skip	◻️	⚠️ skip	◻️	◻️
WiFi_OnOff	❌ Fail	◻️	✅ Pass	❌ Fail	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
cdsp_remoteproc	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
hotplug	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
irq	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
kaslr	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
pinctrl	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
qcom_hwrng	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
remoteproc	❌ Fail	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
rngtest	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
shmbridge	❌ Fail	◻️	❌ Fail	✅ Pass	◻️	✅ Pass	◻️	❌ Fail	◻️	◻️
smmu	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
watchdog	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️
wpss_remoteproc	⚠️ skip	◻️	✅ Pass	✅ Pass	◻️	✅ Pass	◻️	✅ Pass	◻️	◻️

[rahujosh]

LAVA Failed Case Triage Summary

PR: #495

Job 81079 | SoC glymur-crd

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81079

Failed test cases in LAVA job 81079 (SoC: glymur-crd).

  Case 1: cdsp_remoteproc

1. Failed case: cdsp_remoteproc
2. Root cause: On glymur-crd, PR 495 enables CDSP remoteproc with firmware path qcom/glymur/cdsp.mbn, but the test image lacks that glymur CDSP firmware (request_firmware -2), so remoteproc1 stays offline.
3. Possible fix: Add/deploy the glymur DSP firmware bundle (qcom/glymur/cdsp.mbn and matching DTB blob, plus ADSP pair) into the LAVA rootfs firmware path used by this SoC, then re-run the case.
4. Detail analysis attachment: failed_case_job81079_1_detailed.md

  Case 2: remoteproc

1. Failed case: remoteproc
2. Root cause: On glymur-crd, ADSP/CDSP remoteproc nodes are enabled and expect firmware at qcom/glymur/{adsp,cdsp}*.mbn, but firmware loading fails with -2 (file not found), so both remoteprocs stay offline and the test sees running=0/expected=2.
3. Possible fix: Ship/install the matching Glymur ADSP/CDSP firmware set (adsp.mbn, adsp_dtb.mbn, cdsp.mbn, cdsp_dtb.mbn) in the runtime firmware path used by this LAVA image, or align DT firmware-name to the actually deployed SoC firmware layout.
4. Detail analysis attachment: failed_case_job81079_2_detailed.md

  Case 3: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: On glymur-crd, PR Prepare qcom-next based on tag 'Linux 7.0' of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git #495 enables new bring-up nodes (ADSP/CDSP remoteproc, WCN7850 Wi-Fi/BT, LPASS audio/pinctrl), but the boot image lacks required firmware blobs and some LPASS/PCIe dependency paths are not fully ready, so probe/deferred failures are logged and the case fails.
3. Possible fix: For glymur-crd, provide the matching firmware set (qcom/glymur/*, qca/hmtbtfw20.tlv, regulatory.db) and gate/disable not-yet-ready WLAN/audio/remoteproc DT nodes (or case allowlist) until PCIe-MSI and LPASS supplier chains probe cleanly.
4. Detail analysis attachment: failed_case_job81079_3_detailed.md

  Case 4: shmbridge

1. Failed case: shmbridge
2. Root cause: On glymur-crd, the shmbridge testcase’s qcom_scm error-scan falsely flags the boot command line (qcom_scm.download_mode=1 with panic=-1) as a qcom_scm failure even though SCM initialized normally.
3. Possible fix: Update the shmbridge log parser to only match real qcom_scm runtime error lines (exclude Kernel command line/bootargs and non-fatal “untested machine, skipping” messages) and rerun on glymur-crd.
4. Detail analysis attachment: failed_case_job81079_4_detailed.md

  Case 5: WiFi_Firmware_Driver

1. Failed case: WiFi_Firmware_Driver
2. Root cause: On glymur-crd, the WCN7850 Wi-Fi 7 endpoint on PCI domain 0004 enumerates and firmware is present, but ath12k probe aborts because MSI allocation fails with -22, indicating a PCIe/MSI mapping/config regression in the kernel stack for this SoC path.
3. Possible fix: Fix or revert the PR’s PCIe/MSI mapping changes (DT msi-map/#msi-cells handling and related OF MSI translation path) so MSI vectors are successfully allocated for 0004:01:00.0 on glymur-crd before ath12k probe.
4. Detail analysis attachment: failed_case_job81079_5_detailed.md

  Case 6: WiFi_OnOff

1. Failed case: WiFi_OnOff
2. Root cause: On glymur-crd, the WCN7850 WiFi endpoint at /soc@0/pci@1bf0000/pcie@0/wifi@0 fails during PCIe MSI setup (failed to alloc msi: -22), indicating a target-side PCIe/MSI mapping/bring-up regression rather than LAVA worker/debugboard/PDU failure.
3. Possible fix: Validate and fix glymur PCIe0 MSI routing/config (DT msi-map/#msi-cells and related DWC/QCOM PCIe MSI path), then rerun the same LAVA flow to confirm ath12k_wifi7_pci probes successfully.
4. Detail analysis attachment: failed_case_job81079_6_detailed.md

  Case 7: qcom_hwrng

1. Failed case: qcom_hwrng
2. Root cause: On glymur-crd, the boot firmware TRNG path is not initialized (ArmTrngLib could not be correctly initialized), so userspace cannot switch rng_current to qcom_hwrng and the testcase fails.
3. Possible fix: Update the glymur-crd boot/DT image so Qualcomm HWRNG is actually registered and selectable, and make qcom_hwrng test auto-SKIP when qcom_hwrng is absent from rng_available on this board.
4. Detail analysis attachment: failed_case_job81079_7_detailed.md

  Case 8: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: On glymur-crd, the DUT dropped from Linux into Qualcomm ramdump/EDL (boot_dload_entry -> Sahara Open) and LAVA lava-test-shell kept waiting for a root prompt until the 1200s timeout instead of triggering recovery/fail-fast.
3. Possible fix: Add glymur-crd-specific bootrom/EDL detection in the LAVA worker (match RamDump, boot_dload_entry, Sahara) to immediately power-cycle via debugboard.py --board tac and re-enter normal boot or fail the case early.
4. Detail analysis attachment: failed_case_job81079_8_detailed.md

Job 81082 | SoC kaanapali-mtp

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81082

Failed test cases in LAVA job 81082 (SoC: kaanapali-mtp).

  Case 1: login-action

1. Failed case: login-action
2. Root cause: On kaanapali-mtp, the DUT panicked early in Linux and fell back into Qualcomm PBL/USB Sahara (EDL) mode, so LAVA kept waiting for a shell/login prompt that can never appear on that boot path.
3. Possible fix: Update the kaanapali LAVA recovery flow to treat Kernel panic as immediate boot failure and force a full recovery cycle (debugboard.py power-cycle + correct boot mode back to normal boot, reflash if needed) before retrying login.
4. Detail analysis attachment: failed_case_job81082_1_detailed.md

  Case 2: auto-login-action

1. Failed case: auto-login-action
2. Root cause: On kaanapali-mtp, the DUT hits an early display-path kernel panic (msm_disp_snapshot_add_block) after DPU/Adreno bring-up and drops into PBL/APBL logs, so LAVA never receives a valid Linux login:/shell prompt and auto-login-action times out.
3. Possible fix: Align the kaanapali boot stack (kernel/DT/rootfs firmware, especially display firmware expectations) and fix the display snapshot panic path, then keep LAVA robust by using a stricter prompt and forcing reboot-on-panic before login retries.
4. Detail analysis attachment: failed_case_job81082_2_detailed.md

  Case 3: minimal-boot

1. Failed case: minimal-boot
2. Root cause: On kaanapali-mtp, the DUT never reaches a Linux login prompt because it hits an early kernel panic in the display path (msm_disp_snapshot_add_block) and reboots into PBL logs, so LAVA login-action times out.
3. Possible fix: For kaanapali-mtp, treat kernel panic as terminal in minimal-boot (fail fast instead of waiting for login) and fix the display/firmware mismatch causing the msm panic so boot reaches login:/shell prompt.
4. Detail analysis attachment: failed_case_job81082_3_detailed.md

  Case 4: job

1. Failed case: job
2. Root cause: On kaanapali-mtp, the kernel boots but crashes at ~8s with a DRM/MSM display snapshot Oops (msm_disp_snapshot_add_block) after DPU frame-done timeout and missing Adreno SQE firmware, so LAVA later only sees reboot/Sahara output and minimal-boot times out into a job failure.
3. Possible fix: Make the kaanapali boot image/rootfs provide qcom/gen80200_sqe.fw and apply a guard/fix in the MSM display snapshot path (msm_disp_snapshot_add_block caller chain) to prevent invalid memory access during DPU timeout snapshot capture.
4. Detail analysis attachment: failed_case_job81082_4_detailed.md

Job 81085 | SoC lemans-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81085

Failed test cases in LAVA job 81085 (SoC: lemans-evk).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: On lemans-evk, early boot logs include a non-responsive optional SPI TPM (tpm_tis_spi ... -110) and missing optional QCA BT fallback firmware blobs (qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv -> -2), which the testcase treats as hard probe/firmware failures.
3. Possible fix: Make Probe_Failure_Check SoC-aware by allowlisting these known-benign lemans-evk signatures (or alternatively ship the BT blobs and disable/fix the unused TPM DT path), then re-run job 81085 flow.
4. Detail analysis attachment: failed_case_job81085_1_detailed.md

  Case 2: shmbridge

1. Failed case: shmbridge
2. Root cause: On lemans-evk (SA8775P/Lemans), Iris (aa00000.video-codec) is now probed from DT and issues secure SCM video CP requests during boot, but TrustZone/SCM rejects qcom_scm_mem_protect_video_var (-5), and the shmbridge test fails because it treats any qcom_scm kernel error as a testcase failure.
3. Possible fix: Gate/disable Iris secure CP programming on lemans-evk until matching TZ/firmware + DT mapping support is present (or keep &iris disabled on this board config), and in parallel tighten the shmbridge test to check SHM-bridge-specific SCM failures instead of generic qcom_scm log matches.
4. Detail analysis attachment: failed_case_job81085_2_detailed.md

  Case 3: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: On lemans-evk, the test payload hit real platform boot/runtime errors (qcom-iris SCM protect failures and missing WCN BT firmware files, plus TPM probe timeout), and the run ended without an ENDRUN signal so LAVA marked the test run as unfinished/failed.
3. Possible fix: Align the lemans-evk test image/firmware+DT stack (provide expected BT firmware and correct SCM/TZ compatibility or filter known-benign board-specific probe noise) and update the runner to always emit LAVA_SIGNAL_ENDRUN even when subtests fail.
4. Detail analysis attachment: failed_case_job81085_3_detailed.md

Job 81083 | SoC monaco-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81083

Failed test cases in LAVA job 81083 (SoC: monaco-evk).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: On monaco-evk, the testcase flags expected platform-specific boot messages as failures: missing WCN6855 BT firmware blobs (qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv) and a tpm_tis_spi timeout on spi0.0, even though boot continues and no deferred probes remain.
3. Possible fix: Make Probe_Failure_Check SoC-aware for monaco-evk by whitelisting these known benign signatures (or gating them on actual feature enablement), and in parallel align monaco firmware/DT packaging so BT firmware files and TPM node status match board reality.
4. Detail analysis attachment: failed_case_job81083_1_detailed.md

  Case 2: USBHost

1. Failed case: USBHost
2. Root cause: On Monaco-EVK, the USBHost check failed because no host-side USB enumeration happened (unable to initialize usb spec / No USB devices found), which points to a board-specific USB host path dependency (role/VBUS/hub/device presence) rather than a kernel crash.
3. Possible fix: On Monaco-EVK, validate and enforce the active host path (USB1 Type-C/GL3590 hub or USB2 OTG with correct ID/VBUS GPIO/regulator state) and make the USBHost test fail only after confirming controller-up + port-power + fixture device attached.
4. Detail analysis attachment: failed_case_job81083_2_detailed.md

  Case 3: WiFi_OnOff

1. Failed case: WiFi_OnOff
2. Root cause: On monaco-evk, the WLAN path never becomes hardware-visible (no iw phy, no /sys/class/ieee80211, only BT rfkill) even though ath11k modules load, indicating board image/DT+firmware provisioning for the WCN6855 WiFi side is missing or not enabled rather than a LAVA worker control failure.
3. Possible fix: Update the monaco-evk LAVA boot image/device setup to include the correct ath11k firmware tree and Monaco DT wiring/power-enable for the WCN6855 WiFi PCIe path, then rerun WiFi_Firmware_Driver and WiFi_OnOff in the same job flow.
4. Detail analysis attachment: failed_case_job81083_3_detailed.md

  Case 4: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: On monaco-evk, the test definition starts the LAVA run (LAVA_SIGNAL_STARTRUN) but never closes it with LAVA_SIGNAL_ENDRUN, so lava-dispatcher marks the run as unfinished/failed despite the board and TAC debugboard power path staying healthy.
3. Possible fix: Update qcom-next-ci-premerge-tests runner to always emit LAVA_SIGNAL_ENDRUN (via trap on normal/error exits) and keep monaco-evk peripheral-dependent checks (USB/WiFi) reported as testcase failures/skips without breaking run-finalization signaling.
4. Detail analysis attachment: failed_case_job81083_4_detailed.md

Job 81084 | SoC qcs615-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81084

Failed test cases in LAVA job 81084 (SoC: qcs615-ride).

  Case 1: login-action

1. Failed case: login-action
2. Root cause: On qcs615-ride, the console/boot-control path is being interfered by unexpected getvar:product command injection on the serial/bootloader path (while LAVA waits for shell), triggering bootloader watchdog resets and preventing the kernel from reaching a stable login prompt.
3. Possible fix: Enforce exclusive board/serial ownership for this qcs615-ride worker (TAC debugboard + ser2net port + fastboot device ID) and remove external/parallel fastboot probing so only the active LAVA job controls boot and console.
4. Detail analysis attachment: failed_case_job81084_1_detailed.md

  Case 2: auto-login-action

1. Failed case: auto-login-action
2. Root cause: On qcs615-ride, the fastboot boot chain entered an unstable firmware/serial state (repeated Unhandled command: getvar:product and a watchdog reset) after boot-fastboot, so LAVA never saw the expected shell prompt and login-action timed out.
3. Possible fix: In the qcs615-ride LAVA device flow, add a post-fastboot console recovery step (hard reconnect/reset of serial + clean reboot to normal Linux path before auto-login-action) and block concurrent/garbled fastboot traffic on the worker.
4. Detail analysis attachment: failed_case_job81084_2_detailed.md

  Case 3: fastboot-boot

1. Failed case: fastboot-boot
2. Root cause: On qcs615-ride, the fastboot-loaded image enters Linux but never reaches a shell prompt and then the Qualcomm UEFI/XBL watchdog resets the board, so LAVA auto-login-action times out and fastboot-boot fails.
3. Possible fix: Reproduce on the worker and fix the QCS615 boot path so the fastboot booted kernel+initramfs reliably reaches root@...# before watchdog expiry (or temporarily disable/extend the firmware watchdog while debugging), then rerun this LAVA case.
4. Detail analysis attachment: failed_case_job81084_3_detailed.md

  Case 4: job

1. Failed case: job
2. Root cause: On qcs615-ride, the fastboot/UEFI stage received malformed getvar:product traffic (????...) and triggered a watchdog reset, so LAVA never reached the expected root@...# prompt and login-action timed out.
3. Possible fix: Stabilize the qcs615-ride worker fastboot path (single clean fastboot session, USB transport reset/rebind, and hard power-cycle via TAC debugboard before boot) and then rerun with sufficient boot block time for retries.
4. Detail analysis attachment: failed_case_job81084_4_detailed.md

Job 81086 | SoC qcs6490

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81086

Failed test cases in LAVA job 81086 (SoC: qcs6490).

  Case 1: USBHost

1. Failed case: USBHost
2. Root cause: On the qcs6490 RB3gen2 LAVA setup, the USBHost test ran with no downstream USB device presented to the SoC host port (or usbmux path), so enumeration returned none and the testcase failed.
3. Possible fix: In the qcs6490 lab flow, explicitly force the board’s USB-C path to host mode and attach a known USB mass-storage/HID device through the debugboard/mux before running Baseport/USBHost/run.sh.
4. Detail analysis attachment: failed_case_job81086_1_detailed.md

  Case 2: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: On the qcs6490-rb3gen2 LAVA setup, the USBHost subtest failed because no USB peripheral was enumerated (No USB devices found), and the run then exited without an ENDRUN signal so LAVA finalized it as an unfinished failed run.
3. Possible fix: Ensure a known-good USB device/loopback fixture is physically attached and visible to the qcs6490 host port before USBHost runs, and update the qcom-next-ci-premerge runner to always emit LAVA_SIGNAL_ENDRUN even when a testcase fails.
4. Detail analysis attachment: failed_case_job81086_2_detailed.md

Job 81080 | SoC qcs8300-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81080

Failed test cases in LAVA job 81080 (SoC: qcs8300-ride).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: On qcs8300-ride, the external Aquantia AQR115C PHY on the stmmac MDIO path fails probe with -22 (starting from failed to read firmware-name), and this single Ethernet probe failure is treated as a testcase failure.
3. Possible fix: Make the qcs8300-ride Ethernet PHY path probe-clean by adding/correcting the AQR115C DT firmware property (or making it optional in driver for this board) and temporarily exclude this known board-specific probe miss from Probe_Failure_Check gating.
4. Detail analysis attachment: failed_case_job81080_1_detailed.md

  Case 2: 0_qcom-next-ci-pr[

1. Failed case: 0_qcom-next-ci-pr[
2. Root cause: On qcs8300-ride, kernel console noise on the shared ttyMSM0 test channel corrupted the LAVA_SIGNAL_STARTRUN payload (name/UUID got split by a printk line), so LAVA never saw a valid run closure and marked the run unfinished.
3. Possible fix: In the qcs8300-ride premerge runner, quiesce kernel console logging before STARTRUN/ENDRUN emission (for example reduce printk level) and harden signal framing so run-control signals are emitted atomically and parsed cleanly.
4. Detail analysis attachment: failed_case_job81080_2_detailed.md

Job 81078 | SoC qcs9100-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81078

Failed test cases in LAVA job 81078 (SoC: qcs9100-ride).

  Case 1: shmbridge

1. Failed case: shmbridge
2. Root cause: On qcs9100-ride, the Iris codec (aa00000.video-codec) repeatedly fails the SCM secure video memory protect call (qcom_scm_mem_protect_video_var returns -5/-EIO) during boot, and the shmbridge testcase fails because it flags these qcom_scm errors from the current boot log.
3. Possible fix: For qcs9100-ride, fix the Iris secure-memory setup (DT/firmware SCM CP-region + PAS/IOMMU video-firmware path) or temporarily disable Iris probe on this board, and update shmbridge to fail only on actual shm-bridge API failures instead of unrelated SCM client errors.
4. Detail analysis attachment: failed_case_job81078_1_detailed.md

  Case 2: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: On qcs9100-ride, the shmbridge subtest fails after detecting repeated qcom_scm_mem_protect_video_var failed: -5 errors (secure-call path), and the runner then leaves the test run open (no LAVA_SIGNAL_ENDRUN), so LAVA marks the case failed as unfinished.
3. Possible fix: Use a qcs9100-validated DT/firmware bundle for this LAVA job’s secure-media path and update the test wrapper to always emit LAVA_SIGNAL_ENDRUN even when any subtest (like shmbridge) fails.
4. Detail analysis attachment: failed_case_job81078_2_detailed.md

Job 81081 | SoC sm8750-mtp

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81081

Failed test cases in LAVA job 81081 (SoC: sm8750-mtp).

  Case 1: auto-login-action

1. Failed case: auto-login-action
2. Root cause: On sm8750-mtp (Pakala), XBL/AVB reports dtbo_a hash mismatch against vbmeta so boot never reaches kernel banner/login, causing LAVA auto-login-action timeout rather than a TAC/PDU worker failure.
3. Possible fix: Reflash dtbo_a and matching vbmeta_a (or full slot _a) from the same build used for boot.img on this sm8750-mtp device, then rerun the LAVA job.
4. Detail analysis attachment: failed_case_job81081_1_detailed.md

  Case 2: fastboot-boot

1. Failed case: fastboot-boot
2. Root cause: On sm8750-mtp (Pakala), the DUT boot chain reports dtbo_a AVB hash mismatch against vbmeta during fastboot boot, so Linux never starts and the case fails on auto-login-action timeout rather than TAC/PDU control.
3. Possible fix: Reflash a consistent sm8750-mtp slot image set (dtbo_a + vbmeta_a and aligned boot artifacts from the same build) before running fastboot-boot, then rerun the job.
4. Detail analysis attachment: failed_case_job81081_2_detailed.md

  Case 3: job

1. Failed case: job
2. Root cause: On sm8750-mtp, fastboot boot completes but the device never reaches Linux handoff (repeated SBL1/UEFI boot-chain logs and DTB header can get corrupted due to runtime kernel size), so auto-login-action times out and LAVA fails the job when retry budget cannot fit.
3. Possible fix: Rebuild the sm8750-mtp boot artifact so ABL can cleanly hand off to kernel (validate SM8750 DTB/DTBO packaging and boot image size/load layout), and only as a short-term workaround increase the fastboot-boot block timeout.
4. Detail analysis attachment: failed_case_job81081_3_detailed.md

Job 81087 | SoC x1e80100

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/81087

No failed cases detected from the LAVA results section.