Skip to content

Update README test commit - #1445

Open
Salendarsingh Gaud (sgaud-quic) wants to merge 1 commit into
qualcomm-linux:qcom-6.18.yfrom
sgaud-quic:6.18.y_test
Open

Salendarsingh Gaud (sgaud-quic) wants to merge 1 commit into
qualcomm-linux:qcom-6.18.yfrom
sgaud-quic:6.18.y_test

Conversation

@sgaud-quic

Copy link
Copy Markdown
Contributor

No description provided.

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

Copy link
Copy Markdown

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.

3 similar comments
@qswat-orbit-external

Copy link
Copy Markdown

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.

@qswat-orbit-external

Copy link
Copy Markdown

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.

@qswat-orbit-external

Copy link
Copy Markdown

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.

@qlijarvis

Copy link
Copy Markdown

PR #1445 — validate-patch

PR: #1445

Verdict Issues Detailed Report
❌ 4 Full report

Final Summary

  1. Lore link present: No — no lore.kernel.org link found in commit message; no vendor prefix in subject
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — no upstream reference; appears to be a test commit not posted upstream
  4. PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1445 - Update README test commit
Upstream commit: N/A
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream ❌ No lore link to compare against
Body preserves rationale ❌ No upstream source; commit body lacks any rationale or context
Fixes tag present/correct ❌ No Fixes tag; no upstream reference
Authorship preserved N/A No upstream source to verify against
Backport note (if applicable) N/A No upstream source

Diff

File Status Notes
README:1 ⚠️ Changes first line from "Linux kernel" to "Test new new Linux kernel" — appears to be a test commit

Issues

  • No lore.kernel.org link found: The commit message contains no Link: tag pointing to lore.kernel.org, and no vendor prefix (UPSTREAM:, FROMLIST:, BACKPORT:, QCLINUX:, PENDING:, WORKAROUND:) in the subject line.
  • Missing commit message body: The commit has no description explaining the purpose or rationale for the change.
  • Test content in subject: The subject line "Update README test commit" and the diff content ("Test new new Linux kernel") suggest this is a test commit rather than a legitimate kernel change.
  • Not present in qcom-next or topics: The integration presence report confirms this commit is missing from both qcom-next and all topic branches.

Verdict

Do not merge. This appears to be a test commit that was not intended for the kernel tree. It lacks:

  1. Any upstream lore.kernel.org reference
  2. A proper commit message body with rationale
  3. Presence in qcom-next or topic branches
  4. A legitimate kernel change (modifies README with test content)

Recommendation

If this is a test PR, close it without merging. If this was intended to be a real change:

  1. Add a proper commit message body explaining the purpose
  2. If this is an upstream patch, add Link: https://lore.kernel.org/r/<message-id> and use the appropriate prefix (UPSTREAM:/FROMLIST:/BACKPORT:)
  3. If this is a vendor-only change, use the QCLINUX: prefix and provide proper justification
  4. Ensure the change is present in qcom-next or the appropriate topic branch before submitting a PR

Final Summary

  1. Lore link present: No — no lore.kernel.org link found in commit message; no vendor prefix in subject
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — no upstream reference; appears to be a test commit not posted upstream
  4. PR present in qcom-next/topics: No — integration presence report confirms commit is missing from both qcom-next and all topic branches (FAIL: 1/1 commits missing)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: 17bbb4b37bbc4fc5827b4667445a0c43967c0f48
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final
1/1 [PATCH] Update README test commit missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

Final Status

overall_status: FAIL
present_commits: 0/1
partial_commits: 0/1
missing_commits: 1/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

@qlijarvis

Copy link
Copy Markdown

PR #1445 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 2 warnings: missing commit body, repeated word
dt-binding-check ⏭️ No DT binding changes
dtb-check ⏭️ No devicetree changes
sparse-check ⏭️ No C/H file changes
check-uapi-headers ⏭️ No UAPI changes
check-patch-compliance ❌ Missing required prefix
tag-check ❌ Missing required prefix (mandatory for qcom-6.18.y)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1445 - Update README test commit
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/43201441654
Target Branch: qcom-6.18.y
Commit: fd2f57d35c5117c5ed908e6e0263a9e67a129426

Checker Result Summary
checkpatch ❌ 2 warnings: missing commit body, repeated word
dt-binding-check ⏭️ No DT binding changes
dtb-check ⏭️ No devicetree changes
sparse-check ⏭️ No C/H file changes
check-uapi-headers ⏭️ No UAPI changes
check-patch-compliance ❌ Missing required prefix
tag-check ❌ Missing required prefix (mandatory for qcom-6.18.y)

❌ checkpatch

Root cause: Commit has style issues — missing commit description body and repeated word in code.

Failure details:

WARNING: Missing commit description - Add an appropriate one

WARNING: Possible repeated word: 'new'
#17: FILE: README:1:
+Test new new Linux kernel

fd2f57d35c5117c5ed908e6e0263a9e67a129426 total: 0 errors, 2 warnings, 0 checks, 5 lines checked

Fix:

  1. Add commit body — Explain why the README is being updated:

    git rebase -i 286edfb097dc   # mark commit as 'edit'
    git commit --amend
    # In editor, add body after subject line:
    #
    # Update README test commit
    #
    # This is a test commit to verify the kernel checker CI pipeline.
    # It modifies the README header line for testing purposes.
    #
    # Signed-off-by: ...
  2. Fix repeated word — Change README:1 from:

    Test new new Linux kernel
    

    to:

    Test new Linux kernel
    

    Then:

    git add README
    git commit --amend --no-edit
    git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 286edfb097dc..fd2f57d35c51

❌ check-patch-compliance

Root cause: Commit subject does not start with a required prefix (FROMLIST:, FROMGIT:, UPSTREAM:, or BACKPORT:).

Failure details:

Checking commit: Update README test commit
Commit summary does not start with a required prefix

Fix:

The commit subject "Update README test commit" lacks a prefix. Since this is a test commit modifying README (not an upstream-suitable change), the appropriate action depends on intent:

  • If this is vendor-only test code: Use QCLINUX: prefix, but note that check-patch-compliance will still fail (it only accepts FROMLIST/FROMGIT/UPSTREAM/BACKPORT). This is a known checker limitation for vendor-only commits.

  • If this is work-in-progress: Use PENDING: prefix, but same limitation applies.

  • If this should be treated as upstream-ready: Use FROMLIST: and add a Link: trailer pointing to a lore.kernel.org URL (but README test commits are typically not posted upstream).

Example fix:

git rebase -i 286edfb097dc   # mark commit as 'edit'
git commit --amend -m "QCLINUX: Update README test commit"
# Add body as described in checkpatch fix above
git rebase --continue

Note: Using QCLINUX: or PENDING: will satisfy tag-check (Step 2.7) but will NOT satisfy check-patch-compliance — this is expected for vendor-only commits.

Reproduce locally:

cd kernel-checkers
bash check-patch-compliance.sh --kernel-src /path/to/kernel --base 286edfb097dc --head fd2f57d35c51

❌ tag-check

Root cause: Target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), so every commit must have a subject-line prefix. This commit has no prefix.

Failure details:

Commit fd2f57d35c51 ("Update README test commit"): subject line does not start with a required prefix.

All branches except qcom-next and qcom-next-staging require one of:

  • FROMLIST: / FROMGIT: / UPSTREAM: / BACKPORT: / QCLINUX: / PENDING: / WORKAROUND:

Fix:

Same as check-patch-compliance fix above — add an appropriate prefix to the commit subject:

git rebase -i 286edfb097dc   # mark commit as 'edit'
git commit --amend -m "QCLINUX: Update README test commit"
# Add body and fix repeated word as described above
git rebase --continue

Choose the correct prefix based on the patch origin:

  • Posted to lore but not yet merged → FROMLIST:
  • In a maintainer tree → FROMGIT:
  • Merged into Linus's tree → UPSTREAM:
  • Backported with modifications → BACKPORT:
  • Vendor-only, no upstream → QCLINUX:
  • Work-in-progress, not posted → PENDING:
  • Temporary fix, not for upstream → WORKAROUND:

For this test commit, QCLINUX: or PENDING: would be most appropriate.


Verdict

3 blockers must be fixed before merge:

  1. checkpatch — Add commit body and fix repeated word "new new" → "new"
  2. check-patch-compliance — Add subject prefix (e.g., QCLINUX:)
  3. tag-check — Add subject prefix (same fix as Adding Email Checker  #2)

Recommended action:

Amend the commit to:

  • Change subject to: QCLINUX: Update README test commit (or PENDING: if work-in-progress)
  • Add a commit body explaining the purpose (e.g., "Test commit for CI verification")
  • Fix README:1 from "Test new new Linux kernel" to "Test new Linux kernel"

After these fixes:

  • ✅ checkpatch will pass (0 errors, 0 warnings)
  • ✅ tag-check will pass (prefix present)
  • ⚠️ check-patch-compliance will still fail (known limitation for QCLINUX:/PENDING: prefixes — acceptable for vendor-only commits)

If check-patch-compliance must pass, the only option is to use FROMLIST:/FROMGIT:/UPSTREAM:/BACKPORT: and provide a valid lore.kernel.org Link: trailer, but this is not appropriate for a test README commit.

@qcomlnxci

Copy link
Copy Markdown

Test results

Workflow run: 43695128913 attempt 1

Known failures configured: 46

Target Pass Non-pass Total
kbdev-hamoa-iot-evk-multimedia
kbdev-lemans-evk-multimedia 34 2 36
kbdev-monaco-evk-multimedia 5 0 5
kbdev-purwa-iot-evk-multimedia 27 4 31
kbdev-qcs615-ride-multimedia 28 8 36
kbdev-qcs6490-rb3gen2-multimedia 32 4 36
kbdev-qcs8300-ride-multimedia 30 6 36
kbdev-qcs9100-ride-r3-multimedia 29 7 36
kbdev-qrb2210-rb1-multimedia - ⛔ Not submitted -
kbdev-shikra-iqs-evk-multimedia 17 8 25

Test Matrix

Test Case kbdev-hamoa-iot-evk-multimedia kbdev-lemans-evk-multimedia kbdev-monaco-evk-multimedia kbdev-purwa-iot-evk-multimedia kbdev-qcs615-ride-multimedia kbdev-qcs6490-rb3gen2-multimedia kbdev-qcs8300-ride-multimedia kbdev-qcs9100-ride-r3-multimedia kbdev-qrb2210-rb1-multimedia kbdev-shikra-iqs-evk-multimedia
LAVA result ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ⛔ Not submitted ✅ Results
Audio_Card_Registration ◻️ ✅ Pass ◻️ ◻️ ⚠️ skip ✅ Pass ⚠️ skip ⚠️ skip ⛔ Not submitted ◻️
BT_FW_KMD_Service ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_ON_OFF ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_SCAN ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ◻️
CPUFreq_Validation ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
CPU_affinity ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
DSP_AudioPD ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ◻️
Ethernet_Basic_Validation ◻️ ✅ Pass ◻️ ⚠️ skip ⚠️ skip ⚠️ skip ⚠️ skip ❌ Fail ⛔ Not submitted ❌ Fail
Freq_Scaling ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
GIC ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
IPA ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Interrupts ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
KVM_Driver ◻️ ✅ Pass ◻️ ◻️ ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ◻️
KVM_EL2_DTB ◻️ ✅ Pass ◻️ ◻️ ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ◻️
KVM_Infra ◻️ ✅ Pass ◻️ ◻️ ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ◻️
OpenCV ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ◻️
PCIe ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
Probe_Failure_Check ◻️ ❌ Fail ◻️ ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
RMNET ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
UFS_Validation ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
USBHost ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ⚠️ skip ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
WiFi_Firmware_Driver ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ◻️
WiFi_OnOff ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ◻️
adsp_remoteproc ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
cdsp_remoteproc ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
gpdsp_remoteproc ◻️ ✅ Pass ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
hotplug ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
irq ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
kaslr ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
pinctrl ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
qcom_hwrng ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ◻️
rngtest ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
shmbridge ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
smmu ◻️ ❌ Fail ◻️ ❌ Fail ❌ Fail ✅ Pass ✅ Pass ❌ Fail ⛔ Not submitted ✅ Pass
watchdog ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ◻️
wpss_remoteproc ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Failure summary

Known failures

  • kbdev-lemans-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-lemans-evk-multimedia: smmu => fail.
  • kbdev-purwa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-purwa-iot-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-purwa-iot-evk-multimedia: smmu => fail.
  • kbdev-purwa-iot-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs615-ride-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs615-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs615-ride-multimedia: smmu => fail.
  • kbdev-qcs615-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs615-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs615-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs615-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: USBHost => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs8300-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs9100-ride-r3-multimedia: smmu => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Driver => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Infra => fail.
  • kbdev-shikra-iqs-evk-multimedia: adsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: GIC => fail.
  • kbdev-shikra-iqs-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-shikra-iqs-evk-multimedia: UFS_Validation => skip.
  • kbdev-shikra-iqs-evk-multimedia: PCIe => fail.
  • kbdev-shikra-iqs-evk-multimedia: USBHost => fail.

Unexpected failures

  • kbdev-qcs615-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs8300-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs9100-ride-r3-multimedia: Audio_Card_Registration => skip.
  • kbdev-qrb2210-rb1-multimedia did not produce a LAVA result artifact.
  • kbdev-shikra-iqs-evk-multimedia: Ethernet_Basic_Validation => fail.

Result: blocked because unexpected failures were found.

@qcomlnxci

Copy link
Copy Markdown

Test results

Workflow run: 43700239131 attempt 1

Known failures configured: 46

Target Pass Non-pass Total
kbdev-hamoa-iot-evk-multimedia
kbdev-lemans-evk-multimedia 32 4 36
kbdev-monaco-evk-multimedia 33 3 36
kbdev-purwa-iot-evk-multimedia 29 7 36
kbdev-qcs615-ride-multimedia 28 8 36
kbdev-qcs6490-rb3gen2-multimedia 32 4 36
kbdev-qcs8300-ride-multimedia 29 7 36
kbdev-qcs9100-ride-r3-multimedia 29 7 36
kbdev-qrb2210-rb1-multimedia - ⛔ Not submitted -
kbdev-shikra-iqs-evk-multimedia 21 15 36

Test Matrix

Test Case kbdev-hamoa-iot-evk-multimedia kbdev-lemans-evk-multimedia kbdev-monaco-evk-multimedia kbdev-purwa-iot-evk-multimedia kbdev-qcs615-ride-multimedia kbdev-qcs6490-rb3gen2-multimedia kbdev-qcs8300-ride-multimedia kbdev-qcs9100-ride-r3-multimedia kbdev-qrb2210-rb1-multimedia kbdev-shikra-iqs-evk-multimedia
LAVA result ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ⛔ Not submitted ✅ Results
Audio_Card_Registration ◻️ ✅ Pass ✅ Pass ✅ Pass ⚠️ skip ✅ Pass ⚠️ skip ⚠️ skip ⛔ Not submitted ⚠️ skip
BT_FW_KMD_Service ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_ON_OFF ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_SCAN ◻️ ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
CPUFreq_Validation ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
CPU_affinity ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
DSP_AudioPD ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
Ethernet_Basic_Validation ◻️ ⚠️ skip ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip ⚠️ skip ❌ Fail ⛔ Not submitted ❌ Fail
Freq_Scaling ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
GIC ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
IPA ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Interrupts ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
KVM_Driver ◻️ ✅ Pass ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
KVM_EL2_DTB ◻️ ✅ Pass ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
KVM_Infra ◻️ ✅ Pass ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
OpenCV ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
PCIe ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
Probe_Failure_Check ◻️ ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
RMNET ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
UFS_Validation ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
USBHost ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⚠️ skip ❌ Fail ✅ Pass ⛔ Not submitted ❌ Fail
WiFi_Firmware_Driver ◻️ ✅ Pass ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
WiFi_OnOff ◻️ ✅ Pass ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
adsp_remoteproc ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
cdsp_remoteproc ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
gpdsp_remoteproc ◻️ ✅ Pass ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
hotplug ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
irq ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
kaslr ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
pinctrl ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
qcom_hwrng ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
rngtest ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
shmbridge ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
smmu ◻️ ❌ Fail ✅ Pass ❌ Fail ❌ Fail ✅ Pass ✅ Pass ❌ Fail ⛔ Not submitted ✅ Pass
watchdog ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
wpss_remoteproc ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Failure summary

Known failures

  • kbdev-lemans-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-lemans-evk-multimedia: smmu => fail.
  • kbdev-monaco-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-monaco-evk-multimedia: WiFi_Firmware_Driver => fail.
  • kbdev-monaco-evk-multimedia: WiFi_OnOff => fail.
  • kbdev-purwa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-purwa-iot-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-purwa-iot-evk-multimedia: smmu => fail.
  • kbdev-purwa-iot-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-purwa-iot-evk-multimedia: KVM_Driver => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_Infra => fail.
  • kbdev-qcs615-ride-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs615-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs615-ride-multimedia: smmu => fail.
  • kbdev-qcs615-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs615-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs615-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs615-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: USBHost => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs8300-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs9100-ride-r3-multimedia: smmu => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Driver => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Infra => fail.
  • kbdev-shikra-iqs-evk-multimedia: adsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: GIC => fail.
  • kbdev-shikra-iqs-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-shikra-iqs-evk-multimedia: UFS_Validation => skip.
  • kbdev-shikra-iqs-evk-multimedia: PCIe => fail.
  • kbdev-shikra-iqs-evk-multimedia: USBHost => fail.
  • kbdev-shikra-iqs-evk-multimedia: WiFi_OnOff => skip.
  • kbdev-shikra-iqs-evk-multimedia: DSP_AudioPD => skip.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Driver => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Infra => fail.

Unexpected failures

  • kbdev-lemans-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-lemans-evk-multimedia: BT_SCAN => fail.
  • kbdev-qcs615-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs8300-ride-multimedia: USBHost => fail.
  • kbdev-qcs8300-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs9100-ride-r3-multimedia: Audio_Card_Registration => skip.
  • kbdev-qrb2210-rb1-multimedia did not produce a LAVA result artifact.
  • kbdev-shikra-iqs-evk-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-shikra-iqs-evk-multimedia: BT_SCAN => fail.
  • kbdev-shikra-iqs-evk-multimedia: Audio_Card_Registration => skip.

Result: blocked because unexpected failures were found.

@qcomlnxci

Copy link
Copy Markdown

Test results

Workflow run: 43706843012 attempt 1

Known failures configured: 46

Target Pass Non-pass Total
kbdev-hamoa-iot-evk-multimedia
kbdev-lemans-evk-multimedia
kbdev-monaco-evk-multimedia 32 4 36
kbdev-purwa-iot-evk-multimedia 29 7 36
kbdev-qcs615-ride-multimedia 28 8 36
kbdev-qcs6490-rb3gen2-multimedia 32 4 36
kbdev-qcs8300-ride-multimedia 27 9 36
kbdev-qcs9100-ride-r3-multimedia 29 7 36
kbdev-qrb2210-rb1-multimedia - ⛔ Not submitted -
kbdev-shikra-iqs-evk-multimedia 21 15 36

Test Matrix

Test Case kbdev-hamoa-iot-evk-multimedia kbdev-lemans-evk-multimedia kbdev-monaco-evk-multimedia kbdev-purwa-iot-evk-multimedia kbdev-qcs615-ride-multimedia kbdev-qcs6490-rb3gen2-multimedia kbdev-qcs8300-ride-multimedia kbdev-qcs9100-ride-r3-multimedia kbdev-qrb2210-rb1-multimedia kbdev-shikra-iqs-evk-multimedia
LAVA result ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ⛔ Not submitted ✅ Results
Audio_Card_Registration ◻️ ◻️ ✅ Pass ✅ Pass ⚠️ skip ✅ Pass ⚠️ skip ⚠️ skip ⛔ Not submitted ⚠️ skip
BT_FW_KMD_Service ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_ON_OFF ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_SCAN ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
CPUFreq_Validation ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
CPU_affinity ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
DSP_AudioPD ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
Ethernet_Basic_Validation ◻️ ◻️ ⚠️ skip ⚠️ skip ⚠️ skip ⚠️ skip ⚠️ skip ❌ Fail ⛔ Not submitted ❌ Fail
Freq_Scaling ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
GIC ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
IPA ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Interrupts ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
KVM_Driver ◻️ ◻️ ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
KVM_EL2_DTB ◻️ ◻️ ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
KVM_Infra ◻️ ◻️ ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
OpenCV ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
PCIe ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
Probe_Failure_Check ◻️ ◻️ ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
RMNET ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
UFS_Validation ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
USBHost ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⚠️ skip ❌ Fail ✅ Pass ⛔ Not submitted ❌ Fail
WiFi_Firmware_Driver ◻️ ◻️ ❌ Fail ✅ Pass ✅ Pass ✅ Pass ❌ Fail ✅ Pass ⛔ Not submitted ✅ Pass
WiFi_OnOff ◻️ ◻️ ❌ Fail ✅ Pass ✅ Pass ✅ Pass ❌ Fail ✅ Pass ⛔ Not submitted ⚠️ skip
adsp_remoteproc ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
cdsp_remoteproc ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
gpdsp_remoteproc ◻️ ◻️ ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
hotplug ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
irq ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
kaslr ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
pinctrl ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
qcom_hwrng ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
rngtest ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
shmbridge ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
smmu ◻️ ◻️ ✅ Pass ❌ Fail ❌ Fail ✅ Pass ✅ Pass ❌ Fail ⛔ Not submitted ✅ Pass
watchdog ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
wpss_remoteproc ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Failure summary

Known failures

  • kbdev-monaco-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-monaco-evk-multimedia: WiFi_Firmware_Driver => fail.
  • kbdev-monaco-evk-multimedia: WiFi_OnOff => fail.
  • kbdev-purwa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-purwa-iot-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-purwa-iot-evk-multimedia: smmu => fail.
  • kbdev-purwa-iot-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-purwa-iot-evk-multimedia: KVM_Driver => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_Infra => fail.
  • kbdev-qcs615-ride-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs615-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs615-ride-multimedia: smmu => fail.
  • kbdev-qcs615-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs615-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs615-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs615-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: USBHost => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs8300-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs9100-ride-r3-multimedia: smmu => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Driver => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Infra => fail.
  • kbdev-shikra-iqs-evk-multimedia: adsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: GIC => fail.
  • kbdev-shikra-iqs-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-shikra-iqs-evk-multimedia: UFS_Validation => skip.
  • kbdev-shikra-iqs-evk-multimedia: PCIe => fail.
  • kbdev-shikra-iqs-evk-multimedia: USBHost => fail.
  • kbdev-shikra-iqs-evk-multimedia: WiFi_OnOff => skip.
  • kbdev-shikra-iqs-evk-multimedia: DSP_AudioPD => skip.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Driver => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Infra => fail.

Unexpected failures

  • kbdev-monaco-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs615-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs8300-ride-multimedia: USBHost => fail.
  • kbdev-qcs8300-ride-multimedia: WiFi_Firmware_Driver => fail.
  • kbdev-qcs8300-ride-multimedia: WiFi_OnOff => fail.
  • kbdev-qcs8300-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs9100-ride-r3-multimedia: Audio_Card_Registration => skip.
  • kbdev-qrb2210-rb1-multimedia did not produce a LAVA result artifact.
  • kbdev-shikra-iqs-evk-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-shikra-iqs-evk-multimedia: BT_SCAN => fail.
  • kbdev-shikra-iqs-evk-multimedia: Audio_Card_Registration => skip.

Result: blocked because unexpected failures were found.

@qlijarvis

Copy link
Copy Markdown

LAVA Failed Case Triage Summary

PR: #1445

Job 279618 | SoC hamoa-evk

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

No failed cases detected from the LAVA results section.

Job 279619 | SoC monaco-evk

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

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

  Case 1: Probe_Failure_Check — WiFi Driver Probe Failure
  1. Failed case: Probe_Failure_Check — WiFi Driver Probe Failure
  2. Root cause: ath11k_pci WiFi driver probe failed with -ETIMEDOUT (-110) on monaco-evk due to missing or incompatible WiFi firmware (ath11k/WCN6855/hw2.1/nfa765/amss.bin) in the rootfs, preventing the WCN6855 PCIe WiFi module from initializing.
  3. Possible fix: Add the missing ath11k WCN6855 firmware files (specifically ath11k/WCN6855/hw2.1/nfa765/amss.bin and board files) to the rootfs firmware directory (/lib/firmware/), or update the LAVA job to use a rootfs image that includes the complete ath11k firmware package for WCN6855 hardware.
  4. Detail analysis attachment: failed_case_job279619_1_detailed.md
  Case 2: ** WiFi Driver Probe Failure — ath11k_pci MHI firmware missing
  1. Failed case: ** WiFi Driver Probe Failure — ath11k_pci MHI firmware missing
  2. Root cause: ** ath11k_pci driver probe failed with -ETIMEDOUT because the required MHI firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs (-ENOENT). Without this firmware, the MHI subsystem cannot power up the WCN6855 WiFi hardware, causing the probe to timeout after ~320ms. This is a pre-existing image packaging issue, not introduced by PR Update README test commit #1445 (which only modifies README).
  3. Possible fix: Add the missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs image under /lib/firmware/. For monaco-evk (IQ-8275) builds, ensure the linux-firmware-qcom or equivalent firmware package includes the WCN6855 hw2.1 nfa765 variant firmware. Verify the firmware is present in the build artifact before flashing.
  4. Detail analysis attachment: failed_case_job279619_2_detailed.md
  Case 3: WiFi_OnOff — Driver Probe Failure (Firmware Dependency)
  1. Failed case: WiFi_OnOff — Driver Probe Failure (Firmware Dependency)
  2. Root cause: ath11k_pci driver probe failed with error -110 (ETIMEDOUT) on monaco-evk because the required WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs /lib/firmware directory, causing MHI (Modem Host Interface) power-up to timeout during the WCN6855 PCIe WiFi chip initialization sequence.
  3. Possible fix: Add the missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs image under /lib/firmware/ by including the linux-firmware-ath11k package or copying the firmware from the upstream linux-firmware repository (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git).
  4. Detail analysis attachment: failed_case_job279619_3_detailed.md
  Case 4: Driver Probe Failure — ath11k_pci WiFi driver
  1. Failed case: Driver Probe Failure — ath11k_pci WiFi driver
  2. Root cause: ath11k_pci WiFi driver probe failed with error -110 (ETIMEDOUT) during MHI power-up on monaco-evk. The driver failed to power up the MHI interface (failed to power up mhi: -110), which cascaded to failed to start mhi: -110, failed to create soc core: -110, and ultimately probe with driver ath11k_pci failed with error -110. This is a hardware/firmware initialization timeout, not a kernel regression introduced by the PR (which only modified README).
  3. Possible fix: This is a pre-existing platform/firmware issue on monaco-evk, not caused by PR Update README test commit #1445 (README-only change). The WiFi hardware (WCN6855) is failing to respond during MHI initialization. Recommended actions: (1) Verify WiFi hardware is properly seated and powered on the monaco-evk board; (2) Check if WiFi firmware files are present in the rootfs (ath11k/WCN6855/hw2.1/nfa765/amss.bin); (3) Review monaco-evk device tree for correct PCIe/WiFi configuration; (4) If this is a known board-specific issue, suppress these WiFi test failures for monaco-evk in CI configuration.
  4. Detail analysis attachment: failed_case_job279619_4_detailed.md
Job 279620 | SoC qcs6490-rb3gen2

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

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

  Case 1: Probe_Failure_Check — regulatory.db firmware load false positive
  1. Failed case: Probe_Failure_Check — regulatory.db firmware load false positive
  2. Root cause: The Probe_Failure_Check test detected a regulatory.db firmware load failure (Direct firmware load for regulatory.db failed with error -2) during boot. However, this is a known benign false positive: the regulatory.db file is an optional wireless regulatory database used by cfg80211, and its absence does not prevent WiFi functionality. The WiFi_OnOff and WiFi_Firmware_Driver tests both passed, confirming that WiFi is fully functional despite this firmware load message. The PR under test only modifies the README file and introduces no kernel code changes.
  3. Possible fix: Suppress this failure class in the Probe_Failure_Check test logic by excluding regulatory.db firmware load failures when WiFi functional tests pass. Add a suppression rule: "Ignore 'regulatory: Direct firmware load for regulatory.db failed' when WiFi_OnOff or WiFi_Firmware_Driver tests pass." This is a test infrastructure improvement, not a kernel fix. The PR is safe to merge.
  4. Detail analysis attachment: failed_case_job279620_1_detailed.md
  Case 2: 0_qcom-next-ci-premerge-tests
  1. Failed case: 0_qcom-next-ci-premerge-tests
  2. Root cause: LAVA test definition marked as failed because the Probe_Failure_Check sub-test detected a firmware load error: "faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2". This is a pre-existing infrastructure/configuration issue unrelated to the PR (which only modifies README).
  3. Possible fix: This is a false positive for PR validation. The regulatory.db firmware file is missing from the rootfs image but does not impact kernel functionality for this platform. Either: (1) add regulatory.db to the rootfs build, or (2) update Probe_Failure_Check test to suppress known benign firmware load failures for optional regulatory database files.
  4. Detail analysis attachment: failed_case_job279620_2_detailed.md
Job 279621 | SoC qcs9100-ride

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

Failed test cases in LAVA job 279621 (SoC: qcs9100-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: No PR changes required. For platform fixes: (1) regulatory.db failure is benign and can be ignored; (2) Add firmware-name property to Aquantia PHY DT node in arch/arm64/boot/dts/qcom/qcs9100-ride.dts if 10G Ethernet on stmmac-0:08 is required; (3) nvmem-reboot-mode deferred probe is benign and can be suppressed in CI or fixed by correcting nvmem cell bindings in DT.
  4. Detail analysis attachment: failed_case_job279621_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: Test validation logic incorrectly expects parent video-codec device (aa00000.video-codec) to have direct IOMMU group attachment, when the iris driver architecture correctly creates child devices (iris_non_pixel.0, iris_pixel.0) that are properly attached to IOMMU groups 25 and 26.
  3. Possible fix: Update the smmu test validation logic to recognize that iris video codec uses a split-device architecture where child devices (iris_non_pixel.0, iris_pixel.0) handle IOMMU attachment, not the parent platform device. The test should check for child device IOMMU attachment instead of expecting the parent aa00000.video-codec to be directly attached.
  4. Detail analysis attachment: failed_case_job279621_2_detailed.md
  Case 3: Ethernet_Basic_Validation — Driver Runtime Failure (PHY Attachment)
  1. Failed case: Ethernet_Basic_Validation — Driver Runtime Failure (PHY Attachment)
  2. Root cause: Device tree configuration issue on qcs9100-ride platform — MDIO bus for ethernet controller at 23040000 is not probed or PHY device is not registered, causing PHY attachment to fail with -EINVAL when interface is brought up administratively. This is a pre-existing platform issue, not introduced by PR Update README test commit #1445 (which only modifies README).
  3. Possible fix: Review and fix the device tree for qcs9100-ride (qcs9100-ride.dts or lemans-ride.dts): ensure the ethernet@23040000 node has a valid mdio child node with PHY device definitions, and that the phy-handle property correctly references the PHY. Compare with the working 23000000.ethernet configuration or reference device trees for similar Qualcomm platforms. This is a platform DT bug that should be fixed in the kernel tree, not a CI/test infrastructure issue.
  4. Detail analysis attachment: failed_case_job279621_3_detailed.md
  Case 4: KVM_Driver — Platform Limitation (HYP Mode Not Available)
  1. Failed case: KVM_Driver — Platform Limitation (HYP Mode Not Available)
  2. Root cause: The qcs9100-ride (Lemans) platform does not support ARM Virtualization Extensions (EL2/HYP mode), which is a mandatory hardware requirement for KVM. The kernel message "kvm [1]: HYP mode not available" at boot time [4.013514] indicates the CPU does not provide the necessary virtualization support, preventing /dev/kvm creation despite CONFIG_KVM=y being enabled.
  3. Possible fix: This is not a kernel regression or bug — it is a platform hardware limitation. The KVM_Driver test should be skipped on qcs9100-ride targets that lack virtualization extensions. Add platform-specific test filtering to exclude KVM tests on non-virtualization-capable SoCs, or update the test suite to mark KVM tests as "SKIP" (not "FAIL") when HYP mode is unavailable.
  4. Detail analysis attachment: failed_case_job279621_4_detailed.md
  Case 5: ** KVM_EL2_DTB
  1. Failed case: ** KVM_EL2_DTB
  2. Root cause: ** The qcs9100-ride platform boots with the Gunyah hypervisor occupying EL2, preventing KVM from initializing because KVM requires exclusive EL2 access and cannot coexist with another hypervisor at the same exception level.
  3. Possible fix: This is a pre-existing platform configuration issue, not a PR-introduced regression. To enable KVM on qcs9100-ride, either: (1) disable Gunyah hypervisor in the bootloader/firmware configuration, or (2) exclude KVM tests from the qcs9100-ride CI test suite as KVM is architecturally incompatible with Gunyah-enabled platforms.
  4. Detail analysis attachment: failed_case_job279621_5_detailed.md
  Case 6: KVM_Infra — KVM Infrastructure Test
  1. Failed case: KVM_Infra — KVM Infrastructure Test
  2. Root cause: KVM driver initialization failed because the qcs9100-ride platform is not booting at EL2 (hypervisor exception level). The kernel log shows "kvm [1]: HYP mode not available" at boot time, preventing /dev/kvm device node creation. This is a platform firmware/bootloader configuration issue, not a kernel code defect.
  3. Possible fix: Configure the bootloader/firmware on qcs9100-ride to boot Linux at EL2 instead of EL1. This typically requires enabling virtualization extensions in the bootloader (e.g., ABL/XBL configuration) or ensuring the platform's TrustZone configuration allows EL2 access. Alternatively, if the platform hardware does not support EL2, disable KVM tests for this SoC in the CI test matrix.
  4. Detail analysis attachment: failed_case_job279621_6_detailed.md
  Case 7: 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: Mark KVM tests as "skip" or "not applicable" for qcs9100-ride in the LAVA test definition, or enable nested virtualization support in the Gunyah hypervisor configuration if KVM guest support is required. The PR (README-only change) is not the cause and does not require modification.
  4. Detail analysis attachment: failed_case_job279621_7_detailed.md
Job 279622 | SoC qcs615-ride

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

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

  Case 1: Probe_Failure_Check — cfg80211 regulatory.db firmware load failure
  1. Failed case: Probe_Failure_Check — cfg80211 regulatory.db firmware load failure
  2. Root cause: The cfg80211 wireless regulatory subsystem failed to load the regulatory.db firmware file (error -2: ENOENT) during boot. This is a false positive test failure — the regulatory database is optional for WiFi operation, and WiFi functionality is confirmed working (WiFi_OnOff test PASSED). The PR changes only README and does not touch any driver or firmware code. This failure is pre-existing in the test environment (missing regulatory.db file in rootfs) and not introduced by PR Update README test commit #1445.
  3. Possible fix: Suppress this failure as a known benign false positive. The Probe_Failure_Check test should be updated to exclude regulatory.db firmware load failures when WiFi functional tests pass, similar to the existing suppression rules for WiFi/BT firmware in lava-known-benign-failures.md. Short-term: Add regulatory.db file to the rootfs image or update the test filter to exclude cfg80211 regulatory database errors.
  4. Detail analysis attachment: failed_case_job279622_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: Test infrastructure bug — the smmu test expects video-decoder and video-encoder to be registered as separate platform devices with individual IOMMU group attachments, but the qcom-venus driver on qcs615-ride uses "non legacy binding" mode where these are logical sub-devices of the parent aa00000.video-codec device (which is correctly attached to IOMMU group 7). The PR changes only README and introduces no functional kernel changes.
  3. Possible fix: Update the smmu test script to recognize that in "non legacy binding" mode, video-decoder and video-encoder do not appear as separate platform devices in /sys/devices/platform/ or /sys/kernel/iommu_groups/. The test should verify only that the parent video-codec device is attached to an IOMMU group, which it is (group 7).
  4. Detail analysis attachment: failed_case_job279622_2_detailed.md
  Case 3: ** KVM_Driver (Platform Configuration Issue — EL1 Boot)
  1. Failed case: ** KVM_Driver (Platform Configuration Issue — EL1 Boot)
  2. Root cause: ** The QCS615 Ride bootloader/firmware boots the kernel at EL1 (normal kernel mode) instead of EL2 (hypervisor mode). KVM on ARM64 requires the kernel to run at EL2 to enable virtualization extensions. Without EL2, the KVM driver cannot initialize and /dev/kvm is not created.
  3. Possible fix: Configure the bootloader (ABL/UEFI) or device tree to boot the kernel at EL2. For Qualcomm platforms, this typically requires: (1) enabling HYP mode in the bootloader configuration, (2) ensuring the secure monitor (TZ) allows EL2 entry, and (3) verifying the device tree does not force EL1 boot. If EL2 boot is not supported on this hardware revision, KVM tests should be skipped for this platform.
  4. Detail analysis attachment: failed_case_job279622_3_detailed.md
  Case 4: KVM_EL2_DTB — KVM device node unavailable (platform limitation)
  1. Failed case: KVM_EL2_DTB — KVM device node unavailable (platform limitation)
  2. Root cause: The qcs615-ride platform booted without EL2 (hypervisor) mode available, as evidenced by the kernel message kvm [1]: HYP mode not available at boot time (line 3045). Without EL2 access, the KVM driver cannot initialize and /dev/kvm is never created, causing all KVM-dependent tests (KVM_Driver, KVM_EL2_DTB, KVM_Infra) to fail. This is a platform/firmware/bootloader configuration issue, not a kernel regression.
  3. Possible fix: This failure is not PR-related (PR only modifies README). To enable KVM on qcs615-ride: (1) verify the bootloader (ABL/XBL) is configured to boot Linux in EL2 or with VHE (Virtualization Host Extensions) enabled; (2) confirm the device tree does not contain properties that force EL1-only boot; (3) check that TrustZone/secure firmware allows EL2 access to non-secure world; (4) if the platform does not support EL2, mark KVM tests as expected-to-skip for this SoC in the CI configuration.
  4. Detail analysis attachment: failed_case_job279622_4_detailed.md
  Case 5: KVM Infrastructure Test Failure — Platform Configuration Issue
  1. Failed case: KVM Infrastructure Test Failure — Platform Configuration Issue
  2. Root cause: QCS615 Ride board boots with Gunyah hypervisor occupying EL2, forcing Linux kernel to run at EL1; KVM requires kernel execution at EL2 to provide virtualization services, resulting in "HYP mode not available" and missing /dev/kvm device node.
  3. Possible fix: This is expected behavior on platforms with a resident hypervisor. To enable KVM testing: (1) disable Gunyah hypervisor in bootloader/firmware configuration to allow Linux to boot at EL2, OR (2) exclude KVM tests from the CI test suite for QCS615 Ride when Gunyah is enabled, OR (3) use nested virtualization if Gunyah supports exposing virtual EL2 to guest OS (requires Gunyah feature support and kernel configuration).
  4. Detail analysis attachment: failed_case_job279622_5_detailed.md
  Case 6: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: KVM driver initialization detected HYP mode (ARM EL2) is not available on qcs615-ride platform; /dev/kvm device node not created because required hardware virtualization support is absent.
  3. Possible fix: This is a platform hardware limitation, not a software bug. The qcs615-ride board does not support ARM EL2 (Hypervisor mode) required for KVM. Either: (1) exclude KVM tests from qcs615-ride CI test suite, or (2) run KVM tests only on platforms with EL2 support (e.g., rb5, rb3gen2, sa8775p).
  4. Detail analysis attachment: failed_case_job279622_6_detailed.md
Job 279623 | SoC purwa-evk

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

Failed test cases in LAVA job 279623 (SoC: purwa-evk).

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Four probe/firmware errors detected on purwa-evk (iq-x5121-evk): (1) qcom_qseecom_uefisecapp probe failed with -EBUSY (-16), (2-3) two qcom-pcie controllers (1bf8000.pci, 1bd0000.pcie) failed with -ENODATA (-61) due to missing PHY init sequences in qcom-qmp-pcie-phy driver, and (4) regulatory.db firmware file missing (-ENOENT). These are pre-existing platform/configuration issues unrelated to the README-only PR patch.
  3. Possible fix: These probe failures are expected on purwa-evk and do not indicate a kernel regression introduced by this PR. The Probe_Failure_Check test should be updated to whitelist known benign probe failures for purwa-evk: (1) qcom_qseecom_uefisecapp -EBUSY is expected when secure app is unavailable, (2-3) PCIe PHY -ENODATA failures are expected when PHY init sequences are not yet upstreamed for this SoC, (4) regulatory.db -ENOENT is a known benign wireless regulatory database absence. No kernel code fix required for this PR.
  4. Detail analysis attachment: failed_case_job279623_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: The SMMU test expects the video codec device aa00000.video-codec to be attached to an IOMMU group, but on the purwa-evk (X1E80100) platform, the video codec driver (qcom-iris) uses child platform devices (iris_non_pixel.0 and iris_pixel.0) for IOMMU attachment instead of the parent device. Both child devices are correctly attached to IOMMU groups 17 and 18, and the video codec firmware loaded and initialized successfully. This is a test expectation mismatch, not a kernel regression.
  3. Possible fix: Update the SMMU test script to recognize that the qcom-iris video codec driver on X1E80100 uses child platform devices for IOMMU attachment. The test should check for iris_non_pixel.0 and iris_pixel.0 IOMMU group membership instead of (or in addition to) the parent aa00000.video-codec device when validating video codec IOMMU protection.
  4. Detail analysis attachment: failed_case_job279623_2_detailed.md
  Case 3: KVM_Driver
  1. Failed case: KVM_Driver
  2. Root cause: KVM cannot initialize because Gunyah hypervisor is already running at EL2 on the purwa-evk platform; kernel message "kvm [1]: HYP mode not available" indicates KVM detected it cannot access EL2 (HYP mode) as required for ARM KVM operation, resulting in /dev/kvm device node not being created.
  3. Possible fix: This is a platform configuration issue, not a PR-introduced regression (PR only modifies README). For purwa-evk with Gunyah hypervisor, either: (1) disable CONFIG_KVM in the kernel config since nested virtualization is not supported, or (2) boot without the Gunyah hypervisor if KVM testing is required. Update the LAVA test suite to skip KVM tests on platforms running Gunyah/other hypervisors at EL2.
  4. Detail analysis attachment: failed_case_job279623_3_detailed.md
  Case 4: ** KVM_EL2_DTB — Driver Initialization Failure
  1. Failed case: ** KVM_EL2_DTB — Driver Initialization Failure
  2. Root cause: ** KVM driver initialization failed with "HYP mode not available" because the purwa-evk platform does not provide EL2 (Hypervisor mode) access to the kernel. The kernel booted at EL1, preventing KVM from creating /dev/kvm. This is a pre-existing platform/firmware limitation, not a regression introduced by PR Update README test commit #1445 (which only modifies README).
  3. Possible fix: Exclude KVM tests from purwa-evk CI test suite by adding platform-specific test exclusion in the LAVA job definition. If virtualization support is required, work with firmware team to enable EL2 boot or verify if the purwa-evk SoC supports ARM virtualization extensions in hardware.
  4. Detail analysis attachment: failed_case_job279623_4_detailed.md
  Case 5: KVM Infrastructure Unavailable — Hypervisor Conflict
  1. Failed case: KVM Infrastructure Unavailable — Hypervisor Conflict
  2. Root cause: KVM initialization fails on purwa-evk because the Gunyah hypervisor is running at EL2, preventing KVM from accessing HYP mode. The kernel logs "kvm [1]: HYP mode not available" at boot, causing /dev/kvm device node creation to be skipped. This is a platform-specific configuration issue, not a kernel regression.
  3. Possible fix: This is not a test failure requiring a fix — it is expected behavior on purwa-evk. The platform runs Gunyah hypervisor at EL2, which is mutually exclusive with KVM. Either: (1) Skip KVM tests on purwa-evk in the CI job definition (recommended), or (2) Boot purwa-evk without Gunyah hypervisor if KVM testing is required (requires firmware/boot configuration change).
  4. Detail analysis attachment: failed_case_job279623_5_detailed.md
  Case 6: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: KVM driver initialization failed because HYP mode (EL2 exception level) is not available on the purwa-evk platform, preventing /dev/kvm device node creation. The kernel message "kvm [1]: HYP mode not available" indicates the CPU is not running with virtualization extensions enabled or the bootloader did not enter the kernel at EL2.
  3. Possible fix: This is a platform/hardware limitation, not a kernel regression introduced by the PR (which only modified README). Purwa-evk either lacks ARM virtualization extensions (ARMv8-A Virtualization Extensions) or the bootloader is not configured to boot the kernel at EL2. To enable KVM: (1) verify the SoC supports virtualization extensions, (2) configure the bootloader to enter the kernel at EL2 instead of EL1, or (3) if the hardware does not support virtualization, mark KVM tests as expected-fail for this platform in the CI configuration.
  4. Detail analysis attachment: failed_case_job279623_6_detailed.md
Job 279624 | SoC lemans-evk

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

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

  Case 1: Board Hang — login-action timeout (no login prompt after successful kernel boot and userspace init)
  1. Failed case: Board Hang — login-action timeout (no login prompt after successful kernel boot and userspace init)
  2. Root cause: System hangs after kernel boots successfully (last kernel message at 6.158s: UFS driver probe) and userspace init starts (systemd-udevd), but before root filesystem mount completes. Hardware watchdog eventually triggers (~96s silence). A non-fatal "BUG: sleeping function called from invalid context" warning appears during qcom_scm probe (3.139s) but system continues. The hang occurs during device initialization (PCIe/UFS probing phase) on lemans-evk. PR changes only README — this is a pre-existing platform/infra issue, not PR-introduced.
  3. Possible fix: This is a pre-existing board/kernel issue unrelated to the PR (README-only change). Re-trigger the CI job on a different lemans-evk board or with a known-good kernel baseline to confirm the failure is board-specific or environmental. If the issue persists across boards, investigate UFS/PCIe driver initialization hang on lemans-evk (check for missing firmware, DT configuration issues, or driver bugs in the qcom-pcie/ufshcd-qcom paths). The qcom_scm "sleeping function" warning should also be fixed (call qcom_scm_call outside atomic context), but it is not the root cause of the hang.
  4. Detail analysis attachment: failed_case_job279624_1_detailed.md
  Case 2: Board Hang — Complete System Freeze After UFS Driver Probe
  1. Failed case: Board Hang — Complete System Freeze After UFS Driver Probe
  2. Root cause: System hung at approximately 6.158 seconds into boot during UFS host controller initialization (ufshcd-qcom probe), with no further console output for 96+ seconds until login timeout. The hang occurred after a non-fatal BUG message during qcom_scm probe (sleeping function called from invalid context at drivers/firmware/qcom/qcom_scm.c:320 while in atomic context with preempt_count=1, irqs_disabled=1). The system reached early userspace (systemd-udevd started) but never completed boot to a login prompt. This is a lemans-evk platform-specific hang during storage subsystem initialization.
  3. Possible fix: This is a pre-existing kernel issue unrelated to the PR (PR only modifies README). The hang occurs during UFS driver probe on lemans-evk. Immediate mitigation: re-trigger the CI job to confirm reproducibility. If reproducible, investigate UFS driver initialization path on lemans-evk: check for missing device tree properties (vdd-hba-supply regulator warning seen), firmware dependencies, or timing issues in ufshcd-qcom probe. The earlier qcom_scm BUG (sleeping in atomic context during qcom_tzmem_enable) may have corrupted kernel state leading to the subsequent hang. Debug steps: (1) enable UFS driver debug logs, (2) add instrumentation around ufshcd_populate_vreg and subsequent probe steps, (3) verify qcom_scm probe completes correctly despite the BUG warning.
  4. Detail analysis attachment: failed_case_job279624_2_detailed.md
  Case 3: Boot Hang — Login Timeout (System Hang During Userspace Initialization)
  1. Failed case: Boot Hang — Login Timeout (System Hang During Userspace Initialization)
  2. Root cause: System hung during early userspace initialization after kernel successfully booted; last kernel message at timestamp [6.158035] shows UFS driver initialization, followed by complete loss of console output; LAVA login-action timed out after 185 seconds waiting for login prompt that never appeared; system became unresponsive with no further serial output despite multiple retry attempts.
  3. Possible fix: This is NOT a PR-introduced regression — the PR only modifies README documentation and cannot cause a boot hang. Root cause is a pre-existing platform/infrastructure issue on lemans-evk. Recommended actions: (1) Re-trigger the CI job to confirm reproducibility; (2) If reproducible, investigate UFS driver initialization path and systemd-udevd startup on lemans-evk — check for hardware-specific timing issues, missing firmware, or device tree configuration problems; (3) Enable early console debugging (earlycon, ignore_loglevel) to capture any missing kernel messages after UFS init; (4) Check if other lemans-evk LAVA jobs are experiencing similar hangs to rule out board-specific hardware failure.
  4. Detail analysis attachment: failed_case_job279624_3_detailed.md
  Case 4: LAVA Job Timeout — System Hang During Boot
  1. Failed case: LAVA Job Timeout — System Hang During Boot
  2. Root cause: Kernel booted successfully but hung at ~6.2 seconds during driver initialization (last message: UFS driver probe); system became unresponsive and never reached login prompt, triggering LAVA auto-login timeout after 3 retry attempts (600 seconds total); watchdog or timeout forced a warm reboot.
  3. Possible fix: This is a pre-existing kernel hang issue (PR only modifies README). Investigate UFS driver initialization hang on lemans-evk: enable CONFIG_DETECT_HUNG_TASK, CONFIG_SOFTLOCKUP_DETECTOR, and collect serial console output with earlycon to capture the exact hang point; check if UFS controller is waiting indefinitely for hardware response or stuck in a polling loop; verify UFS firmware compatibility and power sequencing for lemans-evk platform.
  4. Detail analysis attachment: failed_case_job279624_4_detailed.md
Job 279625 | SoC shikra-iqs-evk

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

Failed test cases in LAVA job 279625 (SoC: shikra-iqs-evk).

  Case 1: GIC Test Script Bug — Hardcoded CPU Count Mismatch
  1. Failed case: GIC Test Script Bug — Hardcoded CPU Count Mismatch
  2. Root cause: The GIC test script at line 75 (run.sh) hardcodes an expectation of 8 CPUs (0-7) but the shikra-iqs-evk board has only 4 CPUs (0-3). The script attempts to parse interrupt counts for non-existent CPUs 4-7, resulting in bash integer comparison errors ([: GICv3: integer expected, [: Level: integer expected, [: arch_timer: integer expected) when it tries to compare non-numeric fields from the /proc/interrupts output format against integer values. This is a test infrastructure bug, not a kernel regression — the PR changes only README and does not affect CPU topology, GIC functionality, or interrupt delivery.
  3. Possible fix: Update the GIC test script to dynamically detect the number of online CPUs from /sys/devices/system/cpu/online (as the Interrupts and hotplug tests correctly do) instead of hardcoding a loop over CPUs 0-7. The script should iterate only over CPUs present in the system, matching the pattern used by the passing Interrupts test which correctly reports "CPU online list: 0-3" and tests only those 4 CPUs.
  4. Detail analysis attachment: failed_case_job279625_1_detailed.md
  Case 2: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Pre-existing platform-specific probe failures on shikra-iqs-evk: missing firmware files (ucsi_ccg ccg_secondary.cyacd2, regulatory.db), TPM SPI timeout (-110), and audio codec deferred probe (va_macro mclk clock, snd-sc8280xp CPU DAI name) — all unrelated to PR Update README test commit #1445 which only modifies README documentation.
  3. Possible fix: Mark this test case as a known baseline failure for shikra-iqs-evk or suppress these specific probe failures in the test harness. The PR is safe to merge — it does not introduce any kernel code changes and cannot cause probe failures.
  4. Detail analysis attachment: failed_case_job279625_2_detailed.md
  Case 3: ** PCIe — QPS615 Firmware/Driver Validation
  1. Failed case: ** PCIe — QPS615 Firmware/Driver Validation
  2. Root cause: ** Test infrastructure issue — the PCIe test expects vendor-specific firmware (TC956X_Firmware_PCIeBridge.bin) and an out-of-tree driver module (tc956x_pcie_eth) that are not provisioned in the LAVA test environment. The underlying PCIe hardware and kernel drivers are fully functional (7 devices enumerated, links active, no kernel errors). This is not a kernel regression.
  3. Possible fix: Provision the missing test dependencies in the LAVA rootfs: add TC956X_Firmware_PCIeBridge.bin to /lib/firmware/ and build/install the tc956x_pcie_eth kernel module. Alternatively, update the test to skip QPS615-specific validation when these optional components are absent, since the core PCIe functionality (enumeration, link training, driver binding) is already validated and passing.
  4. Detail analysis attachment: failed_case_job279625_3_detailed.md
  Case 4: ** USBHost
  1. Failed case: ** USBHost
  2. Root cause: ** USB controllers on shikra-iqs-evk are configured in gadget/peripheral mode instead of host mode. The device tree or boot configuration has dr_mode set to peripheral or OTG with peripheral as default role, preventing USB root hub enumeration. This is a pre-existing platform configuration issue, not a regression from PR Update README test commit #1445 (which only modifies README).
  3. Possible fix: Update the shikra-iqs-evk device tree to set USB controller dr_mode property to "host" for the USB nodes at 4c00000.usb and 4e00000.usb, or implement USB role switching infrastructure if OTG functionality is required. Short-term: modify the USBHost test to skip on platforms where USB is intentionally configured in gadget mode, or add pre-test logic to switch to host mode via /sys/class/usb_role/*/role if role switching is supported.
  4. Detail analysis attachment: failed_case_job279625_4_detailed.md
  Case 5: Ethernet_Basic_Validation — Network Infrastructure Failure
  1. Failed case: Ethernet_Basic_Validation — Network Infrastructure Failure
  2. Root cause: LAVA lab network infrastructure issue preventing connectivity between target board (10.143.233.240) and gateway (10.143.232.1). The eth1 interface is fully operational (driver loaded, link established at 1000Mb/s full duplex, IP assigned), but all ICMP packets to the gateway are lost, indicating a network path issue external to the kernel. This failure is NOT PR-introduced as the PR only modifies the README file.
  3. Possible fix: Re-trigger the LAVA job to verify if this is a transient network issue. If the failure persists, investigate LAVA lab network infrastructure: verify gateway 10.143.232.1 is reachable from the LAVA worker, check switch/router configuration for the test network segment (10.143.233.0/24), and verify no firewall rules are blocking ICMP between the shikra-iqs-evk board and the gateway.
  4. Detail analysis attachment: failed_case_job279625_5_detailed.md
  Case 6: BT_SCAN — Test Environment Issue (No Discoverable Bluetooth Devices)
  1. Failed case: BT_SCAN — Test Environment Issue (No Discoverable Bluetooth Devices)
  2. Root cause: The BT_SCAN test failed because no Bluetooth devices were discoverable in the test environment during the 3 scan attempts (15s scan window each). The Bluetooth stack is fully functional (hci0 initialized, firmware loaded, power on successful, discovery started/stopped correctly), but the test environment lacks nearby Bluetooth devices to discover. This is a test infrastructure limitation, not a kernel regression. The PR changes only README and cannot affect Bluetooth functionality.
  3. Possible fix: This is not a kernel bug requiring a code fix. The test failure is expected when no Bluetooth devices are present in the LAVA lab environment. To resolve: (1) Place a discoverable Bluetooth device (phone, speaker, beacon) within RF range of the shikra-iqs-evk board during test execution, OR (2) Mark BT_SCAN as an optional/informational test that does not block PR merge when the test environment lacks external Bluetooth devices, OR (3) Add a test environment check that skips BT_SCAN with a clear message when no devices are expected to be present.
  4. Detail analysis attachment: failed_case_job279625_6_detailed.md
  Case 7: KVM_Driver
  1. Failed case: KVM_Driver
  2. Root cause: KVM driver initialization failed because HYP (EL2) mode is not available on this platform — the Shikra IQS EVK is running with Gunyah hypervisor already occupying EL2, preventing KVM from accessing hypervisor mode.
  3. Possible fix: This is a platform configuration issue, not a kernel regression introduced by PR Update README test commit #1445 (which only modifies README). To enable KVM on Shikra IQS EVK, either: (1) boot without Gunyah hypervisor to allow KVM direct EL2 access, or (2) configure nested virtualization if supported by Gunyah, or (3) exclude KVM tests from the CI test suite for platforms running with Gunyah hypervisor.
  4. Detail analysis attachment: failed_case_job279625_7_detailed.md
  Case 8: ** KVM Driver Initialization Failure — HYP mode not available
  1. Failed case: ** KVM Driver Initialization Failure — HYP mode not available
  2. Root cause: ** The Shikra IQS EVK board is running the Gunyah hypervisor at EL2, preventing KVM from accessing hypervisor mode; KVM and Gunyah are mutually exclusive on ARM64, and the platform firmware has Gunyah enabled.
  3. Possible fix: This is a test environment configuration issue, not a kernel bug. To enable KVM testing: (1) disable Gunyah in the board firmware/bootloader configuration, or (2) exclude KVM tests from the CI suite for Gunyah-enabled platforms, or (3) provision separate test boards with and without Gunyah for respective test suites.
  4. Detail analysis attachment: failed_case_job279625_8_detailed.md
  Case 9: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: Platform does not support KVM virtualization — bootloader/firmware does not enable EL2 (HYP mode), causing KVM initialization to fail with "HYP mode not available" at boot time, preventing /dev/kvm device creation.
  3. Possible fix: This is a pre-existing platform limitation (not introduced by PR Update README test commit #1445 which only modifies README). To enable KVM on Shikra IQS EVK: (1) verify bootloader (ABL/UEFI) is configured to boot kernel at EL2 instead of EL1, (2) check if secure firmware (TZ) allows EL2 execution, (3) if platform does not support EL2, exclude KVM tests from the Shikra test suite or mark them as expected-fail for this board.
  4. Detail analysis attachment: failed_case_job279625_9_detailed.md
  Case 10: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: KVM hypervisor infrastructure unavailable — the shikra-iqs-evk platform does not support ARM Virtualization Extensions (EL2/HYP mode), as evidenced by kernel message "kvm [1]: HYP mode not available" at boot time, preventing creation of /dev/kvm device node.
  3. Possible fix: This is a pre-existing platform hardware/firmware limitation, not a kernel regression. The PR (README-only change) did not introduce this failure. To resolve: (1) Skip KVM tests on shikra-iqs-evk in the LAVA job definition, OR (2) Enable EL2/HYP mode in the platform firmware/bootloader if the hardware supports it, OR (3) Use a different platform that supports ARM Virtualization Extensions for KVM testing.
  4. Detail analysis attachment: failed_case_job279625_10_detailed.md
Job 279626 | SoC qcs8300-ride

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

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

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Pre-existing platform-specific hardware initialization issues on qcs8300-ride: (1) xHCI USB host controller probe timeout (-ETIMEDOUT) during hardware setup phase, and (2) cfg80211 regulatory database firmware file missing from rootfs. Neither error is introduced by PR Update README test commit #1445 (README-only change).
  3. Possible fix: These are known benign platform issues on qcs8300-ride and should be suppressed in the Probe_Failure_Check test filter. The xHCI timeout is a hardware/firmware initialization race on this SoC; the regulatory.db missing file is expected when the wireless-regdb package is not installed. Both issues do not affect core kernel functionality (all other tests passed). Recommended action: update Probe_Failure_Check test to exclude these two known qcs8300-ride patterns from failure criteria.
  4. Detail analysis attachment: failed_case_job279626_1_detailed.md
  Case 2: USBHost
  1. Failed case: USBHost
  2. Root cause: xHCI host controller driver probe failure with error -110 (ETIMEDOUT) on qcs8300-ride platform. The xHCI driver times out during controller setup (can't setup: -110) at boot time (25 seconds after kernel start), indicating the USB host controller hardware is not responding to initialization commands. This is a pre-existing platform/board issue unrelated to the PR (which only modifies README).
  3. Possible fix: Investigate USB host controller power/clock/PHY dependencies on qcs8300-ride. Check: (1) USB PHY initialization and power sequencing, (2) USB controller clocks and regulators in device tree (a400000.usb and a600000.usb nodes), (3) firmware dependencies for USB controller, (4) hardware availability on this specific board variant. The PR does not introduce this issue and should not be blocked by this failure.
  4. Detail analysis attachment: failed_case_job279626_2_detailed.md
  Case 3: WiFi_Firmware_Driver — WiFi Board Data File Missing
  1. Failed case: WiFi_Firmware_Driver — WiFi Board Data File Missing
  2. Root cause: ath11k_pci driver probe failed with error -2 (ENOENT) because the required board data file ath11k/QCA6698AQ/hw2.1/board-2.bin is missing from the firmware partition on qcs8300-ride. The driver attempted multiple fallback board-id variants (variant=QC_QCS8300_Ride, qmi-board-id=518, qmi-chip-id=2) but none matched any entry in the board-2.bin file or the file itself is absent.
  3. Possible fix: Add the missing board data file ath11k/QCA6698AQ/hw2.1/board-2.bin with entries for qcs8300-ride (qmi-board-id=518, qmi-chip-id=2, variant=QC_QCS8300_Ride) to the linux-firmware package or the target rootfs /lib/firmware directory. This is a pre-existing firmware packaging issue unrelated to the PR (which only modifies README).
  4. Detail analysis attachment: failed_case_job279626_3_detailed.md
  Case 4: ** WiFi Driver Probe Failure — Missing Board Data File
  1. Failed case: ** WiFi Driver Probe Failure — Missing Board Data File
  2. Root cause: ** The ath11k_pci driver probe failed with error -2 (-ENOENT) because the required board calibration file ath11k/QCA6698AQ/hw2.1/board-2.bin is missing from the rootfs /lib/firmware/ directory on the qcs8300-ride target, despite the main firmware file amss.bin being present.
  3. Possible fix: Add the missing board-2.bin file to the Yocto image recipe or firmware package that provisions /lib/firmware/ath11k/QCA6698AQ/hw2.1/ for qcs8300-ride builds. The board file must contain calibration data matching the hardware identifiers: vendor=17cb, device=1103, subsystem-vendor=17cb, subsystem-device=0108, qmi-chip-id=2, qmi-board-id=518, variant=QC_QCS8300_Ride.
  4. Detail analysis attachment: failed_case_job279626_4_detailed.md
  Case 5: KVM_Driver — /dev/kvm device node not created
  1. Failed case: KVM_Driver — /dev/kvm device node not created
  2. Root cause: QCS8300 Ride platform boots under Gunyah hypervisor at EL1 (not EL2), preventing KVM driver initialization; CONFIG_KVM is enabled but KVM requires EL2 to create /dev/kvm; this is a platform configuration issue, not a kernel regression.
  3. Possible fix: This is expected behavior on QCS8300 when running under Gunyah hypervisor — KVM cannot be used as a nested hypervisor in this configuration; either (1) disable KVM tests for this platform/configuration, or (2) boot without Gunyah to run at EL2 if KVM testing is required.
  4. Detail analysis attachment: failed_case_job279626_5_detailed.md
  Case 6: KVM_EL2_DTB — KVM device node unavailable
  1. Failed case: KVM_EL2_DTB — KVM device node unavailable
  2. Root cause: KVM kernel module (CONFIG_KVM=y) is compiled into the kernel but the /dev/kvm device node is not created at runtime on qcs8300-ride (Monaco) platform, indicating KVM initialization failed silently during boot. The platform runs under Gunyah hypervisor (gunyah-3fe287d48) which may not support nested virtualization or KVM may require additional platform-specific enablement (device tree properties, hypervisor configuration, or EL2 mode prerequisites) that are missing on this SoC.
  3. Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression (PR only modifies README). To enable KVM on qcs8300-ride: (1) verify the platform's Gunyah hypervisor configuration allows KVM/nested virtualization, (2) check device tree for required KVM enablement properties (e.g., psci node with virtualization support, memory reservations), (3) review kernel boot log for silent KVM initialization failures (add kvm-arm.mode= debugging), (4) if KVM is not supported on this platform/hypervisor combination, mark these tests as SKIP for qcs8300-ride in the CI test matrix rather than FAIL.
  4. Detail analysis attachment: failed_case_job279626_6_detailed.md
  Case 7: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: This is a pre-existing platform/firmware issue on qcs8300-ride, not a kernel regression. Verify Gunyah hypervisor firmware version supports KVM on this SoC; if KVM is required, update to a Gunyah firmware build with KVM/KP support enabled, or use a platform configuration that exposes EL2 virtualization to the host OS
  4. Detail analysis attachment: failed_case_job279626_7_detailed.md
  Case 8: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: KVM device node /dev/kvm is not created despite CONFIG_KVM being enabled in kernel config — KVM driver failed to initialize on qcs8300-ride platform, likely due to missing hypervisor support, incorrect EL2 mode configuration, or platform-specific KVM initialization failure unrelated to the PR (which only modifies README documentation).
  3. Possible fix: This is a pre-existing platform issue, not a PR-introduced regression. The PR only changes README documentation and cannot affect KVM functionality. To resolve: (1) verify qcs8300-ride platform supports KVM/virtualization in hardware and firmware; (2) check kernel boot log for KVM initialization errors or warnings; (3) verify EL2 hypervisor mode is properly configured; (4) if KVM is not expected to work on this platform, mark KVM tests as "skip" for qcs8300-ride in the LAVA test definition.
  4. Detail analysis attachment: failed_case_job279626_8_detailed.md

@qcomlnxci

Copy link
Copy Markdown

Test results

Workflow run: 43726898241 attempt 1

Known failures configured: 46

Target Pass Non-pass Total
kbdev-hamoa-iot-evk-multimedia 3 1 4
kbdev-lemans-evk-multimedia
kbdev-monaco-evk-multimedia 21 1 22
kbdev-purwa-iot-evk-multimedia 3 1 4
kbdev-qcs615-ride-multimedia
kbdev-qcs6490-rb3gen2-multimedia 21 4 25
kbdev-qcs8300-ride-multimedia 20 2 22
kbdev-qcs9100-ride-r3-multimedia 22 3 25
kbdev-qrb2210-rb1-multimedia - ⛔ Not submitted -
kbdev-shikra-iqs-evk-multimedia 17 8 25

Test Matrix

Test Case kbdev-hamoa-iot-evk-multimedia kbdev-lemans-evk-multimedia kbdev-monaco-evk-multimedia kbdev-purwa-iot-evk-multimedia kbdev-qcs615-ride-multimedia kbdev-qcs6490-rb3gen2-multimedia kbdev-qcs8300-ride-multimedia kbdev-qcs9100-ride-r3-multimedia kbdev-qrb2210-rb1-multimedia kbdev-shikra-iqs-evk-multimedia
LAVA result ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ⛔ Not submitted ✅ Results
BT_FW_KMD_Service ◻️ ◻️ ◻️ ◻️ ◻️ ✅ Pass ◻️ ✅ Pass ⛔ Not submitted ✅ Pass
BT_ON_OFF ◻️ ◻️ ◻️ ◻️ ◻️ ✅ Pass ◻️ ✅ Pass ⛔ Not submitted ✅ Pass
CPUFreq_Validation ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
CPU_affinity ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Ethernet_Basic_Validation ◻️ ◻️ ◻️ ◻️ ◻️ ⚠️ skip ◻️ ❌ Fail ⛔ Not submitted ❌ Fail
Freq_Scaling ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
GIC ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
IPA ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Interrupts ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
PCIe ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
Probe_Failure_Check ◻️ ◻️ ❌ Fail ◻️ ◻️ ❌ Fail ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
RMNET ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
UFS_Validation ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
USBHost ◻️ ◻️ ✅ Pass ◻️ ◻️ ⚠️ skip ❌ Fail ✅ Pass ⛔ Not submitted ❌ Fail
adsp_remoteproc ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
cdsp_remoteproc ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
gpdsp_remoteproc ⚠️ skip ◻️ ✅ Pass ⚠️ skip ◻️ ⚠️ skip ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
hotplug ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
irq ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
kaslr ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
pinctrl ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
rngtest ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
shmbridge ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
smmu ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ❌ Fail ⛔ Not submitted ✅ Pass
wpss_remoteproc ◻️ ◻️ ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Failure summary

Known failures

  • kbdev-hamoa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-monaco-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-purwa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: USBHost => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs9100-ride-r3-multimedia: smmu => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-shikra-iqs-evk-multimedia: adsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: GIC => fail.
  • kbdev-shikra-iqs-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-shikra-iqs-evk-multimedia: UFS_Validation => skip.
  • kbdev-shikra-iqs-evk-multimedia: PCIe => fail.
  • kbdev-shikra-iqs-evk-multimedia: USBHost => fail.

Unexpected failures

  • kbdev-qcs8300-ride-multimedia: USBHost => fail.
  • kbdev-qrb2210-rb1-multimedia did not produce a LAVA result artifact.
  • kbdev-shikra-iqs-evk-multimedia: Ethernet_Basic_Validation => fail.

Result: blocked because unexpected failures were found.

@qlijarvis

Copy link
Copy Markdown

LAVA Failed Case Triage Summary

PR: #1445

Job 279638 | SoC shikra-iqs-evk

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

Failed test cases in LAVA job 279638 (SoC: shikra-iqs-evk).

  Case 1: GIC
  1. Failed case: GIC
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Update the GIC test script to dynamically detect the number of online CPUs from /sys/devices/system/cpu/online or /proc/cpuinfo and only validate timer counts for CPUs that actually exist on the platform. The script should not hardcode an assumption of 8 CPUs.
  4. Detail analysis attachment: failed_case_job279638_1_detailed.md
  Case 2: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: This PR should not be blocked by these failures. Track platform issues separately: (1) Add va_macro mclk clock binding to shikra DT, (2) Include ccg_secondary.cyacd2 firmware in rootfs if USB-C PD is required, (3) Disable tpm_tis_spi in DT if TPM hardware is not populated on this EVK variant, (4) Update CI baseline to exclude known platform-specific probe failures from PR validation.
  4. Detail analysis attachment: failed_case_job279638_2_detailed.md
  Case 3: ** PCIe — QPS615 Firmware Missing (Pre-existing Infrastructure Issue)
  1. Failed case: ** PCIe — QPS615 Firmware Missing (Pre-existing Infrastructure Issue)
  2. Root cause: ** The PCIe test failed because the required firmware file TC956X_Firmware_PCIeBridge.bin is not present in the rootfs firmware directories. The PCIe controller and QPS615 PCIe switch hardware are functioning correctly (link up, devices enumerated, no kernel errors), but the test validation script expects this firmware file to be present and fails when it cannot find it. This is a pre-existing infrastructure/image configuration issue, not a kernel regression introduced by the PR (which only modifies README documentation).
  3. Possible fix: Add the TC956X_Firmware_PCIeBridge.bin firmware file to the rootfs image in /lib/firmware/ or another standard firmware search path. Additionally, ensure the tc956x_pcie_eth kernel module is built and included in the image if QPS615 Ethernet functionality is required. This is an image/build configuration fix, not a kernel code fix.
  4. Detail analysis attachment: failed_case_job279638_3_detailed.md
  Case 4: USBHost — Type-C Controller Firmware Missing (Infrastructure Issue)
  1. Failed case: USBHost — Type-C Controller Firmware Missing (Infrastructure Issue)
  2. Root cause: UCSI CCG Type-C controller probe failed with error -2 (ENOENT) because firmware file ccg_secondary.cyacd2 is missing from /lib/firmware/. Without this firmware, the Type-C controller cannot initialize, USB role switching is unavailable, and USB ports remain in gadget/peripheral mode. No USB root hubs are exposed for host mode operation, causing the USBHost test to fail.
  3. Possible fix: Add the missing firmware file ccg_secondary.cyacd2 to the root filesystem at /lib/firmware/ in the LAVA test image for shikra-iqs-evk. The firmware should be sourced from the Cypress/Infineon UCSI CCG firmware package or the linux-firmware repository. After adding the firmware, rebuild the test image and re-run the LAVA job to verify USB host mode functionality.
  4. Detail analysis attachment: failed_case_job279638_4_detailed.md
  Case 5: Ethernet_Basic_Validation
  1. Failed case: Ethernet_Basic_Validation
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: This is a pre-existing LAVA lab infrastructure issue (network path/gateway/firewall blocking ICMP or routing misconfiguration between 10.143.232.159 and 10.143.232.1). Re-trigger the CI job. If the issue persists, verify the LAVA lab network configuration for shikra-iqs-evk: check that gateway 10.143.232.1 is reachable from the lab network segment, verify ICMP is not blocked by firewall rules, and confirm the switch/router configuration for the test network.
  4. Detail analysis attachment: failed_case_job279638_5_detailed.md
  Case 6: ** LAVA Job Timeout — External Cancellation (not a kernel crash or test failure)
  1. Failed case: ** LAVA Job Timeout — External Cancellation (not a kernel crash or test failure)
  2. Root cause: ** The LAVA job was externally canceled at 15:50:20 while the BT_SCAN test was actively running (scan attempt 1/3 in progress). The job was canceled 32 minutes and 40 seconds before the declared 40-minute test timeout would have expired. The BT_SCAN test was progressing normally (Bluetooth functional, BT_ON_OFF passed, scan initiated successfully). The PR changes only a README file and cannot cause a test hang. This is a LAVA infrastructure issue, not a kernel regression.
  3. Possible fix: Re-trigger the LAVA job. If the issue recurs, investigate LAVA worker resource limits, check for manual job cancellation in the LAVA scheduler logs, and verify that no hidden timeout policy (e.g., total job duration limit, worker-side timeout) is conflicting with the declared 40-minute test timeout. The shikra-iqs-evk board and kernel are functioning correctly; the failure is on the LAVA infrastructure side.
  4. Detail analysis attachment: failed_case_job279638_6_detailed.md
  Case 7: lava-test-shell (LAVA infrastructure timeout)
  1. Failed case: lava-test-shell (LAVA infrastructure timeout)
  2. Root cause: LAVA job timeout — the lava-test-shell action exceeded its 7-minute (420-second) timeout while the BT_SCAN test was executing a 15-second Bluetooth scan operation; the job was administratively canceled by LAVA dispatcher at 15:50:20 after running for 419.78 seconds.
  3. Possible fix: This is a LAVA job configuration issue, not a kernel or PR issue. Increase the lava-test-shell timeout from 7 minutes to at least 10 minutes in the LAVA job definition to accommodate the full test suite runtime. The PR (README-only change) is not the cause and can proceed.
  4. Detail analysis attachment: failed_case_job279638_7_detailed.md
  Case 8: ** lava-test-retry (LAVA Infrastructure Cancellation)
  1. Failed case: ** lava-test-retry (LAVA Infrastructure Cancellation)
  2. Root cause: ** LAVA job was externally canceled by the CI infrastructure after 7 minutes (419.78 seconds) during the BT_SCAN test execution, despite a 40-minute timeout being configured. The kernel booted successfully, all prior tests passed (including BT_ON_OFF), and the system was healthy when canceled. The PR only modifies README and introduces no functional changes.
  3. Possible fix: Re-trigger the LAVA job. This is a CI infrastructure cancellation, not a kernel issue. If the cancellation recurs, investigate LAVA dispatcher logs and job queue management on the LAVA server to identify why jobs are being prematurely canceled on the shikra-iqs-evk target.
  4. Detail analysis attachment: failed_case_job279638_8_detailed.md
  Case 9: job
  1. Failed case: job
  2. Root cause: LAVA job was externally canceled at 15:50:20 UTC after running for only 7 minutes (419.78s) of the configured 40-minute test timeout, while the BT_SCAN test was in progress (14 seconds into a 15-second Bluetooth scan window).
  3. Possible fix: Re-trigger the LAVA job; the cancellation was external (not caused by the PR or kernel behavior) and occurred well before the configured timeout, suggesting infrastructure-level intervention or resource contention on the LAVA dispatcher.
  4. Detail analysis attachment: failed_case_job279638_9_detailed.md
Job 279639 | SoC qcs6490-rb3gen2

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

No failed cases detected from the LAVA results section.

Job 279640 | SoC hamoa-evk

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

Failed test cases in LAVA job 279640 (SoC: hamoa-evk).

  Case 1: Test Hang — GIC test stalled after initialization
  1. Failed case: Test Hang — GIC test stalled after initialization
  2. Root cause: The GIC (Generic Interrupt Controller) test started execution but hung immediately after printing the initial timer count, producing no further test output for over 2 minutes until LAVA's test timeout (125 seconds) expired and canceled the job. The test appears to have entered an infinite wait or deadlock state during interrupt controller validation. The concurrent qcom-hamoa-ec I2C timeout errors (-110 = ETIMEDOUT) are unrelated pre-existing noise that began at boot and do not correlate with the test hang.
  3. Possible fix: Re-trigger the CI job to determine if this is a transient test infrastructure issue. If the GIC test hang reproduces, investigate the GIC test script (Runner/suites/Kernel/Baseport/GIC/run.sh) for potential deadlocks in interrupt validation logic, and check for hamoa-evk-specific GIC/interrupt controller configuration issues in the device tree or kernel that could cause the test to stall.
  4. Detail analysis attachment: failed_case_job279640_1_detailed.md
  Case 2: lava-test-shell
  1. Failed case: lava-test-shell
  2. Root cause: LAVA job was externally canceled during test execution after 2 minutes and 6 seconds while tests were passing; the cancellation was not triggered by a kernel crash, test failure, or timeout—the job was marked as "The job was canceled" by the LAVA dispatcher, indicating manual cancellation or infrastructure-initiated abort unrelated to the PR under test (which only modifies README documentation).
  3. Possible fix: Re-trigger the LAVA CI job; if cancellation recurs at a similar point, investigate LAVA infrastructure logs and job queue management for resource contention, worker node issues, or administrative job termination policies that may be prematurely canceling long-running test suites on hamoa-evk.
  4. Detail analysis attachment: failed_case_job279640_2_detailed.md
  Case 3: lava-test-retry — LAVA test infrastructure timeout (job canceled)
  1. Failed case: lava-test-retry — LAVA test infrastructure timeout (job canceled)
  2. Root cause: LAVA job canceled due to test inactivity timeout triggered by console flooding from qcom-hamoa-ec driver repeatedly logging "Failed to read EC SCI Event: -110" (ETIMEDOUT) errors at 1Hz rate, preventing test progress detection and causing GIC test to appear hung.
  3. Possible fix: This is a pre-existing hamoa-evk platform issue unrelated to the PR (which only modifies README). The EC driver timeout is a known board-specific firmware/hardware communication issue. Re-trigger the CI job on a different hamoa-evk board or suppress EC console spam via dynamic debug to allow tests to complete.
  4. Detail analysis attachment: failed_case_job279640_3_detailed.md
  Case 4: LAVA Job Timeout — Test Hang (GIC test)
  1. Failed case: LAVA Job Timeout — Test Hang (GIC test)
  2. Root cause: LAVA job canceled after 2-minute timeout during GIC test execution; test started at 15:48:15 but produced no further output after printing initial timer count, causing LAVA to mark the test run as unfinished and cancel the job at 15:50:07. The recurring qcom-hamoa-ec 2-0076: Failed to read EC SCI Event: -110 errors are a pre-existing hamoa-evk platform issue (EC I2C communication timeout) unrelated to the test hang or the PR (README-only change).
  3. Possible fix: Re-trigger the CI job; if the GIC test hang recurs, increase the lava-test-shell timeout from 40 minutes to 60 minutes in the LAVA job definition, and investigate why the GIC test script (/lava-279640/0/tests/0_qcom-next-ci-premerge-tests/Runner/suites/Kernel/Baseport/GIC/run.sh) hangs after printing the initial timer count on hamoa-evk.
  4. Detail analysis attachment: failed_case_job279640_4_detailed.md
Job 279641 | SoC lemans-evk

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

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

  Case 1: Locking/Synchronization Issue — Sleeping function called from atomic context causing system hang
  1. Failed case: Locking/Synchronization Issue — Sleeping function called from atomic context causing system hang
  2. Root cause: During qcom_scm driver probe at boot, qcom_scm_call() (a sleeping function requiring mutex) was invoked from atomic context with preemption disabled (in_atomic(): 1, irqs_disabled(): 1) inside __do_once_start+0x2c, violating kernel locking rules. This occurred in the call chain: qcom_scm_probe → qcom_tzmem_enable → qcom_scm_shm_bridge_enable → __qcom_scm_is_call_available → qcom_scm_call. The atomic context violation caused the system to hang completely after kernel timestamp 6.392s (last message: UFS driver probe), preventing userspace from reaching the login prompt.
  3. Possible fix: Apply upstream fix to remove the __do_once_start atomic context wrapper around the SCM availability check in qcom_scm_shm_bridge_enable(). The SCM call availability check should be performed in normal (sleepable) context during driver probe, not wrapped in a DO_ONCE macro that disables preemption. Verify the fix by confirming the BUG message no longer appears and the system boots to login prompt successfully on lemans-evk.
  4. Detail analysis attachment: failed_case_job279641_1_detailed.md
  Case 2: Boot Hang — System hung during early boot after kernel BUG warning; login prompt never appeared
  1. Failed case: Boot Hang — System hung during early boot after kernel BUG warning; login prompt never appeared
  2. Root cause: System hung at ~6.4 seconds into boot (after systemd-udevd start, during device initialization) following a non-fatal kernel BUG warning "BUG: sleeping function called from invalid context at drivers/firmware/qcom/qcom_scm.c:320" in qcom_scm_probe(). The BUG indicates qcom_scm_call() was invoked with preemption disabled (in_atomic=1, irqs_disabled=1) during qcom_tzmem_enable() → qcom_scm_shm_bridge_enable() path. This is a pre-existing kernel issue (PR only modifies README). The system continued past the BUG but hung silently during subsequent device probe (likely PCIe or UFS initialization on lemans-evk), producing no further console output.
  3. Possible fix: This is a pre-existing kernel bug, not introduced by PR Update README test commit #1445 (which only changes README). The qcom_scm sleeping-in-atomic bug should be fixed by ensuring qcom_scm_call() is not invoked from atomic context during probe. The boot hang may be a separate issue (device driver hang during probe) or a consequence of the corrupted state from the BUG. Recommended actions: (1) Re-trigger the CI job to confirm reproducibility; (2) If reproducible, investigate the qcom_scm atomic context violation (likely introduced by recent qcom_tzmem changes); (3) Add debug instrumentation to identify which device probe is hanging after the 6.4s mark (PCIe PHY or UFS controller are prime suspects based on last log messages).
  4. Detail analysis attachment: failed_case_job279641_2_detailed.md
  Case 3: ** Kernel Boot Hang — System freeze during UFS driver initialization
  1. Failed case: ** Kernel Boot Hang — System freeze during UFS driver initialization
  2. Root cause: ** The kernel hangs during UFS driver probe at approximately 6.4 seconds into boot on lemans-evk. The hang occurs after a "BUG: sleeping function called from invalid context" warning in qcom_scm during early boot (at 3.14s), where qcom_scm_call() is invoked with preemption disabled and IRQs disabled (in_atomic(): 1, irqs_disabled(): 1) from qcom_tzmem_enable() → qcom_scm_shm_bridge_enable() path. While the kernel continues past this BUG warning, the system subsequently hangs with no console output after the UFS driver begins initialization, never reaching the login prompt. The PR changes only README and does not introduce this issue — this is a pre-existing kernel or platform integration problem on lemans-evk.
  3. Possible fix: This is NOT a PR-introduced regression (PR only modifies README). The failure is a pre-existing kernel issue on lemans-evk. Recommended actions: (1) Re-trigger the CI job to confirm reproducibility; (2) If reproducible, investigate the qcom_scm atomic context violation — the __do_once_start path that disables preemption before calling SCM may need rework to avoid sleeping in atomic context; (3) Investigate why UFS probe hangs after the SCM warning — check if the SCM call corruption or incomplete initialization causes downstream UFS/storage subsystem to stall; (4) Check if lemans-evk requires platform-specific DT or firmware updates for stable UFS operation; (5) If this is a known lemans-evk instability, consider marking this board/test as expected-fail or flaky in CI until the kernel fix is merged.
  4. Detail analysis attachment: failed_case_job279641_3_detailed.md
  Case 4: ** Complete System Hang — UFS driver initialization
  1. Failed case: ** Complete System Hang — UFS driver initialization
  2. Root cause: ** lemans-evk board hung during UFS controller initialization at [6.392246] in ufshcd-qcom driver probe, causing complete loss of console output and LAVA login timeout. This is a platform-specific hardware/firmware interaction issue, not caused by the PR (which only changes README).
  3. Possible fix: Re-trigger the CI job on lemans-evk. If the hang recurs, investigate lemans-evk board-specific UFS firmware/hardware state, check for known UFS controller errata on this SoC, verify UFS device connectivity, and collect SDI/watchdog logs to capture CPU state at hang time. Consider testing on a different lemans-evk board to rule out hardware failure.
  4. Detail analysis attachment: failed_case_job279641_4_detailed.md
Job 279642 | SoC qcs615-ride

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

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

  Case 1: Build Load Failure — Board hardware not accessible (debugboard.py serial lookup failure)
  1. Failed case: Build Load Failure — Board hardware not accessible (debugboard.py serial lookup failure)
  2. Root cause: Result: Build Load Failure. The LAVA deploy-flasher action failed because the debugboard.py script could not locate the qcs615-ride board with serial number 98000207100D0224. The exact error is "ValueError: Could not find the board with Serial number: 98000207100D0224". This is a LAVA lab infrastructure issue — the board is either physically disconnected, powered off, or the debug board USB connection is not enumerated on the LAVA worker host.
  3. Possible fix: Report this infrastructure failure to LAVA admins to verify the qcs615-ride board (serial 98000207100D0224) is physically connected, powered, and its debug board USB interface is enumerated on the LAVA worker. Once the board is reconnected and verified accessible via debugboard.py, re-trigger the CI job. This failure is unrelated to PR Update README test commit #1445 (which only modifies README).
  4. Detail analysis attachment: failed_case_job279642_1_detailed.md
  Case 2: ** Build Load Failure — Board hardware not accessible via debugboard.py
  1. Failed case: ** Build Load Failure — Board hardware not accessible via debugboard.py
  2. Root cause: ** Result: Build Load Failure. The qcs615-ride board (serial 98000207100D0224) is not accessible to the LAVA worker's debugboard.py control interface. The deploy-flasher action failed with ValueError: Could not find the board with Serial number: 98000207100D0224 before any flashing attempt could begin. This is a LAVA lab infrastructure issue, not a kernel or build artifact problem.
  3. Possible fix: Check physical connectivity of the qcs615-ride board to the LAVA worker: verify USB debug board connection is intact, confirm board is powered and responsive, and validate the serial number mapping in LAVA device configuration. If the board is offline or disconnected, reconnect it and re-trigger the CI job. If the serial number is incorrect, update the LAVA device dictionary for this board.
  4. Detail analysis attachment: failed_case_job279642_2_detailed.md
  Case 3: Build Load Failure — Debugboard hardware connection failure during deploy-flasher
  1. Failed case: Build Load Failure — Debugboard hardware connection failure during deploy-flasher
  2. Root cause: Result: Build Load Failure. The LAVA dispatcher failed to power off the qcs615-ride board (serial 98000207100D0224) before flashing because the debugboard.py script could not establish a connection to the debug board hardware. The exact error is "ValueError: Could not find the board with Serial number: 98000207100D0224".
  3. Possible fix: This is a LAVA lab infrastructure issue, not a kernel or build artifact problem. The debug board with serial number 98000207100D0224 is either physically disconnected, powered off, or not enumerated on the LAVA worker's USB bus. Contact LAVA lab administrators to verify the debug board hardware connection and USB enumeration on the worker node. If the board is confirmed connected, check if the debugboard.py script's device enumeration logic needs updating for this board type (tac).
  4. Detail analysis attachment: failed_case_job279642_3_detailed.md
  Case 4: Build Load Failure — Flasher deployment failure (debugboard hardware not found)
  1. Failed case: Build Load Failure — Flasher deployment failure (debugboard hardware not found)
  2. Root cause: Result: Build Load Failure. The LAVA deploy-flasher action failed because the debugboard.py script could not find the qcs615-ride board with serial number 98000207100D0224. Error: "ValueError: Could not find the board with Serial number: 98000207100D0224". This is a LAVA infrastructure issue — the board is either offline, disconnected, or the serial number is incorrect in the LAVA job definition. The build artifacts downloaded successfully (999MB image + 36MB test binaries), but the job failed before flashing could begin.
  3. Possible fix: Verify the qcs615-ride board with serial 98000207100D0224 is powered on, connected to the LAVA worker, and accessible via debugboard.py. If the board is offline or unavailable, re-trigger the CI job when the board is back online. If the serial number is incorrect, update the LAVA device dictionary or job definition with the correct serial number. This is a lab infrastructure issue, not a kernel or PR-introduced regression.
  4. Detail analysis attachment: failed_case_job279642_4_detailed.md
Job 279643 | SoC qcs9100-ride

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

Failed test cases in LAVA job 279643 (SoC: qcs9100-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: These are pre-existing qcs9100-ride platform issues not introduced by this PR (PR only modifies README). No action required for this PR. To fix the underlying platform issues: (1) Add nvmem cell "reboot-mode" to qcs9100 device tree tcsr node, (2) Include regulatory.db in rootfs firmware directory (optional — system functions without it), (3) Add "firmware-name" property to Aquantia PHY device tree node at stmmac-0:08 or mark as optional if PHY firmware is not required for this board configuration.
  4. Detail analysis attachment: failed_case_job279643_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: Video codec device aa00000.video-codec on qcs9100-ride is not attached to an IOMMU group, failing the test's critical master protection validation. This is a pre-existing device tree or driver configuration issue, not introduced by the PR (which only modifies README).
  3. Possible fix: This is a false failure for PR validation purposes — the PR does not touch video codec, IOMMU, or device tree code. The test should be updated to exclude qcs9100 video codec from critical master checks until the platform's device tree properly configures IOMMU bindings for this device, or the video codec driver is updated to request IOMMU attachment.
  4. Detail analysis attachment: failed_case_job279643_2_detailed.md
  Case 3: ** Driver Probe Failure — Ethernet PHY (Aquantia AQR115C)
  1. Failed case: ** Driver Probe Failure — Ethernet PHY (Aquantia AQR115C)
  2. Root cause: ** The Aquantia AQR115C PHY driver probe fails with -EINVAL because the device tree for qcs9100-ride is missing the required firmware-name property in the PHY node at MDIO address 0x08 on the stmmac-0 bus. This causes the Ethernet MAC driver (qcom-ethqos 23040000.ethernet) to fail attaching to the PHY, preventing interface end0 from being brought up administratively.
  3. Possible fix: Add the firmware-name property to the Aquantia AQR115C PHY device tree node in arch/arm64/boot/dts/qcom/qcs9100-ride.dtsi (or the appropriate DTS file for this platform). The property should specify the correct firmware file path for the AQR115C PHY, typically firmware-name = "Rhe-05.06-Candidate9-AQR_Mediatek_23B_P5_ID45824_LCLVER1.cld"; or the appropriate firmware file available in /lib/firmware/. Rebuild the DTB and reflash the platform.
  4. Detail analysis attachment: failed_case_job279643_3_detailed.md
  Case 4: LAVA Job External Cancellation — 0_qcom-next-ci-premerge-tests
  1. Failed case: LAVA Job External Cancellation — 0_qcom-next-ci-premerge-tests
  2. Root cause: The LAVA job was externally canceled by the LAVA infrastructure or an administrator while the BT_SCAN test was initializing, after running successfully for 357 seconds (6 minutes) with the kernel fully booted and 30+ tests completed; this is not a kernel crash, test failure, or PR-introduced issue.
  3. Possible fix: Re-trigger the CI job; if cancellations recur on this board (qcs9100-ride), investigate LAVA worker health, board availability conflicts, or job queue priority issues with the LAVA administrator.
  4. Detail analysis attachment: failed_case_job279643_4_detailed.md
  Case 5: ** LAVA Infrastructure Issue — External Job Cancellation
  1. Failed case: ** LAVA Infrastructure Issue — External Job Cancellation
  2. Root cause: ** The LAVA job was externally canceled (error_type: "Canceled") at 15:49:50 UTC while the BT_SCAN test was initializing, after only 10.24 minutes of execution and with all prior tests passing normally; this is a LAVA operational/infrastructure cancellation, not a kernel crash, build failure, or hardware issue.
  3. Possible fix: Re-trigger the LAVA job; if cancellation recurs at similar timing, investigate CI orchestration timeout policies, check for manual cancellation in LAVA scheduler logs, and verify no resource contention or lab infrastructure issues caused premature job termination.
  4. Detail analysis attachment: failed_case_job279643_5_detailed.md
  Case 6: lava-test-retry
  1. Failed case: lava-test-retry
  2. Root cause: LAVA job was externally canceled after exactly 10 minutes of runtime (15:39:50 to 15:49:50 UTC), hitting a global job timeout limit while BT_SCAN test was initializing.
  3. Possible fix: Increase the LAVA job timeout from 10 minutes to at least 15-20 minutes in the job definition to allow the full test suite to complete; the job was making normal progress and had not encountered any kernel or test failures when canceled.
  4. Detail analysis attachment: failed_case_job279643_6_detailed.md
  Case 7: LAVA Job Timeout — BT_SCAN test hang due to qcom_scm atomic context violation
  1. Failed case: LAVA Job Timeout — BT_SCAN test hang due to qcom_scm atomic context violation
  2. Root cause: The BT_SCAN test hung indefinitely after selecting Bluetooth adapter hci0, causing the LAVA job to reach its 10-minute timeout and be canceled. The underlying cause is a qcom_scm atomic context violation ("BUG: sleeping function called from invalid context at drivers/firmware/qcom/qcom_scm.c:320") that affects Bluetooth operations requiring SCM calls.
  3. Possible fix: This is a pre-existing kernel bug unrelated to the PR (which only modifies README). The qcom_scm atomic context violation must be fixed by ensuring qcom_scm_call() is not invoked from atomic context. Specifically, review the call path in qcom_scm_shm_bridge_enable() and qcom_scm_probe() to ensure proper context. As an immediate workaround, re-trigger the CI job to verify if the hang is reproducible; if it recurs consistently, disable the BT_SCAN test until the qcom_scm bug is resolved.
  4. Detail analysis attachment: failed_case_job279643_7_detailed.md
Job 279644 | SoC purwa-evk

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

Failed test cases in LAVA job 279644 (SoC: purwa-evk).

  Case 1: LAVA Infrastructure Issue — External Job Cancellation
  1. Failed case: LAVA Infrastructure Issue — External Job Cancellation
  2. Root cause: The LAVA job was externally canceled by the CI system or infrastructure after running for only 10.43 minutes (well under the 50-minute job timeout). The kernel booted successfully, all completed tests passed (cdsp_remoteproc, adsp_remoteproc, CPUFreq_Validation), and the GIC test had just started initialization when the job was terminated with error message "The job was canceled" (error_type: "Canceled"). This is not a kernel issue or test failure — the PR only modifies the README file and cannot affect runtime behavior.
  3. Possible fix: This is a LAVA infrastructure or CI orchestration issue, not a kernel regression. Recommended actions: (1) Check LAVA job queue and worker status for resource constraints or scheduling issues on purwa-evk-01. (2) Review CI system logs to determine why the job was canceled prematurely — check for concurrent job limits, worker health checks, or manual cancellation events. (3) Re-trigger the job to verify if this is a transient infrastructure issue. If the issue recurs, investigate LAVA dispatcher logs and CI orchestration layer for the root cause of premature cancellation.
  4. Detail analysis attachment: failed_case_job279644_1_detailed.md
  Case 2: LAVA Job External Cancellation
  1. Failed case: LAVA Job External Cancellation
  2. Root cause: The LAVA job was externally canceled by a user or system administrator at 15:50:11 UTC, approximately 10 seconds after the lava-test-shell action started (15:50:01 UTC) and while the GIC test was initializing. The kernel booted successfully (Linux version 6.18.56-03454-g958ab489cc9d present at boot), all prior tests passed (CPUFreq_Validation: PASS), and the GIC test had just begun execution when the cancellation signal was received. The error_type "Canceled" and message "The job was canceled" indicate manual intervention, not a timeout (test timeout was 39:53, only 10 seconds elapsed).
  3. Possible fix: This is not a kernel or PR-introduced issue. The PR changes only the README file and cannot cause a LAVA job cancellation. Re-trigger the LAVA CI job to complete the test suite. If cancellations recur on this board (purwa-evk), investigate whether there is a lab policy, resource contention, or manual intervention pattern causing premature job termination. Check LAVA job queue priority and board reservation status.
  4. Detail analysis attachment: failed_case_job279644_2_detailed.md
  Case 3: lava-test-retry
  1. Failed case: lava-test-retry
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Re-trigger the LAVA job. This failure is not caused by the PR (which only modifies README) and does not indicate any kernel regression. If the job continues to be canceled prematurely, investigate the CI automation or LAVA job scheduler for premature cancellation logic (e.g., resource contention, queue management policies, or manual intervention).
  4. Detail analysis attachment: failed_case_job279644_3_detailed.md
  Case 4: LAVA Job Timeout — Test shell timeout too short (10s)
  1. Failed case: LAVA Job Timeout — Test shell timeout too short (10s)
  2. Root cause: The LAVA job was canceled because the test shell timeout was configured to only 10 seconds (minimum of action and connection timeout), and the GIC test did not produce console output within this window, triggering an automatic cancellation by the LAVA dispatcher.
  3. Possible fix: Increase the test shell timeout in the LAVA job definition by adjusting the connection timeout or action timeout to allow tests sufficient time to complete without requiring continuous console output. A minimum of 60-120 seconds is recommended for baseport tests that may have periods of computation without output.
  4. Detail analysis attachment: failed_case_job279644_4_detailed.md
Job 279645 | SoC monaco-evk

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

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

  Case 1: Probe_Failure_Check — Firmware Load Failures (Pre-existing Infrastructure Issue)
  1. Failed case: Probe_Failure_Check — Firmware Load Failures (Pre-existing Infrastructure Issue)
  2. Root cause: The Probe_Failure_Check test detected 5 firmware load failures (regulatory.db, Bluetooth firmware files, and ath11k WiFi firmware) and one ath11k_pci probe timeout (-110) on monaco-evk. These failures are pre-existing infrastructure issues unrelated to the PR, which only modifies the README file and cannot affect driver probe or firmware loading behavior.
  3. Possible fix: No action required for this PR. The firmware files are missing from the rootfs image deployed to monaco-evk. To resolve the underlying infrastructure issue: (1) add the missing firmware files (regulatory.db, qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv, ath11k/WCN6855/hw2.1/nfa765/amss.bin) to the linux-firmware package in the Yocto build recipe for monaco-evk, or (2) suppress this test case for monaco-evk if WiFi/Bluetooth hardware is not present or not expected to be functional on this platform variant.
  4. Detail analysis attachment: failed_case_job279645_1_detailed.md
  Case 2: 0_qcom-next-ci-premerge-tests
  1. Failed case: 0_qcom-next-ci-premerge-tests
  2. Root cause: LAVA job was externally canceled during test execution (error_type: Canceled) while the Ethernet_Basic_Validation test was in progress; the kernel booted successfully and 19 tests passed before cancellation occurred at 15:50:00 UTC, approximately 5 minutes into the test phase.
  3. Possible fix: Re-trigger the LAVA job; this is a LAVA infrastructure cancellation (not a kernel issue or test failure) — the job was terminated externally, likely due to lab resource constraints, scheduler timeout, or manual intervention. If recurs, investigate LAVA job queue priority and lab resource availability for monaco-evk boards.
  4. Detail analysis attachment: failed_case_job279645_2_detailed.md
  Case 3: lava-test-shell (LAVA Job Cancellation - Infrastructure)
  1. Failed case: lava-test-shell (LAVA Job Cancellation - Infrastructure)
  2. Root cause: The LAVA job was externally canceled at 15:50:00 UTC while the Ethernet_Basic_Validation test was in progress (ping test running successfully). The cancellation occurred after 5 minutes and 4 seconds of test execution, with error_type: "Canceled" indicating manual or policy-driven job termination, not a kernel crash or test failure.
  3. Possible fix: Re-trigger the LAVA job. This is not a kernel regression - the PR only modifies README documentation and cannot cause functional failures. If job cancellations recur on this board (monaco-evk, serial NP37P51A0037), investigate LAVA lab policies for job timeout limits or check if the board is being manually canceled for maintenance/reallocation.
  4. Detail analysis attachment: failed_case_job279645_3_detailed.md
  Case 4: lava-test-retry — External Job Cancellation
  1. Failed case: lava-test-retry — External Job Cancellation
  2. Root cause: The LAVA job was externally canceled at 15:50:00 UTC after running for 9.66 minutes total (5.07 minutes in test phase), interrupting the Ethernet_Basic_Validation test during a ping operation. The cancellation was not triggered by a kernel crash, test failure, or timeout within the test phase (which had a 40-minute limit). Evidence: "The job was canceled" exception at 15:50:00.111856, test phase duration 303.95 seconds (well under the 40-minute timeout), and Ethernet test showing normal progress (2 successful ping responses received before cancellation).
  3. Possible fix: This is not a PR-introduced issue (PR only modifies README). Re-trigger the CI job. If cancellations recur at ~10 minutes, investigate the LAVA dispatcher/scheduler for a global job timeout setting (distinct from per-action timeouts) or check for manual cancellation triggers in the CI pipeline. The monaco-evk board and kernel are functioning correctly.
  4. Detail analysis attachment: failed_case_job279645_4_detailed.md
  Case 5: job
  1. Failed case: job
  2. Root cause: LAVA job was administratively canceled at 15:50:00 UTC after running for approximately 10 minutes; cancellation occurred during the Ethernet_Basic_Validation test while executing a ping connectivity check to gateway 10.143.232.1. This is not a kernel crash, test failure, or build load issue — the error_type "Canceled" indicates an external LAVA infrastructure action (likely job timeout or manual cancellation).
  3. Possible fix: Re-trigger the LAVA job. If the issue recurs, investigate the LAVA job timeout configuration — the job may need a longer timeout window, or check if there is a lab-side policy causing premature cancellation of jobs on the monaco-evk target. The PR changes (README documentation only) cannot cause this failure.
  4. Detail analysis attachment: failed_case_job279645_5_detailed.md
Job 279646 | SoC qcs8300-ride

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

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

  Case 1: Driver Probe Failure — xHCI Host Controller Timeout & Regulatory Firmware Missing
  1. Failed case: Driver Probe Failure — xHCI Host Controller Timeout & Regulatory Firmware Missing
  2. Root cause: Two pre-existing platform issues on qcs8300-ride: (1) xhci-hcd.0.auto probe failed with -110 (ETIMEDOUT) after 18-second timeout during controller setup, indicating USB host controller hardware not responding or power/clock dependencies not met; (2) cfg80211 regulatory.db firmware file missing from rootfs (-2 ENOENT), a non-critical WiFi regulatory database used for region-specific channel restrictions.
  3. Possible fix: For xhci-hcd timeout: Investigate qcs8300-ride USB host controller power sequencing, clock enablement, and PHY initialization in device tree; verify USB_VBUS GPIO configuration and regulator supplies; check if USB host mode is supported on this platform variant or if only device/OTG mode is available. For regulatory.db: Install wireless-regdb package in rootfs or suppress this benign firmware warning if WiFi regulatory enforcement is not required for this test configuration.
  4. Detail analysis attachment: failed_case_job279646_1_detailed.md
  Case 2: USBHost — xHCI Host Controller Probe Failure
  1. Failed case: USBHost — xHCI Host Controller Probe Failure
  2. Root cause: xHCI host controller driver probe failed with -ETIMEDOUT (-110) during controller setup on qcs8300-ride platform; the xHCI hardware did not respond within the expected timeout window during initialization, preventing USB root hub enumeration and causing both runtime validation and lsusb enumeration to fail.
  3. Possible fix: This is a pre-existing platform issue unrelated to PR Update README test commit #1445 (which only modifies README). Investigate qcs8300-ride xHCI controller power/clock/reset dependencies: verify USB PHY initialization completed successfully, confirm all required clocks and regulators for the xHCI controller at address xhci-hcd.0.auto are enabled and stable, check device tree for correct xHCI node configuration (clocks, resets, power-domains), and review platform-specific xHCI quirks or initialization sequences required for qcs8300. If the issue persists across multiple CI runs on this SoC, consider increasing xHCI setup timeout or adding platform-specific initialization delays in the xHCI platform driver for qcs8300.
  4. Detail analysis attachment: failed_case_job279646_2_detailed.md
  Case 3: 0_qcom-next-ci-premerge-tests (LAVA Job Timeout/Cancellation)
  1. Failed case: 0_qcom-next-ci-premerge-tests (LAVA Job Timeout/Cancellation)
  2. Root cause: LAVA job was canceled after the Ethernet_Basic_Validation test hung for 33 seconds while waiting for link-up on eth0 interface (carrier=0, operstate=down). The job exceeded its allocated test execution time budget and was terminated by the LAVA infrastructure. The underlying issue is a pre-existing xHCI USB host controller probe failure (error -110, ETIMEDOUT) on qcs8300-ride platform, unrelated to the PR's README-only change.
  3. Possible fix: Re-trigger the CI job. The xHCI probe failure (error -110) and Ethernet link timeout are known pre-existing platform/infrastructure issues on qcs8300-ride that are not introduced by this PR (which only modifies README). If the Ethernet test continues to time out, increase the LAVA job timeout from the current limit or skip the Ethernet_Basic_Validation test for this platform until the underlying link-up issue is resolved.
  4. Detail analysis attachment: failed_case_job279646_3_detailed.md
  Case 4: lava-test-shell
  1. Failed case: lava-test-shell
  2. Root cause: LAVA job was externally canceled by the CI system or user while the Ethernet_Basic_Validation test was waiting for link establishment on eth0 (carrier=0, operstate=down). The test was waiting for a physical Ethernet link that was not present on the qcs8300-ride board, and the job hit an external timeout/cancellation before the test's internal timeout could trigger.
  3. Possible fix: This is not a kernel regression (PR only changes README). The failure is due to missing Ethernet cable on the test board or an external job cancellation. To prevent recurrence: (1) ensure Ethernet cable is connected to qcs8300-ride board before running Ethernet tests, or (2) skip Ethernet_Basic_Validation test in the LAVA job definition for boards without Ethernet connectivity, or (3) increase the LAVA job timeout if the cancellation was due to overall job duration limits.
  4. Detail analysis attachment: failed_case_job279646_4_detailed.md
  Case 5: lava-test-retry
  1. Failed case: lava-test-retry
  2. Root cause: LAVA job was externally canceled by the CI infrastructure while the Ethernet_Basic_Validation test was actively running and waiting for eth0 link-up (carrier=0 operstate=down), approximately 33 seconds into the test execution.
  3. Possible fix: Re-trigger the LAVA job — this is a CI infrastructure cancellation, not a kernel or test failure; the PR (README-only change) cannot cause this behavior, and all prior tests (including shmbridge, RMNET, IPA, smmu) passed successfully before cancellation.
  4. Detail analysis attachment: failed_case_job279646_5_detailed.md
  Case 6: LAVA Job Timeout/Cancellation — Ethernet test hang
  1. Failed case: LAVA Job Timeout/Cancellation — Ethernet test hang
  2. Root cause: The LAVA job was canceled after the Ethernet_Basic_Validation test hung for 33+ seconds while attempting to bring up the eth0 interface (carrier=0, operstate=down), likely waiting for link establishment or DHCP that never completed, triggering the LAVA test timeout and subsequent job cancellation.
  3. Possible fix: This is not a PR-introduced regression (PR only modifies README). The Ethernet test hang is a pre-existing infrastructure or board connectivity issue. Recommended actions: (1) Verify physical Ethernet cable is connected to the qcs8300-ride board; (2) Check if the network switch port is active; (3) If this is a known lab infrastructure issue, add the Ethernet_Basic_Validation test to the suppression list or increase LINK_TIMEOUT_S from 10s to 30s in the test configuration; (4) Re-trigger the CI job to confirm if the issue is transient.
  4. Detail analysis attachment: failed_case_job279646_6_detailed.md

@qcomlnxci

Copy link
Copy Markdown

Test results

Workflow run: 44073731654 attempt 1

Known failures configured: 46

Target Pass Non-pass Total
kbdev-hamoa-iot-evk-multimedia 29 7 36
kbdev-lemans-evk-multimedia 33 3 36
kbdev-monaco-evk-multimedia 32 4 36
kbdev-purwa-iot-evk-multimedia 23 8 31
kbdev-qcs615-ride-multimedia
kbdev-qcs6490-rb3gen2-multimedia
kbdev-qcs8300-ride-multimedia 30 6 36
kbdev-qcs9100-ride-r3-multimedia 29 7 36
kbdev-qrb2210-rb1-multimedia - ⛔ Not submitted -
kbdev-shikra-iqs-evk-multimedia 21 15 36

Test Matrix

Test Case kbdev-hamoa-iot-evk-multimedia kbdev-lemans-evk-multimedia kbdev-monaco-evk-multimedia kbdev-purwa-iot-evk-multimedia kbdev-qcs615-ride-multimedia kbdev-qcs6490-rb3gen2-multimedia kbdev-qcs8300-ride-multimedia kbdev-qcs9100-ride-r3-multimedia kbdev-qrb2210-rb1-multimedia kbdev-shikra-iqs-evk-multimedia
LAVA result ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ⛔ Not submitted ✅ Results
Audio_Card_Registration ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ⚠️ skip ⚠️ skip ⛔ Not submitted ⚠️ skip
BT_FW_KMD_Service ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_ON_OFF ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_SCAN ✅ Pass ✅ Pass ❌ Fail ❌ Fail ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
CPUFreq_Validation ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
CPU_affinity ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
DSP_AudioPD ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
Ethernet_Basic_Validation ⚠️ skip ⚠️ skip ✅ Pass ⚠️ skip ◻️ ◻️ ⚠️ skip ❌ Fail ⛔ Not submitted ❌ Fail
Freq_Scaling ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
GIC ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
IPA ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Interrupts ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
KVM_Driver ❌ Fail ✅ Pass ✅ Pass ❌ Fail ◻️ ◻️ ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
KVM_EL2_DTB ❌ Fail ✅ Pass ✅ Pass ❌ Fail ◻️ ◻️ ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
KVM_Infra ❌ Fail ✅ Pass ✅ Pass ❌ Fail ◻️ ◻️ ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
OpenCV ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
PCIe ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
Probe_Failure_Check ❌ Fail ❌ Fail ❌ Fail ❌ Fail ◻️ ◻️ ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
RMNET ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
UFS_Validation ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
USBHost ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
WiFi_Firmware_Driver ✅ Pass ✅ Pass ❌ Fail ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
WiFi_OnOff ✅ Pass ✅ Pass ❌ Fail ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
adsp_remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
cdsp_remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
gpdsp_remoteproc ⚠️ skip ✅ Pass ✅ Pass ⚠️ skip ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
hotplug ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
irq ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
kaslr ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
pinctrl ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
qcom_hwrng ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
rngtest ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
shmbridge ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
smmu ❌ Fail ❌ Fail ✅ Pass ❌ Fail ◻️ ◻️ ✅ Pass ❌ Fail ⛔ Not submitted ✅ Pass
watchdog ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
wpss_remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Failure summary

Known failures

  • kbdev-hamoa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-hamoa-iot-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-hamoa-iot-evk-multimedia: smmu => fail.
  • kbdev-hamoa-iot-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-hamoa-iot-evk-multimedia: KVM_Driver => fail.
  • kbdev-hamoa-iot-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-hamoa-iot-evk-multimedia: KVM_Infra => fail.
  • kbdev-lemans-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-lemans-evk-multimedia: smmu => fail.
  • kbdev-monaco-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-monaco-evk-multimedia: WiFi_Firmware_Driver => fail.
  • kbdev-monaco-evk-multimedia: WiFi_OnOff => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_Infra => fail.
  • kbdev-purwa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-purwa-iot-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-purwa-iot-evk-multimedia: smmu => fail.
  • kbdev-purwa-iot-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-purwa-iot-evk-multimedia: KVM_Driver => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs8300-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs8300-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs9100-ride-r3-multimedia: smmu => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Driver => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Infra => fail.
  • kbdev-shikra-iqs-evk-multimedia: adsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: GIC => fail.
  • kbdev-shikra-iqs-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-shikra-iqs-evk-multimedia: UFS_Validation => skip.
  • kbdev-shikra-iqs-evk-multimedia: PCIe => fail.
  • kbdev-shikra-iqs-evk-multimedia: USBHost => fail.
  • kbdev-shikra-iqs-evk-multimedia: WiFi_OnOff => skip.
  • kbdev-shikra-iqs-evk-multimedia: DSP_AudioPD => skip.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Driver => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Infra => fail.

Unexpected failures

  • kbdev-lemans-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-monaco-evk-multimedia: BT_SCAN => fail.
  • kbdev-purwa-iot-evk-multimedia: BT_SCAN => fail.
  • kbdev-qcs8300-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs9100-ride-r3-multimedia: Audio_Card_Registration => skip.
  • kbdev-qrb2210-rb1-multimedia did not produce a LAVA result artifact.
  • kbdev-shikra-iqs-evk-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-shikra-iqs-evk-multimedia: BT_SCAN => fail.
  • kbdev-shikra-iqs-evk-multimedia: Audio_Card_Registration => skip.

Result: blocked because unexpected failures were found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants