QCLINUX : Test change

[sgaud-quic]

No description provided.

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[sgaud-quic]

PR #589 — validate-patch

PR: #589

Verdict	Issues	Detailed Report
⚠️	3	Full report

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: QCLINUX: Test change — PR #589
Upstream commit: N/A
Verdict: ⚠️ N/A — Validation not applicable

Commit Message

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: prefix — no upstream lore equivalent
Body preserves rationale	N/A	Vendor-only commit
Fixes tag present/correct	N/A	Not required for QCLINUX:
Authorship preserved	N/A	Vendor-only commit
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts	N/A	gpi_dma0 status changed okay → disabled; no upstream lore to compare against

Issues

• No lore.kernel.org link present in the commit message — this is expected for QCLINUX: commits, which are vendor-only changes with no upstream equivalent.
• The commit subject uses QCLINUX : Test change (note the space before the colon). Convention is QCLINUX: with no space before the colon.
• The commit body contains only a Signed-off-by: trailer with no rationale or description explaining why gpi_dma0 is being disabled. Even for vendor-only commits, a brief rationale is strongly recommended.

Verdict

Validation skipped — QCLINUX: commits are vendor-only with no upstream lore source; however, the commit should be amended to (1) remove the space before the colon in the prefix (QCLINUX: not QCLINUX :), and (2) add a brief rationale in the commit body explaining why gpi_dma0 is being disabled.

[sgaud-quic]

PR #589 — checker-log-analyzer

PR: #589
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/25954226335

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	MISSING_COMMIT_DESCRIPTION warning on single commit
dt-binding-check	⏭️	No changes in Documentation/devicetree/bindings
dtb-check	✅	Log Summary: Test passed
sparse-check	⏭️	Skipping — no C/H files changed
check-uapi-headers	⏭️	Skipping — no C/H files changed
check-patch-compliance	❌	QCLINUX : prefix not in allowed list
tag-check	❌	QCLINUX : has a trailing space before : — malformed prefix
qcom-next-check	N/A	QCLINUX: commits are vendor-only; no upstream check required

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: QCLINUX : Test change — #589
Run: https://github.com/qualcomm-linux/kernel-config/actions/runs/25954226335
Target branch: qcom-6.18.y (not qcom-next / qcom-next-staging → tag-check is mandatory)
Commit: c41aab9b4df97b9fff67832cb39c4b921559aa1b
Base SHA: 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04

---

Checker	Result	Summary
checkpatch	❌	MISSING_COMMIT_DESCRIPTION warning on single commit
dt-binding-check	⏭️	No changes in Documentation/devicetree/bindings
dtb-check	✅	Log Summary: Test passed
sparse-check	⏭️	Skipping — no C/H files changed
check-uapi-headers	⏭️	Skipping — no C/H files changed
check-patch-compliance	❌	QCLINUX : prefix not in allowed list
tag-check	❌	QCLINUX : has a trailing space before : — malformed prefix
qcom-next-check	N/A	QCLINUX: commits are vendor-only; no upstream check required

---

❌ checkpatch

Root cause: The single commit c41aab9b4df9 ("QCLINUX : Test change") has no commit description body — only a subject line and Signed-off-by:, triggering WARNING: Missing commit description.

Failure details:

WARNING: Missing commit description - Add an appropriate one

c41aab9b4df97b9fff67832cb39c4b921559aa1b total: 0 errors, 1 warnings, 0 checks, 8 lines checked

Commit c41aab9b4df9 ("QCLINUX : Test change") has style problems, please review.

Fix:

git rebase -i 6964936c9bfc   # mark commit as 'edit'
git commit --amend
# Add a description body explaining what the change does and why, e.g.:
#
#   QCLINUX: arm64: dts: qcom: qcs6490-rb3gen2: disable gpi_dma0
#
#   Disable gpi_dma0 on qcs6490-rb3gen2 because <reason>.
#
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES \
  --git 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04..c41aab9b4df97b9fff67832cb39c4b921559aa1b

---

❌ check-patch-compliance

Root cause: The commit subject QCLINUX : Test change uses QCLINUX : (with a space before the colon), which is not a valid prefix. Even the correctly-spelled QCLINUX: is not in the allowed list for check-patch-compliance (which only accepts FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). This is a known checker limitation for vendor-only commits.

Failure details:

Checking commit: QCLINUX : Test change
Commit summary does not start with a required prefix
##[error]Process completed with exit code 1.

Fix:

• If this is a vendor-only change with no upstream equivalent: The QCLINUX: prefix will always fail check-patch-compliance — this is a known limitation. Ensure the prefix is correctly formatted as QCLINUX: (no space before :). The checker failure for QCLINUX: commits is expected and cannot be resolved by a patch change alone.
• If this change has been or will be posted upstream: Change the prefix to FROMLIST: and add a Link: <lore-url> trailer to the commit body.
• In either case, fix the malformed prefix (remove the space before :):

git rebase -i 6964936c9bfc
# mark commit as 'edit'
git commit --amend -m "QCLINUX: arm64: dts: qcom: qcs6490-rb3gen2: disable gpi_dma0"
# (add a proper description body too — see checkpatch fix above)
git rebase --continue

Reproduce locally:

b4 am --single-message -C -l -3 <link>   # only applicable if FROMLIST: is used

---

❌ tag-check

Root cause: The target branch is qcom-6.18.y (not qcom-next / qcom-next-staging), so every commit subject must start with a valid prefix. The subject QCLINUX : Test change has a space before the colon (QCLINUX :) making it malformed — it does not match the required pattern ^(FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND):.

Failure details:

Commit c41aab9b4df9 ("QCLINUX : Test change"):
  subject line does not start with a required prefix.
  (Space before colon: "QCLINUX :" is not "QCLINUX:")

Fix: Rename the commit subject to use a correctly-formatted prefix with no space before ::

git rebase -i 6964936c9bfc
# mark commit as 'edit'
git commit --amend -m "QCLINUX: arm64: dts: qcom: qcs6490-rb3gen2: disable gpi_dma0

Disable gpi_dma0 on qcs6490-rb3gen2 because <reason>.

Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>"
git rebase --continue

---

Verdict

2 real blockers to fix before merge:

1. Malformed prefix — QCLINUX : (space before :) must be corrected to QCLINUX: in the commit subject.
2. Missing commit description — the commit body must include a description explaining the change (not just a subject + Signed-off-by:).

Note: Once the prefix is corrected to QCLINUX:, check-patch-compliance will still report a failure — this is a known checker limitation for vendor-only commits using QCLINUX: and does not require a patch change beyond fixing the malformed prefix. The dtb-check warnings visible in the log (from talos-evk-lvds-auo,g133han01.dtso and hamoa-camera.dtsi) are pre-existing tree-wide issues unrelated to this PR's single-line DTS change, and the checker itself reported Log Summary: Test passed after baseline subtraction.

[qcomlnxci]

Test jobs on c41aab9

• Job 99581 on lemans-evk
• Job 99585 on monaco-evk
• Job 99582 on qcs615-ride
• Job 99584 on qcs6490-rb3gen2
• Job 99588 on qcs8300-ride
• Job 99583 on qcs9100-ride-r3
• Job 99586 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	x1e80100-crd
BT_FW_KMD_Service	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_ON_OFF	◻️	✅ Pass	✅ 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	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️
Ethernet	◻️	✅ Pass	⚠️ skip	⚠️ skip	⚠️ 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	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
WiFi_Firmware_Driver	◻️	⚠️ skip	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
WiFi_OnOff	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
cdsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
gpdsp_remoteproc	◻️	✅ Pass	⚠️ skip	⚠️ skip	✅ Pass	❌ Fail	◻️
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	❌ Fail	◻️
rngtest	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
shmbridge	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
smmu	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[sgaud-quic]

LAVA Failed Case Triage Summary

PR: #589

Job 99581 | SoC unknown_soc_job99581

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

No failed cases detected from the LAVA results section.

Job 99582 | SoC unknown_soc_job99582

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

No failed cases detected from the LAVA results section.

Job 99583 | SoC unknown_soc_job99583

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

No failed cases detected from the LAVA results section.

Job 99584 | SoC unknown_soc_job99584

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

No failed cases detected from the LAVA results section.

Job 99585 | SoC unknown_soc_job99585

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

No failed cases detected from the LAVA results section.

Job 99586 | SoC unknown_soc_job99586

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

No failed cases detected from the LAVA results section.

Job 99588 | SoC unknown_soc_job99588

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

No failed cases detected from the LAVA results section.

[rahujosh]

LAVA Failed Case Triage Summary

PR: #589

Job 99581 | SoC lemans-evk

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

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

  Case 1: ** Kernel Crash — WARNING in cpuidle_idle_call causing boot stall / no login prompt

1. Failed case: ** Kernel Crash — WARNING in cpuidle_idle_call causing boot stall / no login prompt
2. Root cause: ** At kernel uptime T+3.76 s on the lemans-evk (QCS9075/SA9000P), CPU0 (swapper/0) fires WARNING: CPU: 0 PID: 0 at kernel/sched/idle.c:267 cpuidle_idle_call+0x160/0x208; LAVA detects the WARNING: pattern and switches to a restricted prompt set, and the board produces no further console output after T+5.2 s (last message: ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator), causing all three login-action attempts to time out at 200 s each.
3. Possible fix: Investigate and fix the cpuidle/idle-state configuration for the lemans-evk (QCS9075) platform — the WARNING at kernel/sched/idle.c:267 indicates an invalid or unsupported idle state is being entered; check the cpu-idle-states DT node and qcom-cpufreq-hw / cpuidle driver for lemans; as a short-term mitigation, add cpuidle.off=1 to the kernel command line to bypass the faulty idle path and confirm the board boots to login.
4. Detail analysis attachment: failed_case_job99581_1_detailed.md

  Case 2: ** Kernel Crash — WARNING in cpuidle_idle_call causing userspace boot stall / login prompt never reached

1. Failed case: ** Kernel Crash — WARNING in cpuidle_idle_call causing userspace boot stall / login prompt never reached
2. Root cause: ** At kernel timestamp ~3.76s on lemans-evk (SoC: IQ-9075 / LeMans), a WARNING fires in kernel/sched/idle.c:267 (cpuidle_idle_call+0x160/0x208) on CPU 0 (swapper/0, PID 0). After this warning and the console switch from qcom_geni0 (earlycon) to ttyMSM0 at ~4.29s, the board stops producing any serial output — systemd-udevd starts but no further userspace messages appear, and the login prompt is never presented across all 3 login-action retry attempts (each timing out at ~200s).
3. Possible fix: Investigate the cpuidle_idle_call WARNING on lemans-evk — check whether the PR patch (gpi_dma0 disabled in qcs6490-rb3gen2.dts) or a pre-existing kernel issue in the 6.18.25 tree causes a cpuidle/PSCI OSI-mode state machine fault that stalls userspace init; re-run the job on a known-good baseline kernel to determine if this is PR-introduced, and if so revert or fix the gpi_dma0 DT change.
4. Detail analysis attachment: failed_case_job99581_2_detailed.md

  Case 3: ** minimal-boot

1. Failed case: ** minimal-boot
2. Root cause: ** The kernel boots successfully on lemans-evk (IQ-9075) and reaches early userspace (systemd-udevd starts at T+4.4 s), but the system then hangs silently — no further console output is produced and no login prompt appears — causing all three auto-login-action attempts (each 200 s) to time out; a WARNING in cpuidle_idle_call at kernel/sched/idle.c:267 fires at T+3.77 s indicating a cpuidle/PSCI issue that likely causes CPU0 to enter a broken idle state from which it cannot service the serial console or userspace init, stalling the boot.
3. Possible fix: Bisect the regression on lemans-evk between the last known-good kernel and 6.18.25-gc41aab9b4df9; the WARNING: CPU: 0 PID: 0 at kernel/sched/idle.c:267 cpuidle_idle_call is the primary lead — investigate recent changes to kernel/sched/idle.c, drivers/cpuidle/, or Qualcomm PSCI/cpuidle DT bindings for lemans (SA8775P/IQ-9075) that may have broken the idle path; the PR patch itself (qcs6490-rb3gen2.dts gpi_dma0 disable) targets a different SoC (QCS6490/RB3Gen2) and is unrelated to this lemans-evk failure.
4. Detail analysis attachment: failed_case_job99581_3_detailed.md

  Case 4: ** Kernel boot hang — login prompt never reached (userspace stall after `gpi_dma0` disabled)

1. Failed case: ** Kernel boot hang — login prompt never reached (userspace stall after gpi_dma0 disabled)
2. Root cause: ** The PR patch disables gpi_dma0 (GPI DMA controller at 0x800000) in qcs6490-rb3gen2.dts; this causes a silent hang during udev-driven driver probing at ~5.2 s kernel uptime on lemans-evk, because a GENI QUP peripheral driver (I2C/SPI/UART under geniqup@8c0000) blocks indefinitely waiting for a DMA channel that is no longer available, preventing the login prompt from ever appearing.
3. Possible fix: Revert &gpi_dma0 { status = "disabled"; } from the PR, or co-disable all child devices of geniqup@8c0000 that depend on GPI DMA (or switch them to PIO mode) before disabling the DMA controller.
4. Detail analysis attachment: failed_case_job99581_4_detailed.md

Job 99582 | SoC qcs615-ride

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

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

  Case 1: ** Probe_Failure_Check

1. Failed case: ** Probe_Failure_Check
2. Root cause: ** Pre-existing missing regulatory.db firmware file on the qcs615-ride rootfs image; cfg80211 attempts to load it via faux_driver at boot ([8.067515]) and fails with -ENOENT (-2). The Probe_Failure_Check test script finds this single journal entry and reports FAIL. The PR patch (qcs6490-rb3gen2.dts: disable gpi_dma0) targets a different SoC/board entirely and has no effect on this failure.
3. Possible fix: Add regulatory.db (from wireless-regdb / linux-firmware) to the qcom-multimedia-image-qcs615-ride.rootfs build recipe so the file is present at /lib/firmware/regulatory.db on the deployed rootfs.
4. Detail analysis attachment: failed_case_job99582_1_detailed.md

  Case 2: ** SMMU — Missing IOMMU group attachment for video sub-devices

1. Failed case: ** SMMU — Missing IOMMU group attachment for video sub-devices
2. Root cause: ** The qcom-venus driver on qcs615-ride uses the non-legacy binding, which requires video-decoder and video-encoder child sub-devices to each have their own IOMMU group entry; these sub-devices are never added to any IOMMU group because the qcs615 DTS lacks iommus properties (or the sub-nodes themselves) for those children — this is a pre-existing DTS gap, not introduced by this PR.
3. Possible fix: Add iommus properties to the video-decoder and video-encoder child nodes of video-codec@aa00000 in arch/arm64/boot/dts/qcom/qcs615.dtsi (or qcs615-ride.dts) using the correct QCS615 SMMU stream IDs, then verify platform aa00000.video-codec:video-decoder/video-encoder: Adding to iommu group X appears in dmesg on the next boot.
4. Detail analysis attachment: failed_case_job99582_2_detailed.md

  Case 3: ** USBHost

1. Failed case: ** USBHost
2. Root cause: ** No functional USB device was enumerated on the qcs615-ride board's USB host port — only the root hub (1d6b:0002) was visible; the xHCI controller and kernel driver are healthy, but either no external USB device is physically connected to the port or USB VBUS power is not being supplied (UEFI reports UsbPwrCtrlLib_Init Initialize Hardware Configuration Error[Device Error] / PMI8998 not detected).
3. Possible fix: Verify that a functional USB device (e.g., USB storage or USB hub with downstream device) is physically connected to the qcs615-ride board's USB host port in the LAVA lab, and confirm that USB VBUS power is correctly supplied to the port (check PMIC/regulator wiring for the qcs615-ride lab unit).
4. Detail analysis attachment: failed_case_job99582_3_detailed.md

  Case 4: ** shmbridge

1. Failed case: ** shmbridge
2. Root cause: ** The shmbridge test script's kernel-log scan for "qcom_scm-related errors" matched the benign informational message qcom_scm firmware:scm: qseecom: untested machine, skipping (emitted at boot because qseecom is not supported on qcs615), producing a false-positive FAIL with no actual SCM functional failure present.
3. Possible fix: Suppress per Rule 1 of lava-known-benign-failures.md (shmbridge always suppressed as known CI noise); separately, fix the shmbridge run.sh grep pattern to exclude informational strings like untested machine, skipping and match only genuine error/failure keywords.
4. Detail analysis attachment: failed_case_job99582_4_detailed.md

  Case 5: ** `0_qcom-next-ci-premerge-tests`

1. Failed case: ** 0_qcom-next-ci-premerge-tests
2. Root cause: ** The LAVA test-shell run was marked failed by the dispatcher because 4 sub-tests reported RESULT=FAIL — Probe_Failure_Check (missing regulatory.db firmware in rootfs), smmu (Venus non-legacy binding leaves video-decoder/video-encoder sub-devices without individual IOMMU group entries), USBHost (no USB peripheral physically connected to the qcs615-ride host port), and shmbridge (test script false-positive on the benign qcom_scm: qseecom: untested machine, skipping log line); none of these failures are introduced by pr.patch, which only touches qcs6490-rb3gen2.dts.
3. Possible fix: Mark all 4 sub-test failures as pre-existing known issues on qcs615-ride and exclude them from PR-blocking criteria; separately: add regulatory.db to the rootfs image, fix the shmbridge test grep pattern to exclude the qseecom: untested machine message, update the smmu test to handle the non-legacy Venus binding, and ensure a USB peripheral is connected to the DUT's host port in the lab.
4. Detail analysis attachment: failed_case_job99582_5_detailed.md

Job 99583 | SoC qcs9100-ride

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

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

  Case 1: ** `cdsp_remoteproc` — Remoteproc Boot Failure (PAS/SCM authentication failure)

1. Failed case: ** cdsp_remoteproc — Remoteproc Boot Failure (PAS/SCM authentication failure)
2. Root cause: ** qcom_scm skips qseecom initialization for SA8775P (qseecom: untested machine, skipping at T=3.496s), causing qcom_scm_pas_init_image() to return -EINVAL (-22) for all DSP subsystems (cdsp0, cdsp1, gpdsp0, gpdsp1, adsp) on qcs9100-ride; both CDSP instances remain offline.
3. Possible fix: Add SA8775P (qcs9100) to the qseecom tested-machine allowlist in drivers/firmware/qcom/qcom_scm.c so that qcom_scm_pas_init_image() can authenticate DSP firmware images; this is a pre-existing kernel bring-up gap unrelated to PR QCLINUX : Test change #589.
4. Detail analysis attachment: failed_case_job99583_1_detailed.md

  Case 2: ** Remoteproc Firmware Authentication Failure — qseecom "untested machine" blocks PAS init

1. Failed case: ** Remoteproc Firmware Authentication Failure — qseecom "untested machine" blocks PAS init
2. Root cause: ** qcom_scm on SA8775P (qcs9100) detected qseecom version 0x1402000 but printed untested machine, skipping, disabling the qseecom/PIL authentication path; consequently qcom_q6v5_pas returns -EINVAL (-22) from qcom_scm_pas_init_image() for every PAS-authenticated subsystem (adsp, cdsp0, cdsp1, gpdsp0, gpdsp1), leaving all five remoteprocs state=offline.
3. Possible fix: Add SA8775P to the qseecom tested-machine allowlist in drivers/firmware/qcom/qcom_scm.c (qcom_scm_qseecom_init()), or enable the non-qseecom PAS authentication path for this SoC, so that qcom_scm_pas_init_image() can authenticate firmware and all remoteprocs reach is now up. This is a pre-existing kernel issue — PR QCLINUX : Test change #589 only modifies arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts and is unrelated to qcs9100/SA8775P.
4. Detail analysis attachment: failed_case_job99583_2_detailed.md

  Case 3: ** `gpdsp_remoteproc` — Remoteproc Boot Failure (PAS/SCM `-EINVAL`)

1. Failed case: ** gpdsp_remoteproc — Remoteproc Boot Failure (PAS/SCM -EINVAL)
2. Root cause: ** qcom_scm logs qseecom: untested machine, skipping at boot on qcs9100/SA8775P, causing qcom_scm_pas_init_image() to return -EINVAL (-22) for all qcom_q6v5_pas subsystems; both gpdsp0 (20c00000.remoteproc) and gpdsp1 (21c00000.remoteproc) fail to initialise and remain offline.
3. Possible fix: Add qcs9100/sa8775p to the qcom_scm qseecom tested-machine list in drivers/firmware/qcom/qcom_scm.c (or ensure the non-qseecom PAS SCM path is correctly wired for this SoC), so qcom_scm_pas_init_image() succeeds and all qcom_q6v5_pas remoteprocs can boot.
4. Detail analysis attachment: failed_case_job99583_3_detailed.md

  Case 4: ** remoteproc — Remoteproc Bring-up Failure (PAS/SCM firmware init, all 5 subsystems offline)

1. Failed case: ** remoteproc — Remoteproc Bring-up Failure (PAS/SCM firmware init, all 5 subsystems offline)
2. Root cause: ** qcom_scm classifies the qcs9100 (sa8775p) machine as "untested" and skips qcom_scm_qseecom_init(), causing every qcom_q6v5_pas_init_image() call to return -EINVAL (-22) — all 5 remoteproc subsystems (gpdsp0, gpdsp1, cdsp0, cdsp1, adsp) remain offline and the test finds 0 of 5 expected subsystems running.
3. Possible fix: Add qcom,sa8775p to the qseecom machine allowlist in drivers/firmware/qcom/qcom_scm.c so qcom_scm_qseecom_init() proceeds on this SoC, enabling PAS firmware authentication for all DSP subsystems.
4. Detail analysis attachment: failed_case_job99583_4_detailed.md

  Case 5: ** `Probe_Failure_Check` — Driver Probe / Firmware Load Failure (cots-driver-module-issues)

1. Failed case: ** Probe_Failure_Check — Driver Probe / Firmware Load Failure (cots-driver-module-issues)
2. Root cause: ** Two pre-existing, PR-unrelated errors in dmesg triggered the test scanner: (1) regulatory.db absent from rootfs causing faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2 (-ENOENT), and (2) Aquantia AQR115C PHY at stmmac-0:08 failing probe with failed to read firmware-name: -22 (-EINVAL) due to a missing/malformed firmware-name DT property in the qcs9100-ride DTS — neither is caused by PR QCLINUX : Test change #589 which only modifies qcs6490-rb3gen2.dts.
3. Possible fix: (1) Add wireless-regdb/linux-firmware to the qcs9100-ride rootfs image so regulatory.db is present at /lib/firmware/; (2) Fix the qcs9100-ride DTS to add a valid firmware-name property for the AQR115C PHY node at MDIO address 0x08, or patch the Aquantia PHY driver to treat a missing firmware-name property as non-fatal rather than propagating -EINVAL to probe.
4. Detail analysis attachment: failed_case_job99583_5_detailed.md

  Case 6: ** smmu — Missing IOMMU group attachment for critical DMA masters (Video + Audio)

1. Failed case: ** smmu — Missing IOMMU group attachment for critical DMA masters (Video + Audio)
2. Root cause: ** Two critical DMA masters on qcs9100-ride are not attached to any IOMMU group at test time: aa00000.video-codec (qcom-iris) fails core_init with -EINVAL due to VPU firmware load failure (vpu30_p4_s6_16mb.mbn), preventing IOMMU domain setup; interconnect-lpass-ag-noc (LPASS audio NoC) similarly has no IOMMU group attachment — both are pre-existing issues on this SoC unrelated to the PR.
3. Possible fix: This failure is pre-existing on qcs9100-ride and is not introduced by PR QCLINUX : Test change #589 (the patch only modifies qcs6490-rb3gen2.dts, a different SoC/board); fix the qcs9100-ride VPU firmware path/GPI DMA dependency for aa00000.video-codec and ensure the LPASS interconnect node completes IOMMU domain attachment, then update the smmu test's expected-masters list if these devices are intentionally not IOMMU-protected on this platform.
4. Detail analysis attachment: failed_case_job99583_6_detailed.md

  Case 7: ** USBHost

1. Failed case: ** USBHost
2. Root cause: ** No functional USB device is physically connected to the qcs9100-ride board's USB host port in the LAVA lab — the kernel USB host stack initialised correctly (3 xhci buses, all root hubs with 1 port each), but lsusb enumerated only root hubs and the test requires at least one non-hub device.
3. Possible fix: Connect a functional USB device (e.g. USB storage or HID device) to the USB host port of the qcs9100-ride board in the LAVA lab setup; this is a lab infrastructure gap, not a kernel regression.
4. Detail analysis attachment: failed_case_job99583_7_detailed.md

  Case 8: ** shmbridge

1. Failed case: ** shmbridge
2. Root cause: ** Test script false positive — the shmbridge run.sh grepped the kernel log for qcom_scm-related strings and matched the kernel cmdline line (qcom_scm.download_mode=1), not a real driver error; no actual qcom_scm error exists in the boot log. Per lava-known-benign-failures.md Rule 1, all shmbridge failures are always suppressed as known CI infrastructure noise.
3. Possible fix: No fix required — suppress this failure as known benign (Rule 1); if the test script is to be improved, narrow its grep pattern to exclude the kernel cmdline line (e.g., filter out lines matching Kernel command line: before scanning for qcom_scm errors).
4. Detail analysis attachment: failed_case_job99583_8_detailed.md

Job 99584 | SoC qcs6490-rb3gen2

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

Failed test cases in LAVA job 99584 (SoC: qcs6490-rb3gen2).

  Case 1: ** Probe_Failure_Check

1. Failed case: ** Probe_Failure_Check
2. Root cause: ** The rootfs image deployed to qcs6490-rb3gen2 does not include regulatory.db; at boot cfg80211 (via faux_driver regulatory) emits Direct firmware load for regulatory.db failed with error -2 (ENOENT), which the Probe_Failure_Check test script matches as a firmware-related probe error and fails the test — WiFi continues to work via compiled-in regulatory data, confirming this is non-fatal and pre-existing, not introduced by PR#589.
3. Possible fix: Add regulatory.db (package wireless-regdb) to the qcom-multimedia-image-rb3gen2-core-kit rootfs recipe, or add a suppression rule in Probe_Failure_Check / lava-known-benign-failures.md for the faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2 pattern (always suppress, since WiFi functional tests pass).
4. Detail analysis attachment: failed_case_job99584_1_detailed.md

  Case 2: ** USBHost

1. Failed case: ** USBHost
2. Root cause: ** PR QCLINUX : Test change #589 disables gpi_dma0 (GPI DMA controller for geniqup@9c0000) in qcs6490-rb3gen2.dts, which prevents i2c@984000 and its child typec-mux@1c from probing; without the Type-C mux as a USB role-switch supplier, pmic-glink connector@0 cannot switch the USB port to host mode, so the USB controller stays in gadget/peripheral mode and no USB host bus is started — lsusb returns empty output.
3. Possible fix: Revert &gpi_dma0 { status = "disabled"; } back to status = "okay" in arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts; this is a deliberate test-only DT breakage that must not be merged.
4. Detail analysis attachment: failed_case_job99584_2_detailed.md

  Case 3: ** shmbridge

1. Failed case: ** shmbridge
2. Root cause: ** The shmbridge test script's "scan kernel log for qcom_scm errors" step matched the benign informational message qcom_scm firmware:scm: qseecom: untested machine, skipping (emitted at T+3.199s during normal qcom_scm probe on qcs6490-rb3gen2) and incorrectly declared a failure; no actual qcom_scm error, shmbridge driver fault, or kernel crash is present.
3. Possible fix: Suppress per lava-known-benign-failures.md Rule 1 (shmbridge failures are always known CI noise); separately, update the shmbridge test script to exclude the untested machine, skipping informational string from its qcom_scm error-pattern scan so the false positive does not recur.
4. Detail analysis attachment: failed_case_job99584_3_detailed.md

  Case 4: ** `0_qcom-next-ci-premerge-tests` — Test Suite Failure (sub-tests: Probe_Failure_Check, USBHost, shmbridge)

1. Failed case: ** 0_qcom-next-ci-premerge-tests — Test Suite Failure (sub-tests: Probe_Failure_Check, USBHost, shmbridge)
2. Root cause: ** Three sub-tests failed within the test suite: (1) Probe_Failure_Check — the faux_driver regulatory firmware load error (Direct firmware load for regulatory.db failed with error -2) was flagged as a probe failure; (2) USBHost — no USB devices were enumerated (No USB devices found), likely caused by the PR patch disabling gpi_dma0 in qcs6490-rb3gen2.dts, which breaks the GPI DMA engine used by the USB Type-C/PMIC-GLINK subsystem on this SoC; (3) shmbridge — a false-positive failure caused by the test's qcom_scm-error grep matching the kernel command line string qcom_scm.download_mode=1 instead of an actual SCM error.
3. Possible fix: Revert the gpi_dma0 status = "disabled" change in qcs6490-rb3gen2.dts (the PR patch) — disabling gpi_dma0 breaks GPI DMA-dependent peripherals on QCS6490; fix the shmbridge test script to exclude the kernel cmdline from its qcom_scm error scan; and whitelist the regulatory.db firmware-load message in Probe_Failure_Check as a known-benign cfg80211 warning.
4. Detail analysis attachment: failed_case_job99584_4_detailed.md

Job 99585 | SoC monaco-evk

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

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

  Case 1: ** Probe_Failure_Check

1. Failed case: ** Probe_Failure_Check
2. Root cause: ** Probe_Failure_Check matched two BT firmware fallback messages (bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2 and qca/hpbtfw21.tlv failed with error -2) that are a known false positive on monaco-evk — the QCA WCN6855 driver tries these optional NVM patch filenames first, they are absent from the test initramfs, but BT initialises successfully via a fallback path as confirmed by BT_ON_OFF: PASS and BT_FW_KMD_Service: PASS.
3. Possible fix: Suppress this result per lava-known-benign-failures.md Rule 3 (BT firmware false positive — BT_ON_OFF passed); do not block PR QCLINUX : Test change #589. Long-term: update the Probe_Failure_Check script to cross-check BT_ON_OFF result before flagging BT firmware-load errors, or add the missing firmware files to the monaco-evk test initramfs.
4. Detail analysis attachment: failed_case_job99585_1_detailed.md

  Case 2: ** BT_SCAN

1. Failed case: ** BT_SCAN
2. Root cause: ** The WCN6855 BT controller on Monaco EVK is fully operational (hci0 UP RUNNING, BT_ON_OFF passed), but no Bluetooth devices were advertising/discoverable in the LAVA lab RF environment during the 3 × 15-second scan attempts — this is a lab environment condition, not a kernel regression.
3. Possible fix: Place a persistent BT advertising device (BT LE beacon or phone in discoverable mode) in the Monaco EVK LAVA lab cell, or re-trigger the job if a BT peer device is transiently available; alternatively configure BT_SCAN with a target MAC address to avoid relying on ambient discovery.
4. Detail analysis attachment: failed_case_job99585_2_detailed.md

  Case 3: ** WiFi_OnOff — Driver Probe Failure (missing GPI DMA dependency for WCN6855 UART transport)

1. Failed case: ** WiFi_OnOff — Driver Probe Failure (missing GPI DMA dependency for WCN6855 UART transport)
2. Root cause: ** The PR patch disables gpi_dma0 in qcs6490-rb3gen2.dts; on monaco-evk the WCN6855 WiFi+BT combo chip is connected via GENI UART serial@988000 under geniqup@9c0000, which depends on gpi_dma0 for DMA — with the DMA controller disabled the UART transport cannot initialise, so ath11k never registers a wlan interface despite the module loading successfully.
3. Possible fix: Revert gpi_dma0 to status = "okay" in the PR patch (or remove the gpi_dma0 disable from qcs6490-rb3gen2.dts) and re-run the LAVA job to confirm wlan0 appears and WiFi_OnOff passes.
4. Detail analysis attachment: failed_case_job99585_3_detailed.md

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

1. Failed case: ** 0_qcom-next-ci-premerge-tests
2. Root cause: ** Missing WCN6855 Bluetooth firmware files (qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv) in the initramfs firmware image deployed to the monaco-evk board; the firmware load failed at boot with error -2 (ENOENT), leaving the BT controller without a patch image and the WiFi interface (ath11k_pci over PCIe) unable to enumerate — causing Probe_Failure_Check, BT_SCAN, and WiFi_OnOff to fail and LAVA to mark the overall test case as failed.
3. Possible fix: Update the initramfs-firmware-qcs8300-ride-image-qcom-armv8a.cpio.gz (or the equivalent monaco-evk firmware initramfs) to include qca/wcnhpbtfw21.tlv and qca/hpbtfw21.tlv; verify the ath11k PCIe link comes up after firmware is present, then re-trigger the CI job. This is a pre-existing infra/firmware packaging issue unrelated to PR QCLINUX : Test change #589 (which only modifies qcs6490-rb3gen2.dts).
4. Detail analysis attachment: failed_case_job99585_4_detailed.md

Job 99586 | SoC x1e80100

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

Failed test cases in LAVA job 99586 (SoC: x1e80100).

  Case 1: ** Build Load Failure — Fastboot boot image rejected by ABL

1. Failed case: ** Build Load Failure — Fastboot boot image rejected by ABL
2. Root cause: ** Result: Build Load Failure — the x1e80100-CRD ABL (LinuxLoader.efi, BOOT.MXF.2.4-00541-HAMOA-1) rejected the fastboot boot command at the boot stage with Failed to load/authenticate boot image: Load Error because GetSystemPath() failed — the NVME storage is inaccessible (Get BlkIohandles failed) so the ABL cannot resolve the system partition required by its boot flow, causing it to abort loading the image.
3. Possible fix: This is a pre-existing infra/firmware issue unrelated to the PR patch; re-trigger the CI job — if the failure recurs consistently, escalate to the LAVA infra team to investigate NVME/storage accessibility on the x1e80100-CRD board (the ABL Get BlkIohandles failed indicates the storage controller is not enumerating correctly in the firmware environment).
4. Detail analysis attachment: failed_case_job99586_1_detailed.md

  Case 2: ** Build Load Failure — Fastboot boot image rejected by UEFI firmware (Load Error)

1. Failed case: ** Build Load Failure — Fastboot boot image rejected by UEFI firmware (Load Error)
2. Root cause: ** Result: Build Load Failure. The x1e80100 CRD board's UEFI fastboot handler (BOOT.MXF.2.4-00541-HAMOA-1) rejected the boot.img at the boot command stage with the exact error FAILED (remote: 'Failed to load/authenticate boot image: Load Error'). The firmware serial console reveals the precise failure chain: after accepting the 229 MB image transfer successfully, the UEFI boot handler reached GetSystemPath failed! because System partition does not exist — the x1e80100 UEFI fastboot boot command requires a valid system/AVB partition path to complete image authentication even with Secure Boot Off and AVB version 0. This is a pre-existing platform-level UEFI firmware limitation on this specific board/firmware version, not caused by the PR patch (which only modifies qcs6490-rb3gen2.dts, a completely different SoC's DTS file).
3. Possible fix: Re-trigger the CI job; if the failure recurs consistently on x1e80100-crd-01, escalate to the LAVA/platform team to investigate whether the x1e80100 UEFI firmware requires a system partition to be provisioned on the NVMe for fastboot boot to succeed, or whether the LAVA job definition needs to use fastboot flash boot + fastboot reboot instead of fastboot boot for this board.
4. Detail analysis attachment: failed_case_job99586_2_detailed.md

  Case 3: ** Build Load Failure — Fastboot boot rejection: `FAILED (remote: 'Failed to load/authenticate boot image: Load Error')`

1. Failed case: ** Build Load Failure — Fastboot boot rejection: FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
2. Root cause: ** Result: Build Load Failure. The x1e80100-CRD board's ABL calls GetSystemPath() during boot image authentication; the NVMe storage has no system partition flashed, causing GetSystemPath failed! and the ABL returning Load Error to fastboot boot — the kernel never executes.
3. Possible fix: Flash a valid system partition image to the x1e80100-CRD board's NVMe (e.g., fastboot flash system system.img) to restore the board to a bootable lab state; if the board is shared infra, escalate to LAVA admins to reflash the full partition table for device 1dafdb2e.
4. Detail analysis attachment: failed_case_job99586_3_detailed.md

Job 99588 | SoC qcs8300-ride

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

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

  Case 1: ** `Probe_Failure_Check` — Driver Probe Failure (cots-driver-module-issues: Possibility 2 + firmware dependency)

1. Failed case: ** Probe_Failure_Check — Driver Probe Failure (cots-driver-module-issues: Possibility 2 + firmware dependency)
2. Root cause: ** Two pre-existing probe errors in dmesg triggered the test: (1) regulatory.db absent from rootfs (-ENOENT), and (2) Aquantia AQR115C PHY driver on stmmac-0:08 failing with -EINVAL because the firmware-name DT property is missing from the qcs8300-ride DTS — neither failure is introduced by PR#589 (which only modifies qcs6490-rb3gen2.dts).
3. Possible fix: Add firmware-name = "aquantia/AQR115C.cld" to the AQR115C PHY DT node in the qcs8300-ride DTSI, and add wireless-regdb to the qcs8300-ride-sx rootfs image recipe to ship regulatory.db.
4. Detail analysis attachment: failed_case_job99588_1_detailed.md

  Case 2: ** USBHost

1. Failed case: ** USBHost
2. Root cause: ** No external USB device is physically connected to the qcs8300-ride-sx board's USB host port in the LAVA lab — the xHCI controller (a400000.usb) initialised correctly and the USB2 root hub with 1 port was detected, but lsusb returned only 1d6b:0002 Linux Foundation 2.0 root hub with no functional peripheral enumerated.
3. Possible fix: Connect a USB peripheral device (e.g., USB flash drive or USB-to-serial adapter) to the qcs8300-ride-sx board's USB host port in the LAVA lab rack, then re-run the job; alternatively add a SKIP path to the USBHost test script when only root hubs are detected and no device is expected.
4. Detail analysis attachment: failed_case_job99588_2_detailed.md

  Case 3: ** shmbridge

1. Failed case: ** shmbridge
2. Root cause: ** Test script false-positive — the shmbridge test's "scan for qcom_scm errors" step matched the benign kernel command line string qcom_scm.download_mode=1 (a boot parameter, not a driver error), causing it to declare failure despite CONFIG_QCOM_SCM being enabled and the qcom_scm driver probing successfully on qcs8300-ride.
3. Possible fix: Suppress per lava-known-benign-failures.md Rule 1 (shmbridge is always-suppress CI noise); additionally, fix the test script's grep pattern to exclude the Kernel command line: log line so it only matches actual driver error messages (e.g., filter out lines containing command line or require the match to be outside the cmdline banner).
4. Detail analysis attachment: failed_case_job99588_3_detailed.md

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

1. Failed case: ** 0_qcom-next-ci-premerge-tests
2. Root cause: ** Three pre-existing sub-test failures on qcs8300-ride-sx caused the parent test suite to be marked failed: (1) Probe_Failure_Check triggered by a known regulatory.db firmware-not-found error and an Aquantia AQR115C PHY probe failure (-EINVAL on firmware-name DT property read); (2) USBHost failed because no functional USB peripheral devices are physically connected to the board's host port; (3) shmbridge false-positived by matching the benign boot parameter string qcom_scm.download_mode=1 in the kernel cmdline as a "qcom_scm error".
3. Possible fix: These are pre-existing infra/test-definition issues unrelated to the PR; re-trigger the job to confirm reproducibility, then: (a) exclude regulatory.db and AQR115C from Probe_Failure_Check's denylist or fix the qcs8300 DT firmware-name property for the AQR115C PHY node; (b) connect a functional USB device to the qcs8300-ride-sx board's host port or mark USBHost as expected-skip for this board; (c) fix the shmbridge test script to exclude kernel cmdline matches and scan only for actual qcom_scm error/warning log lines.
4. Detail analysis attachment: failed_case_job99588_4_detailed.md

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[sgaud-quic]

PR #589 — validate-patch

PR: #589

Verdict	Issues	Detailed Report
⚠️	2	Full report

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: PR #589 — "QCLINUX : Test change"
Upstream commit: N/A
Verdict: ⚠️ N/A — Validation not applicable

Commit Message

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: prefix — no upstream equivalent
Body preserves rationale	N/A	Vendor-only commit
Fixes tag present/correct	N/A	Not required for QCLINUX:
Authorship preserved	N/A	Submitter is the author; no upstream to compare against
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts	N/A	Single-line change: gpi_dma0 status "okay" → "disabled"; no upstream lore to compare against

Issues

• None from a patch-integrity standpoint. The commit carries the QCLINUX: prefix, which by convention indicates a vendor-only change with no upstream lore link — this is expected and correct per the tree's prefix policy.
• Minor style note: the subject line has an extra space before the colon (QCLINUX : Test change); the conventional form is QCLINUX: Test change (no space before :).

Verdict

Validation is not applicable — QCLINUX: commits are vendor-only by design and have no lore.kernel.org upstream to validate against. The patch may be merged on its own merits; no lore-link or upstream-alignment review is required or possible for this commit type.

[sgaud-quic]

PR #589 — checker-log-analyzer

PR: #589
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/25991485284

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	WARNING: Missing commit description — commit has no body text
dt-binding-check	⏭️	No changes in Documentation/devicetree/bindings
dtb-check	✅	Log Summary: Test passed — no new DTB errors introduced
sparse-check	⏭️	Skipping sparse check as nothing changed — no C/H files modified
check-uapi-headers	⏭️	Skipping uapi check as nothing changed — no C/H files modified
check-patch-compliance	❌	Commit summary does not start with a required prefix — subject is QCLINUX : Test change (space before colon)
tag-check	❌	Subject QCLINUX : Test change does not match QCLINUX: (space before colon breaks the prefix)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: QCLINUX : Test change — #589
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/25991485284
Target branch: qcom-6.18.y (base SHA: 6964936c9bfc, head SHA: f0cfb764d4ad)

Checker	Result	Summary
checkpatch	❌	WARNING: Missing commit description — commit has no body text
dt-binding-check	⏭️	No changes in Documentation/devicetree/bindings
dtb-check	✅	Log Summary: Test passed — no new DTB errors introduced
sparse-check	⏭️	Skipping sparse check as nothing changed — no C/H files modified
check-uapi-headers	⏭️	Skipping uapi check as nothing changed — no C/H files modified
check-patch-compliance	❌	Commit summary does not start with a required prefix — subject is QCLINUX : Test change (space before colon)
tag-check	❌	Subject QCLINUX : Test change does not match QCLINUX: (space before colon breaks the prefix)

---

❌ checkpatch

Root cause: The single commit has no commit description body — only a subject line and Signed-off-by, triggering WARNING: Missing commit description.

Failure details:

WARNING: Missing commit description - Add an appropriate one

f0cfb764d4ad795e075a85c98886dbfdca7bbdde total: 0 errors, 1 warnings, 0 checks, 8 lines checked

Commit f0cfb764d4ad ("QCLINUX : Test change") has style problems, please review.

Fix: Add a meaningful description paragraph to the commit message body explaining what the change does and why:

git rebase -i 6964936c9bfc   # mark commit as 'edit'
git commit --amend
# Add a body paragraph, e.g.:
#   Disable gpi_dma0 on qcs6490-rb3gen2 because <reason>.
git rebase --continue

Reproduce locally:
./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04..f0cfb764d4ad795e075a85c98886dbfdca7bbdde

---

❌ check-patch-compliance

Root cause: The commit subject QCLINUX : Test change has a space before the colon (QCLINUX : instead of QCLINUX:), so it does not match any required prefix pattern.

Failure details:

Checking commit: QCLINUX : Test change
Commit summary does not start with a required prefix

Fix: Rename the subject to use the correct QCLINUX: prefix (no space before colon). Since this is a vendor-only DTS change with no upstream equivalent, QCLINUX: is the right prefix — just fix the formatting:

git rebase -i 6964936c9bfc   # mark commit as 'edit'
git commit --amend -m "QCLINUX: qcs6490-rb3gen2: disable gpi_dma0

<Add a meaningful description here>

Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>"
git rebase --continue

Reproduce locally:
bash kernel-checkers/check-patch-compliance.sh --kernel-src <kernel_src> --base 6964936c9bfc --head f0cfb764d4ad

---

❌ tag-check

Root cause: Target branch is qcom-6.18.y (not qcom-next/qcom-next-staging), so every commit subject must start with a valid prefix. The subject QCLINUX : Test change has a space before the colon and fails the ^QCLINUX: pattern match.

Failure details:

Commit f0cfb764d4ad ("QCLINUX : Test change"):
  subject does not match ^(FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND):
  Found: "QCLINUX :" — space before colon is not a valid prefix delimiter

Fix: Same as check-patch-compliance fix above — change QCLINUX : → QCLINUX: in the subject line.

---

Verdict

2 real blockers to fix before merge — both stem from the same root cause (malformed QCLINUX : prefix with a space before the colon) plus a missing commit description body. Fix the commit subject to QCLINUX: and add a description paragraph; all checkers will then pass.

[sgaud-quic]

PR #589 — validate-patch

PR: #589

Verdict	Issues	Detailed Report
N/A	1	Full report

Verdict: N/A — click to expand

🔍 Patch Validation

PR: PR #589 — "QCLINUX : Test change"
Upstream commit: N/A
Verdict: ⏭️ NOT APPLICABLE — QCLINUX: prefix; no upstream lore link by design

Commit Message

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: — vendor-only, no upstream counterpart
Body preserves rationale	N/A	Vendor-only commit
Fixes tag present/correct	N/A	Not required for QCLINUX:
Authorship preserved	N/A	Vendor-only commit
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts	⏭️ N/A	Single hunk: gpi_dma0 status "okay" → "disabled"; no upstream patch to compare against

Issues

• None from a commit-message / diff-faithfulness perspective. The QCLINUX: prefix explicitly signals a vendor-only change with no upstream lore link — this is correct and expected per the tree's prefix conventions.

Verdict

Validation not applicable — QCLINUX: commits are vendor-only by definition and carry no lore.kernel.org link. No merge-blocking issues found within the scope of this skill; the single-line DTS change (gpi_dma0 status "okay" → "disabled") should be reviewed on its own technical merits by the DTS maintainer.

[sgaud-quic]

PR #589 — checker-log-analyzer

PR: #589
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/26012555745

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	WARNING: Missing commit description
dt-binding-check	⏭️	No changes in Documentation/devicetree/bindings
dtb-check	✅	Log Summary: Test passed
sparse-check	⏭️	Skipping sparse check as nothing changed
check-uapi-headers	⏭️	Skipping uapi check as nothing changed
check-patch-compliance	❌	Commit summary does not start with a required prefix
tag-check	❌	Subject QCLINUX : Test change has a space before : — does not match QCLINUX:

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #589 — QCLINUX : Test change
Run: https://github.com/qualcomm-linux/kernel-config/actions/runs/26012555745
Target branch: qcom-6.18.y (subject-prefix check is mandatory)
Commit: b935b27c0717ca14b588f5c34668ba1f172df8f1 — 1 file changed: arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts

Checker	Result	Summary
checkpatch	❌	WARNING: Missing commit description
dt-binding-check	⏭️	No changes in Documentation/devicetree/bindings
dtb-check	✅	Log Summary: Test passed
sparse-check	⏭️	Skipping sparse check as nothing changed
check-uapi-headers	⏭️	Skipping uapi check as nothing changed
check-patch-compliance	❌	Commit summary does not start with a required prefix
tag-check	❌	Subject QCLINUX : Test change has a space before : — does not match QCLINUX:

---

❌ checkpatch

Root cause: The commit has no body/description in the commit message — checkpatch reports WARNING: Missing commit description.

Failure details:

WARNING: Missing commit description - Add an appropriate one

b935b27c0717ca14b588f5c34668ba1f172df8f1 total: 0 errors, 1 warnings, 0 checks, 8 lines checked

Commit b935b27c0717 ("QCLINUX : Test change") has style problems, please review.

Fix:

git rebase -i 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04
# mark the commit as 'edit'
git commit --amend
# Add a meaningful body to the commit message, e.g.:
#
#   QCLINUX: Test change
#
#   Disable gpi_dma0 on qcs6490-rb3gen2 to <reason>.
#
#   Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04..b935b27c0717ca14b588f5c34668ba1f172df8f1

---

❌ check-patch-compliance

Root cause: The commit subject QCLINUX : Test change has a space before the colon (QCLINUX : instead of QCLINUX:), so it does not match any required prefix pattern.

Failure details:

Checking commit: QCLINUX : Test change
Commit summary does not start with a required prefix

Fix: Rename the commit subject to use the correct QCLINUX: prefix (no space before :):

git rebase -i 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04
# mark the commit as 'edit'
git commit --amend -m "QCLINUX: Test change

<add a meaningful description here>

Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>"
git rebase --continue

Note: QCLINUX: commits always fail check-patch-compliance if the checker also validates that a Link: tag points to a lore upstream. If this is a purely vendor-only change with no upstream equivalent, the QCLINUX: prefix is correct and the compliance failure is a known checker limitation — no further action needed beyond fixing the space.

---

❌ tag-check

Root cause: Target branch is qcom-6.18.y (not qcom-next/qcom-next-staging), so every commit subject must start with a valid prefix. The subject QCLINUX : Test change has a space before : and does not match ^QCLINUX:.

Fix: Same as check-patch-compliance fix above — amend the subject to QCLINUX: Test change (remove the space before :).

---

Verdict

2 real blockers to fix before merge:

1. Fix the commit subject — change QCLINUX : Test change → QCLINUX: Test change (remove the space before :). This resolves both the check-patch-compliance and tag-check failures simultaneously.
2. Add a commit description body — the commit message has no body; add at least one sentence explaining what the change does and why. This resolves the checkpatch Missing commit description warning.

Both issues are in the same commit (b935b27c0717) and can be fixed in a single git commit --amend.

[qcomlnxci]

Test jobs on b935b27

• Job 100428 on lemans-evk
• Job 100426 on monaco-evk
• Job 100427 on qcs615-ride
• Job 100431 on qcs6490-rb3gen2
• Job 100424 on qcs8300-ride
• Job 100429 on qcs9100-ride-r3
• Job 100425 on x1e80100-crd

[qcomlnxci]

Test Matrix

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

[sgaud-quic]

LAVA Failed Case Triage Summary

PR: #589

Job 100424 | SoC unknown_soc_job100424

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

No failed cases detected from the LAVA results section.

Job 100425 | SoC unknown_soc_job100425

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

No failed cases detected from the LAVA results section.

Job 100426 | SoC unknown_soc_job100426

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

No failed cases detected from the LAVA results section.

Job 100427 | SoC unknown_soc_job100427

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

No failed cases detected from the LAVA results section.

Job 100428 | SoC unknown_soc_job100428

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

No failed cases detected from the LAVA results section.

Job 100429 | SoC unknown_soc_job100429

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

No failed cases detected from the LAVA results section.

Job 100431 | SoC unknown_soc_job100431

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

No failed cases detected from the LAVA results section.

[knaveen-qc]

Your comment text here

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[knaveen-qc]

PR #589 — validate-patch

PR: #589

Verdict	Issues	Detailed Report
⚠️	3	Full report

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: QCLINUX : Test change — PR #589
Upstream commit: N/A — QCLINUX: prefix; no upstream lore link expected
Verdict: ⚠️ PARTIAL (validation not applicable; see notes)

Commit Message

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: — vendor-only commit; no upstream to compare against
Body preserves rationale	⚠️	Commit body is empty — no rationale, context, or justification provided for disabling gpi_dma0
Fixes tag present/correct	N/A	Not a bug-fix backport; no Fixes: tag required
Authorship preserved	✅	Single author Salendarsingh Gaud <sgaud@qti.qualcomm.com> with matching Signed-off-by:
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts	✅	Single-hunk change: &gpi_dma0 { status = "okay" → "disabled" }; diff is clean and self-consistent

Issues

• No commit body / rationale: The commit message contains only a subject line (QCLINUX : Test change) and a Signed-off-by:. There is no explanation of why gpi_dma0 is being disabled. A good commit message should describe the problem being solved or the reason for the change, even for vendor-only commits.
• Subject line formatting: There is an extra space before the colon in QCLINUX : — the conventional form is QCLINUX: (no space before the colon).
• "Test change" subject: The subject reads like a placeholder/test commit rather than a production-ready description. If this is intentional (e.g. a CI/workflow test PR), it should be clearly marked as such; if it is a real change, the subject should describe the actual intent (e.g. QCLINUX: arm64: dts: qcom: qcs6490-rb3gen2: disable gpi_dma0).

Verdict

QCLINUX: commits are vendor-only and exempt from lore upstream validation; the diff itself is clean, but the commit message lacks any rationale and uses a placeholder subject — request changes to add a meaningful subject and body before merging.

[knaveen-qc]

PR #589 — checker-log-analyzer

PR: #589
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/26029096715

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	WARNING: Missing commit description — commit has no body/description
dt-binding-check	⏭️	No changes in Documentation/devicetree/bindings — skipped
dtb-check	✅	Log Summary: Test passed — no new DTB errors introduced
sparse-check	⏭️	No C/H files changed — skipped
check-uapi-headers	⏭️	No C/H files changed — skipped
check-patch-compliance	❌	Commit summary does not start with a required prefix
tag-check	❌	Subject QCLINUX : Test change has a space before : — not a valid prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #589 — QCLINUX : Test change
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26029096715
Target branch: qcom-6.18.y (subject-prefix check is mandatory)
Base SHA: 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04
Head SHA: ff45cdcbe1fd4b055aab92ecbe93e0d9ff1e53be

Checker	Result	Summary
checkpatch	❌	WARNING: Missing commit description — commit has no body/description
dt-binding-check	⏭️	No changes in Documentation/devicetree/bindings — skipped
dtb-check	✅	Log Summary: Test passed — no new DTB errors introduced
sparse-check	⏭️	No C/H files changed — skipped
check-uapi-headers	⏭️	No C/H files changed — skipped
check-patch-compliance	❌	Commit summary does not start with a required prefix
tag-check	❌	Subject QCLINUX : Test change has a space before : — not a valid prefix

---

❌ checkpatch

Root cause: The commit ff45cdcbe1fd ("QCLINUX : Test change") has no commit description body — checkpatch requires a meaningful description explaining what the change does and why.

Failure details:

WARNING: Missing commit description - Add an appropriate one

ff45cdcbe1fd4b055aab92ecbe93e0d9ff1e53be total: 0 errors, 1 warnings, 0 checks, 8 lines checked

Commit ff45cdcbe1fd ("QCLINUX : Test change") has style problems, please review.

Fix: Add a commit body describing the change. For example:

QCLINUX: Test change

Disable gpi_dma0 on qcs6490-rb3gen2 because <reason>.

Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>

git rebase -i 6964936c9bfc   # mark commit as 'edit'
git commit --amend            # add description in editor
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04..ff45cdcbe1fd4b055aab92ecbe93e0d9ff1e53be

---

❌ check-patch-compliance

Root cause: The commit subject QCLINUX : Test change does not start with a recognized prefix — the checker requires QCLINUX: (no space before :), but the subject has QCLINUX : (space before :).

Failure details:

Checking commit: QCLINUX : Test change
Commit summary does not start with a required prefix

Fix: Remove the space before : in the subject line so it reads QCLINUX: Test change. Since this is a vendor-only DTS change with no upstream equivalent, QCLINUX: is the correct prefix.

git rebase -i 6964936c9bfc   # mark commit as 'edit'
git commit --amend -m "QCLINUX: Test change

<add description here>

Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>"
git rebase --continue

Reproduce locally:

bash kernel-checkers/check-patch-compliance.sh --kernel-src <kernel-src> \
  --base 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04 \
  --head ff45cdcbe1fd4b055aab92ecbe93e0d9ff1e53be

---

❌ tag-check

Root cause: The commit subject QCLINUX : Test change has a space before the colon (QCLINUX : instead of QCLINUX:), so it does not match any of the required prefix patterns. The target branch qcom-6.18.y requires every commit to start with a valid prefix.

Failure details:

Commit ff45cdcbe1fd ("QCLINUX : Test change"):
  Subject does not match ^(FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND):
  Found: "QCLINUX :" — space before colon makes it unrecognized.

Fix: Same as check-patch-compliance fix above — rename subject to QCLINUX: Test change (no space before :).

---

Verdict

2 real blockers to fix before merge (both caused by the same root issue — a space before : in the commit subject, plus a missing commit description body):

1. Fix the subject prefix: QCLINUX : Test change → QCLINUX: Test change (remove space before :)
2. Add a commit description body explaining what the change does and why gpi_dma0 is being disabled on qcs6490-rb3gen2

Both issues are fixed in a single git commit --amend.

[qcomlnxci]

Test jobs on ff45cdc

• Job 100583 on lemans-evk
• Job 100577 on monaco-evk
• Job 100578 on qcs615-ride
• Job 100580 on qcs6490-rb3gen2
• Job 100579 on qcs8300-ride
• Job 100581 on qcs9100-ride-r3
• Job 100582 on x1e80100-crd

[qcomlnxci]

Test Matrix

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

[knaveen-qc]

LAVA Failed Case Triage Summary

PR: #589

Job 100577 | SoC monaco-evk

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100577_1_detailed.md

  Case 2: WiFi_OnOff

1. Failed case: WiFi_OnOff
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100577_2_detailed.md

  Case 3: ** `0_qcom-next-ci-premerge-tests` — Test Suite Failure (sub-cases WiFi_OnOff + Probe_Failure_Check)

1. Failed case: ** 0_qcom-next-ci-premerge-tests — Test Suite Failure (sub-cases WiFi_OnOff + Probe_Failure_Check)
2. Root cause: ** The LAVA test shell marked the overall 0_qcom-next-ci-premerge-tests definition as failed because two sub-cases failed: WiFi_OnOff (no WiFi interface appeared — ath11k loaded but WiFi firmware absent from initramfs on monaco-evk) and Probe_Failure_Check (cpufreq-dt probe conflict error -17 and missing BT firmware qca/wcnhpbtfw21.tlv/qca/hpbtfw21.tlv error -2); neither failure is introduced by the PR, which only disables gpi_dma0 in the unrelated qcs6490-rb3gen2.dts.
3. Possible fix: Suppress or allowlist the known pre-existing failures on monaco-evk in the CI test plan: add cpufreq-dt probe error -17 and the two BT firmware-load errors to the Probe_Failure_Check benign-filter list, and mark WiFi_OnOff as expected-skip when no WiFi firmware is present in the initramfs for this board; the PR itself requires no changes.
4. Detail analysis attachment: failed_case_job100577_3_detailed.md

Job 100578 | SoC qcs615-ride

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

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

  Case 1: ** download-postprocess-docker

1. Failed case: ** download-postprocess-docker
2. Root cause: ** The postprocess.sh script inside the ghcr.io/mwasilew/docker-mkbootimage:master container failed immediately with cp: cannot stat 'overlay*.tar.gz': No such file or directory (exit code 1) because no overlay*.tar.gz artifact was downloaded into /lava-downloads — only the rootfs flash archive was fetched — causing LAVA to raise Post-processing of downloads failed.
3. Possible fix: Add the missing overlay*.tar.gz artifact as an explicit http-download entry in the LAVA job definition's downloads block so it is present in /lava-downloads before postprocess.sh runs; verify the CI pipeline for build 26028998771 actually produced and uploaded the overlay archive to the S3 artifact store.
4. Detail analysis attachment: failed_case_job100578_1_detailed.md

  Case 2: ** downloads

1. Failed case: ** downloads
2. Root cause: ** The download-postprocess-docker step failed because postprocess.sh executed cp overlay*.tar.gz overlay.tar.gz inside the Docker container but no overlay*.tar.gz file was present in the download directory — only the rootfs flash archive was downloaded — causing the script to exit with code 1 and LAVA to raise Post-processing of downloads failed.
3. Possible fix: Add the missing overlay*.tar.gz artifact as an explicit http-download entry in the LAVA job definition so it is present in /lava-downloads before postprocess.sh runs; alternatively, update postprocess.sh to make the overlay copy conditional (cp overlay*.tar.gz overlay.tar.gz 2>/dev/null || true) if the overlay is optional for qcs615-ride.
4. Detail analysis attachment: failed_case_job100578_2_detailed.md

  Case 3: ** Build Load Failure — postprocess.sh missing overlay*.tar.gz

1. Failed case: ** Build Load Failure — postprocess.sh missing overlay*.tar.gz
2. Root cause: ** Result: Build Load Failure. The download-postprocess-docker stage (step 1.2) failed because postprocess.sh executed cp overlay*.tar.gz overlay.tar.gz inside the Docker container but no overlay*.tar.gz file was present in the downloads directory (/lava-downloads), causing the container to exit with code 1 and LAVA to raise "Post-processing of downloads failed".
3. Possible fix: Verify that the CI artifact upload pipeline for qcs615-ride produces and uploads the overlay*.tar.gz file to the same S3 path as the rootfs image; if the overlay file is intentionally absent for this board, update postprocess.sh to make the cp overlay*.tar.gz step conditional (e.g. cp overlay*.tar.gz overlay.tar.gz 2>/dev/null || true) and re-trigger the job.
4. Detail analysis attachment: failed_case_job100578_3_detailed.md

Job 100579 | SoC qcs8300-ride

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

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

  Case 1: ** Build Load Failure — Missing overlay artifact in download set

1. Failed case: ** Build Load Failure — Missing overlay artifact in download set
2. Root cause: ** Result: Build Load Failure; the download-postprocess-docker stage failed because postprocess.sh executed cp overlay*.tar.gz overlay.tar.gz inside the docker-mkbootimage container but no overlay*.tar.gz file was present in the download directory — only the rootfs flash archive (qcom-multimedia-image-qcs8300-ride-sx.rootfs.qcomflash.tar.gz) was fetched, leaving the glob unmatched and causing cp to exit 1 with cannot stat 'overlay*.tar.gz': No such file or directory.
3. Possible fix: Add the missing overlay*.tar.gz artifact as a second http-download entry in the LAVA job definition's downloads block so it is fetched alongside the rootfs image before postprocess.sh runs; if the overlay artifact is intentionally absent for this job variant, update postprocess.sh (or the LAVA job's postprocess script reference) to make the cp overlay*.tar.gz step conditional/optional.
4. Detail analysis attachment: failed_case_job100579_1_detailed.md

  Case 2: downloads

1. Failed case: downloads
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100579_2_detailed.md

  Case 3: job

1. Failed case: job
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100579_3_detailed.md

Job 100580 | SoC qcs6490-rb3gen2

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

Failed test cases in LAVA job 100580 (SoC: qcs6490-rb3gen2).

  Case 1: ** `download-postprocess-docker`

1. Failed case: ** download-postprocess-docker
2. Root cause: ** The postprocess.sh script inside the ghcr.io/mwasilew/docker-mkbootimage:master container failed immediately with cp: cannot stat 'overlay*.tar.gz': No such file or directory — the expected overlay*.tar.gz artifact was not present in the LAVA downloads directory (/var/lib/lava/dispatcher/tmp/100580/downloads/common/), causing the docker run to exit with code 1 and LAVA to raise "Post-processing of downloads failed".
3. Possible fix: Check the CI artifact pipeline for PR QCLINUX : Test change #589 / run 26028998771 to confirm the overlay*.tar.gz file was built and uploaded alongside the rootfs image; if the overlay artifact is missing from the S3 bucket or was not declared as a download in the LAVA job definition, add it — then re-trigger the job.
4. Detail analysis attachment: failed_case_job100580_1_detailed.md

  Case 2: downloads

1. Failed case: downloads
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100580_2_detailed.md

  Case 3: job

1. Failed case: job
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100580_3_detailed.md

Job 100581 | SoC qcs9100-ride

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

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

  Case 1: download-postprocess-docker

1. Failed case: download-postprocess-docker
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100581_1_detailed.md

  Case 2: downloads

1. Failed case: downloads
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100581_2_detailed.md

  Case 3: ** Build Load Failure — Missing overlay artifact in postprocess.sh

1. Failed case: ** Build Load Failure — Missing overlay artifact in postprocess.sh
2. Root cause: ** Result: Build Load Failure. The download-postprocess-docker stage (step 1.2) failed because postprocess.sh executed cp overlay*.tar.gz overlay.tar.gz but no overlay*.tar.gz file was present in /lava-downloads (the bound download directory), causing the Docker container to exit with code 1 and the error "Post-processing of downloads failed".
3. Possible fix: Re-trigger the CI job; if the failure recurs, inspect the LAVA job definition's postprocess.sh or the artifact pipeline to ensure the overlay*.tar.gz file is correctly generated and placed in the download directory before the postprocess step runs — or update postprocess.sh to handle the missing overlay gracefully (e.g. cp overlay*.tar.gz overlay.tar.gz 2>/dev/null || true) if the overlay is optional for qcs9100-ride.
4. Detail analysis attachment: failed_case_job100581_3_detailed.md

Job 100582 | SoC x1e80100

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

Failed test cases in LAVA job 100582 (SoC: x1e80100).

  Case 1: boot-fastboot

1. Failed case: boot-fastboot
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100582_1_detailed.md

  Case 2: ** Build Load Failure — Fastboot boot image: Load Error

1. Failed case: ** Build Load Failure — Fastboot boot image: Load Error
2. Root cause: ** Result: Build Load Failure. The x1e80100-crd ABL (BOOT.MXF.2.4-00541-HAMOA-1) rejects the fastboot boot command at the boot stage because GetSystemPath() fails with EFI_NOT_FOUND (no system partition present on the board), causing the ABL to abort with the exact error: 'Failed to load/authenticate boot image: Load Error'.
3. Possible fix: This is a pre-existing board/firmware configuration issue unrelated to the PR (which only touches qcs6490-rb3gen2.dts); re-trigger the CI job — if it recurs consistently on x1e80100-crd, the LAVA job definition or board firmware needs to be updated to either flash a stub system partition before fastboot boot, or the ABL needs to be updated to a version that does not require GetSystemPath() to succeed for RAM-boot operations.
4. Detail analysis attachment: failed_case_job100582_2_detailed.md

  Case 3: job

1. Failed case: job
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100582_3_detailed.md

Job 100583 | SoC lemans-evk

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

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

  Case 1: download-postprocess-docker

1. Failed case: download-postprocess-docker
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100583_1_detailed.md

  Case 2: downloads

1. Failed case: downloads
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100583_2_detailed.md

  Case 3: ** Build Load Failure — Missing overlay artifact in postprocess script

1. Failed case: ** Build Load Failure — Missing overlay artifact in postprocess script
2. Root cause: ** Result: Build Load Failure. The download-postprocess-docker stage (step 1.2) failed because postprocess.sh executed cp overlay*.tar.gz overlay.tar.gz inside the Docker container but no overlay*.tar.gz file was present in the downloads directory — only the rootfs flash tarball was downloaded. The LAVA job definition for lemans-evk does not include a separate overlay image URL, so the glob matched nothing and cp exited with code 1, causing Post-processing of downloads failed.
3. Possible fix: Check whether the CI artifact build for lemans-evk (IQ-9075-EVK) is correctly producing and uploading an overlay*.tar.gz alongside the rootfs flash tarball; if the overlay is missing from the S3 artifact set, fix the build pipeline to include it. If the overlay is intentionally embedded inside the flash tarball, update postprocess.sh (or the LAVA job's postprocess steps) to extract it first (e.g. tar -xf qcom-multimedia-image-iq-9075-evk.rootfs.qcomflash.tar.gz overlay*.tar.gz) before the cp step, or add a dedicated overlay download URL to the LAVA job definition's deploy.images block.
4. Detail analysis attachment: failed_case_job100583_3_detailed.md

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[qcomlnxci]

Test jobs on cbbc899

• Job 100832 on lemans-evk
• Job 100836 on monaco-evk
• Job 100828 on qcs615-ride
• Job 100835 on qcs6490-rb3gen2
• Job 100833 on qcs8300-ride
• Job 100829 on qcs9100-ride-r3
• Job 100834 on x1e80100-crd

[qcomlnxci]

Test Matrix

Test Case	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	x1e80100-crd
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	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️
Ethernet	◻️	✅ Pass	⚠️ skip	⚠️ skip	⚠️ 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	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
WiFi_Firmware_Driver	◻️	⚠️ skip	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
WiFi_OnOff	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
cdsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
gpdsp_remoteproc	◻️	✅ Pass	⚠️ skip	⚠️ skip	✅ Pass	❌ Fail	◻️
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	❌ Fail	◻️
rngtest	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
shmbridge	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
smmu	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️

[knaveen-qc]

LAVA Failed Case Triage Summary

PR: #589

Job 100828 | SoC qcs615-ride

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100828_1_detailed.md

  Case 2: smmu

1. Failed case: smmu
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100828_2_detailed.md

  Case 3: USBHost

1. Failed case: USBHost
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100828_3_detailed.md

  Case 4: shmbridge

1. Failed case: shmbridge
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100828_4_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100828_5_detailed.md

Job 100829 | SoC qcs9100-ride

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

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

  Case 1: cdsp_remoteproc

1. Failed case: cdsp_remoteproc
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100829_1_detailed.md

  Case 2: adsp_remoteproc

1. Failed case: adsp_remoteproc
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100829_2_detailed.md

  Case 3: gpdsp_remoteproc

1. Failed case: gpdsp_remoteproc
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100829_3_detailed.md

  Case 4: remoteproc

1. Failed case: remoteproc
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100829_4_detailed.md

  Case 5: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100829_5_detailed.md

  Case 6: smmu

1. Failed case: smmu
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100829_6_detailed.md

  Case 7: USBHost

1. Failed case: USBHost
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100829_7_detailed.md

  Case 8: shmbridge

1. Failed case: shmbridge
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100829_8_detailed.md

Job 100832 | SoC lemans-evk

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

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

  Case 1: login-action

1. Failed case: login-action
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100832_1_detailed.md

  Case 2: auto-login-action

1. Failed case: auto-login-action
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100832_2_detailed.md

  Case 3: minimal-boot

1. Failed case: minimal-boot
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100832_3_detailed.md

  Case 4: job

1. Failed case: job
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100832_4_detailed.md

Job 100833 | SoC qcs8300-ride

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100833_1_detailed.md

  Case 2: USBHost

1. Failed case: USBHost
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100833_2_detailed.md

  Case 3: shmbridge

1. Failed case: shmbridge
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100833_3_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100833_4_detailed.md

Job 100834 | SoC x1e80100

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

Failed test cases in LAVA job 100834 (SoC: x1e80100).

  Case 1: boot-fastboot

1. Failed case: boot-fastboot
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100834_1_detailed.md

  Case 2: fastboot-boot

1. Failed case: fastboot-boot
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100834_2_detailed.md

  Case 3: job

1. Failed case: job
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100834_3_detailed.md

Job 100835 | SoC qcs6490-rb3gen2

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

Failed test cases in LAVA job 100835 (SoC: qcs6490-rb3gen2).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100835_1_detailed.md

  Case 2: USBHost

1. Failed case: USBHost
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100835_2_detailed.md

  Case 3: shmbridge

1. Failed case: shmbridge
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100835_3_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100835_4_detailed.md

Job 100836 | SoC monaco-evk

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100836_1_detailed.md

  Case 2: WiFi_OnOff

1. Failed case: WiFi_OnOff
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100836_2_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Collect additional focused logs and rerun the failed test case.
4. Detail analysis attachment: failed_case_job100836_3_detailed.md