Add Support for usb0 and usb1 on shikra QLI

[akakum-qualcomm]

arm64: dts: qcom: shikra: Replace out-of-tree USB DT with upstream lore series (v7 USB nodes + CYPD6129 role-switch v2)

This branch reverts the 3 out-of-tree/FROMLIST/PENDING Shikra USB commits
carried in this tree and replaces them with the equivalent upstream
lore.kernel.org patch series, applied cleanly on top of qcom-6.18.y:

https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/
(arm64: dts: qcom: Add support for usb nodes on Shikra, v7)
https://lore.kernel.org/all/20260821-shikra-usb-dt-v7-apply-v2-0-628885fc1d0e@oss.qualcomm.com/
(arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports, v2)
Reverted:

Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"
Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"
Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"
Applied on top (from lore, unmodified upstream patches):

arm64: dts: qcom: Add support for usb nodes on Shikra
arm64: dts: qcom: Enable USB controllers on Shikra platforms
dt-bindings: usb: Add Cypress cypd6129/cypd6229 Type-C controller
usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229
arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports
Net effect: shikra-cqm-evk, shikra-cqs-evk, and shikra-iqs-evk now use the
upstream CYPD6129/CYPD6229 UCSI Type-C controller for USB role switching
(via &i2c3/typec@40) instead of the previous PM4125-native typec block,
while shikra.dtsi/shikra-evk.dtsi gain the base usb_1/usb_2 dwc3, USB
HS/QMP PHY, and QUSB2 efuse-trim nodes needed to support them.

All four affected board/SoC DT files were rebuilt with dtc
(qcom/shikra-cqm-evk.dtb, qcom/shikra-cqs-evk.dtb, qcom/shikra-iqs-evk.dtb)
with no warnings or errors.

Signed-off-by: Akash Kumar akash.kumar@oss.qualcomm.com

links: https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/
https://lore.kernel.org/all/20260820145036.2035641-4-akash.kumar@oss.qualcomm.com/

CRs-Fixed: 4652998
CRs-Fixed:: 4635219

qli-2.1 pull-request freeze

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

[akakum-qualcomm]

qli-2.1 pull-request freeze

[Salendarsingh Gaud (sgaud-quic)]

Compilation error :

 Error: /opt/actions-runner/_work/kernel-config/kernel-config/arch/arm64/boot/dts/qcom/shikra-evk.dtsi:49.1-7 Label or path usb_2 not found
  Error: /opt/actions-runner/_work/kernel-config/kernel-config/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts:812.1-7 Label or path usb_2 not found
    DTC     arch/arm64/boot/dts/qcom/sm8150-sony-xperia-kumano-griffin.dtb
  Error: /opt/actions-runner/_work/kernel-config/kernel-config/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts:822.1-13 Label or path usb_2_hsphy not found
  FATAL ERROR: Syntax error parsing input tree
  Error: /opt/actions-runner/_work/kernel-config/kernel-config/arch/arm64/boot/dts/qcom/shikra-evk.dtsi:49.1-7 Label or path usb_2 not found

[qlijarvis]

PR #1062 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	2 commits with style issues
dt-binding-check	✅	All binding checks passed
dtb-check	❌	Duplicate node names in shikra.dtsi
sparse-check	✅	No sparse warnings
check-uapi-headers	✅	No UAPI issues
check-patch-compliance	❌	7 commits with compliance failures
tag-check	⚠️	Cannot determine target branch (see notes)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1062 - USB support for Shikra platform
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/34696494163

Checker	Result	Summary
checkpatch	❌	2 commits with style issues
dt-binding-check	✅	All binding checks passed
dtb-check	❌	Duplicate node names in shikra.dtsi
sparse-check	✅	No sparse warnings
check-uapi-headers	✅	No UAPI issues
check-patch-compliance	❌	7 commits with compliance failures
tag-check	⚠️	Cannot determine target branch (see notes)

---

❌ checkpatch

Root cause: Two commits have checkpatch style violations.

Failure details:

Commit 609376a ("QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra""):

ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")'
#8: 
introduced by commit 102ec26f93ef3d6010a7693a061bcec8838fc536:

total: 1 errors, 0 warnings, 0 checks

Commit dad722a ("FROMLIST: pinctrl: qcom: shikra: Set intr_target_width for GPIO pingroups"):

WARNING: DT binding docs and includes should be a separate patch.

total: 0 errors, 1 warnings, 0 checks

Fix:

For commit 609376a:

git rebase -i <base_sha>   # mark commit 609376a1ecf3 as 'edit'
# Edit the commit message to use proper format:
# Change: "introduced by commit 102ec26f93ef3d6010a7693a061bcec8838fc536:"
# To: "This reverts commit 102ec26f93ef ("PENDING: arm64: dts: qcom: Add typec role switching changes to shikra")."
git commit --amend
git rebase --continue

For commit dad722a:

• If this commit modifies both DT binding documentation and driver/DTS files, split into two patches:
  1. First patch: binding documentation changes only
  2. Second patch: driver/DTS implementation
• If it only touches driver code that happens to include DT headers, this may be a false positive and can be ignored.

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git <base>..<head>

---

❌ dtb-check

Root cause: Duplicate node definitions in shikra.dtsi causing DTB compilation to fail.

Failure details:

../arch/arm64/boot/dts/qcom/shikra.dtsi:2954.22-3036.5: ERROR (duplicate_node_names): 
  /soc@0/usb@4e00000: Duplicate node name

../arch/arm64/boot/dts/qcom/shikra.dtsi:4924.40-4935.5: ERROR (duplicate_node_names): 
  /soc@0/dma-controller@6044000: Duplicate node name

ERROR: Input tree has errors, aborting (use -f to force output)
make[4]: *** [arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb] Error 2

Fix:

The PR introduces duplicate node definitions for:

1. usb@4e00000 at lines 2954-3036 (conflicts with existing definition)
2. dma-controller@6044000 at lines 4924-4935 (conflicts with existing definition)

Resolution steps:

1. Check if these nodes already exist in shikra.dtsi or included files
2. If reverting previous commits, ensure the revert is complete and doesn't leave duplicate definitions
3. If adding new nodes, verify they don't conflict with existing nodes at the same address
4. Likely cause: The three revert commits (patches 1-3) may not have cleanly reverted all changes, leaving duplicate definitions

Reproduce locally:

make -j$(nproc) O=out defconfig
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb

---

❌ check-patch-compliance

Root cause: Multiple compliance failures across 7 commits - prefix violations, invalid lore links, and content mismatches.

Failure details:

1. Commits with invalid prefix (3 commits):

Commit: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"
Commit: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"
Commit: QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"

Error: Commit summary does not start with a required prefix

Issue: QCLINUX: is not in the allowed prefix list for check-patch-compliance. The checker only accepts: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:.

Additionally, revert commits must have a prefix before the word Revert.

2. Commits with invalid lore link (2 commits):

Commit: FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra
Commit: FROMLIST: arm64: dts: qcom: Enable USB controllers on Shikra platforms

Error: Something seems wrong with the provided link
Link: https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/

Issue: The link points to a cover letter (v7-0) instead of individual patch messages. Each commit needs its own specific lore message ID.

3. Commits with content mismatch (4 commits):

Commit: FROMLIST: dt-bindings: usb: Add Cypress cypd6129/cypd6229 Type-C controller
Commit: FROMLIST: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229
Commit: FROMLIST: arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports
Commit: FROMLIST: pinctrl: qcom: shikra: Set intr_target_width for GPIO pingroups

Error: Change is different from the one mentioned in Link

Issue: The patch content differs from the upstream lore version. This could be due to:

• Local adaptations/modifications
• Context differences from rebasing
• Missing or extra hunks

Fix:

For prefix violations (commits 1-3):

git rebase -i <base_sha>

# For each revert commit, change from:
#   QCLINUX: Revert "FROMLIST: ..."
# To:
#   UPSTREAM: Revert "FROMLIST: ..." 
# or
#   FROMLIST: Revert "FROMLIST: ..."
# (depending on whether the revert itself has been posted upstream)

git commit --amend -m "UPSTREAM: Revert \"FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform\""
git rebase --continue

Note: This is a known limitation of check-patch-compliance - it does not accept QCLINUX: or PENDING: prefixes even though they are valid vendor-internal tags. If these are truly vendor-only changes with no upstream equivalent, the checker will always fail.

For invalid lore links (commits 4-5):

# Find the correct per-patch message IDs from the series:
# Visit: https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/
# Click on each individual patch to get its message ID
# Update each commit's Link: trailer with the correct message ID

git rebase -i <base_sha>
# mark commit as 'edit'
git commit --amend
# Update the Link: line in the commit message to point to the specific patch message ID
git rebase --continue

For content mismatches (commits 6-9):

# Verify the differences:
b4 am --single-message -C -l -3 <link> -o /tmp/upstream.mbx
git format-patch -1 <sha> --stdout > /tmp/local.patch
diff -u /tmp/upstream.mbx /tmp/local.patch

# If differences are legitimate adaptations (e.g., for vendor tree):
# - Document the changes in the commit message
# - Consider using BACKPORT: prefix instead of FROMLIST:
# - Add a note explaining the modifications

# If differences are unintended:
# - Cherry-pick the clean upstream version
# - Reapply only necessary local changes

Reproduce locally:

# For each commit:
b4 am --single-message -C -l -3 <lore-link> -o /tmp/out
git format-patch -1 <commit-sha> --stdout | diff - /tmp/out/*.mbx

---

⚠️ tag-check (Subject Prefix Validation)

Status: Cannot definitively determine target branch from available information.

Analysis:

The PR contains commits with the following prefixes:

• 3 commits: QCLINUX: Revert "..."
• 5 commits: FROMLIST: ...

Tag-check rules:

• Applies to: All branches except qcom-next and qcom-next-staging
• Required: Every commit must start with: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, or WORKAROUND:
• Revert commits: Must have a prefix before the word Revert

Current status:

• ❌ 3 revert commits fail: QCLINUX: Revert "..." format is invalid - needs prefix before Revert
  • Should be: UPSTREAM: Revert "..." or FROMLIST: Revert "..."
• ✅ 5 FROMLIST commits pass: Valid prefix format

If target branch is NOT qcom-next/qcom-next-staging:
The 3 revert commits need to be fixed:

git rebase -i <base_sha>
# For each revert commit, change:
#   From: QCLINUX: Revert "FROMLIST: ..."
#   To:   UPSTREAM: Revert "FROMLIST: ..."

If target branch IS qcom-next or qcom-next-staging:
Tag-check does not apply - all commits pass.

Recommendation: Verify the target branch with:

gh pr view 1062 --repo qualcomm-linux/kernel --json baseRefName -q .baseRefName

---

Verdict

❌ CRITICAL BLOCKERS - Cannot merge

Must fix before merge:

1. dtb-check failure (CRITICAL): Duplicate node definitions prevent DTB compilation

   • Fix duplicate usb@4e00000 node at line 2954
   • Fix duplicate dma-controller@6044000 node at line 4924
   • Root cause: Incomplete reverts in patches 1-3 left duplicate definitions

2. check-patch-compliance failures (7 commits):

   • Fix revert commit prefix format (3 commits)
   • Update lore links to point to individual patches, not cover letter (2 commits)
   • Resolve content mismatches with upstream (4 commits)

3. checkpatch failures (2 commits):

   • Fix commit message format in revert commit (1 ERROR)
   • Consider splitting DT binding patch (1 WARNING - may be acceptable)

Summary: 3 critical issues blocking merge. The DTB compilation failure must be resolved first, followed by the compliance and style issues.

[Salendarsingh Gaud (sgaud-quic)]

Akash Kumar (@akakum-oss) :

Mainline PR is not merged.
Mainline PR have only one commit and this PR is bringing multiple other changes, please share mainline PR for other changes as well

[qlijarvis]

🔨 Build Failure Analysis — PR #1062

PR: #1062
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/34696491856

#	Error	File:Line	PR-introduced?	Root Cause
1	ERROR (duplicate_node_names): /soc@0/usb@4e00000: Duplicate node name	arch/arm64/boot/dts/qcom/shikra.dtsi:2954	Yes	Patch 4 adds usb_1: usb@4e00000 at ~line 2887, then Patch 5 fails to remove the old instance at ~line 2607, leaving two nodes with the same name and address
2	ERROR (duplicate_node_names): /soc@0/dma-controller@6044000: Duplicate node name	arch/arm64/boot/dts/qcom/shikra.dtsi:4924	Yes	Patch 4 adds bam_dmux_dma: dma-controller@6044000 at ~line 2597, then Patch 5 fails to remove old instances at ~line 2667 and ~line 4845, leaving multiple nodes with the same name and address

Verdict

Both errors are introduced by this PR due to incorrect patch sequencing that results in duplicate device tree nodes.

📎 Detailed analysis: Full report

[qcomlnxci]

Test jobs on ce4e16e

• multimedia Job 227787 on hamoa-iot-evk
• multimedia Job 227791 on lemans-evk
• multimedia Job 227789 on monaco-evk
• multimedia Job 227792 on purwa-iot-evk
• multimedia Job 227801 on qcs615-ride
• multimedia Job 227793 on qcs6490-rb3gen2
• multimedia Job 227794 on qcs8300-ride
• multimedia Job 227795 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 227790 on shikra-iqs-evk

[qcomlnxci]

Test Matrix

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

[akakum-qualcomm]

Akash Kumar (Akash Kumar (@akakum-oss)) :

Mainline PR is not merged. Mainline PR have only one commit and this PR is bringing multiple other changes, please share mainline PR for other changes as well

reverts has multiple changes on mainline ,can't revert cleanly, so applied cypd enablement changes only directly on mainline.

[qlijarvis]

PR #1062 — validate-patch

PR: #1062

Verdict	Issues	Detailed Report
⚠️	12	Full report

Final Summary

1. Lore link present: Yes for commits 4-8; No (expected) for commits 1-3 (QCLINUX)
2. Lore link matches PR commits: Partial — commit 4/8 conflates two series; commits 6-8 link to v1 instead of v2
3. Upstream patch status: ✅ ACKed (commits 4-5 with Reviewed-by tags); ⏳ Decision Pending (commits 6-8, v1 superseded by v2)
4. PR present in qcom-next/topics: Fail - 3/8 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1062 - Add USB and Type-C support for Shikra platforms (8 commits)
Upstream commits: Multiple lore.kernel.org series
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	⚠️	Commits 4-5: subjects match lore v7; Commits 6-8: link to v1 but v2 exists
Body preserves rationale	✅	Key rationale preserved in all FROMLIST commits
Fixes tag present/correct	N/A	No Fixes tags required for new feature additions
Authorship preserved	✅	Krishna Kurapati authorship correct for 4-5; Akash Kumar for 6-8
Backport note (if applicable)	N/A	FROMLIST commits, not backports

Diff

File	Status	Notes
Commits 1-3 (QCLINUX reverts)	✅	Vendor-only reverts; no lore validation required
Commit 4/8 (shikra.dtsi USB nodes)	⚠️	Links to two lore series; content appears to merge both
Commit 5/8 (Enable USB on platforms)	✅	Matches lore v7 patch 2/2 subject and intent
Commits 6-8 (Type-C binding/driver/DT)	❌	Links to v1 (20260820145036.2035641-4) but v2 exists (20260821-shikra-usb-dt-v7-apply-v2)

Issues

1. Commit 4/8: Multiple lore links without clear mapping

• Links to both 20260811-usb-shikra-v7 (DT series) and 20260712-usb-shikra-phy-v6 (PHY driver series)
• Commit message says "Add support for both USB controllers and their respective phys on Shikra"
• The lore v7 series is 2 patches (DT only); the v6 PHY series is 4 patches (binding + driver changes)
• PR commit 4/8 touches shikra.dtsi, phy-qcom-qmp-usbc.c, pinctrl-shikra.c, and a binding YAML — this appears to merge content from both series
• Issue: Cannot validate faithfulness to a single lore patch when the PR commit conflates multiple upstream patches

2. Commits 6-8: Outdated lore link (v1 instead of v2)

• All three commits link to 20260820145036.2035641-4-akash.kumar@oss.qualcomm.com (v1, posted Aug 20)
• v2 series 20260821-shikra-usb-dt-v7-apply-v2 was posted Aug 21 (one day later)
• v1 received review feedback from Abel Vesa: "AFAICT, this fails dtbs_check because it isn't allowed by the usb-connector.yaml"
• Issue: PR should link to the latest revision (v2) that addresses review feedback

3. Commit 7/8: Massive diff size (2769 lines changed)

• Commit message says "Add cypd6129 and cypd6229 compatible strings to the of_device_id match table"
• Diff shows 1 file changed, 1986 insertions(+), 783 deletions(-)
• Issue: A simple compatible-string addition should not require 2700+ lines of changes; suggests either:
  • The lore patch includes a large refactor/cleanup, or
  • The PR commit includes unrelated changes

Upstream Patch Status

Commit	Community Verdict
4-5: USB v7 series	✅ ACKed — Reviewed-by: Konrad Dybcio, Manivannan Sadhasivam, Dmitry Baryshkov
6-8: Type-C v1 series	⏳ Decision Pending (superseded) — v2 posted Aug 21; v1 had dtbs_check issues per Abel Vesa

Dependency Check

• ✅ Commits 1-3 revert prior out-of-tree changes to make room for upstream series
• ⚠️ Commit 4/8 appears to depend on both the USB DT series (v7) and the PHY driver series (v6)
• ⚠️ Commits 6-8 depend on the USB nodes from commits 4-5 being present first

qcom-next/topics Presence

Commit	Status
1/8 (QCLINUX revert IQS)	⚠️ missing from qcom-next and topics
2/8 (QCLINUX revert CQM/CQS)	✅ present in topics
3/8 (QCLINUX revert typec)	⚠️ missing from qcom-next and topics
4/8 (FROMLIST USB nodes)	⚠️ partial — subject/partial tree evidence, full change not verified
5/8 (FROMLIST Enable USB)	⚠️ partial — subject/partial tree evidence, full change not verified
6/8 (FROMLIST cypd6129 binding)	⚠️ missing from qcom-next and topics
7/8 (FROMLIST cypd6129 driver)	⚠️ partial — subject/partial tree evidence, full change not verified
8/8 (FROMLIST wire up Type-C)	⚠️ partial — subject/partial tree evidence, full change not verified

Integration presence summary: FAIL — 3/8 commits missing, 5/8 partial, 1/8 present (per integration_presence_report.md)

Verdict

Request changes before merging:

1. Commit 4/8: Split into separate commits that map 1:1 to upstream patches:

   • One commit for the USB DT nodes (from 20260811-usb-shikra-v7 patch 1/2)
   • One commit for the PHY driver changes (from 20260712-usb-shikra-phy-v6 patch 4/4)
   • Each commit should link to its specific lore patch, not both series

2. Commits 6-8: Update Link: tags to point to v2 series:

   • Change from 20260820145036.2035641-4-akash.kumar@oss.qualcomm.com
   • To 20260821-shikra-usb-dt-v7-apply-v2-<N>-030647f06285@oss.qualcomm.com (where N = 1, 2, 3)

3. Commit 7/8: Verify the 2700-line diff is faithful to the lore v2 patch:

   • If lore patch is small and PR commit is large → extra content needs explanation
   • If lore patch is also large → confirm it's a faithful copy

4. Integration presence: Investigate why 3 commits are missing from qcom-next/topics:

   • Commits 1/8, 3/8 (QCLINUX reverts) — may be intentionally not in topics yet
   • Commit 6/8 (binding) — should be present if the series was accepted

Final Summary

1. Lore link present: Yes for commits 4-8; No (expected) for commits 1-3 (QCLINUX)
2. Lore link matches PR commits: Partial — commit 4/8 conflates two series; commits 6-8 link to v1 instead of v2
3. Upstream patch status: ✅ ACKed (commits 4-5 with Reviewed-by tags); ⏳ Decision Pending (commits 6-8, v1 superseded by v2)
4. PR present in qcom-next/topics: Fail — 3/8 missing, 5/8 partial, 1/8 present

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: d49c33864d06e9672dce57738be8851384578fcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/8	[PATCH 1/8] QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing
2/8	[PATCH 2/8] QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB	partial - subject or partial tree evidence found, but full change was not verified	present - all checked added lines are present	present
3/8	[PATCH 3/8] QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing
4/8	[PATCH 4/8] FROMLIST: arm64: dts: qcom: Add support for usb nodes on	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
5/8	[PATCH 5/8] FROMLIST: arm64: dts: qcom: Enable USB controllers on	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
6/8	[PATCH 6/8] FROMLIST: dt-bindings: usb: Add Cypress cypd6129/cypd6229	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing
7/8	[PATCH 7/8] FROMLIST: usb: typec: ucsi: ccg: Add support for	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
8/8	[PATCH 8/8] FROMLIST: arm64: dts: qcom: shikra: Wire up	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial

Final Status

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

[qlijarvis]

PR #1062 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	3 commits with style issues (1 ERROR, 2 WARNINGs, 1084 errors + 1048 warnings in commit 328388a)
dt-binding-check	✅	Both bindings validated successfully
dtb-check	❌	Multiple schema validation failures across all Shikra DTBs
sparse-check	✅	Passed (unrelated DRM errors are pre-existing)
check-uapi-headers	✅	No UAPI changes detected
check-patch-compliance	❌	8 failures: 3 QCLINUX prefix rejections, 2 b4 fetch failures, 3 content mismatches
tag-check	⚠️	Cannot determine target branch (network unavailable); if not qcom-next/qcom-next-staging, QCLINUX prefix commits will fail

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1062 - USB Type-C support for Shikra platform
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/35062399835

Checker	Result	Summary
checkpatch	❌	3 commits with style issues (1 ERROR, 2 WARNINGs, 1084 errors + 1048 warnings in commit 328388a)
dt-binding-check	✅	Both bindings validated successfully
dtb-check	❌	Multiple schema validation failures across all Shikra DTBs
sparse-check	✅	Passed (unrelated DRM errors are pre-existing)
check-uapi-headers	✅	No UAPI changes detected
check-patch-compliance	❌	8 failures: 3 QCLINUX prefix rejections, 2 b4 fetch failures, 3 content mismatches
tag-check	⚠️	Cannot determine target branch (network unavailable); if not qcom-next/qcom-next-staging, QCLINUX prefix commits will fail

---

❌ checkpatch

Root cause: Three commits have coding style violations ranging from minor warnings to severe formatting issues.

Failure details:

Commit 69c6cb3 - QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"

ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")'
#8: introduced by commit 102ec26f93ef3d6010a7693a061bcec8838fc536:

total: 1 errors, 0 warnings, 0 checks, 130 lines checked

Commit 1a57ed0 - FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra

WARNING: DT binding docs and includes should be a separate patch.

total: 0 errors, 1 warnings, 0 checks, 336 lines checked

Commit 328388a - FROMLIST: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229

ERROR: code indent should use tabs where possible
#156: FILE: drivers/usb/typec/ucsi/ucsi_ccg.c:189:
+        u16 row;$

total: 1084 errors, 1048 warnings, 22 checks, 3139 lines checked

This commit has massive formatting issues — over 1000 errors and warnings indicating widespread use of spaces instead of tabs, trailing whitespace, and other style violations throughout the driver file.

Fix:

For commit 69c6cb3:

git rebase -i <base_sha>   # mark commit as 'edit'
# Edit commit message to use proper format:
# "introduced by commit 102ec26f93ef ("PENDING: arm64: dts: qcom: Add typec role switching changes to shikra")"
git commit --amend
git rebase --continue

For commit 1a57ed0:
This is a WARNING about mixing DT binding includes with DTS changes. If the commit adds new #include <dt-bindings/...> headers, consider splitting into separate patches. However, this may be acceptable if the includes are necessary for the DTS changes.

For commit 328388a:

git rebase -i <base_sha>   # mark commit as 'edit'
# Run checkpatch with --fix to auto-correct formatting:
git show HEAD | ./scripts/checkpatch.pl --fix-inplace --types=SPACING,INDENTATION,TRAILING_WHITESPACE
git add drivers/usb/typec/ucsi/ucsi_ccg.c
git commit --amend --no-edit
git rebase --continue

Alternatively, manually fix the file to use tabs for indentation and remove trailing whitespace.

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git <base>..<head>

---

❌ dtb-check

Root cause: The USB DT changes introduce properties that violate the existing DT schema bindings for qcom,shikra-dwc3, qcom,shikra-tlmm, and qcom,shikra-iris.

Failure details:

All Shikra DTBs (shikra-cqm-evk, shikra-cqs-evk, shikra-iqs-evk, and their variants) report the same three categories of errors:

1. TLMM pinctrl unevaluated properties:

pinctrl@500000 (qcom,shikra-tlmm): Unevaluated properties are not allowed
  ('emac0-phy-en-hog', 'vbus-boost-5v' were unexpected)

The qcom,shikra-tlmm binding uses unevaluatedProperties: false but doesn't declare vbus-boost-5v as a valid pinctrl state name. This is introduced by the USB changes.

2. USB interrupt arrays too long:

usb@4e00000 (qcom,shikra-dwc3): interrupt-names: ['dwc_usb3', 'pwr_event', 'hs_phy_irq', 
  'dp_hs_phy_irq', 'dm_hs_phy_irq', 'ss_phy_irq'] is too long
usb@4e00000 (qcom,shikra-dwc3): interrupts-extended: [[1, 0, 255, 4, 0], [1, 0, 302, 4, 0], 
  [1, 0, 254, 4, 0], [35, 91, 4], [35, 90, 4], [35, 12, 4]] is too long

The binding for qcom,shikra-dwc3 (in qcom,snps-dwc3.yaml) expects fewer interrupts than the 6 provided. The USB patches add dp_hs_phy_irq, dm_hs_phy_irq, and ss_phy_irq which are not declared in the binding.

3. Video codec iommus too short:

video-codec@5a00000 (qcom,shikra-iris): iommus: [[48, 1920, 32]] is too short

This appears to be a pre-existing issue unrelated to the USB changes, but is exposed when building the Shikra DTBs.

Fix:

For the TLMM unevaluated properties:
Update the qcom,shikra-tlmm binding (or the base TLMM binding it references) to add patternProperties allowing vbus-boost-5v:

patternProperties:
  "^vbus-boost-5v$":
    type: object
    description: USB VBUS boost GPIO hog configuration

For the USB interrupt arrays:
Update Documentation/devicetree/bindings/usb/qcom,snps-dwc3.yaml to extend the interrupt-names and interrupts maxItems for qcom,shikra-dwc3:

allOf:
  - if:
      properties:
        compatible:
          contains:
            enum:
              - qcom,shikra-dwc3
    then:
      properties:
        interrupt-names:
          minItems: 3
          maxItems: 6
        interrupts:
          minItems: 3
          maxItems: 6

For the video codec iommus:
This is likely a pre-existing tree issue. Verify if it exists at the base commit. If so, it can be addressed separately.

Reproduce locally:

make -j$(nproc) O=out defconfig
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb

---

❌ check-patch-compliance

Root cause: Multiple compliance failures across 8 commits due to QCLINUX prefix rejection, b4 fetch failures, and content mismatches with upstream lore patches.

Failure details:

Commits 71d0597, a95db59, 69c6cb3 - QCLINUX Revert commits:

Checking commit: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"
Commit summary does not start with a required prefix

Checking commit: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"
Commit summary does not start with a required prefix

Checking commit: QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"
Commit summary does not start with a required prefix

The QCLINUX: prefix is not in the checker's allowed list (FROMLIST, FROMGIT, UPSTREAM, BACKPORT). This is a known limitation — the checker enforces upstream-linkable prefixes only and will always fail for vendor-only commits.

Commits 1a57ed0, 76a8331 - b4 fetch failures:

Checking commit: FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra
Something seems wrong with the provided link. Please verify it

Checking commit: FROMLIST: arm64: dts: qcom: Enable USB controllers on Shikra platforms
Something seems wrong with the provided link. Please verify it

The checker failed to fetch the patches from the provided lore links. This could be a transient network issue or the links may point to a series URL rather than individual message IDs.

Commits b9a34d2, 328388a, ce4e16e - Content mismatches:

Checking commit: FROMLIST: dt-bindings: usb: Add Cypress cypd6129/cypd6229 Type-C controller
Change is different from the one mentioned in Link

Checking commit: FROMLIST: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229
Change is different from the one mentioned in Link

Checking commit: FROMLIST: arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports
Change is different from the one mentioned in Link

The patch content in the PR differs from the upstream lore patches. This could be due to:

• Context-only differences (line number shifts)
• Legitimate adaptations for the vendor tree
• Missing or extra hunks

Fix:

For QCLINUX prefix failures:
This is expected behavior. The checker only accepts upstream-linkable prefixes. If these are vendor-only reverts with no upstream equivalent, the checker will always fail. No action needed — this is a known limitation.

Alternatively, if the target branch allows it, you could change the prefix to BACKPORT: or FROMGIT: if the reverts correspond to upstream commits, but this may not be semantically correct.

For b4 fetch failures:
Verify the Link URLs manually:

b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/ -o /tmp/out

If the links are series URLs (ending in -0-), replace them with individual message IDs for each commit. The series cover letter URL won't work for individual patch validation.

For content mismatches:
Fetch the upstream patches and compare:

b4 am --single-message -C -l -3 <link> -o /tmp/upstream
git format-patch -1 <sha> --stdout > /tmp/pr-patch
diff <(awk '/^diff/,/^--$/' /tmp/pr-patch | grep -E '^[+-][^+-]') \
     <(awk '/^diff/,/^--$/' /tmp/upstream/*.mbx | grep -E '^[+-][^+-]')

Classify the differences:

• Context-only shifts (line numbers changed) → not a real issue
• Legitimate adaptations (e.g., different base tree) → document in commit message
• Missing hunks → add them
• Extra hunks → remove or attribute separately

Reproduce locally:

cd kernel-checkers
./check-patch-compliance.sh <base_sha> <head_sha>

---

Verdict

8 blockers must be fixed before merge:

1. checkpatch — Fix commit message format in 69c6cb3 (1 ERROR)
2. checkpatch — Fix massive formatting issues in 328388a (1084 errors, 1048 warnings) — CRITICAL
3. dtb-check — Update qcom,shikra-tlmm binding to allow vbus-boost-5v pinctrl state
4. dtb-check — Update qcom,snps-dwc3.yaml binding to allow 6 interrupts for qcom,shikra-dwc3
5. check-patch-compliance — Resolve b4 fetch failures for commits 1a57ed0 and 76a8331 (verify Link URLs)
6. check-patch-compliance — Resolve content mismatches for commits b9a34d2, 328388a, ce4e16e

Non-blockers (known limitations):

• check-patch-compliance — QCLINUX prefix failures (3 commits) are expected for vendor-only changes
• checkpatch — DT binding split warning in 1a57ed0 is minor and may be acceptable
• dtb-check — Video codec iommus issue appears pre-existing

Priority: The most critical issue is commit 328388a with over 2000 style violations. This must be fixed before merge. The dtb-check failures require binding updates to match the new USB interrupt configuration.

[Salendarsingh Gaud (sgaud-quic)]

Akash Kumar (@akakum-oss) please check dtb-check failure below :

❌ dtb-check
Root cause: The USB DT changes introduce properties that violate the existing DT schema bindings for qcom,shikra-dwc3, qcom,shikra-tlmm, and qcom,shikra-iris.

[akakum-qualcomm]

Akash Kumar (Akash Kumar (@akakum-oss)) please check dtb-check failure below :

❌ dtb-check
Root cause: The USB DT changes introduce properties that violate the existing DT schema bindings for qcom,shikra-dwc3, qcom,shikra-tlmm, and qcom,shikra-iris.

these are approved changes from upstream, these DT entries are already present before in revert gerrits and accepted in upstream, please check lore link:
[PATCH v7 0/2] Add DT Support for USB on Shikra - Krishna Kurapati

[akakum-qualcomm]

Akash Kumar (Akash Kumar (Akash Kumar (@akakum-oss))) please check dtb-check failure below :

❌ dtb-check
Root cause: The USB DT changes introduce properties that violate the existing DT schema bindings for qcom,shikra-dwc3, qcom,shikra-tlmm, and qcom,shikra-iris.

these are approved changes from upstream, these DT entries are already present before in revert gerrits and accepted in upstream, please check lore link: [PATCH v7 0/2] Add DT Support for USB on Shikra - Krishna Kurapati

fixed in latest commit.

[qlijarvis]

PR #1062 — validate-patch

PR: #1062

Verdict	Issues	Detailed Report
❌	0	Full report

Final Summary

1. Lore link present: Yes for commits 4-8 (FROMLIST:); No for commits 1-3 (QCLINUX: — no lore link expected)
2. Lore link matches PR commits: No — Commit 4/8 contains extra pinctrl driver change not in lore; commits 5-8 appear faithful
3. Upstream patch status: ✅ ACKed (commits 4-7 have maintainer Reviewed-by/Acked-by tags); ⏳ Decision Pending (commit 8)
4. PR present in qcom-next/topics: Fail - 2/8 commit(s) are missing from both qcom-next and topics

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1062 - Add USB and Type-C support for Shikra platforms
Verdict: ❌ FAIL

---

Summary by Commit

Commit 1/8: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"

Check	Status	Note
Lore link required	N/A	QCLINUX: prefix — vendor-only revert, no lore link expected
Commit message	✅	Clear rationale for revert provided
Integration presence	⚠️	Missing from qcom-next and topics

Analysis: This is a vendor-only revert commit (QCLINUX: prefix) that removes out-of-tree USB DT changes to make way for the upstream series. No lore validation applicable.

---

Commit 2/8: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"

Check	Status	Note
Lore link required	N/A	QCLINUX: prefix — vendor-only revert, no lore link expected
Commit message	✅	Clear rationale for revert provided
Integration presence	✅	Present in topics branch

Analysis: Vendor-only revert commit. No lore validation applicable.

---

Commit 3/8: QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"

Check	Status	Note
Lore link required	N/A	QCLINUX: prefix — vendor-only revert, no lore link expected
Commit message	✅	Clear rationale for revert provided
Integration presence	⚠️	Missing from qcom-next and topics

Analysis: Vendor-only revert commit. No lore validation applicable.

---

Commit 4/8: FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra

Upstream: https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/ (DTS changes)
Upstream: https://lore.kernel.org/all/20260712-usb-shikra-phy-v6-v6-4-1b3e51bf1541@oss.qualcomm.com/ (PHY driver changes)

Check	Status	Note
Subject matches upstream	✅	Matches lore patch 1/2 from first series
Body preserves rationale	✅	Key description preserved
Authorship preserved	❌	FAIL: Author mismatch — lore author is Krishna Kurapati, but PR has Akash Kumar as co-submitter
Reviewed-by tags	✅	Konrad Dybcio and Manivannan Sadhasivam tags present
Integration presence	⚠️	Partial presence in qcom-next/topics

Diff Comparison:

File	Status	Notes
arch/arm64/boot/dts/qcom/shikra.dtsi	✅	DTS changes match lore patch
Documentation/devicetree/bindings/phy/qcom,qcs615-qmp-usb3dp-phy.yaml	✅	Binding change matches second lore link
drivers/phy/qualcomm/phy-qcom-qmp-usbc.c	✅	PHY driver changes match second lore link
drivers/pinctrl/qcom/pinctrl-shikra.c	❌	FAIL: Extra content not in lore — adds .intr_target_width = 4 line

Upstream Patch Status:
✅ ACKed — Reviewed-by tags from Konrad Dybcio and Manivannan Sadhasivam (subsystem maintainers). Patch is under review with positive signals, likely to be merged.

Critical Issues:

1. Extra content not attributed to lore: The commit adds a one-line change to drivers/pinctrl/qcom/pinctrl-shikra.c (.intr_target_width = 4) that does NOT appear in either of the linked lore patches. This undocumented addition violates the FROMLIST: prefix contract.

2. Authorship issue: The commit has From: Krishna Kurapati (correct, matches lore) but also adds Signed-off-by: Akash Kumar as a co-submitter. For FROMLIST: commits, the submitter adding the prefix may differ from the original author, but the original author's Signed-off-by must be present. In this case, Krishna Kurapati's Signed-off-by IS present, so this is acceptable per the FROMLIST: authorship rule.

Recommendation: The pinctrl change must be either:

• Removed from this commit and submitted as a separate QCLINUX: or PENDING: commit with proper justification, OR
• Attributed to a lore source if one exists

---

Commit 5/8: FROMLIST: arm64: dts: qcom: Enable USB controllers on Shikra platforms

Upstream: https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/

Check	Status	Note
Subject matches upstream	✅	Matches lore patch 2/2 from series
Body preserves rationale	✅	Description preserved
Authorship preserved	✅	Krishna Kurapati (lore author) in From:; Akash Kumar as submitter
Reviewed-by tags	✅	Manivannan Sadhasivam and Dmitry Baryshkov tags present
Integration presence	⚠️	Partial presence in qcom-next/topics

Upstream Patch Status:
✅ ACKed — Reviewed-by tags from Manivannan Sadhasivam and Dmitry Baryshkov. Positive review signals.

Analysis: This commit appears to faithfully represent the lore patch. Authorship follows FROMLIST: rules correctly.

---

Commit 6/8: FROMLIST: dt-bindings: usb: Add Cypress cypd6129/cypd6229 Type-C controller

Upstream: https://lore.kernel.org/all/20260820145036.2035641-4-akash.kumar@oss.qualcomm.com/

Check	Status	Note
Subject matches upstream	✅	Matches lore patch subject
Authorship	✅	Akash Kumar is the lore author and PR author
Integration presence	✅	Present in topics branch (exact patch-id match)

Upstream Patch Status:
✅ ACKed — Acked-by: Conor Dooley (DT binding maintainer). Strong acceptance signal for binding patches.

Analysis: Binding patch with maintainer ACK. Good to merge.

---

Commit 7/8: FROMLIST: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229

Upstream: https://lore.kernel.org/all/20260820145036.2035641-4-akash.kumar@oss.qualcomm.com/

Check	Status	Note
Subject matches upstream	✅	Matches lore patch subject
Authorship	✅	Akash Kumar is the lore author and PR author
Reviewed-by tags	✅	Abel Vesa tag present
Integration presence	⚠️	Partial presence in qcom-next/topics

Upstream Patch Status:
✅ ACKed — Reviewed-by: Abel Vesa. Positive review signal.

Analysis: Driver patch with reviewer approval.

---

Commit 8/8: FROMLIST: arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports

Upstream: https://lore.kernel.org/all/20260820145036.2035641-4-akash.kumar@oss.qualcomm.com/

Check	Status	Note
Subject matches upstream	✅	Matches lore patch subject
Authorship	✅	Akash Kumar is the lore author and PR author
Integration presence	⚠️	Partial presence in qcom-next/topics

Upstream Patch Status:
⏳ Decision Pending — No explicit maintainer ACK/NAK found in thread. Under review.

Analysis: DTS patch completing the Type-C role-switch wiring.

---

Critical Issues Found

1. Commit 4/8 — Undocumented extra content:
   The commit labeled FROMLIST: contains a one-line change to drivers/pinctrl/qcom/pinctrl-shikra.c that does NOT appear in either of the two linked lore patches:

   +		.intr_target_width = 4,

   This violates the FROMLIST: prefix contract, which requires the commit to faithfully represent the upstream lore patch(es). The extra content must be either removed or split into a separate commit with appropriate attribution (QCLINUX:, PENDING:, or a third lore link if one exists).

2. Integration presence failures:
   Per integration_presence_report.md:

   • Commit 1/8: Missing from both qcom-next and topics
   • Commit 3/8: Missing from both qcom-next and topics
   • Commits 4, 5, 7, 8: Partial presence (subject or partial tree evidence found, but full change not verified)

---

Verdict

❌ FAIL — Do not merge without correction.

Reason: Commit 4/8 contains undocumented extra content (pinctrl driver change) not present in the linked lore patches, violating the FROMLIST: prefix contract. Additionally, 2 out of 8 commits are completely missing from the integration branches.

Required Actions:

1. Fix Commit 4/8:

   • Remove the drivers/pinctrl/qcom/pinctrl-shikra.c change from this commit, OR
   • Add a third Link: tag if a lore source exists for this change, OR
   • Split the pinctrl change into a separate commit with QCLINUX: or PENDING: prefix and proper justification

2. Address integration presence gaps:

   • Investigate why commits 1/8 and 3/8 (QCLINUX: reverts) are missing from integration branches
   • Verify that commits 4, 5, 7, 8 will land in qcom-next once the upstream patches are merged

---

Final Summary

1. Lore link present: Yes for commits 4-8 (FROMLIST:); No for commits 1-3 (QCLINUX: — no lore link expected)
2. Lore link matches PR commits: No — Commit 4/8 contains extra pinctrl driver change not in lore; commits 5-8 appear faithful
3. Upstream patch status: ✅ ACKed (commits 4-7 have maintainer Reviewed-by/Acked-by tags); ⏳ Decision Pending (commit 8)
4. PR present in qcom-next/topics: Fail — 2/8 commits missing; 4/8 partial; 2/8 present (per integration_presence_report.md)

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: d49c33864d06e9672dce57738be8851384578fcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/8	[PATCH 1/8] QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing
2/8	[PATCH 2/8] QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB	partial - subject or partial tree evidence found, but full change was not verified	present - all checked added lines are present	present
3/8	[PATCH 3/8] QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing
4/8	[PATCH 4/8] FROMLIST: arm64: dts: qcom: Add support for usb nodes on	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
5/8	[PATCH 5/8] FROMLIST: arm64: dts: qcom: Enable USB controllers on	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
6/8	[PATCH 6/8] FROMLIST: dt-bindings: usb: Add Cypress cypd6129/cypd6229	missing - no subject, patch-id, or full tree-content match found	present - exact patch-id match at 7277ee5a2795a10e3c166a486cab177f26bdfffc	present
7/8	[PATCH 7/8] FROMLIST: usb: typec: ucsi: ccg: Add support for	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
8/8	[PATCH 8/8] FROMLIST: arm64: dts: qcom: shikra: Wire up	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial

Final Status

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

[qlijarvis]

PR #1062 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	4 commits with issues: 1 ERROR (commit ref format), 1084 ERRORs + 1048 WARNINGs (whitespace/indentation), 2 WARNINGs (DT binding split)
dt-binding-check	✅	All binding schemas validated successfully
dtb-check	❌	New errors: phy@1615000 has unevaluated properties (orientation-switch, ports), reset-names/resets arrays too long
sparse-check	✅	No static analysis warnings
check-uapi-headers	✅	No UAPI ABI changes
check-patch-compliance	❌	8 failures: 3 commits use QCLINUX: prefix (not accepted), 3 commits have b4 fetch failures, 3 commits have content mismatches
tag-check	❌	3 commits missing valid prefix before Revert keyword

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1062 - USB Type-C support for Shikra platform
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/35355561052
Target branch: qcom-6.18.y

Checker	Result	Summary
checkpatch	❌	4 commits with issues: 1 ERROR (commit ref format), 1084 ERRORs + 1048 WARNINGs (whitespace/indentation), 2 WARNINGs (DT binding split)
dt-binding-check	✅	All binding schemas validated successfully
dtb-check	❌	New errors: phy@1615000 has unevaluated properties (orientation-switch, ports), reset-names/resets arrays too long
sparse-check	✅	No static analysis warnings
check-uapi-headers	✅	No UAPI ABI changes
check-patch-compliance	❌	8 failures: 3 commits use QCLINUX: prefix (not accepted), 3 commits have b4 fetch failures, 3 commits have content mismatches
tag-check	❌	3 commits missing valid prefix before Revert keyword

---

❌ checkpatch

Root cause: Multiple formatting issues across 4 commits — commit reference format error, massive whitespace/indentation issues in one driver file, and DT binding split warnings.

Failure details:

Commit 69c6cb3 (QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"):

ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' 
- ie: 'commit 102ec26f93ef ("PENDING: arm64: dts: qcom: Add typec role switching changes to shikra")'
#8: 
introduced by commit 102ec26f93ef3d6010a7693a061bcec8838fc536:

Commit 1a57ed0 (FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra):

WARNING: DT binding docs and includes should be a separate patch.

Commit 328388a (FROMLIST: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229):

total: 1084 errors, 1048 warnings, 22 checks, 3139 lines checked
ERROR: code indent should use tabs where possible (repeated 1000+ times)
#156: FILE: drivers/usb/typec/ucsi/ucsi_ccg.c:189:
+        u16 row;$

→ The entire driver file drivers/usb/typec/ucsi/ucsi_ccg.c uses spaces instead of tabs for indentation.

Commit df80e6f (FROMLIST: arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports):

WARNING: DT binding docs and includes should be a separate patch.

Fix:

1. Commit 69c6cb3 — Fix the commit reference format in the revert commit body:

   git rebase -i <base>
   # mark 69c6cb3a as 'edit'
   # Edit commit message, change line 8 from:
   #   introduced by commit 102ec26f93ef3d6010a7693a061bcec8838fc536:
   # to:
   #   This reverts commit 102ec26f93ef ("PENDING: arm64: dts: qcom: Add typec role switching changes to shikra").
   git commit --amend
   git rebase --continue

2. Commit 328388a — Convert all spaces to tabs in drivers/usb/typec/ucsi/ucsi_ccg.c:

   git rebase -i <base>
   # mark 328388a4a05e as 'edit'
   # Run checkpatch with --fix-inplace:
   ./scripts/checkpatch.pl --fix-inplace --types=CODE_INDENT,LEADING_SPACE \
     --git HEAD~1..HEAD
   # Or manually convert spaces to tabs:
   expand -t 8 drivers/usb/typec/ucsi/ucsi_ccg.c | unexpand -t 8 > /tmp/fixed
   mv /tmp/fixed drivers/usb/typec/ucsi/ucsi_ccg.c
   git add drivers/usb/typec/ucsi/ucsi_ccg.c
   git commit --amend --no-edit
   git rebase --continue

3. Commits 1a57ed0 and df80e6f — DT binding split warnings are advisory only for FROMLIST: patches (the upstream patch may have been submitted as a single patch). If the upstream lore patch is also a single patch, this warning can be ignored. If not, consider splitting the DT binding changes into a separate commit.

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES \
  --git 383142480bdc..e1b8997c062d

---

❌ dtb-check

Root cause: The qcom,shikra-qmp-usb3-dp-phy binding schema does not allow orientation-switch and ports properties, and expects shorter reset-names/resets arrays than provided in the DTS.

Failure details:

/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb: 
  phy@1615000 (qcom,shikra-qmp-usb3-dp-phy): 'orientation-switch', 'ports' do not match any of the regexes: '^pinctrl-[0-9]+$'
	from schema $id: http://devicetree.org/schemas/phy/qcom,qcs615-qmp-usb3dp-phy.yaml

  phy@1615000 (qcom,shikra-qmp-usb3-dp-phy): reset-names: ['phy_phy', 'dp_phy', 'phy'] is too long
	from schema $id: http://devicetree.org/schemas/phy/qcom,qcs615-qmp-usb3dp-phy.yaml

  phy@1615000 (qcom,shikra-qmp-usb3-dp-phy): resets: [[37, 18], [37, 19], [37, 20]] is too long
	from schema $id: http://devicetree.org/schemas/phy/qcom,qcs615-qmp-usb3dp-phy.yaml

Fix:

The binding schema Documentation/devicetree/bindings/phy/qcom,qcs615-qmp-usb3dp-phy.yaml needs to be updated to allow:

1. orientation-switch property (for USB Type-C orientation switching)
2. ports property (for graph bindings to connect to Type-C controller)
3. Longer reset-names and resets arrays (currently expects 2 entries, DTS provides 3)

Option 1: Update the binding schema to add these properties under qcom,shikra-qmp-usb3-dp-phy:

properties:
  compatible:
    items:
      - enum:
          - qcom,shikra-qmp-usb3-dp-phy
      - const: qcom,qcs615-qmp-usb3-dp-phy

allOf:
  - if:
      properties:
        compatible:
          contains:
            const: qcom,shikra-qmp-usb3-dp-phy
    then:
      properties:
        orientation-switch:
          type: boolean
        ports:
          $ref: /schemas/graph.yaml#/properties/ports
        reset-names:
          minItems: 2
          maxItems: 3
        resets:
          minItems: 2
          maxItems: 3

Option 2: If the DTS is incorrect, remove the extra reset entry and the orientation-switch/ports properties from the DTS nodes.

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb

---

❌ check-patch-compliance

Root cause: Three types of failures: (1) QCLINUX: prefix not accepted by checker, (2) b4 fetch failures for lore links, (3) content mismatches between PR patches and upstream lore patches.

Failure details:

Commits 71d0597, a95db59, 69c6cb3 — QCLINUX: prefix:

Checking commit: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"
Commit summary does not start with a required prefix

Checking commit: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"
Commit summary does not start with a required prefix

Checking commit: QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"
Commit summary does not start with a required prefix

→ QCLINUX: is not in the checker's allowed prefix list (FROMLIST, FROMGIT, UPSTREAM, BACKPORT). This is a known checker limitation for vendor-only commits. These are revert commits for vendor-specific changes, so they will always fail this check.

Commits 1a57ed0, 76a8331 — b4 fetch failures:

Checking commit: FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra
Something seems wrong with the provided link. Please verify it

Checking commit: FROMLIST: arm64: dts: qcom: Enable USB controllers on Shikra platforms
Something seems wrong with the provided link. Please verify it

→ The checker could not fetch the patches from the provided lore links using b4 am. This could be a network issue, an invalid link, or the patch may not exist at the provided URL.

Commits b9a34d2, 328388a, df80e6f — content mismatches:

Checking commit: FROMLIST: dt-bindings: usb: Add Cypress cypd6129/cypd6229 Type-C controller
Change is different from the one mentioned in Link

Checking commit: FROMLIST: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229
Change is different from the one mentioned in Link

Checking commit: FROMLIST: arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports
Change is different from the one mentioned in Link

→ The patch content in the PR differs from the upstream lore patch. This could be due to:

• Context-only differences (line number shifts)
• Legitimate adaptations for the vendor tree
• Missing or extra hunks

Fix:

1. QCLINUX: prefix failures — These are expected for vendor-only revert commits. No action needed (known checker limitation). However, see tag-check below for a related issue.

2. b4 fetch failures — Verify the Link: tags in commits 1a57ed0 and 76a8331:

   git show 1a57ed0ae7e0 | grep "^Link:"
   git show 76a8331c71f9 | grep "^Link:"
   # Test the links manually:
   b4 am --single-message -C -l -3 <link> -o /tmp/test

   If the links are invalid, update them to the correct lore.kernel.org URLs.

3. Content mismatches — For each failing commit, fetch the upstream patch and compare:

   # Example for commit b9a34d2e:
   git show b9a34d2e | grep "^Link:"
   b4 am --single-message -C -l -3 <link> -o /tmp/upstream
   git format-patch -1 b9a34d2e --stdout > /tmp/pr-patch
   # Compare the diff hunks:
   diff <(awk '/^diff/,/^--$/' /tmp/pr-patch | grep -E '^[+-][^+-]') \
        <(awk '/^diff/,/^--$/' /tmp/upstream/*.mbx | grep -E '^[+-][^+-]')

   If the differences are legitimate adaptations (e.g., vendor-specific changes), document them in the commit message. If they are unintended, fix the patch to match upstream.

Reproduce locally:

cd /path/to/kernel
../kernel-checkers/check-patch-compliance.sh --base <base_sha> --head <head_sha>

---

❌ tag-check

Root cause: Three revert commits use QCLINUX: as the prefix, but QCLINUX: is not a valid prefix for the target branch qcom-6.18.y (only qcom-next and qcom-next-staging are exempt from the prefix requirement).

Failure details:

The following commits have QCLINUX: as the subject prefix:

• 71d0597 — QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"
• a95db59 — QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"
• 69c6cb3 — QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"

Analysis:

The target branch is qcom-6.18.y, which is not qcom-next or qcom-next-staging. Therefore, every commit must start with a valid prefix:

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

However, these are revert commits, and the kernel convention is that revert commits should themselves carry a prefix before the word Revert. The current subjects are:

QCLINUX: Revert "FROMLIST: ..."

This is technically valid (the prefix QCLINUX: is present), but it conflicts with check-patch-compliance, which only accepts FROMLIST:, FROMGIT:, UPSTREAM:, and BACKPORT: as valid prefixes.

Recommendation:

Since these are reverts of upstream-posted patches (FROMLIST: and PENDING:), the correct prefix should be UPSTREAM: or FROMLIST: (depending on whether the revert itself was posted upstream):

UPSTREAM: Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"
UPSTREAM: Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"
UPSTREAM: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"

Fix:

git rebase -i <base_sha>
# Mark commits 71d0597f, a95db59f, 69c6cb3a as 'reword'
# Change each subject from:
#   QCLINUX: Revert "FROMLIST: ..."
# to:
#   UPSTREAM: Revert "FROMLIST: ..."
# (or FROMLIST: if the revert itself was posted to the mailing list)
git rebase --continue

Verdict: ❌ FAIL — 3 commits need prefix correction.

---

Verdict

❌ 7 blockers must be fixed before merge:

1. checkpatch — Fix commit reference format in commit 69c6cb3 (1 ERROR)
2. checkpatch — Convert spaces to tabs in drivers/usb/typec/ucsi/ucsi_ccg.c for commit 328388a (1084 ERRORs)
3. dtb-check — Update qcom,qcs615-qmp-usb3dp-phy.yaml binding to allow orientation-switch, ports, and 3-entry reset-names/resets arrays
4. check-patch-compliance — Verify and fix Link: tags for commits 1a57ed0 and 76a8331 (b4 fetch failures)
5. check-patch-compliance — Resolve content mismatches for commits b9a34d2, 328388a, df80e6f
6. tag-check — Change prefix from QCLINUX: to UPSTREAM: (or FROMLIST:) for revert commits 71d0597, a95db59, 69c6cb3
7. checkpatch — Consider splitting DT binding changes in commits 1a57ed0 and df80e6f (2 WARNINGs, advisory only)

Priority order:

1. Fix commit 328388a whitespace issues (1084 errors) — this is the largest blocker
2. Fix tag-check prefix issues (3 commits) — this will also resolve the check-patch-compliance prefix failures
3. Fix dtb-check binding schema issues
4. Verify and fix Link: tags and content mismatches
5. Fix commit reference format in commit 69c6cb3
6. (Optional) Split DT binding changes if required by upstream submission guidelines

[qcomlnxci]

Test jobs on df80e6f

• multimedia Job 231247 on hamoa-iot-evk
• multimedia Job 231239 on lemans-evk
• multimedia Job 231241 on monaco-evk
• multimedia Job 231246 on purwa-iot-evk
• multimedia Job 231244 on qcs615-ride
• multimedia Job 231243 on qcs6490-rb3gen2
• multimedia Job 231245 on qcs8300-ride
• multimedia Job 231240 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 231242 on shikra-iqs-evk

[qcomlnxci]

Test Matrix

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

[qlijarvis]

LAVA Failed Case Triage Summary

PR: #1062

Job 231239 | SoC lemans-evk

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Test detected deferred probe devices (4 PMIC temp-alarm sensors, 1 audio DAI) and missing firmware files (regulatory.db, Bluetooth firmware) that are unrelated to the PR's USB device tree changes; these are pre-existing platform configuration issues on lemans-evk, not regressions introduced by this PR.
3. Possible fix: No action required for this PR. The deferred probe warnings are benign (devices may probe later or are optional), and the firmware load failures are known false positives when the corresponding functional tests (WiFi ON/OFF, BT ON/OFF) pass. The Probe_Failure_Check test should apply suppression rules from lava-known-benign-failures.md or be tuned to ignore these known-benign patterns on lemans-evk.
4. Detail analysis attachment: failed_case_job231239_1_detailed.md

  Case 2: ** rngtest

1. Failed case: ** rngtest
2. Root cause: ** Statistical test failure — RNG hardware produced 994/1000 passing blocks (99.4%), falling 0.3% short of the 997/1000 (99.7%) threshold due to random chance, not a kernel defect.
3. Possible fix: Re-run the test. If failure persists across 3+ runs, increase rngtest sample size to -c 10000 and lower pass threshold to 99.0% to reduce false positives. No kernel changes required — the subsequent qcom_hwrng test passed with 99.98% success rate, proving RNG hardware is functioning correctly.
4. Detail analysis attachment: failed_case_job231239_2_detailed.md

  Case 3: smmu

1. Failed case: smmu
2. Root cause: Video codec device aa00000.video-codec on lemans-evk is missing IOMMU group attachment — the device is not bound to any IOMMU group, failing the SMMU test's critical master protection validation.
3. Possible fix: Add the missing iommus property to the video-codec DT node in arch/arm64/boot/dts/qcom/lemans.dtsi or lemans-evk.dts to bind it to the appropriate SMMU instance, following the pattern used by other critical masters (GPU, USB, Display) on this platform.
4. Detail analysis attachment: failed_case_job231239_3_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: LAVA test infrastructure marked the test run as "unfinished" after the test runner completed normally; all individual test cases that ran passed successfully, but LAVA expected additional tests or a different completion signal from the test runner.
3. Possible fix: This is a LAVA test definition/infrastructure issue, not a kernel issue. Re-trigger the CI job with the same kernel build. If the issue persists, review the LAVA test definition to ensure the test runner completion signal matches what LAVA expects, or check if there are missing test cases in the test suite configuration that LAVA is waiting for.
4. Detail analysis attachment: failed_case_job231239_4_detailed.md

Job 231240 | SoC qcs9100-ride

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

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

  Case 1: Probe_Failure_Check — Probe/firmware errors and deferred probe devices

1. Failed case: Probe_Failure_Check — Probe/firmware errors and deferred probe devices
2. Root cause: Two distinct pre-existing platform issues unrelated to PR Add Support for usb0 and usb1 on shikra QLI #1062: (1) regulatory.db firmware file missing from rootfs (benign WiFi regulatory database); (2) Aquantia AQR115C Ethernet PHY probe failure due to missing firmware-name DT property (-EINVAL); (3) Four PMIC temp-alarm devices stuck in deferred probe due to missing thermal zone dependencies. None of these issues are introduced by the PR, which only reverts and replaces USB DT nodes on Shikra platforms.
3. Possible fix: (1) regulatory.db: benign — WiFi driver falls back to built-in regulatory rules; no action required unless strict regulatory compliance needed. (2) Aquantia PHY: add firmware-name property to the Ethernet PHY DT node at stmmac-0:08 in qcs9100-ride DTS, or verify PHY firmware is loaded via bootloader. (3) temp-alarm deferred probe: verify thermal zone DT nodes reference the correct PMIC temp-alarm phandles; if thermal zones are intentionally disabled, suppress this test warning for qcs9100-ride.
4. Detail analysis attachment: failed_case_job231240_1_detailed.md

  Case 2: smmu

1. Failed case: smmu
2. Root cause: Video codec device (aa00000.video-codec) is missing IOMMU group attachment on qcs9100-ride platform — the test detected that this critical master device is not protected by SMMU, which is a platform-specific device tree configuration issue unrelated to the PR's USB DT changes.
3. Possible fix: Add the missing iommus property to the video-codec@aa00000 device tree node in arch/arm64/boot/dts/qcom/qcs9100.dtsi to attach it to an IOMMU group. The property should reference the appropriate SMMU instance (likely <&apps_smmu 0x2180 0x0> based on similar Qualcomm SoC patterns). This is a pre-existing platform configuration gap, not introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062.
4. Detail analysis attachment: failed_case_job231240_2_detailed.md

  Case 3: Ethernet_Basic_Validation

1. Failed case: Ethernet_Basic_Validation
2. Root cause: Aquantia AQR115C PHY (stmmac-0:08) probe failure during boot prevents end0 interface from attaching to PHY; error -EINVAL (-22) indicates missing or invalid firmware-name property in device tree for the Aquantia PHY driver
3. Possible fix: Add the missing firmware-name property to the Aquantia AQR115C PHY node in the qcs9100-ride device tree (arch/arm64/boot/dts/qcom/qcs9100-ride.dts or qcs9100.dtsi); the property should specify the Aquantia firmware file path (typically "Rhe-05.06-Candidate9-AQR_Mediatek_23B_P5_ID45824_LCLVER1.cld" or similar); this is a pre-existing platform configuration issue unrelated to PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only modifies USB nodes)
4. Detail analysis attachment: failed_case_job231240_3_detailed.md

  Case 4: KVM_Driver — /dev/kvm device node missing

1. Failed case: KVM_Driver — /dev/kvm device node missing
2. Root cause: KVM initialization failed because Gunyah hypervisor is already running at EL2 on qcs9100-ride, preventing KVM from entering HYP mode. Boot log shows "kvm [1]: HYP mode not available" immediately after "Hypervisor cold boot, version: gunyah-cdfb73831 perf".
3. Possible fix: This is a platform configuration issue, not a kernel regression. The qcs9100-ride board boots with Gunyah hypervisor enabled by default. To enable KVM testing: (1) disable Gunyah in the bootloader/firmware configuration for this board, OR (2) exclude KVM tests from the CI test suite for qcs9100-ride and other Gunyah-enabled platforms, OR (3) configure the board to boot without a hypervisor when KVM testing is required.
4. Detail analysis attachment: failed_case_job231240_4_detailed.md

  Case 5: KVM_EL2_DTB — /dev/kvm unavailable (HYP mode not available)

1. Failed case: KVM_EL2_DTB — /dev/kvm unavailable (HYP mode not available)
2. Root cause: KVM initialization failed because Gunyah hypervisor is running at EL2 on qcs9100-ride, preventing KVM from accessing HYP mode. The kernel message kvm [1]: HYP mode not available at boot time (3.866507s) indicates KVM detected it cannot operate because EL2 is already claimed by the Gunyah hypervisor (Hypervisor cold boot, version: gunyah-cdfb73831). This is a platform-level architectural constraint, not a kernel regression.
3. Possible fix: This is expected behavior on qcs9100-ride when Gunyah hypervisor is enabled. To run KVM tests, either: (1) disable Gunyah hypervisor in the firmware/bootloader configuration to free EL2 for KVM, or (2) skip KVM tests on platforms where Gunyah is required. This is not a PR-introduced issue — it is a pre-existing platform configuration where native KVM and Gunyah hypervisor are mutually exclusive.
4. Detail analysis attachment: failed_case_job231240_5_detailed.md

  Case 6: KVM_Infra — /dev/kvm device node unavailable

1. Failed case: KVM_Infra — /dev/kvm device node unavailable
2. Root cause: KVM subsystem detected "HYP mode not available" at boot (line 3.866507 in kernel log). The qcs9100-ride platform is running without EL2 (hypervisor) support, preventing KVM device node creation. CONFIG_KVM is enabled in the kernel, but the hardware/firmware does not provide the required EL2 execution level for ARM64 KVM operation.
3. Possible fix: This is a platform limitation, not a kernel regression. The qcs9100-ride board does not support virtualization (EL2/HYP mode). To resolve: (1) verify the board's TrustZone/secure firmware configuration allows EL2 access, or (2) if the platform genuinely lacks EL2 support, exclude KVM tests from the qcs9100-ride test suite, or (3) test KVM functionality on a platform with confirmed EL2 support (e.g., rb3gen2, which typically supports virtualization).
4. Detail analysis attachment: failed_case_job231240_6_detailed.md

  Case 7: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM infrastructure test failed because the kernel detected at boot that HYP (EL2 hypervisor) mode is not available on the qcs9100-ride platform, preventing /dev/kvm device creation despite CONFIG_KVM being enabled in the kernel configuration.
3. Possible fix: This is a pre-existing platform/firmware/bootloader configuration issue, not a regression introduced by this PR (which only modifies USB device tree nodes for Shikra platforms). The qcs9100-ride board's bootloader/firmware is not configured to boot the kernel in EL2 mode, which is a prerequisite for KVM functionality. To enable KVM on this platform: (1) verify the bootloader (ABL/XBL) is configured to enter the kernel at EL2 instead of EL1, (2) ensure the ARM TrustZone/secure firmware allows EL2 execution, or (3) if KVM is not required for this platform's test matrix, mark the KVM_Infra test as expected-fail or skip it for qcs9100-ride in the LAVA job definition.
4. Detail analysis attachment: failed_case_job231240_7_detailed.md

Job 231241 | SoC monaco-evk

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: ath11k_pci WiFi driver probe failure (error -110: timeout) due to missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin on monaco-evk target. The MHI (Modem Host Interface) power-up sequence timed out after firmware load failed, causing the ath11k_pci driver probe to fail with -ETIMEDOUT (-110). Bluetooth firmware load failures (qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv) and regulatory.db failure are benign — BT_ON_OFF test passed, confirming BT functional despite firmware warnings.
3. Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/ath11k/WCN6855/hw2.1/nfa765/). This firmware is required for the WCN6855 WiFi chipset on monaco-evk. The firmware can be obtained from the linux-firmware repository or Qualcomm's firmware package for WCN6855 hw2.1 variant. After adding the firmware, rebuild the rootfs and re-run the test to verify ath11k_pci probe succeeds.
4. Detail analysis attachment: failed_case_job231241_1_detailed.md

  Case 2: WiFi_Firmware_Driver — WiFi driver probe failure (ath11k_pci)

1. Failed case: WiFi_Firmware_Driver — WiFi driver probe failure (ath11k_pci)
2. Root cause: ath11k_pci probe failed with error -110 (ETIMEDOUT) on monaco-evk because MHI firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs (-ENOENT), causing MHI power-up to time out after firmware load failure.
3. Possible fix: Add the missing WCN6855 hw2.1 nfa765 firmware files to the monaco-evk rootfs. The firmware package should include ath11k/WCN6855/hw2.1/nfa765/amss.bin and related board files. This is a rootfs/firmware packaging issue, not a kernel regression introduced by this PR (PR only touches Shikra USB DT nodes, unrelated to Monaco WiFi).
4. Detail analysis attachment: failed_case_job231241_2_detailed.md

  Case 3: WiFi_OnOff — WiFi driver probe failure

1. Failed case: WiFi_OnOff — WiFi driver probe failure
2. Root cause: ath11k_pci driver probe failed with -ETIMEDOUT (-110) because MHI firmware (ath11k/WCN6855/hw2.1/nfa765/amss.bin) failed to load with -ENOENT (-2), preventing the WCN6855 WiFi chip from powering up and initializing on monaco-evk (QCS8300 SoC).
3. Possible fix: Add the missing WCN6855 firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/). This is a board-specific firmware packaging issue, not a kernel regression introduced by the PR (which only modifies USB DT nodes for Shikra platform, unrelated to monaco-evk WiFi).
4. Detail analysis attachment: failed_case_job231241_3_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: LAVA test suite reported failure due to ath11k_pci WiFi driver probe failure (error -110 ETIMEDOUT) caused by missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin in the rootfs. This is a pre-existing infrastructure/rootfs issue, not a kernel regression introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062.
3. Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs image used for monaco-evk LAVA testing. The firmware should be sourced from the linux-firmware repository or Qualcomm's firmware package and placed in /lib/firmware/ath11k/WCN6855/hw2.1/nfa765/ on the target rootfs.
4. Detail analysis attachment: failed_case_job231241_4_detailed.md

Job 231242 | SoC shikra-iqs-evk

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

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

  Case 1: GIC

1. Failed case: GIC
2. Root cause: Test script parsing bug — the GIC test script at line 75 attempts integer comparison on non-numeric fields from /proc/interrupts output (specifically "GICv3", "Level", and "arch_timer" strings), causing bash arithmetic errors and false failures for CPUs 4-7 on shikra-iqs-evk (4-CPU system).
3. Possible fix: Fix the test script /lava-231242/0/tests/0_qcom-next-ci-premerge-tests/Runner/suites/Kernel/Baseport/GIC/run.sh line 75 to correctly parse only the numeric timer count fields from /proc/interrupts, skipping non-numeric tokens. The kernel and GIC are functioning correctly — CPUs 0-3 passed, and the system has only 4 CPUs (0-3), so CPUs 4-7 do not exist and should not be tested.
4. Detail analysis attachment: failed_case_job231242_1_detailed.md

  Case 2: Probe_Failure_Check — USB Type-C Controller Firmware Load Failure

1. Failed case: Probe_Failure_Check — USB Type-C Controller Firmware Load Failure
2. Root cause: The ucsi_ccg driver (Cypress CCG USB Type-C controller at I2C address 3-0040) detects empty firmware version (fw_version=0) during probe and attempts to flash firmware from file ccg_secondary.cyacd2, but the firmware file is missing from the rootfs, causing probe to fail with error -2 (ENOENT). This is a direct consequence of PR Add Support for usb0 and usb1 on shikra QLI #1062 which reverts out-of-tree USB DT nodes and introduces upstream USB/Type-C support including the ucsi_ccg device node, but the corresponding firmware blob was not added to the rootfs image.
3. Possible fix: Add the missing Cypress CCG firmware file ccg_secondary.cyacd2 to the rootfs at /lib/firmware/ (or the appropriate firmware search path). The firmware should be sourced from the Cypress CCG firmware package for the cypd6129/cypd6229 controller family (as referenced in PR patch 6/8 which adds dt-bindings for these controllers). Alternatively, if the CCG controller is not required for this test configuration, disable the ucsi_ccg device node in the shikra-iqs-evk device tree to prevent the probe attempt.
4. Detail analysis attachment: failed_case_job231242_2_detailed.md

  Case 3: PCIe — QPS615 Firmware Missing

1. Failed case: PCIe — QPS615 Firmware Missing
2. Root cause: The PCIe test failed because the required firmware file TC956X_Firmware_PCIeBridge.bin for the QPS615 PCIe-to-Ethernet bridge (Toshiba TC956X chip, vendor ID 0x1179, device ID 0x0623/0x0220) is not present in the standard firmware search paths (/lib/firmware, /lib/firmware/updates, etc.) on the shikra-iqs-evk target. The QPS615 hardware is correctly enumerated on the PCIe bus (7 devices detected, 2 Ethernet functions at 0000:05:00.0 and 0000:05:00.1 are unbound), but the test validation logic requires this firmware file to be readable to pass the "firmware validation" check, even though the Ethernet driver module (tc956x_pcie_eth) is also missing from the running kernel.
3. Possible fix: This is NOT a PR-introduced regression. The PR changes only revert and re-apply USB device tree nodes for shikra-iqs-evk and do not touch PCIe, firmware packaging, or the QPS615 hardware configuration. The failure is a pre-existing test environment issue: the test rootfs image does not include the TC956X firmware file or the tc956x_pcie_eth driver module. To resolve: (1) Add TC956X_Firmware_PCIeBridge.bin to the rootfs firmware directory (typically sourced from the Toshiba TC956X SDK or linux-firmware repository), and (2) ensure the tc956x_pcie_eth kernel module is built and included in the test image. If QPS615 Ethernet is not a validation requirement for this platform, the test should be updated to skip the firmware check when the hardware is optional.
4. Detail analysis attachment: failed_case_job231242_3_detailed.md

  Case 4: USBHost

1. Failed case: USBHost
2. Root cause: USB controllers are configured in OTG mode with Type-C role switching, but no USB root hubs are exposed because the controllers are not in host mode and no Type-C role switch has occurred to activate host functionality.
3. Possible fix: This is not a PR-introduced regression. The PR correctly implements USB OTG with Type-C role switching for shikra-iqs-evk. The USBHost test failure is expected behavior when USB is in OTG mode without an active host role. The test should either: (1) trigger a role switch to host mode before checking for root hubs, or (2) be updated to recognize OTG-configured USB as valid even when no root hubs are currently exposed.
4. Detail analysis attachment: failed_case_job231242_4_detailed.md

  Case 5: BT_FW_KMD_Service

1. Failed case: BT_FW_KMD_Service
2. Root cause: Bluetooth hardware initialization failure due to persistent regulator voltage constraint violation (l2 regulator: unsupportable voltage range 3500000-3296000uV) preventing QCA Bluetooth controller (wcn399x) from powering up correctly, resulting in command timeouts and failure to read QCA version information.
3. Possible fix: Investigate and correct the l2 regulator voltage range configuration in the device tree for shikra-iqs-evk. The regulator is requesting a voltage range (3500000-3296000uV) that violates the constraint where min_uV (3500000) > max_uV (3296000). This is likely introduced by the PR's USB DT changes that modified regulator supply wiring. Review the pm8150_l2 or pm4125_l2 regulator node definition and ensure voltage ranges are correctly specified with min ≤ max. Additionally, verify that the Bluetooth UART power supply dependencies are correctly wired after the USB DT node changes.
4. Detail analysis attachment: failed_case_job231242_5_detailed.md

  Case 6: BT_ON_OFF — Bluetooth ON/OFF functional test

1. Failed case: BT_ON_OFF — Bluetooth ON/OFF functional test
2. Root cause: Bluetooth hardware initialization failure on shikra-iqs-evk — the WCN399x Bluetooth controller fails to respond to QCA version query commands (0xfc00), timing out repeatedly with error -110 (ETIMEDOUT), preventing firmware load and leaving adapter hci0 without a valid BD address. The failure correlates with a persistent regulator voltage range error ("l2: unsupportable voltage range: 3500000-3296000uV") that floods the kernel log, indicating a power supply misconfiguration likely affecting the Bluetooth power sequencing subsystem (pwrseq-qcom_wcn).
3. Possible fix: Investigate the "l2" regulator DT configuration for shikra-iqs-evk — the requested voltage range (3500000-3296000uV, min > max) is invalid and suggests a DT typo or incorrect supply wiring for the WCN399x Bluetooth/WiFi combo chip. Cross-reference the PR's USB supply removals with the Bluetooth power sequencing requirements: the PR removes pm8150_l4, pm8150_l12, pm8150_l13, and pm8150_l6 supply assignments from USB nodes, but these PMICs may also supply the WCN399x power sequencer. Verify that the WCN399x PMU node (wcn3988-pmu) has correct vddaon, vdddig, vddio, vddrfa1p2, vddrfa1p8, and vddch1 supply mappings in the DT, and that the "l2" regulator (likely pm8150_l2 or similar) has a valid voltage range (min ≤ max). If the regulator error persists after DT correction, check for a hardware issue with the PMIC or WCN399x module on this specific board.
4. Detail analysis attachment: failed_case_job231242_6_detailed.md

  Case 7: BT_SCAN

1. Failed case: BT_SCAN
2. Root cause: Bluetooth adapter hci0 fails to initialize with a valid BD (Bluetooth Device) address due to repeated command timeouts (-110 ETIMEDOUT) when reading QCA version information from the WCN399x Bluetooth controller. The controller never reaches a usable runtime state despite multiple recovery attempts, preventing any Bluetooth scanning functionality.
3. Possible fix: This is a pre-existing platform/firmware issue unrelated to the PR changes. The PR only modifies USB DT nodes and does not touch Bluetooth, UART, or power management paths. The "l2: unsupportable voltage range" regulator warnings are benign noise (a known platform issue with PM8150 l2 regulator constraints) and do not cause the Bluetooth failure. The root cause is a WCN399x firmware/hardware initialization failure specific to the shikra-iqs-evk platform. Recommended action: (1) Verify WCN399x firmware files are present and correct version for this platform; (2) Check UART transport configuration and baud rate settings for Bluetooth; (3) Verify power sequencing and regulators for the Bluetooth controller; (4) If issue persists, escalate to Bluetooth/WCN399x firmware team for platform-specific debugging.
4. Detail analysis attachment: failed_case_job231242_7_detailed.md

  Case 8: **Kernel Crash — Synchronous External Abort in qcom_rng driver**

1. Failed case: Kernel Crash — Synchronous External Abort in qcom_rng driver
2. Root cause: Hardware RNG (qcom_rng) driver attempted to read from an MMIO register that triggered a synchronous external abort (bus error 0x96000010). The crash occurred in qcom_rng_read+0xc4 when the dd command (via qcom_hwrng test) read from /dev/hwrng. The abort indicates the hardware register at the accessed address is either not powered, not clocked, or the MMIO mapping is incorrect for the shikra-iqs-evk platform.
3. Possible fix: Investigate the qcom_rng device tree configuration for shikra-iqs-evk. Verify that: (1) the MMIO base address in the DT matches the hardware specification for this SoC, (2) the RNG hardware block is properly powered and clocked before driver access, (3) the reg property in the qcom,prng DT node is correct. Check if the PR's USB DT changes inadvertently affected power/clock dependencies for the RNG block. As an immediate workaround, disable the qcom_hwrng test or blacklist the qcom_rng module until the hardware configuration is corrected.
4. Detail analysis attachment: failed_case_job231242_8_detailed.md

  Case 9: **Kernel Crash — synchronous external abort in qcom_rng driver**

1. Failed case: Kernel Crash — synchronous external abort in qcom_rng driver
2. Root cause: The qcom_rng driver crashed with a synchronous external abort (bus error) at offset +0xc4 in qcom_rng_read() while reading from the hardware RNG MMIO registers. This is a hardware access fault indicating the RNG hardware block is either not powered, not clocked, or the MMIO mapping is invalid on the shikra-iqs-evk platform. The crash occurred during the qcom_hwrng test (not the KVM test), triggered by a dd read from /dev/hwrng.
3. Possible fix: This is a pre-existing platform/firmware issue unrelated to PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only changes USB DT nodes). The KVM_EL2_DTB test failed because /dev/kvm is not present, which is expected if CONFIG_KVM is enabled but KVM initialization failed or the kvm.ko module is not loaded. However, the board crashed before KVM could be properly investigated. Recommended action: (1) Investigate why qcom_rng hardware access fails on shikra-iqs-evk — check power/clock domains, MMIO address correctness, and firmware initialization of the RNG block. (2) Disable or skip the qcom_hwrng test on shikra-iqs-evk until the RNG hardware issue is resolved. (3) Re-run the KVM tests after fixing the RNG crash to determine if /dev/kvm absence is a separate issue or a consequence of incomplete boot.
4. Detail analysis attachment: failed_case_job231242_9_detailed.md

  Case 10: Kernel Crash — synchronous external abort in qcom_rng driver

1. Failed case: Kernel Crash — synchronous external abort in qcom_rng driver
2. Root cause: Hardware bus error (synchronous external abort) when qcom_rng driver attempts to read from PRNG hardware registers during /dev/hwrng access. The fault occurs at qcom_rng_read+0xc4 when dereferencing a hardware MMIO address, indicating either: (1) PRNG hardware block is not clocked/powered, (2) MMIO mapping is incorrect/stale, or (3) hardware block is in a bad state on shikra-iqs-evk.
3. Possible fix: This is a pre-existing platform/firmware issue, NOT introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only touches USB DT nodes). The qcom_hwrng test triggers a latent hardware access bug. Recommended actions: (1) Verify PRNG clock/power domain is enabled in shikra-iqs-evk DT, (2) Check if PRNG hardware requires explicit initialization that is missing, (3) Add error handling in qcom_rng driver to gracefully handle MMIO faults, (4) Skip qcom_hwrng test on shikra-iqs-evk until hardware issue is resolved.
4. Detail analysis attachment: failed_case_job231242_10_detailed.md

  Case 11: Kernel Crash — synchronous external abort in qcom_rng driver

1. Failed case: Kernel Crash — synchronous external abort in qcom_rng driver
2. Root cause: The kernel panicked with a synchronous external abort (bus error) at timestamp 1234.168s while the qcom_hwrng test was reading from /dev/hwrng. The crash occurred in qcom_rng_read+0xc4/0x228 when accessing hardware RNG registers, indicating the RNG hardware block became inaccessible or was not properly powered/clocked at the time of access. This is a pre-existing platform issue unrelated to the PR's USB DT changes.
3. Possible fix: This failure is NOT PR-introduced. The PR only reverts and replaces USB DT nodes for shikra-iqs-evk; it does not touch RNG, power, or clock configuration. The crash is a pre-existing hardware/firmware issue on the shikra-iqs-evk platform where the RNG hardware block is not reliably accessible. Recommended action: (1) Re-trigger the CI job to confirm if this is a transient hardware issue; (2) If reproducible, investigate RNG power domain, clock gating, or firmware configuration on shikra-iqs-evk; (3) The PR itself can proceed as the failure is unrelated to the USB changes.
4. Detail analysis attachment: failed_case_job231242_11_detailed.md

  Case 12: lava-test-shell timeout (not a CoT classification - this is a kernel crash leading to EDL entry)

1. Failed case: lava-test-shell timeout (not a CoT classification - this is a kernel crash leading to EDL entry)
2. Root cause: Kernel panic triggered by synchronous external abort (hardware fault) in qcom_rng driver at qcom_rng_read+0xc4 while process 'dd' (PID 14445) was reading from /dev/hwrng. The crash occurred at ~1234 seconds (20 minutes) into runtime. After the panic, the kernel attempted to write crash logs via EFI pstore but encountered repeated EFI firmware bugs ("Unable to handle paging request in EFI runtime service"), preventing crashdump collection. The board then entered EDL (Emergency Download) ramdump mode and remained there until LAVA timed out after 2400 seconds.
3. Possible fix: This is a hardware/firmware issue on the shikra-iqs-evk board, not a kernel regression introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only reverts USB DT nodes). The synchronous external abort indicates the RNG hardware register at the accessed address is not responding correctly - likely a clock/power/firmware configuration issue specific to this board instance or a transient hardware fault. Recommended actions: (1) Re-trigger the CI job to confirm if this is a transient hardware fault. (2) If the issue reproduces, investigate the RNG hardware power/clock configuration on shikra-iqs-evk - check if the RNG block is properly powered and clocked before driver access. (3) Check if EFI firmware needs an update to fix the pstore write failures that prevented crashdump collection. (4) The PR changes (USB DT reverts) are unrelated to this RNG hardware fault and should not be blocked by this failure.
4. Detail analysis attachment: failed_case_job231242_12_detailed.md

  Case 13: Kernel Crash — synchronous external abort in qcom_rng driver

1. Failed case: Kernel Crash — synchronous external abort in qcom_rng driver
2. Root cause: The kernel panicked with a synchronous external abort (memory access fault) at PC qcom_rng_read+0xc4/0x228 in the qcom_rng driver while the qcom_hwrng test was reading entropy from /dev/hwrng. The crash occurred when accessing hardware RNG registers (instruction b940035c = ldr w28, [x26]), indicating the RNG hardware block was either not powered/clocked correctly or the MMIO mapping was invalid. This is NOT a PR-introduced regression — the PR only reverts USB DT nodes and adds upstream USB patches; it does not touch RNG, clocks, power domains, or MMIO mappings. The crash is a pre-existing platform/firmware issue on shikra-iqs-evk where the RNG hardware is not properly initialized or accessible at runtime.
3. Possible fix: This is a pre-existing platform issue, not a PR regression. The PR should not be blocked. To fix the underlying RNG crash: (1) verify the RNG device tree node in arch/arm64/boot/dts/qcom/shikra.dtsi has correct reg, clocks, and power-domains properties; (2) confirm the RNG clock and power domain are enabled in the kernel boot log before the crash; (3) if the RNG hardware is not functional on this platform, disable the RNG node in shikra-iqs-evk.dts with status = "disabled"; until the hardware/firmware issue is resolved; (4) re-run the LAVA job to confirm tests pass without the RNG test triggering the crash.
4. Detail analysis attachment: failed_case_job231242_13_detailed.md

  Case 14: Kernel Crash — Synchronous External Abort in qcom_rng driver

1. Failed case: Kernel Crash — Synchronous External Abort in qcom_rng driver
2. Root cause: Synchronous external abort (bus error) at PC qcom_rng_read+0xc4 when the qcom_rng driver attempted to read from hardware RNG registers during the qcom_hwrng test; the fault occurred at instruction b940035c (ldr w28, [x26, #0]) indicating a hardware register read failure, likely due to clock/power gating or incorrect MMIO mapping for the RNG hardware block on shikra-iqs-evk.
3. Possible fix: Verify that the qcom_rng device tree node for shikra-iqs-evk includes correct clock and power domain bindings; if clocks are missing or the RNG block is not powered on, add the required clocks and power-domains properties to the &qrng node in arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts following the pattern used in other Qualcomm SoC device trees (e.g., sc7280, sm8450); as a short-term workaround, disable the qcom_hwrng test on shikra-iqs-evk until the DT is corrected.
4. Detail analysis attachment: failed_case_job231242_14_detailed.md

Job 231243 | SoC qcs6490-rb3gen2

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Two benign probe failures detected: (1) regulatory.db firmware load failure (error -2) — a known false positive when regulatory database is compiled into the kernel or not required; (2) xhci-pci-renesas 0001:04:00.0 probe failure (error -2) — Renesas USB firmware not present in rootfs, but this is a PCIe-attached USB controller that is not critical for qcs6490-rb3gen2 platform operation.
3. Possible fix: No action required. Both failures are benign: (1) regulatory.db is not needed when cfg80211 regulatory domain is compiled-in or when WiFi operates without regulatory enforcement; (2) Renesas USB controller firmware (renesas_usb_fw.mem) is optional and the platform has other functional USB controllers (8c00000.usb and a600000.usb both passed SMMU attachment and are operational). If Renesas USB functionality is required, add the firmware file to the rootfs at /lib/firmware/renesas_usb_fw.mem.
4. Detail analysis attachment: failed_case_job231243_1_detailed.md

  Case 2: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: KVM subsystem initialization failed at boot because HYP (Hypervisor) mode is not available on the qcs6490-rb3gen2 platform. The kernel message kvm [1]: HYP mode not available at boot time (line 3.394886) indicates the CPU did not enter EL2 (Exception Level 2, required for KVM/virtualization support), preventing creation of the /dev/kvm device node.
3. Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The PR (USB DT reverts for Shikra) does not touch KVM, virtualization, or boot-mode configuration. To enable KVM on qcs6490-rb3gen2: (1) verify the bootloader (ABL/XBL) is configured to boot the kernel at EL2 instead of EL1; (2) confirm the SoC/firmware supports virtualization extensions; (3) if the platform fundamentally lacks EL2 support, mark KVM tests as "not applicable" for this target in the CI job definition.
4. Detail analysis attachment: failed_case_job231243_2_detailed.md

  Case 3: KVM_EL2_DTB

1. Failed case: KVM_EL2_DTB
2. Root cause: KVM cannot initialize on qcs6490-rb3gen2 because the platform does not boot into EL2 (hypervisor mode) — kernel message "kvm [1]: HYP mode not available" indicates the CPU is running at EL1 and lacks the architectural support required for KVM virtualization.
3. Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The PR only modifies USB device tree nodes for Shikra platform and does not touch KVM, virtualization, or boot mode configuration. No kernel fix is required. To enable KVM on this platform, the bootloader/firmware must be configured to boot the kernel at EL2, or the test should be skipped on platforms without hypervisor support.
4. Detail analysis attachment: failed_case_job231243_3_detailed.md

  Case 4: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Mark KVM tests as "expected skip" for qcs6490-rb3gen2 in the LAVA test suite configuration with reason: "Platform does not boot in EL2 mode — KVM not supported". Alternatively, work with the bootloader team to modify ABL/UEFI to enter EL2 before booting Linux (long-term solution requiring firmware changes).
4. Detail analysis attachment: failed_case_job231243_4_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: The LAVA test suite completed successfully but was marked as failed because 4 individual test cases failed: (1) Probe_Failure_Check reported kernel probe/firmware-related errors, and (2) three KVM tests (KVM_Driver, KVM_EL2_DTB, KVM_Infra) failed because /dev/kvm device node is not available despite CONFIG_KVM being enabled in the kernel configuration.
3. Possible fix: For the KVM failures: investigate why the KVM kernel module is not creating /dev/kvm despite CONFIG_KVM=y - check if the KVM module is loaded (lsmod | grep kvm), verify KVM initialization in dmesg for errors, and ensure the platform supports virtualization extensions. For Probe_Failure_Check: review the probe_failures.log file referenced in the test output to identify which drivers are failing to probe and address the root cause of those probe failures. The PR changes revert USB DT nodes for Shikra/IQS platforms which may have introduced probe failures if dependent drivers are affected.
4. Detail analysis attachment: failed_case_job231243_5_detailed.md

Job 231244 | SoC qcs615-ride

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

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

  Case 1: smmu

1. Failed case: smmu
2. Root cause: Video codec sub-devices (aa00000.video-codec:video-decoder and aa00000.video-codec:video-encoder) are missing IOMMU group attachments on qcs615-ride; the parent device aa00000.video-codec is correctly attached to IOMMU group 7, but the test expects the child video-decoder and video-encoder devices to also have explicit IOMMU group attachments, which are absent in this kernel configuration.
3. Possible fix: This is a pre-existing platform configuration issue unrelated to the PR's USB changes for Shikra; the PR modifies only Shikra DTS files and USB drivers, while the failure occurs on qcs615-ride. The video codec IOMMU binding issue exists in the baseline qcs615 device tree and is not introduced by this PR. No action required for PR merge; track separately as a qcs615 platform DT issue.
4. Detail analysis attachment: failed_case_job231244_1_detailed.md

  Case 2: ** Bluetooth Firmware Initialization Timeout — WCN6855 UART communication failure

1. Failed case: ** Bluetooth Firmware Initialization Timeout — WCN6855 UART communication failure
2. Root cause: ** UART transport layer failure between kernel hci_uart/btqca driver and WCN6855 Bluetooth controller on qcs615-ride. The kernel successfully loads the BT stack and issues HCI commands over UART, but the controller does not respond (RX bytes:0, events:0), causing repeated command tx timeout (-ETIMEDOUT) and preventing firmware version read and setup completion. The HCI interface remains DOWN with invalid BD address (00:00:00:00:00:00).
3. Possible fix: This is a pre-existing qcs615-ride platform/infra issue, not a PR-introduced regression (PR Add Support for usb0 and usb1 on shikra QLI #1062 only touches USB DT on Shikra). Recommended actions: (1) Verify UART hardware wiring and signal integrity on qcs615-ride board; (2) Check WCN6855 power/clock sequencing in DT (qcom,wcn6855-bt node regulators, enable-gpios); (3) Confirm UART baud rate and flow control settings match controller expectations; (4) Test with a known-good qcs615-ride board to isolate hardware vs firmware issue; (5) If issue persists, collect UART bus traces and escalate to Qualcomm BT firmware team.
4. Detail analysis attachment: failed_case_job231244_2_detailed.md

  Case 3: BT_ON_OFF

1. Failed case: BT_ON_OFF
2. Root cause: WCN6855 Bluetooth controller on qcs615-ride fails to respond to HCI commands over UART — repeated command timeouts (-ETIMEDOUT) during QCA version read prevent firmware download and adapter initialization, leaving hci0 without a valid BD address.
3. Possible fix: This is a hardware/firmware communication failure on the qcs615-ride board, not introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only touches USB/Type-C DT nodes on Shikra platform). Recommended actions: (1) Verify UART signal integrity and baud rate configuration for the Bluetooth UART on qcs615-ride; (2) Check WCN6855 power/reset sequencing and regulators; (3) Verify firmware files in /lib/firmware/qca are correct for WCN6855; (4) Re-run the test on a different qcs615-ride board to rule out hardware fault; (5) Check if this is a known issue on qcs615-ride in the baseline (no baseline available for comparison).
4. Detail analysis attachment: failed_case_job231244_3_detailed.md

  Case 4: BT_SCAN — Bluetooth Scan Test Failure

1. Failed case: BT_SCAN — Bluetooth Scan Test Failure
2. Root cause: Bluetooth hardware (WCN6855) failed to initialize during boot on qcs615-ride. The QCA Bluetooth controller repeatedly timed out during firmware version read operations (command 0xfc00 tx timeout, Reading QCA version information failed (-110)), preventing the hci0 adapter from acquiring a valid BD address. The BT_SCAN test correctly detected this runtime failure after exhausting 2 recovery attempts over ~3 minutes.
3. Possible fix: This is a hardware/firmware communication failure, not a kernel regression introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only modifies USB DT nodes for Shikra platform, unrelated to qcs615-ride Bluetooth). The failure is specific to the qcs615-ride board's WCN6855 Bluetooth hardware. Recommended actions: (1) Verify WCN6855 power/clock supplies and regulators in qcs615-ride DT; (2) Check for known WCN6855 firmware compatibility issues with kernel 6.18.44; (3) Re-run the test on a different qcs615-ride board to rule out hardware fault; (4) If reproducible across boards, bisect kernel versions to identify when WCN6855 initialization regressed on this platform.
4. Detail analysis attachment: failed_case_job231244_4_detailed.md

  Case 5: KVM_Driver — /dev/kvm device node not available

1. Failed case: KVM_Driver — /dev/kvm device node not available
2. Root cause: qcs615-ride platform does not support EL2/HYP mode (required for KVM virtualization); kernel message at boot: "kvm [1]: HYP mode not available" indicates hardware lacks virtualization extensions or firmware has not enabled EL2.
3. Possible fix: This is a platform hardware/firmware limitation, not a kernel regression. The qcs615 SoC does not support ARM virtualization extensions (or they are disabled in firmware/TrustZone). No kernel fix is possible. Either: (1) skip KVM tests on qcs615-ride in CI, or (2) verify with hardware team whether EL2 can be enabled via firmware/bootloader configuration for this platform.
4. Detail analysis attachment: failed_case_job231244_5_detailed.md

  Case 6: KVM_EL2_DTB — /dev/kvm not available (HYP mode not supported on platform)

1. Failed case: KVM_EL2_DTB — /dev/kvm not available (HYP mode not supported on platform)
2. Root cause: QCS615 Ride platform does not support ARM Virtualization Extensions (VHE/nVHE) required for KVM. The kernel detected during early boot that "HYP mode not available" and did not create the /dev/kvm device node, causing all KVM-dependent tests to fail at their availability gate.
3. Possible fix: This is a platform hardware limitation, not a kernel bug. The QCS615 SoC does not implement EL2 (Hypervisor mode) required for KVM. No kernel fix is possible. Recommended action: exclude KVM tests from the CI test suite for qcs615-ride and other platforms without virtualization extensions, or mark them as expected-skip when CONFIG_KVM is enabled but HYP mode is unavailable.
4. Detail analysis attachment: failed_case_job231244_6_detailed.md

  Case 7: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM hypervisor mode (EL2) is not available on the qcs615-ride platform — the kernel message kvm [1]: HYP mode not available at boot indicates the bootloader/firmware did not enable EL2 or the SoC does not support virtualization extensions, preventing /dev/kvm creation despite CONFIG_KVM being enabled in the kernel.
3. Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression (the PR only modifies USB device tree nodes). To enable KVM on qcs615-ride: (1) verify the SoC supports ARM virtualization extensions, (2) ensure the bootloader (ABL/XBL) boots the kernel in EL2 (not EL1), and (3) confirm TrustZone firmware allows EL2 access. If the platform does not support virtualization, mark KVM tests as "not applicable" for qcs615-ride in the CI test matrix.
4. Detail analysis attachment: failed_case_job231244_7_detailed.md

  Case 8: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM infrastructure test failed because /dev/kvm device node is not present. The kernel log shows kvm [1]: HYP mode not available at boot, indicating the qcs615-ride platform does not support ARM virtualization extensions (EL2/HYP mode) required for KVM operation.
3. Possible fix: This is a platform hardware limitation, not a software bug. The qcs615-ride SoC does not support ARM virtualization extensions. The test should be skipped on this platform, or the test framework should be updated to mark this as an expected skip rather than a failure for platforms without HYP mode support.
4. Detail analysis attachment: failed_case_job231244_8_detailed.md

Job 231245 | SoC qcs8300-ride

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

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

  Case 1: Probe_Failure_Check — Known Benign WiFi Firmware False Positive (Suppressed)

1. Failed case: Probe_Failure_Check — Known Benign WiFi Firmware False Positive (Suppressed)
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 WiFi driver initialization on qcs8300-ride. However, this is a known benign false positive — the regulatory.db file is loaded asynchronously by the cfg80211 subsystem, and the test probed firmware state before the driver completed initialization. WiFi functionality is confirmed working (WiFi_Firmware_Driver and WiFi_OnOff tests both PASSED).
3. Possible fix: No fix required.** This failure should be suppressed per LAVA Known Benign Failure Suppression Rule 2. The regulatory.db firmware is successfully loaded at runtime as evidenced by passing WiFi functional tests. The Probe_Failure_Check test has a known timing issue where it checks firmware load status too early in the boot sequence. Consider updating the Probe_Failure_Check test to exclude regulatory.db firmware load errors when corresponding WiFi functional tests pass, or add a delay/retry mechanism to allow asynchronous firmware loading to complete.
4. Detail analysis attachment: failed_case_job231245_1_detailed.md

  Case 2: KVM_Driver — /dev/kvm not available (expected behavior, not a bug)

1. Failed case: KVM_Driver — /dev/kvm not available (expected behavior, not a bug)
2. Root cause: qcs8300-ride is running Gunyah hypervisor which occupies EL2 (hypervisor mode). Linux boots as a guest at EL1 without access to EL2 virtualization extensions. KVM driver performs early check (is_hyp_mode_available()) during kvm_arch_init() and silently skips initialization when EL2 is unavailable, resulting in no /dev/kvm device node creation. Evidence: Gunyah boot message "Hypervisor cold boot, version: gunyah-cdfb73831" at log timestamp 2026-09-18T15:40:43.190579; CONFIG_KVM=y confirmed but no KVM init messages in kernel log.
3. Possible fix: This is not a kernel bug or PR-introduced regression — it is expected platform behavior. Update LAVA test suite to skip KVM tests when hypervisor is detected: add check in test initialization to detect Gunyah presence via dmesg | grep -q "Hypervisor cold boot" and exit with SKIP status. Mark KVM_Driver, KVM_EL2_DTB, and KVM_Infra as "expected skip" for qcs8300-ride under Gunyah.
4. Detail analysis attachment: failed_case_job231245_2_detailed.md

  Case 3: KVM_EL2_DTB — Missing /dev/kvm device node

1. Failed case: KVM_EL2_DTB — Missing /dev/kvm device node
2. Root cause: qcs8300-ride runs under Gunyah hypervisor at EL2, preventing KVM from initializing. CONFIG_KVM=y but KVM driver cannot create /dev/kvm because virtualization extensions are already owned by Gunyah. This is a platform configuration constraint, not a kernel bug.
3. Possible fix: Skip KVM tests on qcs8300-ride when Gunyah hypervisor is detected. Add a test gate in the LAVA job definition or test runner that checks for /sys/hypervisor/type or Gunyah boot messages before attempting KVM tests. Alternatively, mark KVM test suite as "not applicable" for this platform in the CI configuration.
4. Detail analysis attachment: failed_case_job231245_3_detailed.md

  Case 4: KVM_Infra — /dev/kvm device node not created

1. Failed case: KVM_Infra — /dev/kvm device node not created
2. Root cause: KVM driver failed to initialize on qcs8300-ride (Monaco SoC). CONFIG_KVM is enabled in kernel config but the KVM ARM driver did not probe successfully, preventing /dev/kvm device node creation. This is a platform-specific KVM initialization failure, not a test infrastructure issue.
3. Possible fix: Investigate KVM ARM driver initialization on qcs8300-ride/Monaco platform. Check dmesg for KVM probe errors (none visible in current log, suggesting silent failure). Verify hypervisor mode (EL2) is available and accessible on this SoC — QCS8300 may be running under Gunyah hypervisor (boot log shows "Gunyah based bootup") which may prevent nested KVM. If Gunyah is active, KVM cannot initialize as it requires direct EL2 access. Recommended action: confirm whether KVM is expected to work on qcs8300-ride under Gunyah, or mark these tests as expected-fail for this platform.
4. Detail analysis attachment: failed_case_job231245_4_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: LAVA test suite marked as failed because multiple sub-tests failed: (1) Probe_Failure_Check failed due to missing regulatory.db firmware file (known benign - not a kernel regression); (2) KVM_Driver, KVM_EL2_DTB, and KVM_Infra tests failed because /dev/kvm device node is not present on qcs8300-ride platform running under Gunyah hypervisor, despite CONFIG_KVM being enabled in kernel config - this is a platform/hypervisor compatibility limitation, not a kernel crash or regression introduced by the PR (which only modifies USB device tree nodes for Shikra/IQS platforms).
3. Possible fix: (1) For regulatory.db: This is a known benign firmware file absence that does not affect kernel functionality - no fix required. (2) For KVM failures: These tests should be skipped on qcs8300-ride platform when running under Gunyah hypervisor, as KVM virtualization is not supported in this configuration. Update the LAVA test job definition to skip KVM tests for qcs8300-ride, or add a platform compatibility check in the KVM test scripts to gracefully skip when Gunyah hypervisor is detected.
4. Detail analysis attachment: failed_case_job231245_5_detailed.md

Job 231246 | SoC purwa-evk

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: The Probe_Failure_Check test detected 5 probe/firmware errors in dmesg on purwa-evk (x5121 platform): (1) qcom_qseecom_uefisecapp probe failed with -EBUSY (-16) — QSEE secure app already registered; (2) two qcom-pcie devices (1bd0000, 1bf8000) failed with -ENODATA (-61) — PHY poweron failed, likely missing PCIe configuration or hardware not present on this board variant; (3) qcom-spmi-lpg PWM probe failed with -EINVAL (-22) — invalid multi-LED "reg" property in device tree; (4) regulatory.db firmware load failed with -ENOENT (-2) — expected benign failure (file not shipped in rootfs, cfg80211 falls back to built-in regulatory data).
3. Possible fix: These are pre-existing platform configuration issues, not PR-introduced regressions. The PR only touches USB device tree nodes for shikra/iqs platforms and does not modify qseecom, pcie, lpg, or regulatory drivers. No baseline exists for purwa-evk to confirm, but the boot log comparison shows identical probe failure patterns across all 9 targets (including targets unaffected by the PR), indicating these are known platform limitations. Recommended action: suppress these known benign probe failures in the Probe_Failure_Check test filter — (1) qcom_qseecom_uefisecapp -16 is expected when secure world is already initialized; (2) qcom-pcie -61 is expected on boards without PCIe hardware or with incomplete DT; (3) qcom-spmi-lpg -22 is a known DT issue tracked separately; (4) regulatory.db -2 is expected and harmless (cfg80211 uses built-in data). If suppression is not acceptable, fix the root causes: (1) adjust qcom_qseecom probe to tolerate re-probe; (2) add missing PCIe DT nodes or mark status="disabled" for absent hardware; (3) fix qcom-spmi-lpg DT multi-LED reg property; (4) ship regulatory.db in rootfs or suppress this specific firmware load failure.
4. Detail analysis attachment: failed_case_job231246_1_detailed.md

  Case 2: smmu (Test Infrastructure False Positive — Pre-existing Platform Issue)

1. Failed case: smmu (Test Infrastructure False Positive — Pre-existing Platform Issue)
2. Root cause: The SMMU test on purwa-evk (x5121) platform reports FAIL because 6 critical bus masters (5 USB controllers: a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb; and 1 video codec: aa00000.video-codec) are missing IOMMU group attachments in the device tree. This is a pre-existing platform configuration issue unrelated to PR Add Support for usb0 and usb1 on shikra QLI #1062, which only modifies Shikra platform device trees and does not touch purwa-evk files.
3. Possible fix: This is not a PR-introduced regression. The test failure indicates a pre-existing device tree configuration gap on purwa-evk where USB and video codec nodes lack iommus properties. To fix: add IOMMU bindings to the missing devices in arch/arm64/boot/dts/qcom/purwa*.dts* files (example: iommus = <&apps_smmu 0x... 0x0>;). However, this fix is outside the scope of PR Add Support for usb0 and usb1 on shikra QLI #1062 validation and should be tracked separately as a platform enablement task.
4. Detail analysis attachment: failed_case_job231246_2_detailed.md

  Case 3: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: KVM initialization failed because the CPU is not running in EL2 (hypervisor mode). The kernel message kvm [1]: HYP mode not available at boot time indicates that the platform firmware/bootloader did not configure the CPU to boot into EL2, which is a prerequisite for KVM functionality on ARM64. CONFIG_KVM is enabled in the kernel configuration, but /dev/kvm cannot be created because the KVM subsystem failed to initialize due to missing hypervisor mode support.
3. Possible fix: This is a platform/firmware configuration issue, not a kernel regression. The purwa-evk board's bootloader/firmware must be configured to boot the kernel in EL2 mode to enable KVM support. If KVM testing is required on this platform, update the bootloader configuration to enable EL2 boot. Alternatively, skip KVM tests on platforms where hypervisor mode is not available or not required.
4. Detail analysis attachment: failed_case_job231246_3_detailed.md

  Case 4: KVM_EL2_DTB

1. Failed case: KVM_EL2_DTB
2. Root cause: KVM cannot initialize on purwa-evk because the Gunyah hypervisor is already running at EL2 (HYP mode). The kernel message kvm [1]: HYP mode not available at boot time indicates that KVM detected another hypervisor occupying EL2, preventing KVM from installing its own hypervisor. This is expected behavior on platforms where Gunyah is enabled — KVM and Gunyah cannot coexist as both require exclusive EL2 access.
3. Possible fix: This is not a kernel regression introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only reverts USB DT changes for Shikra). This is a platform configuration issue: purwa-evk boots with Gunyah hypervisor enabled by default. To enable KVM testing on this platform, either (1) disable Gunyah in the firmware/bootloader configuration and rebuild the boot image, or (2) exclude KVM tests from the purwa-evk test suite, as KVM and Gunyah are mutually exclusive.
4. Detail analysis attachment: failed_case_job231246_4_detailed.md

  Case 5: KVM_Infra — KVM unavailable (platform limitation)

1. Failed case: KVM_Infra — KVM unavailable (platform limitation)
2. Root cause: The purwa-evk platform boots without EL2 (Hypervisor) mode available, as evidenced by the kernel message "kvm [1]: HYP mode not available" at boot time. Without EL2, the KVM driver cannot create /dev/kvm, causing all KVM tests to fail.
3. Possible fix: This is not a kernel regression. The failure is expected on platforms that do not boot into EL2. Either: (1) exclude KVM tests from the purwa-evk test suite, or (2) configure the platform firmware/bootloader to boot the kernel at EL2 if virtualization support is required for this SoC.
4. Detail analysis attachment: failed_case_job231246_5_detailed.md

  Case 6: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM module initialization failed because the kernel is not running in EL2 (hypervisor mode) on purwa-evk — kernel log shows "kvm [1]: HYP mode not available" at boot, preventing /dev/kvm device node creation despite CONFIG_KVM being enabled.
3. Possible fix: This is a platform/firmware configuration issue, not a kernel regression introduced by this PR. The PR only modifies USB device tree nodes for Shikra platforms and does not affect KVM/virtualization. To enable KVM on purwa-evk: (1) verify the bootloader/firmware boots the kernel at EL2 instead of EL1, (2) check if the platform supports virtualization extensions and EL2 is not disabled by secure firmware, or (3) if this platform is not intended to support KVM, exclude the KVM_Infra test from the purwa-evk test suite.
4. Detail analysis attachment: failed_case_job231246_6_detailed.md

Job 231247 | SoC hamoa-evk

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: No action required for this PR. These are pre-existing platform issues unrelated to the USB DT changes for Shikra. The qseecom and regulatory.db failures are known benign. The qcom-spmi-lpg failure is a pre-existing device tree issue in hamoa-evk.dts that should be fixed separately by correcting the multi-LED "reg" property in the SPMI LPG node.
4. Detail analysis attachment: failed_case_job231247_1_detailed.md

  Case 2: smmu (LAVA test infrastructure issue — not a CoT-applicable kernel failure)

1. Failed case: smmu (LAVA test infrastructure issue — not a CoT-applicable kernel failure)
2. Root cause: SMMU test fails because USB PHY devices (a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb) and video codec (aa00000.video-codec) are missing IOMMU group attachments on hamoa-evk. The test expects these "critical masters" to be IOMMU-protected, but they are either not present in the DT or not configured with iommus properties. Kernel SMMU subsystem is functioning correctly (no faults, TLB sync timeouts, or NOC errors in dmesg).
3. Possible fix: This is a test expectation mismatch, not a kernel regression. The PR reverts USB DT nodes for Shikra/IQS platforms but does not touch hamoa-evk DT. The missing USB PHY and video codec IOMMU attachments are pre-existing on hamoa-evk and unrelated to this PR. Recommended action: Update the SMMU test's critical master list to exclude USB PHY devices and video codec on hamoa-evk, or add iommus properties to these devices in arch/arm64/boot/dts/qcom/x1e80100.dtsi if IOMMU protection is genuinely required for them.
4. Detail analysis attachment: failed_case_job231247_2_detailed.md

  Case 3: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: Platform does not support EL2 (hypervisor mode) — hamoa-evk firmware boots directly into EL1, preventing KVM initialization. Kernel log shows kvm [1]: HYP mode not available at boot time.
3. Possible fix: This is a platform limitation, not a kernel bug. To enable KVM on hamoa-evk: (1) Update platform firmware/bootloader to enable EL2 support, or (2) Exclude KVM tests from hamoa-evk CI runs, as this platform is not designed for virtualization workloads. The PR under test (USB DT changes) is unrelated and does not cause this failure.
4. Detail analysis attachment: failed_case_job231247_3_detailed.md

  Case 4: KVM_EL2_DTB — KVM device node unavailable (not a crash)

1. Failed case: KVM_EL2_DTB — KVM device node unavailable (not a crash)
2. Root cause: The hamoa-evk platform boots under the Gunyah hypervisor (EL2 already occupied), preventing KVM from initializing. The kernel log shows "kvm [1]: HYP mode not available" at boot, and the device tree reserves memory for "gunyah-hyp@80000000" and "hyp-elf-package@80800000". KVM requires exclusive EL2 access to create /dev/kvm, which is impossible when a hypervisor is already running at EL2.
3. Possible fix: This is a platform configuration issue, not a kernel regression. The hamoa-evk board is configured to run with Gunyah hypervisor, which is incompatible with KVM. To enable KVM testing: (1) disable Gunyah hypervisor in the boot chain (ABL/UEFI firmware configuration), or (2) exclude KVM tests from the hamoa-evk CI job definition, as this platform is not intended for native KVM use. The PR does not introduce this issue — it is a pre-existing platform characteristic.
4. Detail analysis attachment: failed_case_job231247_4_detailed.md

  Case 5: KVM_Infra — /dev/kvm device node unavailable

1. Failed case: KVM_Infra — /dev/kvm device node unavailable
2. Root cause: KVM cannot initialize on hamoa-evk because the platform is running Gunyah hypervisor in EL2, preventing KVM from claiming HYP mode. The kernel log shows kvm [1]: HYP mode not available at boot, and the hypervisor boot message confirms Hypervisor cold boot, version: gunyah-mobile-ad1fb25c6. When a type-1 hypervisor (Gunyah) is already running at EL2, KVM cannot initialize because ARM architecture allows only one entity to control EL2 at a time.
3. Possible fix: This is not a PR-introduced regression — it is a platform configuration issue specific to hamoa-evk. The test failure is expected on this SoC when Gunyah hypervisor is enabled. To resolve: (1) If KVM functionality is required, disable Gunyah hypervisor in the bootloader/firmware configuration and rebuild the boot image, or (2) Mark KVM tests as "not applicable" for hamoa-evk in the LAVA test definition when Gunyah is enabled, or (3) Use a different target platform that does not run a type-1 hypervisor for KVM validation.
4. Detail analysis attachment: failed_case_job231247_5_detailed.md

  Case 6: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM device node /dev/kvm is not created at runtime despite CONFIG_KVM being enabled in the kernel configuration — KVM driver failed to initialize or probe successfully during boot on hamoa-evk platform.
3. Possible fix: Investigate KVM driver initialization in the boot log for hamoa-evk; check for missing KVM-ARM prerequisites (EL2 hypervisor mode, virtualization extensions enabled in firmware/bootloader), verify device tree has correct KVM/hypervisor configuration, and ensure no conflicting hypervisor is running. If KVM is not supported on hamoa-evk hardware/firmware, mark the test as SKIP for this platform.
4. Detail analysis attachment: failed_case_job231247_6_detailed.md

---

🔎 Boot Log Comparison — PR #1062 vs qcom-6.18.y baseline

PR: #1062
Baseline branch: qcom-6.18.y
Targets compared: 9

Target	Boot lines (PR)	Boot lines (baseline)	New issues	Critical	High	Medium	Low
lemans-evk	1965	no baseline	16	0	2	12	2
qcs9100-ride	1343	no baseline	15	0	2	12	1
monaco-evk	1064	no baseline	11	0	0	11	0
shikra-iqs-evk	1040	no baseline	12	0	0	11	1
qcs6490-rb3gen2	1057	no baseline	19	0	0	18	1
qcs615-ride	959	no baseline	4	0	0	4	0
qcs8300-ride	1235	no baseline	24	0	2	22	0
purwa-evk	1504	no baseline	24	0	1	21	2
hamoa-evk	1600	no baseline	20	0	1	19	0

⚠️ 9 target(s) have no stored baseline — all their issues are listed below but cannot be confirmed as PR-introduced without a baseline.

🟠 High-severity new boot issues: 145 new issue(s) across 9 target(s).

Target: lemans-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 16 (0 critical, 2 high, 12 medium, 2 low)

🔵 FIRMWARE_FAIL (low) ← PR symbols: port, Status, Found

FmpDxe(Qualcomm System Firmware Update Driver): Failed to get the controller state.  Status = Not Found

Context

    ====================================
Selected FW GUID =: 78462415-6133-431C-9FAE-48F2BAFD5C71 
  Platform = 20 
FmpDxe(Qualcomm System Firmware Update Driver): Failed to get the controller state.  Status = Not Found
UsbEnumNewDevRootHub: HIGH on port 0
XHCI: Don't support multi-TT feature for Hub now. (force to disable MTT)
XHCI: Don't support multi-TT feature for Hub now. (force to disable MTT)

🟡 ERROR (medium) ← PR symbols: failed, port, Device

XhcControlTransfer: error - Device Error, transfer - 2

Context

POST Time      [ 2353] OS Loader
UsbEnumNewDevRootHub: SUPER_PLUS on port 1
XhcCheckUrbResult: STALL_ERROR! Completecode = 6
XhcControlTransfer: error - Device Error, transfer - 2
UsbHubInit: failed to read HUB descriptor Device Error
UsbSelectConfig: failed to connect driver Device Error, ignored
- {"dt": "2026-09-18T15:44:36.717436", "lvl": "target", "msg": "\0S - \b\b\b\bFormat: Log Type - Time(microsec) - Message - Optional Info"}

🟡 ERROR (medium) ← PR symbols: failed, port, Device

UsbHubInit: failed to read HUB descriptor Device Error

Context

UsbEnumNewDevRootHub: SUPER_PLUS on port 1
XhcCheckUrbResult: STALL_ERROR! Completecode = 6
XhcControlTransfer: error - Device Error, transfer - 2
UsbHubInit: failed to read HUB descriptor Device Error
UsbSelectConfig: failed to connect driver Device Error, ignored
- {"dt": "2026-09-18T15:44:36.717436", "lvl": "target", "msg": "\0S - \b\b\b\bFormat: Log Type - Time(microsec) - Message - Optional Info"}
S - ����Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic

🟡 ERROR (medium) ← PR symbols: failed, Device, Optional

UsbSelectConfig: failed to connect driver Device Error, ignored

Context

XhcCheckUrbResult: STALL_ERROR! Completecode = 6
XhcControlTransfer: error - Device Error, transfer - 2
UsbHubInit: failed to read HUB descriptor Device Error
UsbSelectConfig: failed to connect driver Device Error, ignored
- {"dt": "2026-09-18T15:44:36.717436", "lvl": "target", "msg": "\0S - \b\b\b\bFormat: Log Type - Time(microsec) - Message - Optional Info"}
S - ����Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.MXF.1.0.c1-00569-KODIAKLA-1

🔵 FIRMWARE_FAIL (low) ← PR symbols: Status, Found

FmpDxe(Qualcomm System Firmware Update Driver): Failed to get the controller state.  Status = Not Found

Context

    ====================================
Selected FW GUID =: 78462415-6133-431C-9FAE-48F2BAFD5C71 
  Platform = 20 
FmpDxe(Qualcomm System Firmware Update Driver): Failed to get the controller state.  Status = Not Found
SoftSKUDxe: GetChipFamily() : 131, GetChipId: 676 
SoftSKUDxeInitialize: SoftSKU not supported for this chip
MinidumpTADxe: Minidump TA loading not enabled.

🟡 ERROR (medium) ← PR symbols: failed, interrupt, names

[    3.199080][    T1] DT AEST: registered 3 AEST error source(s) from DT

Context

[    3.162676][    T1] DT AEST: node /aest/aest-processor-0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.174752][    T1] DT AEST: node /aest/aest-l3-cluster0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.186775][    T1] DT AEST: node /aest/aest-l3-cluster1: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.199080][    T1] DT AEST: registered 3 AEST error source(s) from DT
[    3.205916][    T1] clocksource: Switched to clocksource arch_sys_counter
[    3.216081][    T1] VFS: Disk quotas dquot_6.6.0
[    3.220864][    T1] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

🟡 WARNING (medium) ← PR symbols: already, with

[    4.265641][    T1] WARNING: CPU: 4 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.242593][    T1] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 (0,8000003f) counters available
[    4.260169][    T1] ------------[ cut here ]------------
[    4.265621][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.265641][    T1] WARNING: CPU: 4 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.282243][    T1] Modules linked in:
[    4.286097][    T1] CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.44-g4ae8784cc4c3 #1 PREEMPT 
[    4.295648][    T1] Hardware name: Qualcomm Technologies, Inc. Lemans EVK (DT)

🟠 CALL_TRACE (high)

[    4.406768][    T1] Call trace:

Context

[    4.382676][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002bf
[    4.390707][    T1] x5 : 00000000000002c0 x4 : 40000000fffff2bf x3 : 0000000000000000
[    4.398737][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.406768][    T1] Call trace:
[    4.409996][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.415714][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.421343][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 WARNING (medium) ← PR symbols: already

[    4.518289][    T1] WARNING: CPU: 4 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.506147][    T1] ---[ end trace 0000000000000000 ]---
[    4.512828][    T1] ------------[ cut here ]------------
[    4.518281][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.518289][    T1] WARNING: CPU: 4 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.534879][    T1] Modules linked in:
[    4.538728][    T1] CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Tainted: G        W           6.18.44-g4ae8784cc4c3 #1 PREEMPT 
[    4.549878][    T1] Tainted: [W]=WARN

🟠 CALL_TRACE (high)

[    4.664748][    T1] Call trace:

Context

[    4.640659][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002e9
[    4.648688][    T1] x5 : 00000000000002ea x4 : 40000000fffff2e9 x3 : 0000000000000000
[    4.656718][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.664748][    T1] Call trace:
[    4.667975][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.673693][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.679322][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 ERROR (medium) ← PR symbols: failed, device, found

[    8.175640][  T102] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    8.145343][  T184] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    8.174990][  T202] platform 21c00000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 27
[    8.175494][   T73] hub 1-0:1.0: USB hub found
[    8.175640][  T102] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.175655][  T102] cfg80211: failed to load regulatory.db
[    8.182443][  T110] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)
[    8.187636][  T202] platform 21c00000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 28

🟡 ERROR (medium) ← PR symbols: port, connector, with

[    8.200749][  T110] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[    8.188239][  T186] /soc@0/display-subsystem@ae00000/displayport-controller@af5c000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[    8.188992][  T202] platform 21c00000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 29
[    8.189103][   T73] hub 1-0:1.0: 1 port detected
[    8.200749][  T110] tpm tpm0: A TPM error (256) occurred attempting the self test
[    8.209267][   T73] /connector-1: Fixed dependency cycle(s) with /soc@0/usb@a800000/hub@1
[    8.222621][  T110] tpm tpm0: starting up the TPM manually
[    8.228772][   T73] /soc@0/usb@a800000/hub@1: Fixed dependency cycle(s) with /connector-1

🟡 ERROR (medium) ← PR symbols: failed, with

[    8.530409][  T111] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2

Context

[    8.528253][  T184] ath11k_pci 0000:01:00.0: MSI vectors: 32
[    8.530118][  T111] Bluetooth: hci0: QCA controller version 0x12110201
[    8.530124][  T111] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.530409][  T111] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.530428][  T111] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.530433][  T111] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.530683][  T111] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

🟡 ERROR (medium) ← PR symbols: failed, data, with

[    8.530683][  T111] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

Context

[    8.530409][  T111] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.530428][  T111] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.530433][  T111] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.530683][  T111] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.530700][  T111] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.530703][  T111] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.530706][  T111] Bluetooth: hci0: HFP non-HCI data transport is supported

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   25.236028][  T353] EXT4-fs (sda2): orphan cleanup on readonly fs
[   25.242887][  T353] EXT4-fs (sda2): mounted filesystem 7f081a84-7045-4209-949a-773694ad02be ro with ordered data mode. Quota mode: none.
done.

Target: qcs9100-ride

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 15 (0 critical, 2 high, 12 medium, 1 low)

🟡 ERROR (medium) ← PR symbols: failed, interrupt, names

[    3.696571][    T1] DT AEST: registered 3 AEST error source(s) from DT

Context

[    3.660168][    T1] DT AEST: node /aest/aest-processor-0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.672227][    T1] DT AEST: node /aest/aest-l3-cluster0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.684278][    T1] DT AEST: node /aest/aest-l3-cluster1: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.696571][    T1] DT AEST: registered 3 AEST error source(s) from DT
[    3.703417][    T1] clocksource: Switched to clocksource arch_sys_counter
[    3.710950][    T1] VFS: Disk quotas dquot_6.6.0
[    3.715734][    T1] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

🟡 WARNING (medium) ← PR symbols: already, with

[    4.619490][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.594485][    T1] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 (0,8000003f) counters available
[    4.614011][    T1] ------------[ cut here ]------------
[    4.619466][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.619490][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.636095][    T1] Modules linked in:
[    4.639956][    T1] CPU: 5 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.44-g4ae8784cc4c3 #1 PREEMPT 
[    4.649501][    T1] Hardware name: Qualcomm Technologies, Inc. Lemans Ride Rev3 (DT)

🟠 CALL_TRACE (high)

[    4.761249][    T1] Call trace:

Context

[    4.737129][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002c9
[    4.745167][    T1] x5 : 00000000000002ca x4 : 40000000fffff2c9 x3 : 0000000000000000
[    4.753207][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.761249][    T1] Call trace:
[    4.764483][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.770208][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.775841][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 WARNING (medium) ← PR symbols: already

[    4.873032][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.860705][    T1] ---[ end trace 0000000000000000 ]---
[    4.867564][    T1] ------------[ cut here ]------------
[    4.873018][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.873032][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.889626][    T1] Modules linked in:
[    4.893486][    T1] CPU: 5 UID: 0 PID: 1 Comm: swapper/0 Tainted: G        W           6.18.44-g4ae8784cc4c3 #1 PREEMPT 
[    4.904632][    T1] Tainted: [W]=WARN

🟠 CALL_TRACE (high)

[    5.020112][    T1] Call trace:

Context

[    4.996001][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002f3
[    5.004040][    T1] x5 : 00000000000002f4 x4 : 40000000fffff2f3 x3 : 0000000000000000
[    5.012077][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    5.020112][    T1] Call trace:
[    5.023344][    T1]  notifier_chain_register+0x64/0x150 (P)
[    5.029066][    T1]  raw_notifier_chain_register+0x1c/0x30
[    5.034699][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[    8.220735][  T190] qcom_eud 88e1000.eud: error -ENODEV: failed to get controller node for path 0

Context

[    8.204161][   T85] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
[    8.211557][  T188] coresight cti_sys0: CTI initialized 0
[    8.220418][   T85] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    8.220735][  T190] qcom_eud 88e1000.eud: error -ENODEV: failed to get controller node for path 0
[    8.229722][   T85] qcom-pcie 1c00000.pcie: host bridge /pcie@1c00000 ranges:
[    8.245717][   T85] qcom-pcie 1c00000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000
[    8.252909][  T107] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller

🟡 ERROR (medium) ← PR symbols: failed, with

[    9.934749][   T55] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    9.927846][  T201] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    9.934355][  T201] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.934562][  T201] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.934749][   T55] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.936723][  T114] Bluetooth: hci0: setting up wcn6855
[    9.937690][  T210] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.937690][  T210] :39

🟡 ERROR (medium) ← PR symbols: failed, write, with

[    9.937690][  T210] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f

Context

[    9.934562][  T201] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.934749][   T55] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.936723][  T114] Bluetooth: hci0: setting up wcn6855
[    9.937690][  T210] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.937690][  T210] :39
[    9.937782][  T210] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.937782][  T210] :43

🟡 ERROR (medium) ← PR symbols: write

[    9.937782][  T210] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

Context

[    9.936723][  T114] Bluetooth: hci0: setting up wcn6855
[    9.937690][  T210] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.937690][  T210] :39
[    9.937782][  T210] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.937782][  T210] :43
[    9.944938][  T210] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.944938][  T210] :39

🟡 ERROR (medium) ← PR symbols: failed, write

[    9.944938][  T210] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f

Context

[    9.937690][  T210] :39
[    9.937782][  T210] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.937782][  T210] :43
[    9.944938][  T210] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.944938][  T210] :39
[    9.948726][  T292] msm_dpu ae01000.display-controller: bound af54000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    9.949479][   T55] cfg80211: failed to load regulatory.db

🟡 ERROR (medium) ← PR symbols: write

[    9.956073][  T210] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

Context

[    9.950225][  T292] msm_dpu ae01000.display-controller: bound ae94000.dsi (ops dsi_ops [msm])
[    9.950306][  T292] msm_dpu ae01000.display-controller: bound ae96000.dsi (ops dsi_ops [msm])
[    9.951330][  T292] [drm:dpu_kms_hw_init:1201] dpu hardware revision:0x80040000
[    9.956073][  T210] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.956073][  T210] :43
[    9.996184][  T114] Bluetooth: hci0: QCA Product ID   :0x00000013
[   10.072846][  T292] [drm] Initialized msm-kms 1.13.0 for ae01000.display-controller on minor 1

🔵 FIRMWARE_FAIL (low) ← PR symbols: failed, qcom, data

[   11.983069][  T204] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22

Context

[   11.431982][  T114] Bluetooth: hci0: QCA FW build version: BTFW.HSP.2.1.2-00072-PATCHZ-2
[   11.443012][  T114] Bluetooth: hci0: QCA setup on UART is completed
[   11.449687][  T114] Bluetooth: hci0: HFP non-HCI data transport is supported
[   11.983069][  T204] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   12.005906][  T204] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   12.853845][  T204] hwmon hwmon51: temp1_input not attached to any thermal zone
[   12.886240][  T201] qcom-ethqos 23040000.ethernet end0: renamed from eth1

🟡 ERROR (medium) ← PR symbols: failed, qcom, data

[   12.005906][  T204] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22

Context

[   11.443012][  T114] Bluetooth: hci0: QCA setup on UART is completed
[   11.449687][  T114] Bluetooth: hci0: HFP non-HCI data transport is supported
[   11.983069][  T204] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   12.005906][  T204] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   12.853845][  T204] hwmon hwmon51: temp1_input not attached to any thermal zone
[   12.886240][  T201] qcom-ethqos 23040000.ethernet end0: renamed from eth1
[   12.893786][  T200] qcom-ethqos 23000000.ethernet end1: renamed from eth0

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   30.923483][  T384] EXT4-fs (sda2): orphan cleanup on readonly fs
[   30.930264][  T384] EXT4-fs (sda2): mounted filesystem 57198697-7c20-47a4-944c-71a7b61d6a7e ro with ordered data mode. Quota mode: none.
done.

Target: monaco-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 11 (0 critical, 0 high, 11 medium, 0 low)

🟡 ERROR (medium) ← PR symbols: supply, found, regulator

[    8.357657][  T228] usb usb2-port1: config error

Context

[    8.334202][  T175] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 22
[    8.345271][  T183] pca953x 3-003b: supply vcc not found, using dummy regulator
[    8.351012][  T186] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    8.357657][  T228] usb usb2-port1: config error
[    8.381587][  T183] pca953x 3-003b: using no AI
[    8.382148][  T207] Bluetooth: Core ver 2.22
[    8.388566][  T186] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'

🟡 ERROR (medium) ← PR symbols: failed, interrupt, device

[    8.446717][  T113] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    8.407114][  T207] Bluetooth: HCI socket layer initialized
[    8.407119][  T207] Bluetooth: L2CAP socket layer initialized
[    8.407135][  T207] Bluetooth: SCO socket layer initialized
[    8.446717][  T113] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.447499][  T183] irq: IRQ337: trimming hierarchy from :soc@0:interrupt-controller@b220000-9
[    8.456548][  T113] cfg80211: failed to load regulatory.db
[    8.462911][  T147] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)

🟡 ERROR (medium) ← PR symbols: failed, supply, device

[    8.480072][  T147] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[    8.456548][  T113] cfg80211: failed to load regulatory.db
[    8.462911][  T147] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)
[    8.465853][  T183] pca953x 3-003c: supply vcc not found, using dummy regulator
[    8.480072][  T147] tpm tpm0: A TPM error (256) occurred attempting the self test
[    8.489167][  T175] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 24
[    8.493980][  T147] tpm tpm0: starting up the TPM manually
[    8.505817][  T183] pca953x 3-003c: using no AI

🟡 ERROR (medium) ← PR symbols: failed, supply, found

[    8.842354][  T112] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2

Context

[    8.811884][  T186] ath11k_pci 0000:01:00.0: MSI vectors: 32
[    8.811907][  T186] ath11k_pci 0000:01:00.0: wcn6855 hw2.1
[    8.834491][  T112] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.842354][  T112] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.851141][  T183] lt8713sx 2-004f: supply vdd not found, using dummy regulator
[    8.851994][  T112] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.866538][  T183] lt8713sx 2-004f: supply vcc not found, using dummy regulator

🟡 ERROR (medium) ← PR symbols: failed, supply, found

[    8.882420][  T112] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

Context

[    8.851994][  T112] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.866538][  T183] lt8713sx 2-004f: supply vcc not found, using dummy regulator
[    8.867948][  T112] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.882420][  T112] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.891754][  T112] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.899921][  T112] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.900051][  T201] at24 1-0050: supply vcc not found, using dummy regulator

🟡 ERROR (medium) ← PR symbols: success, failed, power

[    8.980152][  T112] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2

Context

[    8.969982][  T186] mhi mhi0: Requested to power ON
[    8.976496][   T63] adreno 3d00000.gpu: supply vdd not found, using dummy regulator
[    8.979924][  T186] mhi mhi0: Power on setup success
[    8.980152][  T112] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    8.980167][  T112] mhi mhi0: Error loading firmware: -2
[    8.987954][   T63] adreno 3d00000.gpu: supply vddcx not found, using dummy regulator
[    8.993031][  T186] ath11k_pci 0000:01:00.0: failed to power up mhi: -110

🟡 ERROR (medium) ← PR symbols: success, failed, power

[    8.980167][  T112] mhi mhi0: Error loading firmware: -2

Context

[    8.976496][   T63] adreno 3d00000.gpu: supply vdd not found, using dummy regulator
[    8.979924][  T186] mhi mhi0: Power on setup success
[    8.980152][  T112] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    8.980167][  T112] mhi mhi0: Error loading firmware: -2
[    8.987954][   T63] adreno 3d00000.gpu: supply vddcx not found, using dummy regulator
[    8.993031][  T186] ath11k_pci 0000:01:00.0: failed to power up mhi: -110
[    9.017791][   T63] msm_dpu ae01000.display-controller: bound 3d00000.gpu (ops a3xx_ops [msm])

🟡 ERROR (medium) ← PR symbols: bits, failed, qcom

[    9.375039][  T228] usb usb2-port1: config error

Context

[    9.311506][   T43] hub 1-1:1.0: USB hub found
[    9.316446][   T63] qcom-ethqos 23040000.ethernet: Using 36/40 bits DMA host/device width
[    9.330222][   T43] hub 1-1:1.0: 4 ports detected
[    9.375039][  T228] usb usb2-port1: config error
[    9.395839][  T186] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110
[    9.467565][  T190] qcom-ethqos 23040000.ethernet end0: renamed from eth0
[    9.635647][  T228] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd

🟡 ERROR (medium) ← PR symbols: bits, failed, qcom

[    9.395839][  T186] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110

Context

[    9.316446][   T63] qcom-ethqos 23040000.ethernet: Using 36/40 bits DMA host/device width
[    9.330222][   T43] hub 1-1:1.0: 4 ports detected
[    9.375039][  T228] usb usb2-port1: config error
[    9.395839][  T186] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110
[    9.467565][  T190] qcom-ethqos 23040000.ethernet end0: renamed from eth0
[    9.635647][  T228] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd
[    9.709898][  T228] hub 2-1:1.0: USB hub found

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   31.781646][  T373] EXT4-fs (sda2): orphan cleanup on readonly fs
[   31.789064][  T373] EXT4-fs (sda2): mounted filesystem 513728bc-9c18-4a66-a6fb-01735755aeed ro with ordered data mode. Quota mode: none.
done.

Target: shikra-iqs-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 12 (0 critical, 0 high, 11 medium, 1 low)

🟡 ERROR (medium) ← PR symbols: failed, default, with

[    7.661781][  T138] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22

Context

[    7.551793][  T151]  cs_system_cfg: CoreSight Configuration manager initialised
[    7.622428][  T160] geni_i2c 4a8c000.i2c: Bus frequency not specified, default to 100kHz.
[    7.622918][  T141] input: pm8941_resin as /devices/platform/soc@0/1c40000.spmi/spmi-0/0-00/1c40000.spmi:pmic@0:pon@800/1c40000.spmi:pmic@0:pon@800:resin/input/input2
[    7.661781][  T138] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    7.675707][  T138] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.688699][  T138] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.701931][  T138] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22

🟡 ERROR (medium) ← PR symbols: failed, default, with

[    7.675707][  T138] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22

Context

[    7.622428][  T160] geni_i2c 4a8c000.i2c: Bus frequency not specified, default to 100kHz.
[    7.622918][  T141] input: pm8941_resin as /devices/platform/soc@0/1c40000.spmi/spmi-0/0-00/1c40000.spmi:pmic@0:pon@800/1c40000.spmi:pmic@0:pon@800:resin/input/input2
[    7.661781][  T138] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    7.675707][  T138] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.688699][  T138] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.701931][  T138] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.703867][  T161] mc: Linux media interface: v0.10

🟡 ERROR (medium) ← PR symbols: failed, with

[    7.688699][  T138] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22

Context

[    7.622918][  T141] input: pm8941_resin as /devices/platform/soc@0/1c40000.spmi/spmi-0/0-00/1c40000.spmi:pmic@0:pon@800/1c40000.spmi:pmic@0:pon@800:resin/input/input2
[    7.661781][  T138] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    7.675707][  T138] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.688699][  T138] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.701931][  T138] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.703867][  T161] mc: Linux media interface: v0.10
[    7.742957][   T90] l2: unsupportable voltage range: 3500000-3296000uV

🟡 ERROR (medium) ← PR symbols: failed, with

[    7.701931][  T138] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22

Context

[    7.661781][  T138] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    7.675707][  T138] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.688699][  T138] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.701931][  T138] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.703867][  T161] mc: Linux media interface: v0.10
[    7.742957][   T90] l2: unsupportable voltage range: 3500000-3296000uV
[    7.798422][   T60] arm-smmu 59a0000.iommu: probing hardware configuration...

🟡 ERROR (medium) ← PR symbols: failed, register, with

[    9.997226][   T48] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17

Context

[    9.966496][   T48] cpu cpu0: EM: created perf domain
[    9.981319][   T48] cpu cpu3: EM: created perf domain
[    9.990329][   T48] cpufreq-dt cpufreq-dt: failed register driver: -17
[    9.997226][   T48] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17
[   10.003912][  T149] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   10.031725][  T149] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.041131][  T149] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'

🟡 ERROR (medium) ← PR symbols: failed, qcom, found

[   10.066904][   T31] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   10.031725][  T149] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.041131][  T149] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.054837][   T78] Bluetooth: hci0: setting up wcn399x
[   10.066904][   T31] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.077178][   T31] cfg80211: failed to load regulatory.db
[   10.115449][   T90] l2: unsupportable voltage range: 3500000-3296000uV
[   10.151635][  T143] qcom-ethqos 5d20000.ethernet: IRQ eth_wake_irq not found

🟡 ERROR (medium) ← PR symbols: failed, remote, interrupt

[   10.522675][   T48] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110

Context

[   10.355851][   T90] l2: unsupportable voltage range: 3500000-3296000uV
[   10.396466][   T45] remoteproc remoteproc2: remote processor lpaicp is now up
[   10.478429][  T137] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[   10.522675][   T48] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110
[   10.567205][   T90] l2: unsupportable voltage range: 3500000-3296000uV
[   10.581835][  T155] irq: IRQ203: trimming hierarchy from :soc@0:interrupt-controller@f200000-1
[   10.594927][  T141] irq: IRQ204: trimming hierarchy from :soc@0:interrupt-controller@f200000-1

🟡 ERROR (medium) ← PR symbols: failed, request_firmware, with

[   10.742503][  T141] ucsi_ccg 3-0040: Direct firmware load for ccg_secondary.cyacd2 failed with error -2

Context

[   10.723787][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 15
[   10.726980][  T141] ucsi_ccg 3-0040: requesting firmware: ccg_secondary.cyacd2
[   10.737710][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 16
[   10.742503][  T141] ucsi_ccg 3-0040: Direct firmware load for ccg_secondary.cyacd2 failed with error -2
[   10.758256][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 17
[   10.762172][  T141] ucsi_ccg 3-0040: request_firmware(ccg_secondary.cyacd2) failed (-2)
[   10.776676][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 18

🔵 FIRMWARE_FAIL (low) ← PR symbols: failed, request_firmware, ccg_fw_update

[   10.762172][  T141] ucsi_ccg 3-0040: request_firmware(ccg_secondary.cyacd2) failed (-2)

Context

[   10.737710][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 16
[   10.742503][  T141] ucsi_ccg 3-0040: Direct firmware load for ccg_secondary.cyacd2 failed with error -2
[   10.758256][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 17
[   10.762172][  T141] ucsi_ccg 3-0040: request_firmware(ccg_secondary.cyacd2) failed (-2)
[   10.776676][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 18
[   10.779288][  T141] ucsi_ccg 3-0040: ccg_fw_update failed - -2
[   10.791787][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 19

🟡 ERROR (medium) ← PR symbols: failed, with, read

[   10.826550][  T141] ucsi_ccg 3-0040: probe with driver ucsi_ccg failed with error -2

Context

[   10.796758][   T90] l2: unsupportable voltage range: 3500000-3296000uV
[   10.807682][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 20
[   10.823331][  T138] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@9: Adding to iommu group 21
[   10.826550][  T141] ucsi_ccg 3-0040: probe with driver ucsi_ccg failed with error -2
[   11.027539][   T90] l2: unsupportable voltage range: 3500000-3296000uV
[   11.070385][  T152] lt9611c 4-0041: failed to read chip id.
Begin: Loading essential drivers ... done.

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p53

Context

[   22.461191][  T222] blkid (222) used greatest stack depth: 10168 bytes left
[   22.487953][   T90] l2: unsupportable voltage range: 3500000-3296000uV
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p53
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: while, failed, status

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p53
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   22.699933][   T90] l2: unsupportable voltage range: 3500000-3296000uV
[   22.911580][   T90] l2: unsupportable voltage range: 3500000-3296000uV
[   23.123959][   T90] l2: unsupportable voltage range: 3500000-3296000uV

Target: qcs6490-rb3gen2

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 19 (0 critical, 0 high, 18 medium, 1 low)

🟡 ERROR (medium) ← PR symbols: failed, with

[    7.091016][   T97] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    7.074204][  T163] coresight cti_sys1: CTI initialized 0
[    7.076706][  T194] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    7.088296][  T163] coresight cti_sys2: CTI initialized 0
[    7.091016][   T97] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    7.102129][  T192] remoteproc remoteproc2: wpss is available
[    7.102380][   T97] cfg80211: failed to load regulatory.db
[    7.130468][  T163] coresight cti_sys3: CTI initialized 0

🟡 ERROR (medium) ← PR symbols: supply, device, found

[    9.154496][  T169] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.130896][  T102] Bluetooth: hci0: setting up wcn6750
[    9.132006][  T169] /soc@0/display-subsystem@ae00000/dsi@ae94000: Fixed dependency cycle(s) with /soc@0/geniqup@9c0000/i2c@980000/hdmi-bridge@2b
[    9.150797][   T85] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[    9.154496][  T169] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.154502][  T169] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.197819][  T102] Bluetooth: hci0: QCA Product ID   :0x00000015
[    9.226901][  T164] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)

🟡 ERROR (medium) ← PR symbols: qcom, supply, device

[    9.154502][  T169] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.132006][  T169] /soc@0/display-subsystem@ae00000/dsi@ae94000: Fixed dependency cycle(s) with /soc@0/geniqup@9c0000/i2c@980000/hdmi-bridge@2b
[    9.150797][   T85] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[    9.154496][  T169] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.154502][  T169] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.197819][  T102] Bluetooth: hci0: QCA Product ID   :0x00000015
[    9.226901][  T164] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[    9.227849][  T255] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1

🟡 ERROR (medium) ← PR symbols: qcom, device, EINVAL

[    9.228086][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.226901][  T164] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[    9.227849][  T255] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[    9.227972][  T255] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[    9.228086][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.228098][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.228814][  T188] platform 3700000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 16
[    9.229782][  T188] platform 3700000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 17

🟡 ERROR (medium) ← PR symbols: qcom, EINVAL

[    9.228098][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.227849][  T255] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[    9.227972][  T255] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[    9.228086][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.228098][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.228814][  T188] platform 3700000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 16
[    9.229782][  T188] platform 3700000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 17
[    9.230601][  T188] platform 3700000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 18

🔵 FIRMWARE_FAIL (low) ← PR symbols: failed, fw_version, with

[    9.406566][  T182] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2

Context

[    9.338466][  T188] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 25
[    9.382001][  T212] ath11k 17a10040.wifi: chip_id 0x1 chip_family 0xb board_id 0xff soc_id 0x40140110
[    9.405651][  T188] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 26
[    9.406566][  T182] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2
[    9.406577][  T182] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2
[    9.412037][  T212] ath11k 17a10040.wifi: fw_version 0x200400cc fw_build_timestamp 2024-06-08 03:23 fw_build_id WLAN.MSL.2.0.c2-00204-QCAMSLSWPLZ-1
[    9.413309][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: failed, fw_version, with

[    9.406577][  T182] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2

Context

[    9.382001][  T212] ath11k 17a10040.wifi: chip_id 0x1 chip_family 0xb board_id 0xff soc_id 0x40140110
[    9.405651][  T188] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 26
[    9.406566][  T182] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2
[    9.406577][  T182] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2
[    9.412037][  T212] ath11k 17a10040.wifi: fw_version 0x200400cc fw_build_timestamp 2024-06-08 03:23 fw_build_id WLAN.MSL.2.0.c2-00204-QCAMSLSWPLZ-1
[    9.413309][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.413315][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: failed, fw_version, with

[    9.413309][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.406566][  T182] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2
[    9.406577][  T182] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2
[    9.412037][  T212] ath11k 17a10040.wifi: fw_version 0x200400cc fw_build_timestamp 2024-06-08 03:23 fw_build_id WLAN.MSL.2.0.c2-00204-QCAMSLSWPLZ-1
[    9.413309][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.413315][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.455688][  T339] scsi_id (339) used greatest stack depth: 10656 bytes left
[    9.464306][  T188] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@11: Adding to iommu group 27

🟡 ERROR (medium) ← PR symbols: failed, fw_version, with

[    9.413315][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.406577][  T182] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2
[    9.412037][  T212] ath11k 17a10040.wifi: fw_version 0x200400cc fw_build_timestamp 2024-06-08 03:23 fw_build_id WLAN.MSL.2.0.c2-00204-QCAMSLSWPLZ-1
[    9.413309][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.413315][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.455688][  T339] scsi_id (339) used greatest stack depth: 10656 bytes left
[    9.464306][  T188] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@11: Adding to iommu group 27
[    9.467040][  T168] mcp251xfd spi3.0 can0: MCP2518FD rev0.0 (-RX_INT -PLL -MAB_NO_WARN +CRC_REG +CRC_RX +CRC_TX +ECC -HD o:40.00MHz c:40.00MHz m:10.00MHz rs:10.00MHz es:0.00MHz rf:10.00MHz ef:0.00M

🟡 ERROR (medium) ← PR symbols: qcom, supply, vdda

[    9.687775][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.536389][  T190] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-001c for /pmic-glink/connector@0
[    9.664120][  T188] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@13: Adding to iommu group 29
[    9.676293][  T188] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@14: Adding to iommu group 30
[    9.687775][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.688104][  T180] qcom-edp-phy aec2a00.phy: supply vdda-phy not found, using dummy regulator
[    9.698000][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.707649][  T180] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator

🟡 ERROR (medium) ← PR symbols: qcom, supply, vdda

[    9.698000][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.676293][  T188] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@14: Adding to iommu group 30
[    9.687775][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.688104][  T180] qcom-edp-phy aec2a00.phy: supply vdda-phy not found, using dummy regulator
[    9.698000][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.707649][  T180] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator
[    9.724358][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.735355][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: qcom, supply, vdda

[    9.724358][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.688104][  T180] qcom-edp-phy aec2a00.phy: supply vdda-phy not found, using dummy regulator
[    9.698000][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.707649][  T180] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator
[    9.724358][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.735355][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.755014][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.763323][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: qcom, supply, vdda

[    9.735355][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.698000][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.707649][  T180] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator
[    9.724358][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.735355][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.755014][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.763323][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.773515][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: qcom, supply, vdda

[    9.755014][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

Context

[    9.707649][  T180] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator
[    9.724358][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.735355][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.755014][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.763323][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.773515][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.783516][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[    9.763323][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

Context

[    9.724358][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.735355][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.755014][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.763323][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.773515][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.783516][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.788792][  T184] lt9611uxc 0-002b: LT9611 revision: 0x17.04.93

🟡 ERROR (medium) ← PR symbols: EINVAL

[    9.773515][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.735355][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.755014][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.763323][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.773515][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.783516][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.788792][  T184] lt9611uxc 0-002b: LT9611 revision: 0x17.04.93
[    9.858553][  T184] lt9611uxc 0-002b: LT9611 version: 0x50

🟡 ERROR (medium) ← PR symbols: EINVAL

[    9.783516][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    9.755014][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.763323][   T85] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[    9.773515][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.783516][   T85] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.788792][  T184] lt9611uxc 0-002b: LT9611 revision: 0x17.04.93
[    9.858553][  T184] lt9611uxc 0-002b: LT9611 version: 0x50
[    9.934387][  T184] msm_dpu ae01000.display-controller: bound ae94000.dsi (ops dsi_ops [msm])

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   33.113004][  T393] EXT4-fs (sda2): orphan cleanup on readonly fs
[   33.121339][  T393] EXT4-fs (sda2): mounted filesystem 698d30c1-1e68-4325-852e-0d99efa1467f ro with ordered data mode. Quota mode: none.
done.

Target: qcs615-ride

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 4 (0 critical, 0 high, 4 medium, 0 low)

🟡 ERROR (medium) ← PR symbols: supply, vdda, found

[    9.017580][  T214] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    8.947475][  T165] /soc@0/display-subsystem@ae00000/dsi@ae94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[    8.965433][  T165] msm_dsi_phy ae94400.phy: supply vdda not found, using dummy regulator
[    8.999908][  T214] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[    9.017580][  T214] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.027488][  T214] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.052388][  T214] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    9.064802][  T214] msm_dpu ae01000.display-controller: bound ae94000.dsi (ops dsi_ops [msm])

🟡 ERROR (medium) ← PR symbols: supply, vdda, found

[    9.027488][  T214] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    8.965433][  T165] msm_dsi_phy ae94400.phy: supply vdda not found, using dummy regulator
[    8.999908][  T214] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[    9.017580][  T214] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.027488][  T214] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.052388][  T214] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    9.064802][  T214] msm_dpu ae01000.display-controller: bound ae94000.dsi (ops dsi_ops [msm])
[    9.075623][  T214] adreno 5000000.gpu: supply vdd not found, using dummy regulator

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Running /scripts/local-premount ... done.
[   26.045616][  T327] blkid (327) used greatest stack depth: 8512 bytes left
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   31.216171][  T337] EXT4-fs (sda2): orphan cleanup on readonly fs
[   31.224725][  T337] EXT4-fs (sda2): mounted filesystem 005fdba6-605e-4778-b1f7-ba98dc88617a ro with ordered data mode. Quota mode: none.
done.

Target: qcs8300-ride

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 24 (0 critical, 2 high, 22 medium, 0 low)

🟡 WARNING (medium) ← PR symbols: qcom, clocks, supply

[    5.184194][    T1] WARNING: CPU: 1 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98

Context

[    5.180703][   T63] qcom-pcie 1c10000.pci: supply vdda not found, using dummy regulator
[    5.183631][    T1] clk: Disabling unused clocks
[    5.184192][    T1] ------------[ cut here ]------------
[    5.184194][    T1] WARNING: CPU: 1 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98
[    5.184202][    T1] Modules linked in:
[    5.184206][    T1] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Tainted: G S      W           6.18.44-g4ae8784cc4c3 #1 PREEMPT 
[    5.184210][    T1] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN

🟠 CALL_TRACE (high)

[    5.184243][    T1] Call trace:

Context

[    5.184236][    T1] x8 : ffff800082c3bbe8 x7 : 0000000000000000 x6 : 0000000000000001
[    5.184238][    T1] x5 : ffff800080b41778 x4 : 000000000007706c x3 : 000000000007706c
[    5.184240][    T1] x2 : ffff800080b42e88 x1 : 0000000000000001 x0 : 0000000000000001
[    5.184243][    T1] Call trace:
[    5.184244][    T1]  phy_mux_is_enabled+0x7c/0x98 (P)
[    5.184246][    T1]  clk_core_is_enabled+0x44/0x120
[    5.184250][    T1]  clk_disable_unused_subtree+0x88/0x258

🟡 WARNING (medium) ← PR symbols: qcom

[    5.184304][    T1] WARNING: CPU: 1 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98

Context

[    5.184269][    T1]  ret_from_fork+0x10/0x20
[    5.184272][    T1] ---[ end trace 0000000000000000 ]---
[    5.184303][    T1] ------------[ cut here ]------------
[    5.184304][    T1] WARNING: CPU: 1 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98
[    5.184307][    T1] Modules linked in:
[    5.184309][    T1] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Tainted: G S      W           6.18.44-g4ae8784cc4c3 #1 PREEMPT 
[    5.184311][    T1] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN

🟠 CALL_TRACE (high)

[    5.184341][    T1] Call trace:

Context

[    5.184335][    T1] x8 : ffff800082c3bbe8 x7 : 0000000000000000 x6 : 0000000000000001
[    5.184337][    T1] x5 : ffff800080b41778 x4 : 00000000000a906c x3 : 00000000000a906c
[    5.184339][    T1] x2 : ffff800080b42e88 x1 : 0000000000000001 x0 : 0000000000000001
[    5.184341][    T1] Call trace:
[    5.184342][    T1]  phy_mux_is_enabled+0x7c/0x98 (P)
[    5.184344][    T1]  clk_core_is_enabled+0x44/0x120
[    5.184347][    T1]  clk_disable_unused_subtree+0x88/0x258

🟡 ERROR (medium) ← PR symbols: failed, assigned, device

[   11.167086][  T297] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   11.127797][  T162] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   11.151575][  T162] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.158568][  T162] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.167086][  T297] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.176880][  T297] cfg80211: failed to load regulatory.db
[   11.244529][  T162] ath11k_pci 0000:01:00.0: BAR 0 [mem 0x40400000-0x405fffff 64bit]: assigned
[   11.253437][  T162] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002)

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   34.848135][  T392] EXT4-fs (sda2): orphan cleanup on readonly fs
[   34.857056][  T392] EXT4-fs (sda2): mounted filesystem 985e5d67-cfc5-4f20-bc82-74addca41f10 ro with ordered data mode. Quota mode: none.
done.

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.111627][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   35.833919][    T1] Segment Routing with IPv6
[   35.838762][    T1] In-situ OAM (IOAM) with IPv6
[   36.106507][  T286] refgen: disabling
[   36.111627][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.121835][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.132548][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.141857][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.132548][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.106507][  T286] refgen: disabling
[   36.111627][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.121835][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.132548][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.141857][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.149558][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.160451][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.160451][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.132548][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.141857][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.149558][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.160451][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.169919][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.567817][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:00:00.0
[   36.577253][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.587978][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.169919][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.567817][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:00:00.0
[   36.577253][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.587978][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.597288][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.605066][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   36.614480][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.625467][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.597288][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.605066][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   36.614480][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.625467][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.634940][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.643864][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.654060][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.643864][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   36.614480][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.625467][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.634940][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.643864][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.654060][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.664779][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.674070][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.664779][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.634940][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.643864][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.654060][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.664779][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.674070][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.681768][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.692668][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.692668][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.664779][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.674070][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.681768][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.692668][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.702146][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.710064][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0 (no details found
[18t[   36.786183][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:00:00.0

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.710064][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0 (no details found

Context

[   36.681768][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.692668][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.702146][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.710064][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0 (no details found
[18t[   36.786183][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:00:00.0
[   36.795606][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.806327][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.806327][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.710064][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0 (no details found
[18t[   36.786183][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:00:00.0
[   36.795606][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.806327][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.815630][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.823325][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   36.832728][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.843620][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.815630][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.823325][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   36.832728][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.843620][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.853093][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.860980][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   37.004723][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

🟡 ERROR (medium) ← PR symbols: status, type, device

[   37.004723][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   36.843620][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.853093][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.860980][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   37.004723][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   37.014981][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.025743][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   37.035036][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   37.025743][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.860980][  T363] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   37.004723][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   37.014981][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.025743][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   37.035036][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   37.042743][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.053641][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium) ← PR symbols: mode, status, type

[   37.053641][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   37.025743][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   37.035036][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   37.042743][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.053641][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   37.063106][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
7[32766;32766H[6n8[!p]104\[0m[?7h[1G[0J[   37.420865][    T1] systemd[1]: systemd 261.2 running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA +IPE -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +
[   37.454390][    T1] systemd[1]: Detected architecture arm64.

🟡 ERROR (medium) ← PR symbols: mode, status, type

[   37.470478][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   37.063106][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
7[32766;32766H[6n8[!p]104\[0m[?7h[1G[0J[   37.420865][    T1] systemd[1]: systemd 261.2 running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA +IPE -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +
[   37.454390][    T1] systemd[1]: Detected architecture arm64.
[   37.470478][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   37.480836][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.491575][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   37.501061][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   37.491575][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   37.454390][    T1] systemd[1]: Detected architecture arm64.
[   37.470478][  T363] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   37.480836][  T363] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.491575][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   37.501061][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   37.508769][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.508772][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium) ← PR symbols: status, type, device

[   37.508772][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   37.491575][  T363] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   37.501061][  T363] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   37.508769][  T363] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.508772][  T363] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   37.508774][  T363] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)

[0;1;39mWelcome to [0m[1mQualcomm Linux Reference Distro 2.99+snapshot-d58a9f2dddfdeb4e74ef99929072ff6721590dc9[0m[0;1;39m![0m

Target: purwa-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 24 (0 critical, 1 high, 21 medium, 2 low)

🟡 WATCHDOG (medium) ← PR symbols: with

[    6.336514][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.

Context

[    6.284516][    T1] usbcore: registered new interface driver uas
[    6.293366][    T1] usbcore: registered new interface driver usb-storage
[    6.317844][    T1] i2c_dev: i2c /dev entries driver
[    6.336514][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.348070][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.355145][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.360453][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium) ← PR symbols: failed, already, with

[    6.394186][   T65] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    6.381214][    T1] pstore: Registered efi_pstore as persistent store backend
[    6.388811][   T65] efivars: efivars already registered
[    6.388919][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    6.394186][   T65] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    6.414215][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    6.426081][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    6.434840][    T1] usbcore: registered new interface driver usbhid

🔵 FIRMWARE_FAIL (low) ← PR symbols: failed, qcom

[    8.969129][   T75] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16

Context

[    8.938988][   T75] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_perf_level_get_fc_force]
[    8.952092][   T89] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    8.963860][   T75] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_clock_rates_triplet_out_of_spec]
[    8.969129][   T75] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    8.972646][   T89] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    8.980921][   T75] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    8.989153][   T89] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host

🔵 FIRMWARE_FAIL (low) ← PR symbols: failed, qcom, with

[    8.980921][   T75] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16

Context

[    8.963860][   T75] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_clock_rates_triplet_out_of_spec]
[    8.969129][   T75] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    8.972646][   T89] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    8.980921][   T75] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    8.989153][   T89] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.007077][   T75] cpu cpu0: EM: created perf domain
[    9.014691][   T89] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61

🟡 ERROR (medium) ← PR symbols: failed, qcom, with

[    8.989153][   T89] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host

Context

[    8.969129][   T75] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    8.972646][   T89] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    8.980921][   T75] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    8.989153][   T89] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.007077][   T75] cpu cpu0: EM: created perf domain
[    9.014691][   T89] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.083064][  T197] coresight stm0: STM32 initialized

🟡 ERROR (medium) ← PR symbols: failed, qcom, with

[    9.014691][   T89] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61

Context

[    8.980921][   T75] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    8.989153][   T89] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.007077][   T75] cpu cpu0: EM: created perf domain
[    9.014691][   T89] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.083064][  T197] coresight stm0: STM32 initialized
[    9.163704][  T229] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.171638][   T75] cpu cpu4: EM: created perf domain

🟡 ERROR (medium) ← PR symbols: failed, qcom, connector

[    9.461690][   T89] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host

Context

[    9.453094][  T111] /soc@0/pci@1c08000/pcie@0: Fixed dependency cycle(s) with /wifi-bt-connector
[    9.453172][  T163] scsi 0:0:0:49476: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.461597][   T89] phy phy-1bfc000.phy.0: phy poweron failed --> -61
[    9.461690][   T89] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host
[    9.474217][  T163] scsi 0:0:0:49456: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.474272][  T205] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-0008 for /pmic-glink/connector@0
[    9.474278][  T205] /soc@0/phy@fd5000: Fixed dependency cycle(s) with /soc@0/geniqup@bc0000/i2c@b8c000/typec-mux@8

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[    9.481593][   T89] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61

Context

[    9.478073][  T205] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 3-0008 for /pmic-glink/connector@1
[    9.478080][  T205] /soc@0/phy@fda000: Fixed dependency cycle(s) with /soc@0/geniqup@bc0000/i2c@b9c000/typec-mux@8
[    9.478241][  T205] /soc@0/geniqup@bc0000/i2c@b9c000/typec-mux@8: Fixed dependency cycle(s) with /soc@0/phy@fda000
[    9.481593][   T89] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61
[    9.481751][  T111] qcom-pcie 1c08000.pci: supply vdda not found, using dummy regulator
[    9.481867][  T111] qcom-pcie 1c08000.pci: supply vddpe-3v3 not found, using dummy regulator
[    9.482065][  T111] qcom-pcie 1c08000.pci: host bridge /soc@0/pci@1c08000 ranges:

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[   10.516825][  T219] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led

Context

[   10.493540][  T161] pcieport 0005:00:00.0: AER: enabled with IRQ 195
[   10.502925][  T161] qcom-pcie 1c08000.pci: supply vdda not found, using dummy regulator
[   10.513016][  T161] qcom-pcie 1c08000.pci: supply vddpe-3v3 not found, using dummy regulator
[   10.516825][  T219] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   10.521944][  T161] qcom-pcie 1c08000.pci: host bridge /soc@0/pci@1c08000 ranges:
[   10.533982][  T219] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   10.538874][  T161] qcom-pcie 1c08000.pci:       IO 0x007c200000..0x007c2fffff -> 0x0000000000

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[   10.533982][  T219] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22

Context

[   10.513016][  T161] qcom-pcie 1c08000.pci: supply vddpe-3v3 not found, using dummy regulator
[   10.516825][  T219] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   10.521944][  T161] qcom-pcie 1c08000.pci: host bridge /soc@0/pci@1c08000 ranges:
[   10.533982][  T219] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   10.538874][  T161] qcom-pcie 1c08000.pci:       IO 0x007c200000..0x007c2fffff -> 0x0000000000
[   10.558138][  T161] qcom-pcie 1c08000.pci:      MEM 0x007c300000..0x007dffffff -> 0x007c300000
[   10.582168][  T208] videodev: Linux video capture interface: v2.00

🟡 ERROR (medium) ← PR symbols: device, with, self

[   11.281153][  T161] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[   11.243774][  T161] pcieport 0004:00:00.0: AER: enabled with IRQ 223
[   11.269335][  T161] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   11.278556][  T216] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   11.281153][  T161] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.283154][  T220] platform iris_non_pixel.0: Adding to iommu group 16
[   11.283771][  T220] platform iris_pixel.0: Adding to iommu group 17
[   11.292045][  T216] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'

🟡 ERROR (medium) ← PR symbols: failed, qcom, type

[   11.328629][  T301] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   11.292045][  T216] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.295053][  T161] tpm tpm0: starting up the TPM manually
[   11.301983][  T216] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.328629][  T301] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.338294][  T301] cfg80211: failed to load regulatory.db
[   11.356456][  T208] qcom-camss acb7000.isp: Entity type for entity msm_tpg0 was not initialized!
[   11.365493][  T208] qcom-camss acb7000.isp: Entity type for entity msm_tpg1 was not initialized!

🟡 ERROR (medium) ← PR symbols: with, EINVAL

[   11.691764][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.626385][  T221] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   11.650937][  T221] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   11.667272][  T221] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   11.691764][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.701634][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.714792][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.724687][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: with, EINVAL

[   11.701634][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.650937][  T221] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   11.667272][  T221] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   11.691764][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.701634][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.714792][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.724687][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.735931][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: with, EINVAL

[   11.714792][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.667272][  T221] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   11.691764][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.701634][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.714792][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.724687][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.735931][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.745825][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   11.724687][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.691764][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.701634][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.714792][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.724687][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.735931][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.745825][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.759125][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   11.735931][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.701634][  T111] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.714792][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.724687][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.735931][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.745825][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.759125][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.761448][  T209] Bluetooth: Core ver 2.22

🟡 ERROR (medium) ← PR symbols: EINVAL

[   11.745825][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.714792][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.724687][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.735931][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.745825][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.759125][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.761448][  T209] Bluetooth: Core ver 2.22
[   11.768960][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   11.759125][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.724687][  T111] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.735931][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.745825][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.759125][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.761448][  T209] Bluetooth: Core ver 2.22
[   11.768960][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.773387][  T209] NET: Registered PF_BLUETOOTH protocol family

🟡 ERROR (medium) ← PR symbols: device, with, EINVAL

[   11.768960][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.745825][  T111] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.759125][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.761448][  T209] Bluetooth: Core ver 2.22
[   11.768960][  T111] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.773387][  T209] NET: Registered PF_BLUETOOTH protocol family
[   11.785667][  T111] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   11.789363][  T209] Bluetooth: HCI device and connection manager initialized

🟡 WARNING (medium) ← PR symbols: typec

[   12.022298][  T111] WARNING: CPU: 4 PID: 111 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   11.857003][  T326] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
[   11.869062][  T326] Bluetooth: hci0: QCA: patch rome 0x190200 build 0x8567, firmware rome 0x190200 build 0x43fb
[   12.016833][  T111] ------------[ cut here ]------------
[   12.022298][  T111] WARNING: CPU: 4 PID: 111 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   12.034637][  T111] Modules linked in: btusb btrtl btintel btbcm panel_edp(+) bluetooth ecdh_generic ecc ath12k_wifi7 msm ath12k ocmem mac80211 qcom_camss gpu_sched v4l2_fwnode rpmsg_ctrl libarc4 v
[   12.034880][  T111]  videocc_x1p42100 qcom_stats mc ubwc_config libdes dispcc_x1e80100 phy_qcom_edp drm qcom_common phy_qcom_qmp_usb phy_qcom_qmp_ufs authenc snd_soc_lpass_tx_macro phy_snps_eusb2 s
[   12.203439][  T111] CPU: 4 UID: 0 PID: 111 Comm: kworker/u33:3 Not tainted 6.18.44-g4ae8784cc4c3 #1 PREEMPT 

🟠 CALL_TRACE (high)

[   12.334062][  T111] Call trace:

Context

[   12.309939][  T111] x8 : ffff8000841ab468 x7 : 0000000000000000 x6 : 0000000000000001
[   12.317979][  T111] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   12.326020][  T111] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   12.334062][  T111] Call trace:
[   12.337296][  T111]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   12.344176][  T111]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   12.349995][  T111]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   33.731188][  T420] EXT4-fs (sda2): orphan cleanup on readonly fs
[   33.737846][  T420] EXT4-fs (sda2): mounted filesystem 2e16df27-6eab-4d72-84b7-a63f5340d8a3 ro with ordered data mode. Quota mode: none.
done.

Target: hamoa-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 20 (0 critical, 1 high, 19 medium, 0 low)

🟡 WATCHDOG (medium) ← PR symbols: with

[    6.974126][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.

Context

[    6.921688][    T1] usbcore: registered new interface driver usb-storage
[    6.932104][   T89] Freeing initrd memory: 61068K
[    6.951015][    T1] i2c_dev: i2c /dev entries driver
[    6.974126][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.986039][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.993107][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.998410][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium) ← PR symbols: failed, already, with

[    7.032154][   T89] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    7.019186][    T1] pstore: Registered efi_pstore as persistent store backend
[    7.026786][   T89] efivars: efivars already registered
[    7.026893][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    7.032154][   T89] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    7.039769][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    7.063744][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    7.072479][    T1] usbcore: registered new interface driver usbhid

🟡 ERROR (medium) ← PR symbols: qcom, connector, typec

[   11.496218][  T263] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led

Context

[   11.477126][  T254] remoteproc remoteproc0: adsp is available
[   11.477617][  T262] /soc@0/geniqup@bc0000/i2c@b84000/typec-mux@8: Fixed dependency cycle(s) with /soc@0/phy@fdf000
[   11.495832][  T255] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: registered as rtc0
[   11.496218][  T263] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   11.497267][  T281] input: pmic_pwrkey as /devices/platform/soc@0/c400000.arbiter/spmi-0/0-00/c42d000.spmi:pmic@0:pon@1300/c42d000.spmi:pmic@0:pon@1300:pwrkey/input/input0
[   11.497581][  T257] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier fd5000.phy for /pmic-glink/connector@0
[   11.498161][  T254] remoteproc remoteproc1: cdsp is available

🟡 ERROR (medium) ← PR symbols: failed, qcom, clock

[   11.512871][  T263] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22

Context

[   11.503591][  T255] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: setting system clock to 1980-01-06T00:00:21 UTC (315964821)
[   11.508816][  T332] remoteproc remoteproc1: powering up cdsp
[   11.508819][  T332] remoteproc remoteproc1: Booting fw image qcom/x1e80100/cdsp.mbn, size 3215784
[   11.512871][  T263] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   11.533075][  T298] platform iris_non_pixel.0: Adding to iommu group 16
[   11.533192][  T315] remoteproc remoteproc0: powering up adsp
[   11.533197][  T315] remoteproc remoteproc0: Booting fw image qcom/x1e80100/adsp.mbn, size 17922440

🟡 ERROR (medium) ← PR symbols: failed, device, with

[   11.797613][  T315] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   11.795732][  T209] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   11.797182][  T296] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.797443][  T296] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.797613][  T315] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.797623][  T315] cfg80211: failed to load regulatory.db
[   11.799648][  T209] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.799651][  T209] tpm tpm0: starting up the TPM manually

🟡 ERROR (medium) ← PR symbols: failed, qcom, port

[   11.799648][  T209] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[   11.797443][  T296] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.797613][  T315] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.797623][  T315] cfg80211: failed to load regulatory.db
[   11.799648][  T209] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.799651][  T209] tpm tpm0: starting up the TPM manually
[   11.801025][  T122] hub 1-0:1.0: 1 port detected
[   11.810927][  T127] qcom,apr 6800000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2

🟡 ERROR (medium) ← PR symbols: device, with, EINVAL

[   12.331969][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.288448][  T292] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   12.304937][  T292] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   12.330345][  T281] Bluetooth: Core ver 2.22
[   12.331969][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.334801][  T281] NET: Registered PF_BLUETOOTH protocol family
[   12.344598][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.350788][  T281] Bluetooth: HCI device and connection manager initialized

🟡 ERROR (medium) ← PR symbols: device, EINVAL

[   12.344598][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.330345][  T281] Bluetooth: Core ver 2.22
[   12.331969][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.334801][  T281] NET: Registered PF_BLUETOOTH protocol family
[   12.344598][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.350788][  T281] Bluetooth: HCI device and connection manager initialized
[   12.362806][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.367898][  T281] Bluetooth: HCI socket layer initialized

🟡 ERROR (medium) ← PR symbols: device, EINVAL

[   12.362806][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.334801][  T281] NET: Registered PF_BLUETOOTH protocol family
[   12.344598][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.350788][  T281] Bluetooth: HCI device and connection manager initialized
[   12.362806][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.367898][  T281] Bluetooth: HCI socket layer initialized
[   12.377725][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.383466][  T281] Bluetooth: L2CAP socket layer initialized

🟡 ERROR (medium) ← PR symbols: device, EINVAL

[   12.377725][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.350788][  T281] Bluetooth: HCI device and connection manager initialized
[   12.362806][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.367898][  T281] Bluetooth: HCI socket layer initialized
[   12.377725][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.383466][  T281] Bluetooth: L2CAP socket layer initialized
[   12.395318][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.399238][  T281] Bluetooth: SCO socket layer initialized

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.395318][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.367898][  T281] Bluetooth: HCI socket layer initialized
[   12.377725][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.383466][  T281] Bluetooth: L2CAP socket layer initialized
[   12.395318][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.399238][  T281] Bluetooth: SCO socket layer initialized
[   12.409076][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.426365][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: with, EINVAL

[   12.409076][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.383466][  T281] Bluetooth: L2CAP socket layer initialized
[   12.395318][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.399238][  T281] Bluetooth: SCO socket layer initialized
[   12.409076][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.426365][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.436259][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.446879][  T122] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel

🟡 ERROR (medium) ← PR symbols: with, EINVAL

[   12.426365][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.395318][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.399238][  T281] Bluetooth: SCO socket layer initialized
[   12.409076][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.426365][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.436259][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.446879][  T122] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   12.464647][  T122] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000

🟡 ERROR (medium) ← PR symbols: with, EINVAL

[   12.436259][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.399238][  T281] Bluetooth: SCO socket layer initialized
[   12.409076][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.426365][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.436259][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.446879][  T122] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   12.464647][  T122] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   12.485577][  T281] usbcore: registered new interface driver btusb

🟡 WARNING (medium) ← PR symbols: typec, fw_version

[   12.661174][  T122] WARNING: CPU: 1 PID: 122 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   12.622007][  T127] ath12k_wifi7_pci 0004:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0x10e soc_id 0x40170200
[   12.632457][  T127] ath12k_wifi7_pci 0004:01:00.0: fw_version 0x1103006c fw_build_timestamp 2026-03-06 09:10 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_
[   12.655683][  T122] ------------[ cut here ]------------
[   12.661174][  T122] WARNING: CPU: 1 PID: 122 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   12.673532][  T122] Modules linked in: qrtr_mhi panel_edp(+) btusb btrtl btintel btbcm bluetooth ecdh_generic ecc ath12k_wifi7 ath12k mac80211 msm snd_q6apm(+) libarc4 apr cfg80211 tpm_tis_spi ocme
[   12.673784][  T122]  qcom_sysmon pinctrl_lpass_lpi phy_snps_eusb2 snd_soc_wcd938x phy_qcom_qmp_usb sha1 qcom_common soundwire_qcom snd_soc_lpass_rx_macro snd_soc_lpass_wsa_macro snd_soc_wcd938x_sdw
[   12.842244][  T122] CPU: 1 UID: 0 PID: 122 Comm: kworker/u50:10 Not tainted 6.18.44-g4ae8784cc4c3 #1 PREEMPT 

🟠 CALL_TRACE (high)

[   12.973352][  T122] Call trace:

Context

[   12.949168][  T122] x8 : ffff80008442b468 x7 : 0000000000000000 x6 : 0000000000000001
[   12.957229][  T122] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   12.965290][  T122] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   12.973352][  T122] Call trace:
[   12.976605][  T122]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   12.983518][  T122]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   12.989358][  T122]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium) ← PR symbols: EINVAL

[   13.158691][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   13.132580][  T122]  ret_from_fork+0x10/0x20
[   13.137000][  T122] ---[ end trace 0000000000000000 ]---
[   13.142641][  T122] panel-simple-dp-aux aux-aea0000.displayport-controller: Unknown panel BOE 0x0b21, using conservative timings
[   13.158691][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.168554][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.176615][  T412] Bluetooth: hci0: using NVM file: qca/nvm_usb_00190200_010e.bin
[   13.183393][  T122] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium) ← PR symbols: EINVAL

[   13.168554][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   13.137000][  T122] ---[ end trace 0000000000000000 ]---
[   13.142641][  T122] panel-simple-dp-aux aux-aea0000.displayport-controller: Unknown panel BOE 0x0b21, using conservative timings
[   13.158691][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.168554][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.176615][  T412] Bluetooth: hci0: using NVM file: qca/nvm_usb_00190200_010e.bin
[   13.183393][  T122] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   13.200111][  T122] msm_dpu ae01000.display-controller: bound ae98000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   32.200687][  T515] EXT4-fs (sda2): orphan cleanup on readonly fs
[   32.207382][  T515] EXT4-fs (sda2): mounted filesystem 2afe7eee-2d67-4173-9b85-5b1918477db3 ro with ordered data mode. Quota mode: none.
done.

[qlijarvis]

PR #1062 — validate-patch

PR: #1062

Verdict	Issues	Detailed Report
⚠️	5	Full report

Final Summary

1. Lore link present: Yes for commits 4-8 (FROMLIST); No for commits 1-3 (QCLINUX vendor-only, no lore link expected)
2. Lore link matches PR commits: No — Commit 4/8 bundles extra driver/binding changes; Commit 7/8 contains 1986 lines of unrelated firmware code; Commit 8/8 bundles unrelated binding changes; Commits 6/7/8 have invalid lore links (patch 4/3)
3. Upstream patch status: ✅ ACKed for commits 4-7 (positive reviews from maintainers); ⏳ Decision Pending for commit 8
4. PR present in qcom-next/topics: Fail - 2/8 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1062 - Add USB support for Shikra platforms
Verdict: ⚠️ PARTIAL

---

Summary by Commit

Commit 1/8: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"

Upstream commit: N/A (vendor-only revert)
Verdict: ✅ PASS (vendor-only)

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: prefix — vendor-only revert
Body preserves rationale	✅	Clear explanation of why revert is needed
Fixes tag present/correct	N/A	Revert commit
Authorship preserved	✅	Akash Kumar (submitter)
Backport note	N/A	Not a backport

Diff: Reverts USB nodes from shikra-iqs-evk.dts — clean revert operation.

---

Commit 2/8: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"

Upstream commit: N/A (vendor-only revert)
Verdict: ✅ PASS (vendor-only)

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: prefix — vendor-only revert
Body preserves rationale	✅	Clear explanation of superseding by upstream series
Fixes tag present/correct	N/A	Revert commit
Authorship preserved	✅	Akash Kumar (submitter)
Backport note	N/A	Not a backport

Diff: Reverts USB nodes from shikra-cqm-evk.dts, shikra-cqs-evk.dts, and shikra.dtsi — clean revert operation.

---

Commit 3/8: QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"

Upstream commit: N/A (vendor-only revert)
Verdict: ✅ PASS (vendor-only)

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: prefix — vendor-only revert
Body preserves rationale	✅	Explains removal of typec role-switch wiring
Fixes tag present/correct	N/A	Revert commit
Authorship preserved	✅	Akash Kumar (submitter)
Backport note	N/A	Not a backport

Diff: Reverts typec role-switch wiring — clean revert operation.

---

Commit 4/8: FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra

Upstream commit: https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/
Verdict: ❌ FAIL

Check	Status	Note
Subject matches upstream	⚠️	Subject matches but content diverges significantly
Body preserves rationale	⚠️	Body text matches upstream
Fixes tag present/correct	N/A	No Fixes tag in upstream
Authorship preserved	❌	FAIL: Author mismatch — PR shows Krishna Kurapati but has Signed-off-by: Akash Kumar added
Backport note	N/A	FROMLIST: not a backport

Diff:

File	Status	Notes
Documentation/devicetree/bindings/phy/qcom,qcs615-qmp-usb3dp-phy.yaml	❌	FAIL: Extra content — binding change not in lore patch
arch/arm64/boot/dts/qcom/shikra.dtsi	✅	USB node additions match upstream
drivers/phy/qualcomm/phy-qcom-qmp-usbc.c	❌	FAIL: Extra content — driver changes not in lore patch
drivers/pinctrl/qcom/pinctrl-shikra.c	❌	FAIL: Extra content — pinctrl change not in lore patch

Issues

Commit 4/8 — Content Mismatch:

The lore patch at https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/ is a cover letter for a 2-patch series:

• Patch 1/2: arm64: dts: qcom: Add support for usb nodes on Shikra
• Patch 2/2: arm64: dts: qcom: Enable USB controllers on Shikra platforms

The PR commit 4/8 claims to be "FROMLIST" of the first patch but contains:

1. DT binding changes (qcom,qcs615-qmp-usb3dp-phy.yaml) — not in the lore DT patch
2. PHY driver changes (phy-qcom-qmp-usbc.c) — not in the lore DT patch
3. Pinctrl driver changes (pinctrl-shikra.c) — not in the lore DT patch

These extra changes appear to be dependencies from other patch series (likely the PHY binding/driver series mentioned in the cover letter dependencies). They should be split into separate commits with their own lore links, not bundled into a DT-only FROMLIST commit.

Authorship Issue:

• Lore patch author: Krishna Kurapati krishna.kurapati@oss.qualcomm.com
• PR commit From: field: Krishna Kurapati (correct)
• PR commit has additional Signed-off-by: Akash Kumar — this is acceptable for FROMLIST commits where the submitter adds their sign-off, but the original author's Signed-off-by: must also be present. ✅ It is present.

---

Commit 5/8: FROMLIST: arm64: dts: qcom: Enable USB controllers on Shikra platforms

Upstream commit: https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/
Verdict: ✅ PASS

Check	Status	Note
Subject matches upstream	✅	Matches lore patch 2/2 subject
Body preserves rationale	✅	Body text matches upstream
Fixes tag present/correct	N/A	No Fixes tag in upstream
Authorship preserved	✅	Krishna Kurapati + Akash Kumar sign-off (correct for FROMLIST)
Backport note	N/A	FROMLIST: not a backport

Diff:

File	Status	Notes
arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts	✅	USB phy supply wiring matches upstream
arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts	✅	USB phy supply wiring matches upstream
arch/arm64/boot/dts/qcom/shikra-evk.dtsi	✅	dr_mode = "peripheral" matches upstream
arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts	✅	USB phy supply wiring matches upstream
arch/arm64/boot/dts/qcom/shikra.dtsi	✅	Removal of usb_qmpphy_out/usb_1_dwc3_hs endpoints matches upstream

---

Commit 6/8: FROMLIST: dt-bindings: usb: Add Cypress cypd6129/cypd6229 Type-C controller

Upstream commit: https://lore.kernel.org/all/20260820145036.2035641-4-akash.kumar@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Check	Status	Note
Subject matches upstream	⚠️	Subject matches but lore link points to patch 4/3 (invalid)
Body preserves rationale	✅	Body text matches upstream
Fixes tag present/correct	N/A	No Fixes tag in upstream
Authorship preserved	✅	Akash Kumar (correct)
Backport note	N/A	FROMLIST: not a backport

Diff:

File	Status	Notes
Documentation/devicetree/bindings/usb/cypress,cypd6129.yaml	✅	Binding content matches upstream

Issue: The lore link 20260820145036.2035641-4-akash.kumar@oss.qualcomm.com is patch 4 of a 3-patch series (0/3 cover letter exists). This is likely a typo — should be patch 2/3 or 3/3. The lore thread shows this is part of a series titled "Add usb-role-switch support for USB Type-C ports on Shikra" with patches:

• 0/3: Cover letter
• 1/3: dt-bindings: phy: qcom,qcs615-qmp-usb3dp-phy: Document orientation-switch
• 2/3: dt-bindings: usb: Add Cypress cypd6129/cypd6229 Type-C controller
• 3/3: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229

The link should point to patch 2/3, not 4/3.

---

Commit 7/8: FROMLIST: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229

Upstream commit: https://lore.kernel.org/all/20260820145036.2035641-4-akash.kumar@oss.qualcomm.com/
Verdict: ❌ FAIL

Check	Status	Note
Subject matches upstream	⚠️	Subject matches but lore link points to patch 4/3 (invalid)
Body preserves rationale	❌	FAIL: Body text does not match upstream
Fixes tag present/correct	N/A	No Fixes tag in upstream
Authorship preserved	✅	Akash Kumar (correct)
Backport note	N/A	FROMLIST: not a backport

Diff:

File	Status	Notes
drivers/usb/typec/ucsi/ucsi_ccg.c	❌	FAIL: Massive content divergence — PR shows 2769 insertions, 783 deletions; upstream patch is ~10 lines adding compatible strings

Critical Issue: The PR commit claims to be a simple driver update adding cypd6129/cypd6229 compatible strings (matching the upstream commit message), but the actual diff shows 1986 insertions and 783 deletions — a massive rewrite of the ucsi_ccg driver including:

• New HPIv2 core addresses and register definitions
• Flash row read/write infrastructure
• Firmware update logic
• Module parameter for firmware file override
• Complete driver restructuring

The upstream lore patch (patch 3/3 of the series) is a simple 2-line addition to the of_device_id table. The PR commit contains unrelated firmware update infrastructure that has no lore attribution.

This is a severe validation failure — the commit is mislabeled as FROMLIST when it contains substantial vendor-specific code with no upstream equivalent.

---

Commit 8/8: FROMLIST: arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports

Upstream commit: https://lore.kernel.org/all/20260820145036.2035641-4-akash.kumar@oss.qualcomm.com/
Verdict: ❌ FAIL

Check	Status	Note
Subject matches upstream	⚠️	Subject matches but lore link points to patch 4/3 (invalid)
Body preserves rationale	✅	Body text matches upstream
Fixes tag present/correct	N/A	No Fixes tag in upstream
Authorship preserved	✅	Akash Kumar (correct)
Backport note	N/A	FROMLIST: not a backport

Diff:

File	Status	Notes
Documentation/devicetree/bindings/media/qcom,qcm2290-venus.yaml	❌	FAIL: Unrelated binding change — removes iommus property, not in lore patch
Documentation/devicetree/bindings/phy/qcom,qcs615-qmp-usb3dp-phy.yaml	⚠️	Binding updates for orientation-switch — should be separate commit with its own lore link
Documentation/devicetree/bindings/pinctrl/qcom,shikra-tlmm.yaml	⚠️	Adds gpio-hog pattern — not in lore patch
Documentation/devicetree/bindings/usb/qcom,snps-dwc3.yaml	⚠️	Moves shikra-dwc3 to different schema section — not in lore patch
arch/arm64/boot/dts/qcom/shikra-*.dts	✅	Typec node and role-switch wiring matches upstream

Issues:

1. Unrelated binding changes bundled — the venus, phy, pinctrl, and USB controller binding updates are not part of the lore patch and should be separate commits.
2. Lore link error — same issue as commits 6 and 7 (patch 4/3 doesn't exist).

---

Upstream Patch Status

Commit	Community Verdict
1/8 (QCLINUX revert)	N/A — vendor-only
2/8 (QCLINUX revert)	N/A — vendor-only
3/8 (QCLINUX revert)	N/A — vendor-only
4/8 (USB nodes)	✅ ACKed — Reviewed-by: Konrad Dybcio, Manivannan Sadhasivam, Dmitry Baryshkov (lore thread shows positive reviews)
5/8 (Enable USB)	✅ ACKed — Reviewed-by: Manivannan Sadhasivam, Dmitry Baryshkov
6/8 (cypd6129 binding)	✅ ACKed — Acked-by: Conor Dooley (DT binding maintainer)
7/8 (cypd6129 driver)	✅ ACKed — Reviewed-by: Abel Vesa (lore thread shows review tag)
8/8 (role-switch wiring)	⏳ Decision Pending — no maintainer merge confirmation found in lore thread

---

Integration Presence (from integration_presence_report.md)

Commit	qcom-next	topics	Final
1/8	missing	missing	❌ missing
2/8	partial	present	✅ present
3/8	missing	missing	❌ missing
4/8	partial	partial	⚠️ partial
5/8	partial	partial	⚠️ partial
6/8	missing	present	✅ present
7/8	partial	partial	⚠️ partial
8/8	partial	partial	⚠️ partial

Overall: FAIL — 2/8 commits missing from both qcom-next and topics.

---

Final Verdict

⚠️ PARTIAL — Requires Corrections Before Merge

Critical Issues:

1. Commit 4/8 — Content Bundling: The FROMLIST commit bundles PHY binding, PHY driver, and pinctrl driver changes that are not in the linked lore patch. These should be split into separate commits with their own lore links (likely from the PHY series mentioned in dependencies).

2. Commit 7/8 — Severe Content Mismatch: The commit claims to add cypd6129/cypd6229 compatible strings (matching the lore patch) but actually contains 1986 lines of unrelated firmware update infrastructure with no lore attribution. This is a validation failure — the commit is mislabeled as FROMLIST when it contains substantial vendor-specific code.

3. Commit 8/8 — Unrelated Binding Changes: Bundles venus, phy, pinctrl, and USB controller binding updates that are not in the lore patch. These should be separate commits.

4. Commits 6/7/8 — Invalid Lore Links: All three commits link to 20260820145036.2035641-4-akash.kumar@oss.qualcomm.com (patch 4 of a 3-patch series). The correct links should be:

   • Commit 6: patch 2/3 (cypd6129 binding)
   • Commit 7: patch 3/3 (cypd6129 driver)
   • Commit 8: Should be a separate lore series (DT wiring patch)

5. Integration Presence: 2/8 commits (1/8 and 3/8) are missing from both qcom-next and topics. These are QCLINUX reverts, so this may be expected, but should be verified.

Recommendations:

1. Split commit 4/8 into:

   • DT-only commit (FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra) with link to the DT patch
   • PHY binding commit (FROMLIST: dt-bindings: phy: ...) with link to the PHY binding patch
   • PHY driver commit (FROMLIST: phy: qcom: qmp-usbc: Add Shikra support) with link to the PHY driver patch
   • Pinctrl driver commit (if needed) with appropriate prefix and link

2. Fix commit 7/8 — Remove the 1986 lines of firmware update infrastructure. If this code is needed, it should be in a separate commit with:

   • QCLINUX: prefix (if vendor-only)
   • Or FROMLIST: with a link to the upstream firmware update series (if it exists)
   • The current commit should contain only the 2-line compatible string addition from the lore patch

3. Split commit 8/8 into:

   • Binding updates (separate commits for venus, phy, pinctrl, USB controller) with their own lore links
   • DT wiring commit (FROMLIST: arm64: dts: qcom: shikra: Wire up usb-role-switch) with corrected lore link

4. Fix lore links for commits 6/7/8 to point to the correct patch numbers in the series.

5. Verify integration presence for commits 1/8 and 3/8 — if these reverts are intentional and not yet in qcom-next/topics, document why.

---

Final Summary

1. Lore link present: Yes for commits 4-8 (FROMLIST); No for commits 1-3 (QCLINUX vendor-only, no lore link expected)
2. Lore link matches PR commits: No — Commit 4/8 bundles extra driver/binding changes; Commit 7/8 contains 1986 lines of unrelated firmware code; Commit 8/8 bundles unrelated binding changes; Commits 6/7/8 have invalid lore links (patch 4/3)
3. Upstream patch status: ✅ ACKed for commits 4-7 (positive reviews from maintainers); ⏳ Decision Pending for commit 8
4. PR present in qcom-next/topics: Fail — 2/8 commits missing; 4/8 partial; 2/8 present

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: d49c33864d06e9672dce57738be8851384578fcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/8	[PATCH 1/8] QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing
2/8	[PATCH 2/8] QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB	partial - subject or partial tree evidence found, but full change was not verified	present - all checked added lines are present	present
3/8	[PATCH 3/8] QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing
4/8	[PATCH 4/8] FROMLIST: arm64: dts: qcom: Add support for usb nodes on	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
5/8	[PATCH 5/8] FROMLIST: arm64: dts: qcom: Enable USB controllers on	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
6/8	[PATCH 6/8] FROMLIST: dt-bindings: usb: Add Cypress cypd6129/cypd6229	missing - no subject, patch-id, or full tree-content match found	present - exact patch-id match at 7277ee5a2795a10e3c166a486cab177f26bdfffc	present
7/8	[PATCH 7/8] FROMLIST: usb: typec: ucsi: ccg: Add support for	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
8/8	[PATCH 8/8] FROMLIST: arm64: dts: qcom: shikra: Wire up	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial

Final Status

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

[qlijarvis]

PR #1062 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	3 commits with issues: 1 ERROR, 2 WARNINGs, 1 commit with 1084 errors/1048 warnings
dt-binding-check	✅	Passed
dtb-check	⚠️	Pre-existing tree issue (qcom,shikra-tlmm unevaluated properties)
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	6 failures: 3 prefix issues, 3 content mismatches
tag-check	❌	3 commits with invalid prefix format

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1062 - USB Type-C support for Shikra platforms
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/35587908718

Checker	Result	Summary
checkpatch	❌	3 commits with issues: 1 ERROR, 2 WARNINGs, 1 commit with 1084 errors/1048 warnings
dt-binding-check	✅	Passed
dtb-check	⚠️	Pre-existing tree issue (qcom,shikra-tlmm unevaluated properties)
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	6 failures: 3 prefix issues, 3 content mismatches
tag-check	❌	3 commits with invalid prefix format

---

❌ checkpatch

Root cause: Multiple formatting and style violations across 3 commits.

Failure details:

Commit 69c6cb3 (QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"):

ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")'
#8: introduced by commit 102ec26f93ef3d6010a7693a061bcec8838fc536:

total: 1 errors, 0 warnings, 0 checks

Commit 1a57ed0 (FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra):

WARNING: DT binding docs and includes should be a separate patch.
total: 0 errors, 1 warnings, 0 checks

Commit 956a080 (FROMLIST: arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports):

WARNING: DT binding docs and includes should be a separate patch.
total: 0 errors, 1 warnings, 0 checks

Commit 328388a (FROMLIST: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229):

ERROR: space required after that ',' (ctx:VxV)
#3134: FILE: drivers/usb/typec/ucsi/ucsi_ccg.c:2704:
+	pr_err("Ak:%s done status:%d\n",__func__, status);
 	                               ^

CHECK: Please don't use multiple blank lines
#3120: FILE: drivers/usb/typec/ucsi/ucsi_ccg.c:2695:

total: 1084 errors, 1048 warnings, 22 checks, 3139 lines checked

Fix:

1. Commit 69c6cb3 — Fix commit reference format:

   git rebase -i <base>  # mark commit as 'edit'
   # Edit commit message to use proper format:
   # "introduced by commit 102ec26f93ef ("PENDING: arm64: dts: qcom: Add typec...")"
   git commit --amend
   git rebase --continue

2. Commits 1a57ed0 & 956a080 — DT binding warning is acceptable if the binding change is minimal and tightly coupled to the DTS change. If the binding is substantial, split into separate patches.

3. Commit 328388a — This commit has 1084 errors and 1048 warnings, indicating it's likely a large vendor driver import with extensive style violations. This requires comprehensive cleanup:

   git rebase -i <base>  # mark commit as 'edit'
   # Fix spacing issues:
   sed -i 's/,__func__/, __func__/g' drivers/usb/typec/ucsi/ucsi_ccg.c
   # Remove multiple blank lines
   # Fix all trailing whitespace, spacing, and formatting issues
   ./scripts/checkpatch.pl --strict --fix-inplace --types=SPACING,TRAILING_WHITESPACE drivers/usb/typec/ucsi/ucsi_ccg.c
   git add drivers/usb/typec/ucsi/ucsi_ccg.c
   git commit --amend --no-edit
   git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git <base>..<head>

---

❌ check-patch-compliance

Root cause: Revert commits use invalid prefix format, and 3 commits have content mismatches with upstream links.

Failure details:

Prefix failures (3 commits):

Checking commit: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"
Commit summary does not start with a required prefix

Checking commit: QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"
Commit summary does not start with a required prefix

Checking commit: QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"
Commit summary does not start with a required prefix

Link/content failures (3 commits):

Checking commit: FROMLIST: arm64: dts: qcom: Add support for usb nodes on Shikra
Something seems wrong with the provided link. Please verify it
Try: b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/

Checking commit: FROMLIST: dt-bindings: usb: Add Cypress cypd6129/cypd6229 Type-C controller
Change is different from the one mentioned in Link

Checking commit: FROMLIST: usb: typec: ucsi: ccg: Add support for cypd6129/cypd6229
Change is different from the one mentioned in Link

Checking commit: FROMLIST: arm64: dts: qcom: shikra: Wire up usb-role-switch for USB Type-C ports
Change is different from the one mentioned in Link

Fix:

Prefix failures — Revert commits must carry a prefix before the word Revert:

git rebase -i <base>
# For each revert commit, change subject from:
#   QCLINUX: Revert "FROMLIST: ..."
# to:
#   FROMLIST: Revert "FROMLIST: ..."
# or:
#   UPSTREAM: Revert "FROMLIST: ..."
git commit --amend -m "FROMLIST: Revert \"FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform\""
git rebase --continue

Link failures — Verify the lore links are correct and the patch content matches:

# Fetch upstream patch for comparison:
b4 am --single-message -C -l -3 <lore-url> -o /tmp/upstream
# Compare diff hunks:
git format-patch -1 <commit-sha> --stdout > /tmp/pr-patch
diff <(grep -E '^[+-][^+-]' /tmp/pr-patch) <(grep -E '^[+-][^+-]' /tmp/upstream/*.mbx)

If the PR patch has legitimate adaptations (e.g., context differences, backport adjustments), document them in the commit message. If the link is wrong, update it. If the content diverges significantly, either align the patch with upstream or change the prefix to BACKPORT: and document the changes.

Reproduce locally:

cd kernel-checkers
./check-patch-compliance.sh <base-sha> <head-sha>

---

❌ tag-check

Root cause: Three revert commits use QCLINUX: prefix, which is not in the allowed list for check-patch-compliance and creates ambiguity about upstream status.

Failure details:

The following commits start with QCLINUX: Revert, which fails the prefix check:

1. QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform"
2. QCLINUX: Revert "FROMLIST: arm64: dts: qcom: Add USB changes for Shikra"
3. QCLINUX: Revert "PENDING: arm64: dts: qcom: Add typec role switching changes to shikra"

Note: This check applies to all branches except qcom-next and qcom-next-staging. If this PR targets one of those branches, this check does not apply. However, based on the presence of QCLINUX: prefixes and the nature of the changes, this appears to target a non-qcom-next branch.

Fix:

Revert commits must carry a valid prefix before the word Revert. Change from:

QCLINUX: Revert "FROMLIST: ..."

to:

FROMLIST: Revert "FROMLIST: ..."

or:

UPSTREAM: Revert "FROMLIST: ..."

Choose the prefix based on whether the revert itself has been posted upstream or is vendor-only.

git rebase -i <base>
# Mark each revert commit as 'edit'
git commit --amend -m "FROMLIST: Revert \"FROMLIST: arm64: dts: qcom: Add changes for usb on IQS platform\""
git rebase --continue

Reproduce locally:

git log <base>..<head> --format="%H %s" | while read sha subject; do
  if ! echo "$subject" | grep -qE '^(FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND):' &&
     ! echo "$subject" | grep -qE '^(FROMLIST|FROMGIT|UPSTREAM|BACKPORT): Revert'; then
    echo "MISSING prefix: $sha $subject"
  fi
done

---

⚠️ dtb-check

Root cause: Pre-existing tree issue — qcom,shikra-tlmm binding does not declare camera sensor pinctrl state names.

Failure details:

shikra-cqm-evk-camx.dtb: pinctrl@500000 (qcom,shikra-tlmm): Unevaluated properties are not allowed
  ('cam-sensor-active-rst0', 'cam-sensor-active-rst1', 'cam-sensor-mclk0-active',
   'cam-sensor-mclk0-suspend', 'cam-sensor-mclk1-active', 'cam-sensor-mclk1-suspend',
   'cam-sensor-mclk2-active', 'cam-sensor-mclk2-suspend', 'cam-sensor-mclk3-active',
   'cam-sensor-mclk3-suspend', 'cam-sensor-suspend-rst0', 'cam-sensor-suspend-rst1',
   'cci-i2c-scl0-active', 'cci-i2c-scl0-suspend', 'cci-i2c-sda0-active',
   'cci-i2c-sda0-suspend', 'cci-i2c-sda1-active', 'cci-i2c-sda1-suspend' were unexpected)

Analysis: This is a recurring tree-wide issue documented in log-patterns.md Section 8. The qcom,shikra-tlmm binding uses unevaluatedProperties: false but does not declare camera sensor pin state names or CCI I2C pin state names. This error appears in multiple PRs and is not introduced by this PR — it's a pre-existing binding deficiency.

Fix (for tree maintainers, not this PR):

Add patternProperties to the qcom,shikra-tlmm binding YAML to allow:

• cam-sensor-*, cci-i2c-*, mclk* pin state names

Verdict for this PR: This is a pre-existing tree issue. The PR does not introduce new dtb-check failures. ✅ Not a blocker for this PR.

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-cqm-evk-camx.dtb

---

Verdict

6 blockers must be fixed before merge:

1. checkpatch — Fix commit reference format in commit 69c6cb3 (1 ERROR)
2. checkpatch — Clean up 1084 errors + 1048 warnings in commit 328388a (ucsi_ccg driver)
3. check-patch-compliance — Fix 3 revert commit prefixes (change QCLINUX: Revert → FROMLIST: Revert)
4. check-patch-compliance — Verify and fix 3 content mismatches with upstream lore links
5. tag-check — Same as ci: Add email checker #3 (revert prefix issue)

Non-blockers:

• checkpatch — 2 DT binding warnings (acceptable if binding changes are minimal)
• dtb-check — Pre-existing tree issue (qcom,shikra-tlmm unevaluated properties)

Recommendation: Fix the 6 blockers listed above, then re-run CI. The ucsi_ccg driver commit (328388a) requires the most work — consider using checkpatch.pl --fix-inplace to automate spacing/whitespace fixes, then manually review remaining issues.

[qcomlnxci]

Test jobs on 956a080

• multimedia Job 234772 on hamoa-iot-evk
• multimedia Job 234774 on lemans-evk
• multimedia Job 234768 on monaco-evk
• multimedia Job 234773 on purwa-iot-evk
• multimedia Job 234775 on qcs615-ride
• multimedia Job 234769 on qcs6490-rb3gen2
• multimedia Job 234777 on qcs8300-ride
• multimedia Job 234766 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 234771 on shikra-iqs-evk

[qcomlnxci]

Test Matrix

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

[qlijarvis]

LAVA Failed Case Triage Summary

PR: #1062

Job 234766 | SoC qcs9100-ride

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: The test detected 4 deferred probe devices (SPMI PMIC temp-alarm sensors) and 2 probe failures (regulatory.db firmware load and Aquantia Ethernet PHY probe), but these are pre-existing platform issues unrelated to the PR changes, which only modified USB DT nodes for Shikra platform.
3. Possible fix: No fix required for this PR. The deferred probe devices (temp-alarm sensors) are waiting for thermal zone dependencies that may not be fully configured on qcs9100-ride in the current kernel. The regulatory.db firmware is intentionally missing (benign). The Aquantia PHY probe failure (-EINVAL/-22) indicates a DT property mismatch or missing firmware-name property, which is a pre-existing board-specific issue. Since no baseline exists for qcs9100-ride and the PR only touches Shikra USB nodes, these failures are not PR-introduced regressions.
4. Detail analysis attachment: failed_case_job234766_1_detailed.md

  Case 2: smmu

1. Failed case: smmu
2. Root cause: The smmu test detected that the video codec device (aa00000.video-codec) is not attached to any IOMMU group on qcs9100-ride. This is a platform-specific device tree or driver configuration issue where the video codec master device lacks the required iommus property in its DT node, preventing SMMU protection. The test correctly identified 54 IOMMU groups and verified that critical masters (UFS, Display, Ethernet, GPU, USB) are protected, but the video codec is missing from the protected device list.
3. Possible fix: This failure is NOT introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only modifies USB DT nodes for Shikra platform, not video codec or qcs9100-ride). The video codec IOMMU attachment issue is a pre-existing platform configuration gap on qcs9100-ride. To fix: add the iommus property to the video-codec@aa00000 DT node in arch/arm64/boot/dts/qcom/qcs9100.dtsi, referencing the appropriate SMMU instance (likely <&apps_smmu 0x2180 0x0>). Verify the correct stream ID from hardware documentation. This is a qcs9100-ride platform enablement task, not a PR regression.
4. Detail analysis attachment: failed_case_job234766_2_detailed.md

  Case 3: Ethernet_Basic_Validation — Ethernet PHY probe failure

1. Failed case: Ethernet_Basic_Validation — Ethernet PHY probe failure
2. Root cause: Aquantia AQR115C PHY driver probe failed with -EINVAL (-22) because the device tree node for the PHY is missing the required "firmware-name" property, causing the driver to reject the PHY during initialization and preventing the qcom-ethqos Ethernet interface (end0) from attaching to the PHY.
3. Possible fix: Add the "firmware-name" property to the Aquantia AQR115C PHY device tree node in the qcs9100-ride DTS file, specifying the correct firmware file path (e.g., firmware-name = "Rhe-05.06-Candidate9-AQR_Mediatek_23B_P5_ID45824_LCLVER1.cld";). If the firmware file is not present in the rootfs, also ensure the firmware binary is included in the firmware search paths.
4. Detail analysis attachment: failed_case_job234766_3_detailed.md

  Case 4: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: KVM cannot initialize on qcs9100-ride because the Gunyah hypervisor is running at EL2, preventing KVM from accessing HYP mode. The kernel message kvm [1]: HYP mode not available indicates KVM detected it cannot operate when another hypervisor owns EL2. This is expected platform behavior for qcs9100-ride with Gunyah, not a PR-introduced regression.
3. Possible fix: This is not a bug requiring a fix. The KVM_Driver test should be skipped on platforms running Gunyah hypervisor (qcs9100-ride, lemans-evk). Add platform detection to the test suite to skip KVM tests when Gunyah is detected in boot logs or when /sys/firmware/devicetree/base/gunyah exists. Alternatively, update the test expectation for qcs9100-ride to mark KVM unavailability as expected/pass rather than fail.
4. Detail analysis attachment: failed_case_job234766_4_detailed.md

  Case 5: KVM_EL2_DTB — KVM device node unavailable

1. Failed case: KVM_EL2_DTB — KVM device node unavailable
2. Root cause: KVM initialization failed during kernel boot because the qcs9100-ride (LeMans Ride Rev3) platform does not have EL2 (Hypervisor) mode available. The kernel message "kvm [1]: HYP mode not available" at boot time (3.868706s) indicates the ARM CPU is not running in a virtualization-capable mode or the bootloader/firmware did not enable EL2 before handing control to the kernel. Without EL2, the KVM subsystem cannot create /dev/kvm, causing all KVM-dependent tests (KVM_Driver, KVM_EL2_DTB, KVM_Infra) to fail with the same root cause.
3. Possible fix: This is a platform hardware/firmware limitation, not a kernel regression. The qcs9100-ride target does not support KVM virtualization in its current configuration. To resolve: (1) verify the bootloader/firmware enables EL2 mode before kernel entry (check ABL/XBL configuration); (2) if the SoC supports virtualization, ensure the secure firmware (TrustZone) allows EL2 access; (3) if the platform fundamentally lacks virtualization support, mark KVM tests as "not applicable" for this target in the CI test matrix to avoid false failures. This failure is NOT introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only reverts USB DT changes for Shikra platform).
4. Detail analysis attachment: failed_case_job234766_5_detailed.md

  Case 6: KVM_Infra — KVM device node unavailable (platform does not support virtualization)

1. Failed case: KVM_Infra — KVM device node unavailable (platform does not support virtualization)
2. Root cause: The qcs9100-ride platform does not support KVM virtualization — kernel message kvm [1]: HYP mode not available at boot indicates the CPU/firmware did not enter EL2 hypervisor mode, preventing KVM initialization and /dev/kvm device node creation. CONFIG_KVM is enabled in the kernel but the hardware/firmware does not provide the required EL2 virtualization support.
3. Possible fix: This is not a kernel regression — it is a platform hardware/firmware limitation. The KVM tests should be skipped on qcs9100-ride or the test suite should check for HYP mode availability before running KVM tests. No kernel code fix is required; the test infrastructure should be updated to skip KVM tests when dmesg | grep "HYP mode not available" is present.
4. Detail analysis attachment: failed_case_job234766_6_detailed.md

  Case 7: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM is not available on qcs9100-ride because the platform does not support HYP (Hypervisor) mode — kernel message "kvm [1]: HYP mode not available" at boot confirms this is a hardware/platform limitation, not a kernel regression.
3. Possible fix: Mark KVM tests as expected-fail or skip for qcs9100-ride in the LAVA test definition, as this platform does not have virtualization extensions enabled. This is not a PR-introduced issue — the USB DT changes in PR Add Support for usb0 and usb1 on shikra QLI #1062 do not affect KVM/virtualization support.
4. Detail analysis attachment: failed_case_job234766_7_detailed.md

Job 234768 | SoC monaco-evk

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Missing firmware files in rootfs for WiFi (ath11k WCN6855), Bluetooth (QCA), and regulatory database; these are known benign failures on monaco-evk as BT_ON_OFF test passed (indicating BT firmware loaded successfully at runtime) and the failures are pre-existing infrastructure issues, not PR-introduced regressions.
3. Possible fix: No kernel fix required. The Probe_Failure_Check test flags missing firmware files at early boot, but functional tests confirm the hardware works correctly. For WiFi: the WiFi_OnOff test also failed, indicating a genuine WiFi issue separate from firmware load timing. For BT: suppress the firmware load failures per lava-known-benign-failures.md Rule 3 since BT_ON_OFF passed. For regulatory.db: this is a known benign failure (cfg80211 regulatory database is optional). The ath11k_pci probe failure (-110 timeout) is the genuine WiFi issue and should be investigated separately from the Probe_Failure_Check test.
4. Detail analysis attachment: failed_case_job234768_1_detailed.md

  Case 2: WiFi_Firmware_Driver — ath11k PCIe probe timeout

1. Failed case: WiFi_Firmware_Driver — ath11k PCIe probe timeout
2. Root cause: ath11k_pci driver probe failed with error -110 (ETIMEDOUT) during MHI power-up on monaco-evk (QCS8300). The WiFi PCIe device at 0000:01:00.0 failed to respond within the expected timeout during firmware load and MHI initialization. This is a pre-existing platform/firmware issue unrelated to the PR's USB/Type-C DT changes.
3. Possible fix: This failure is not PR-introduced (PR only modifies USB/Type-C device tree nodes for Shikra platform, not WiFi or PCIe). The monaco-evk WiFi hardware or firmware may require: (1) verify PCIe link training completed successfully, (2) check if ath11k firmware files are present and correct version for WCN7850/ncm865, (3) increase MHI power-on timeout if hardware is slow to respond, (4) verify PCIe power supplies and clocks are stable, (5) check for known errata on QCS8300 WiFi PCIe interface.
4. Detail analysis attachment: failed_case_job234768_2_detailed.md

  Case 3: WiFi_OnOff — WiFi driver probe failure

1. Failed case: WiFi_OnOff — WiFi driver probe failure
2. Root cause: ath11k_pci driver probe failed with error -110 (ETIMEDOUT) on monaco-evk due to MHI firmware load failure; the firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs, causing MHI power-up to timeout and the WiFi driver to fail initialization.
3. Possible fix: Add the missing WCN6855 firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/ath11k/WCN6855/hw2.1/nfa765/), or if the firmware path has changed, update the driver's firmware search path to match the available firmware location in the build.
4. Detail analysis attachment: failed_case_job234768_3_detailed.md

  Case 4: ** 0_qcom-next-ci-premerge-tests (WiFi driver probe failure)

1. Failed case: ** 0_qcom-next-ci-premerge-tests (WiFi driver probe failure)
2. Root cause: ** The ath11k_pci WiFi driver failed to probe the PCIe WiFi device (0000:01:00.0) with error -110 (ETIMEDOUT). The MHI (Modem Host Interface) subsystem failed to power up the WiFi firmware, indicating either a firmware loading timeout, PCIe communication failure, or WiFi card power/reset sequencing issue on the monaco-evk platform.
3. Possible fix: Investigate the ath11k WiFi driver probe sequence on monaco-evk: (1) Verify the WiFi firmware files (ath11k/WCN6855/hw2.1/nfa765/amss.bin) are present in the rootfs; (2) Check PCIe link status and power supplies for the WiFi card; (3) Review the PR patch changes to USB/power supplies — the reverted USB DT nodes may have inadvertently affected shared power rails or regulators used by the WiFi card; (4) Compare with a known-good kernel boot log to identify any missing regulator/power domain initialization; (5) If the issue persists, add debug logs to the ath11k_pci and MHI drivers to trace the exact point of failure during firmware loading.
4. Detail analysis attachment: failed_case_job234768_4_detailed.md

Job 234769 | SoC qcs6490-rb3gen2

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

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

  Case 1: GIC

1. Failed case: GIC
2. Root cause: Test script bug — the GIC test script fails to handle offline CPUs (CPU6 and CPU7) that did not boot due to PSCI firmware configuration, causing a bash integer comparison error at line 75 when parsing /proc/interrupts output for non-existent CPUs.
3. Possible fix: Update the GIC test script to skip validation for CPUs that are not online, or filter /proc/interrupts to only include online CPUs before parsing. The kernel and GIC hardware are functioning correctly — CPUs 0-5 all show incrementing timer interrupts as expected.
4. Detail analysis attachment: failed_case_job234769_1_detailed.md

  Case 2: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Two benign probe failures detected: (1) cfg80211 regulatory.db firmware load failure (-ENOENT) — WiFi regulatory database is optional and WiFi functional tests (WiFi_OnOff, WiFi_Firmware_Driver) passed, confirming WiFi operates correctly without it; (2) xhci-pci-renesas firmware load failure (-ENOENT) — Renesas USB 3.0 host controller firmware (renesas_usb_fw.mem) is optional and the controller falls back to a working mode without external firmware.
3. Possible fix: No fix required. Both failures are known benign: (1) regulatory.db is an optional WiFi regulatory database that can be provided by userspace or compiled-in certificates (present in this build: "Loaded X.509 cert 'sforshee'" and "Loaded X.509 cert 'wens'"); WiFi functional tests confirm correct operation. (2) Renesas USB firmware is optional; the xhci-pci-renesas driver probe failure does not prevent USB functionality on the platform. The Probe_Failure_Check test should be updated to exclude these two known-benign firmware load failures from its failure criteria, or the test threshold should be adjusted to allow optional firmware failures when corresponding functional tests pass.
4. Detail analysis attachment: failed_case_job234769_2_detailed.md

  Case 3: Freq_Scaling

1. Failed case: Freq_Scaling
2. Root cause: Test expects 8 CPUs (CPU0-7) but only 6 CPUs (CPU0-5) are online on qcs6490-rb3gen2. CPU6 and CPU7 failed to boot during early kernel initialization with PSCI error -22 (EINVAL). The Freq_Scaling test iterates through all expected CPUs checking for cpufreq interface presence; it passes for CPU0-6 but fails when it cannot find CPU7, reporting "CPUFreq interface not found. Test Failed".
3. Possible fix: This is a pre-existing platform issue unrelated to PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only modifies USB device tree nodes on Shikra platform). The CPU boot failure is a known hardware/firmware limitation on qcs6490-rb3gen2 where CPU6 and CPU7 are not functional. The Freq_Scaling test should be updated to dynamically detect the number of online CPUs using /sys/devices/system/cpu/online or /sys/devices/system/cpu/present instead of assuming a fixed CPU count, or the test should be marked as expected-fail/skip for qcs6490-rb3gen2 until the CPU6/7 boot issue is resolved at the firmware/hardware level.
4. Detail analysis attachment: failed_case_job234769_3_detailed.md

  Case 4: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: KVM/virtualization not supported on qcs6490-rb3gen2 (Kodiak) platform — kernel reports "HYP mode not available" at boot, indicating the SoC/firmware does not provide EL2 hypervisor support required for KVM operation. CONFIG_KVM is enabled in kernel config but /dev/kvm device node is never created because kvm_arch_init() fails when HYP mode is unavailable.
3. Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The PR changes only USB device tree nodes for Shikra platform and does not affect KVM/virtualization subsystem. Recommended action: exclude qcs6490-rb3gen2 from KVM test suite, or mark KVM tests as expected-fail/skip for this target in the LAVA job definition, since this SoC does not support virtualization extensions.
4. Detail analysis attachment: failed_case_job234769_4_detailed.md

  Case 5: KVM_EL2_DTB

1. Failed case: KVM_EL2_DTB
2. Root cause: KVM hypervisor mode (EL2) is not available on the qcs6490-rb3gen2 platform — the kernel boot log shows kvm [1]: HYP mode not available at boot time, which prevents the KVM driver from creating the /dev/kvm device node. The test correctly detects that CONFIG_KVM=y is enabled in the kernel configuration, but the device node cannot be created because the hardware/firmware does not support EL2 virtualization on this SoC.
3. Possible fix: This is a platform hardware/firmware limitation, not a kernel regression introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062 (the PR contains only USB device tree reverts with no KVM-related changes). The test failure is expected on qcs6490-rb3gen2 and should be suppressed or the test should be skipped on platforms without EL2 support. To resolve: (1) add a platform capability check to skip KVM tests on boards without EL2 support, or (2) update the LAVA job definition to exclude KVM tests from the qcs6490-rb3gen2 test matrix, or (3) enable EL2 in the board's firmware/bootloader configuration if the SoC hardware supports it but firmware has it disabled.
4. Detail analysis attachment: failed_case_job234769_5_detailed.md

  Case 6: KVM_Infra — KVM device node unavailable (pre-existing platform limitation)

1. Failed case: KVM_Infra — KVM device node unavailable (pre-existing platform limitation)
2. Root cause: The qcs6490-rb3gen2 (Kodiak) platform does not support EL2/HYP mode, as evidenced by the kernel boot message kvm [1]: HYP mode not available at boot time, preventing the creation of /dev/kvm device node required by all KVM tests.
3. Possible fix: This is not a PR-introduced regression — the PR only reverts USB DT changes for Shikra platform (unrelated to KVM). This is a pre-existing hardware/firmware limitation of the qcs6490-rb3gen2 platform. No kernel fix is required. To resolve: either (1) skip KVM tests on platforms without EL2 support, or (2) enable EL2/HYP mode in the platform firmware/bootloader if the hardware supports it.
4. Detail analysis attachment: failed_case_job234769_6_detailed.md

  Case 7: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM cannot initialize because Gunyah hypervisor is already running at EL2 on qcs6490-rb3gen2 (Kodiak). The kernel boot log shows "kvm [1]: HYP mode not available" and "Hypervisor cold boot, version: gunyah-cdfb73831", indicating EL2 is occupied by the Gunyah hypervisor, preventing KVM from accessing the required privilege level.
3. Possible fix: This is not a PR-introduced regression - it is the expected platform configuration for qcs6490-rb3gen2 running with Gunyah hypervisor. The PR only reverts USB DT changes and does not modify KVM or virtualization configuration. To enable KVM on this platform, the board must be configured to boot without the Gunyah hypervisor (boot in non-virtualized mode), or the test should be skipped for platforms running with a hypervisor at EL2. No code fix is required - this is a test environment configuration issue.
4. Detail analysis attachment: failed_case_job234769_7_detailed.md

Job 234771 | SoC shikra-iqs-evk

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

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

  Case 1: GIC (Test Script Bug — Not a Kernel Issue)

1. Failed case: GIC (Test Script Bug — Not a Kernel Issue)
2. Root cause: The GIC test script (run.sh line 75) has a parsing bug that attempts to extract numeric timer interrupt counts for CPUs 4-7, but the shikra-iqs-evk platform has only 4 CPUs (0-3). When the script parses /proc/interrupts for non-existent CPUs, it encounters string tokens ("GICv3", "Level", "arch_timer") instead of numbers, causing bash integer comparison errors and false test failures.
3. Possible fix: Update the GIC test script to dynamically detect the number of online CPUs from /sys/devices/system/cpu/online before attempting to parse timer counts, and only test CPUs that actually exist on the platform. This is a test infrastructure bug, not a kernel regression introduced by the PR.
4. Detail analysis attachment: failed_case_job234771_1_detailed.md

  Case 2: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Pre-existing probe failures unrelated to PR Add Support for usb0 and usb1 on shikra QLI #1062 — all probe failures (coresight-etm4x -EINVAL, cpufreq-dt -EEXIST, tpm_tis_spi -ETIMEDOUT, ucsi_ccg firmware -ENOENT, regulatory.db firmware -ENOENT) are present in the baseline boot log comparison for shikra-iqs-evk and are not introduced by this PR's USB DT revert changes.
3. Possible fix: No action required for PR Add Support for usb0 and usb1 on shikra QLI #1062 — these probe failures are pre-existing platform/configuration issues unrelated to the USB DT changes in this PR. The test case Probe_Failure_Check is flagging known benign failures that do not block boot or core functionality. To address the underlying issues: (1) coresight-etm4x -EINVAL: requires ETM DT node fixes or driver update for this SoC variant; (2) cpufreq-dt -EEXIST: expected when another cpufreq driver already registered; (3) tpm_tis_spi -ETIMEDOUT: TPM chip communication issue, non-critical; (4) ucsi_ccg firmware -ENOENT: Type-C controller firmware missing from rootfs, non-critical; (5) regulatory.db -ENOENT: WiFi regulatory database missing, non-critical for boot.
4. Detail analysis attachment: failed_case_job234771_2_detailed.md

  Case 3: PCIe — Test Infrastructure/Configuration Issue

1. Failed case: PCIe — Test Infrastructure/Configuration Issue
2. Root cause: The PCIe test failed because required firmware file TC956X_Firmware_PCIeBridge.bin is missing from the firmware search path and the kernel module tc956x_pcie_eth is not built/included in the kernel image. The kernel PCIe subsystem is functioning correctly: all 7 PCIe devices are enumerated, links are established (5.0 GT/s and 8.0 GT/s), MSI interrupts are configured, and no PCIe controller or AER errors are present. The QPS615 PCIe switch (vendor 0x1179, device 0x0623) and its downstream Ethernet functions (device 0x0220) are detected and active. The test validation logic expects both the TC956X firmware file and the tc956x_pcie_eth driver module to be present for QPS615 Ethernet validation, but these are missing from the test environment.
3. Possible fix: This is NOT a kernel regression introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062. The PR changes only USB device tree nodes for Shikra platforms (reverting out-of-tree USB DT and preparing for upstream USB series) and does not touch PCIe, firmware loading, or Ethernet drivers. The failure is a pre-existing test environment configuration issue. To resolve: (1) Add TC956X_Firmware_PCIeBridge.bin to the rootfs firmware directory (typically /lib/firmware/), and (2) Enable CONFIG_TC956X_PCIE_ETH in the kernel config and rebuild, or include the tc956x_pcie_eth.ko module in the rootfs if built as a module. If QPS615 Ethernet validation is not required for this platform/test configuration, update the test to skip QPS615-specific checks when the hardware is not present or the driver/firmware are intentionally excluded.
4. Detail analysis attachment: failed_case_job234771_3_detailed.md

  Case 4: USBHost

1. Failed case: USBHost
2. Root cause: USB host controllers (usb_1 at 4c00000 and usb_qmpphy at 1615000) are disabled in device tree after PR Add Support for usb0 and usb1 on shikra QLI #1062 reverted the USB enablement patches for shikra-iqs-evk. The PR removed status = "okay" from &usb_1, &usb_1_hsphy, and &usb_qmpphy nodes, causing USB PHY and controller drivers to not probe. Without active USB controllers, no root hubs are exposed to userspace and lsusb cannot enumerate the USB bus.
3. Possible fix: This is a PR-introduced regression. The PR description states it reverts out-of-tree USB DT changes to prepare for upstream-accepted USB series, but the upstream series was not applied in the same PR. To fix: either (1) do not merge this PR until the upstream USB series is also applied, or (2) apply the upstream USB series patches immediately after this revert to restore USB functionality on shikra-iqs-evk.
4. Detail analysis attachment: failed_case_job234771_4_detailed.md

  Case 5: KVM_Driver — KVM not available (platform limitation)

1. Failed case: KVM_Driver — KVM not available (platform limitation)
2. Root cause: KVM initialization failed at boot with "kvm [1]: HYP mode not available" because the Shikra IQS EVK platform does not support ARM virtualization extensions (EL2/HYP mode). CONFIG_KVM is enabled in the kernel config, but the hardware does not provide the required virtualization support.
3. Possible fix: This is not a kernel bug or PR-introduced regression. The Shikra IQS EVK platform does not support KVM/virtualization. Either: (1) Skip KVM tests on this platform in the CI configuration, or (2) Use a different platform that supports ARM virtualization extensions for KVM testing.
4. Detail analysis attachment: failed_case_job234771_5_detailed.md

  Case 6: ** Kernel Crash — Synchronous External Abort in qcom_rng driver

1. Failed case: ** Kernel Crash — Synchronous External Abort in qcom_rng driver
2. Root cause: ** The qcom_rng hardware random number generator driver crashed with a synchronous external abort (bus fault) when attempting to read from hardware registers during the qcom_hwrng test. The fault occurred at PC qcom_rng_read+0xc4 when the driver tried to access MMIO registers. This is a hardware access fault indicating the RNG hardware block was not accessible (likely powered down, clocked off, or in an invalid state) when the driver attempted to read from it. The crash caused a kernel panic, which prevented subsequent tests (including KVM_EL2_DTB) from running.
3. Possible fix: This is a pre-existing platform/firmware issue unrelated to the PR changes (which only modify USB DT nodes). The RNG hardware block requires proper power/clock configuration in the device tree or firmware. Immediate mitigation: Skip or disable the qcom_hwrng test on shikra-iqs-evk until the RNG hardware access issue is resolved. Proper fix: Investigate why the RNG hardware block is not accessible — check device tree for missing clock/regulator supplies, verify firmware initialization of the RNG block, and ensure the hardware is properly powered and clocked before driver access. The boot log shows an earlier warning "WARN: /dev/hwrng read failed or timed out" which indicates this is a known issue on this platform.
4. Detail analysis attachment: failed_case_job234771_6_detailed.md

  Case 7: Kernel Crash — synchronous external abort in qcom_rng driver (hardware register access fault)

1. Failed case: Kernel Crash — synchronous external abort in qcom_rng driver (hardware register access fault)
2. Root cause: The qcom_hwrng test triggered a synchronous external abort at qcom_rng_read+0xc4 when the qcom_rng driver attempted to read from a hardware MMIO register. The crash occurred during a userspace dd read from /dev/hwrng, causing a fatal bus error that panicked the kernel. The KVM_Infra test failure is a secondary symptom — the test ran immediately after the crash and failed because /dev/kvm was unavailable (CONFIG_KVM is enabled but the device node doesn't exist), but this is unrelated to the crash itself.
3. Possible fix: Investigate the qcom_rng driver's MMIO register access in qcom_rng_read() at offset +0xc4. The synchronous external abort indicates the hardware register being accessed is either not mapped correctly, not powered, or not accessible on the Shikra IQS EVK platform. Check: (1) Device tree configuration for the qcom_rng node (reg property, clocks, power domains), (2) Whether the RNG hardware block is properly initialized and powered before the driver accesses it, (3) Whether the MMIO address being accessed (visible in x1 register: ffff80008329d000) is correctly mapped. The PR changes USB DT nodes but does not touch RNG — this crash is likely a pre-existing platform/firmware issue exposed by the test sequence, not introduced by this PR.
4. Detail analysis attachment: failed_case_job234771_7_detailed.md

  Case 8: Kernel Crash — synchronous external abort in qcom_rng driver

1. Failed case: Kernel Crash — synchronous external abort in qcom_rng driver
2. Root cause: Hardware access fault (synchronous external abort 0x96000010) occurred in qcom_rng_read+0xc4 when the dd process attempted to read from /dev/hwrng. The RNG hardware register access at instruction b940035c (load word) triggered a bus error, indicating the RNG hardware block was either not powered, not clocked, or in an inaccessible state at the time of access.
3. Possible fix: This is a pre-existing hardware/driver initialization issue on shikra-iqs-evk, not introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062 (which only reverts USB DT nodes). The RNG driver probe likely succeeded but the hardware was not properly initialized or powered. Recommended actions: (1) Check RNG clock/power domain dependencies in shikra.dtsi and shikra-iqs-evk.dts; (2) Verify RNG driver probe sequence and hardware initialization in drivers/char/hw_random/qcom-rng.c; (3) Add runtime PM or clock gating checks before register access; (4) Re-trigger the CI job to confirm reproducibility — if intermittent, this may be a race condition in RNG hardware initialization vs. first userspace access.
4. Detail analysis attachment: failed_case_job234771_8_detailed.md

  Case 9: Kernel Crash — synchronous external abort in qcom_rng driver

1. Failed case: Kernel Crash — synchronous external abort in qcom_rng driver
2. Root cause: The shikra-iqs-evk board crashed at 718 seconds into the test run with a synchronous external abort (bus error) in qcom_rng_read+0xc4 while the RNG test was reading from /dev/hwrng. The crash occurred during a hardware register access (b940035c instruction at PC), indicating the qcom_rng hardware block became inaccessible or was incorrectly mapped. After the panic, the board correctly entered EDL/ramdump mode per platform policy, but LAVA timed out waiting for ramdump collection to complete (28 minutes in EDL with no progress). The PR removes USB DT nodes from shikra-iqs-evk; while the crash is in the RNG driver (not USB), the USB DT changes may have affected power sequencing, clocking, or interconnect configuration that indirectly destabilized the RNG hardware block's MMIO access.
3. Possible fix: Revert the USB DT node removal for shikra-iqs-evk (patches 1/8 and 2/8 in PR Add Support for usb0 and usb1 on shikra QLI #1062) and re-test to confirm whether the RNG crash reproduces. If the crash persists after revert, add debug instrumentation to drivers/char/hw_random/qcom-rng.c to log the MMIO base address, clock status, and interconnect vote state before each register access, then capture a ramdump to inspect the RNG hardware block's power/clock/reset state and the SMMU translation table for the RNG MMIO range.
4. Detail analysis attachment: failed_case_job234771_9_detailed.md

  Case 10: Kernel Crash — synchronous external abort in qcom_rng driver

1. Failed case: Kernel Crash — synchronous external abort in qcom_rng driver
2. Root cause: The kernel panicked with a synchronous external abort (0x0000000096000010) at PC qcom_rng_read+0xc4 while the hwrng_test was reading from /dev/hwrng. The crash occurred when the qcom_rng driver attempted to access hardware RNG registers, triggering a bus fault. This is a hardware/driver issue unrelated to the PR's USB DT changes.
3. Possible fix: This is a pre-existing kernel/driver issue, not introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062. The PR only reverts USB device tree nodes and does not touch the qcom_rng driver or any RNG-related code. Re-trigger the CI job to confirm reproducibility. If the crash recurs, investigate the qcom_rng driver's register access patterns and hardware state on shikra-iqs-evk; check if the RNG hardware block requires additional power/clock configuration or if there's a known errata for this SoC.
4. Detail analysis attachment: failed_case_job234771_10_detailed.md

  Case 11: Kernel Crash — Synchronous External Abort in qcom_rng driver

1. Failed case: Kernel Crash — Synchronous External Abort in qcom_rng driver
2. Root cause: The qcom_rng driver triggered a synchronous external abort (bus fault) at offset 0xc4 in qcom_rng_read() while servicing a read from /dev/hwrng during the qcom_hwrng test. The fault indicates the driver attempted to access a hardware register that is unmapped, unpowered, or otherwise inaccessible. This is likely a side effect of the PR's USB DT changes (reverting usb_1/usb_qmpphy nodes and their regulator supplies) inadvertently affecting shared power domains or regulators that the RNG hardware block depends on for the shikra-iqs-evk platform.
3. Possible fix: Verify that the RNG hardware block's power domain, clocks, and regulator supplies are correctly described in the shikra-iqs-evk device tree after the USB DT revert. Cross-check the PM8150 regulator assignments (l4, l6, l12, l13) that were removed in the USB revert — if any of these supplies are shared with the RNG block, they must be retained or the RNG node must explicitly declare its own supply references. Add explicit regulator/clock/power-domain properties to the RNG device node if missing. If the RNG hardware shares a power domain with USB, ensure the domain remains enabled even when USB nodes are disabled.
4. Detail analysis attachment: failed_case_job234771_11_detailed.md

Job 234772 | SoC hamoa-evk

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

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

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Three pre-existing platform-specific probe failures unrelated to the PR changes: (1) qcom_qseecom_uefisecapp probe failure (-EBUSY, error -16) due to efivars already registered by EFI runtime services, (2) qcom-spmi-lpg probe failure (-EINVAL, error -22) due to invalid multi-LED "reg" property in device tree, and (3) regulatory.db firmware load failure (-ENOENT, error -2) which is a known benign missing optional firmware file for cfg80211 wireless regulatory database.
3. Possible fix: These are not PR-introduced regressions. The PR only modifies USB/Type-C device tree nodes for Shikra platform and does not touch QSEECOM, SPMI-LPG, or wireless regulatory components. The test failure is a false positive caused by the Probe_Failure_Check test flagging pre-existing platform issues that do not affect system functionality. Recommendation: (1) Update the Probe_Failure_Check test to exclude known benign probe failures (qcom_qseecom_uefisecapp -EBUSY when efivars already registered, regulatory.db -ENOENT as optional firmware), or (2) Fix the underlying platform issues: add proper efivars coordination for qcom_qseecom_uefisecapp, correct the multi-LED "reg" property in the hamoa-evk device tree for qcom-spmi-lpg, and include regulatory.db firmware in the rootfs if wireless regulatory enforcement is required.
4. Detail analysis attachment: failed_case_job234772_1_detailed.md

  Case 2: smmu (LAVA test case failure — not a kernel crash)

1. Failed case: smmu (LAVA test case failure — not a kernel crash)
2. Root cause: The smmu test detected that 5 USB controllers (a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb) and 1 video codec (aa00000.video-codec) are missing IOMMU group attachments on hamoa-evk. The test passed all kernel config checks, found 36 IOMMU groups, verified critical masters (UFS, GPU, Display, 5 other USB controllers) are protected, and found no SMMU/IOMMU errors in dmesg — but failed because these 6 "critical masters" lack IOMMU protection.
3. Possible fix: This is a device tree configuration issue, not a kernel regression introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062. The PR reverts out-of-tree USB DT changes for Shikra (not hamoa-evk) to prepare for upstream USB series integration. The missing IOMMU attachments on hamoa-evk are pre-existing and unrelated to the PR changes. To fix: add iommus = <&apps_smmu ...> properties to the 5 USB PHY nodes (a0f8800, a2f8800, a4f8800, a6f8800, a8f8800) and the video codec node (aa00000) in arch/arm64/boot/dts/qcom/hamoa.dtsi or the hamoa-evk board DTS, following the pattern used by the working USB controllers (a000000.usb, a200000.usb, a400000.usb, a600000.usb, a800000.usb).
4. Detail analysis attachment: failed_case_job234772_2_detailed.md

  Case 3: KVM_Driver — /dev/kvm device node not available

1. Failed case: KVM_Driver — /dev/kvm device node not available
2. Root cause: The hamoa-evk platform does not support KVM virtualization because HYP (EL2 hypervisor) mode is not available on this SoC/firmware configuration. The kernel message kvm [1]: HYP mode not available during boot indicates that the ARM KVM driver detected it cannot initialize because the CPU is not running at EL2 or EL2 is not accessible, preventing the creation of the /dev/kvm device node required for virtualization.
3. Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The PR only modifies USB/Type-C device tree nodes for the Shikra platform and does not touch KVM, virtualization, or hamoa-evk configuration. No baseline exists for comparison, but the boot log shows no KVM-related changes and the failure signature (HYP mode unavailable) indicates a fundamental platform constraint. To enable KVM on hamoa-evk, the platform firmware/bootloader must be configured to boot Linux at EL2 (or provide VHE support), or the SoC must support nested virtualization if running under a hypervisor. If KVM is not a requirement for this platform, mark these tests as expected-to-skip for hamoa-evk in the CI configuration.
4. Detail analysis attachment: failed_case_job234772_3_detailed.md

  Case 4: KVM_EL2_DTB — /dev/kvm not available

1. Failed case: KVM_EL2_DTB — /dev/kvm not available
2. Root cause: KVM cannot initialize on hamoa-evk because the platform is running under the Gunyah hypervisor (EL2 already occupied). The kernel log shows "kvm [1]: HYP mode not available" at boot, indicating KVM detected that EL2 (hypervisor mode) is already in use by Gunyah and cannot create /dev/kvm. This is a platform architectural limitation, not a kernel bug.
3. Possible fix: This is not a fixable issue in the kernel — it is expected behavior. KVM requires exclusive access to EL2 (hypervisor mode), but on hamoa-evk the Gunyah hypervisor is already running at EL2. The test should be skipped on platforms running under a hypervisor. Recommendation: Add platform detection to skip KVM tests on boards where a hypervisor is present (check for "Hypervisor" in boot log or CONFIG_GUNYAH in kernel config).
4. Detail analysis attachment: failed_case_job234772_4_detailed.md

  Case 5: KVM Infrastructure Failure — KVM driver initialization blocked by Gunyah hypervisor

1. Failed case: KVM Infrastructure Failure — KVM driver initialization blocked by Gunyah hypervisor
2. Root cause: KVM driver probe failed with "HYP mode not available" because the Gunyah hypervisor is running at EL2 and has not configured nested virtualization support or KVM passthrough for this platform (hamoa-evk). The kernel has CONFIG_KVM=y but cannot access EL2 resources required to initialize /dev/kvm.
3. Possible fix: This is a platform firmware/hypervisor configuration issue, not a kernel regression introduced by this PR. The PR only reverts USB DT nodes and does not touch KVM, virtualization, or hypervisor configuration. To enable KVM on hamoa-evk with Gunyah: (1) verify Gunyah firmware supports nested virtualization or KVM passthrough for this SoC, (2) if supported, enable it in the Gunyah resource manager configuration (passthrough.xml or equivalent), (3) if not supported, KVM tests should be skipped on this platform configuration. This is a pre-existing platform limitation, not a PR-introduced regression.
4. Detail analysis attachment: failed_case_job234772_5_detailed.md

  Case 6: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM cannot initialize on hamoa-evk because EL2 (hypervisor mode) is already occupied by the Gunyah hypervisor, which boots before Linux and prevents KVM from taking control of EL2; kernel message "kvm [1]: HYP mode not available" confirms this.
3. Possible fix: This is a platform configuration issue, not a PR-introduced regression. The PR only modifies USB device tree nodes and does not affect KVM or hypervisor configuration. To enable KVM on this platform, either: (1) disable Gunyah hypervisor in the boot chain (ABL/UEFI), or (2) use a nested virtualization configuration if Gunyah supports it, or (3) skip KVM tests on platforms where Gunyah is enabled. No kernel code change is required.
4. Detail analysis attachment: failed_case_job234772_6_detailed.md

Job 234773 | SoC purwa-evk

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

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

  Case 1: ** Probe_Failure_Check — Kernel probe/unprobe/firmware-related errors detected

1. Failed case: ** Probe_Failure_Check — Kernel probe/unprobe/firmware-related errors detected
2. Root cause: ** Five driver probe failures detected during boot on purwa-evk: (1) qcom_qseecom_uefisecapp (-EBUSY, device already in use or resource conflict), (2) qcom-spmi-lpg (-EINVAL, invalid device tree configuration for multi-LED), (3-4) two qcom-pcie instances (-ENODATA, missing PHY init sequences in device tree), and (5) regulatory.db firmware (-ENOENT, expected missing file). These are platform-specific configuration issues unrelated to the PR's USB/Type-C changes for Shikra.
3. Possible fix: These probe failures are not PR-introduced. The PR only modifies USB and Type-C device tree nodes for the Shikra platform (reverts out-of-tree changes and applies upstream USB series). None of the failing drivers (qcom_qseecom, qcom-spmi-lpg, qcom-pcie, cfg80211) are touched by the PR. Without a baseline for purwa-evk, these failures cannot be confirmed as regressions. Recommend: (1) establish a baseline for purwa-evk on qcom-6.18.y branch, (2) if these failures exist in baseline, suppress them as known platform issues, (3) if new, investigate purwa-evk device tree and firmware configuration separately from this PR.
4. Detail analysis attachment: failed_case_job234773_1_detailed.md

  Case 2: ** smmu

1. Failed case: ** smmu
2. Root cause: ** Test detected 6 devices (5 USB PHY nodes and 1 video codec) missing IOMMU group attachment on purwa-evk. This is an expected intermediate state caused by PR Add Support for usb0 and usb1 on shikra QLI #1062 reverting out-of-tree USB DT nodes to prepare for upstream USB series integration. The SMMU/IOMMU subsystem itself is functioning correctly — all enabled critical masters are protected, no SMMU faults occurred, and IOMMU groups are properly configured.
3. Possible fix: This is not a genuine failure requiring a fix. The test should be updated to distinguish between "device exists but not IOMMU-protected" (genuine failure) vs "device node disabled/absent in DT" (expected configuration state). For this specific PR, the failure is expected and benign — the upstream USB series will re-add these nodes with proper IOMMU configuration.
4. Detail analysis attachment: failed_case_job234773_2_detailed.md

  Case 3: KVM_Driver — /dev/kvm device node not present

1. Failed case: KVM_Driver — /dev/kvm device node not present
2. Root cause: Platform does not support KVM — kernel reports "HYP mode not available" at boot because the Gunyah hypervisor is running in a configuration that does not expose EL2 (hypervisor mode) to the Linux kernel, preventing KVM initialization and /dev/kvm creation.
3. Possible fix: This is a platform configuration issue, not a kernel regression. The purwa-evk board is running under Gunyah hypervisor in a mode where Linux runs as a guest VM without nested virtualization support. To enable KVM on this platform: (1) reconfigure the Gunyah hypervisor to expose EL2 to the primary VM, or (2) mark KVM tests as "not applicable" for purwa-evk in the CI test matrix, as this platform does not support KVM by design when running under Gunyah in the current configuration.
4. Detail analysis attachment: failed_case_job234773_3_detailed.md

  Case 4: KVM_EL2_DTB

1. Failed case: KVM_EL2_DTB
2. Root cause: KVM initialization failed because HYP mode (EL2) is not available — the Gunyah hypervisor is already running at EL2 (detected at boot: "Hypervisor cold boot, version: gunyah-mobile-ad1fb25c6"), preventing KVM from claiming that exception level. The kernel message kvm [1]: HYP mode not available at 5.787s confirms KVM detected this condition and aborted initialization, leaving /dev/kvm uncreated.
3. Possible fix: This is a platform configuration issue, not a PR-introduced regression. The PR changes only USB device tree nodes for Shikra/IQS platforms and does not touch KVM, virtualization, or hypervisor configuration. To enable KVM on purwa-evk, the platform must boot without a hypervisor at EL2, or use a hypervisor that supports nested virtualization. For CI purposes, suppress KVM tests on platforms where Gunyah is enabled, or configure the platform to boot Linux directly at EL2 without Gunyah.
4. Detail analysis attachment: failed_case_job234773_4_detailed.md

  Case 5: KVM Infrastructure Test — /dev/kvm device node unavailable

1. Failed case: KVM Infrastructure Test — /dev/kvm device node unavailable
2. Root cause: KVM subsystem failed to initialize during kernel boot because HYP mode (EL2) is not available on the purwa-evk platform. The kernel message kvm [1]: HYP mode not available at boot time (5.787s) indicates the CPU is not running in hypervisor mode, which is a prerequisite for KVM functionality on ARM64.
3. Possible fix: This is a platform firmware/bootloader configuration issue, not a kernel regression. The purwa-evk board's bootloader (ABL/XBL) must be configured to boot the kernel at EL2 instead of EL1. If KVM testing is required on this platform, update the bootloader configuration to enable EL2 entry. Alternatively, exclude KVM tests from the purwa-evk CI test suite since this platform does not support virtualization in its current firmware configuration.
4. Detail analysis attachment: failed_case_job234773_5_detailed.md

  Case 6: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: Platform does not support EL2 (hypervisor mode) — KVM driver detected "HYP mode not available" at boot, preventing /dev/kvm device creation.
3. Possible fix: This is not a kernel regression. The purwa-evk platform does not have EL2 enabled in firmware/bootloader. Either (1) enable EL2 support in the platform's firmware/bootloader configuration, or (2) exclude KVM tests from the purwa-evk CI test suite as this platform does not support virtualization.
4. Detail analysis attachment: failed_case_job234773_6_detailed.md

Job 234774 | SoC lemans-evk

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

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

  Case 1: Probe_Failure_Check — Deferred probe and firmware load failures

1. Failed case: Probe_Failure_Check — Deferred probe and firmware load failures
2. Root cause: Four SPMI PMIC temp-alarm devices (pmic@0, 2 (@2), bene (@4), 6 (@6) at c440000.spmi) remain in deferred probe state, indicating missing dependencies (likely thermal zone or SPMI controller initialization ordering issue). Additionally, regulatory.db firmware file is missing from rootfs (benign — cfg80211 falls back to built-in regulatory database). Bluetooth firmware load failures are false positives (BT_ON_OFF test passed, confirming BT is functional).
3. Possible fix: For temp-alarm deferred probes: verify SPMI controller and thermal framework initialization order in device tree; ensure qcom-spmi-temp-alarm driver dependencies (thermal zones, nvmem cells) are available before temp-alarm probe. For regulatory.db: add regulatory.db firmware file to rootfs if wireless regulatory domain enforcement is required, or accept built-in fallback. Bluetooth firmware failures are benign per suppression Rule 3 (BT_ON_OFF passed).
4. Detail analysis attachment: failed_case_job234774_1_detailed.md

  Case 2: smmu

1. Failed case: smmu
2. Root cause: Video codec device aa00000.video-codec is not attached to any IOMMU group on lemans-evk. The SMMU test validates that critical DMA masters (UFS, Ethernet, USB, GPU, Display, Video) are protected by IOMMU groups. All other critical masters passed (UFS→group 6, Ethernet→group 14, USB devices→groups 8/9/10, GPU→group 20, Display→group 11), but the video codec device has no IOMMU group assignment, indicating missing or incorrect device tree IOMMU binding for this device on this SoC.
3. Possible fix: Add the missing iommus property to the video codec device tree node (aa00000.video-codec) in the lemans-evk device tree. Cross-reference with other Qualcomm SoCs (e.g., sm8450, sm8550) to identify the correct SMMU stream ID and context bank assignment for the video codec on lemans (SA8775P). Verify the SMMU device tree node includes the video codec's stream mapping, then rebuild the DTB and retest.
4. Detail analysis attachment: failed_case_job234774_2_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: The LAVA test suite 0_qcom-next-ci-premerge-tests was marked as failed because the smmu test case detected that the video codec device aa00000.video-codec is missing IOMMU group attachment, which is a critical requirement for memory protection on this SoC (lemans-evk / SA8775P).
3. Possible fix: Verify that the video codec device tree node at aa00000.video-codec includes the required iommus property pointing to the appropriate SMMU stream ID. If the PR's removal of the iommus property from the qcom,qcm2290-venus.yaml binding affects lemans-evk's video codec configuration, restore the IOMMU binding or ensure the lemans DT explicitly defines the IOMMU attachment for the video codec device.
4. Detail analysis attachment: failed_case_job234774_3_detailed.md

Job 234775 | SoC qcs615-ride

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

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

  Case 1: login-action

1. Failed case: login-action
2. Root cause: Complete system hang after USB enumeration success on qcs615-ride; kernel stops producing console output at 11:50:45 after "usb: ENUM success" bootloader message and never reaches login prompt, causing LAVA login-action to timeout after 200 seconds (3 retries). The hang correlates with PR Add Support for usb0 and usb1 on shikra QLI #1062's introduction of USB Type-C role switching support and a large debug patch to the ucsi_ccg driver (patch 7/8 with extensive modifications including probe-time firmware flashing, disabled runtime PM, and altered error handling). The qcs615-ride target is the only one showing a critical kernel panic in the boot comparison report, indicating this SoC has specific USB/Type-C driver compatibility issues with the PR changes.
3. Possible fix: Revert patch 7/8 ("PENDING: usb: typec: ucsi: ucsi_ccg: Add debug changes for bringup") from PR Add Support for usb0 and usb1 on shikra QLI #1062 as it contains non-upstream debug code that likely causes the hang (probe-time firmware flash, disabled PM, altered probe flow). If USB Type-C support is required on qcs615-ride, apply only the upstream-accepted patches (4/8, 5/8, 6/8, 8/8) and test incrementally. Add console=ttyMSM0,115200 to kernel cmdline if not present to ensure serial output visibility. If hang persists after reverting patch 7/8, bisect patches 4-8 to identify the specific change causing the qcs615-ride hang.
4. Detail analysis attachment: failed_case_job234775_1_detailed.md

  Case 2: Kernel Crash — synchronous external abort during USB enumeration

1. Failed case: Kernel Crash — synchronous external abort during USB enumeration
2. Root cause: The kernel panicked with a synchronous external abort (bus error) at 7.25 seconds into boot while attempting to copy USB descriptor data via SWIOTLB bounce buffer during USB hub enumeration on qcs615-ride. The crash occurred in __pi_memcpy_generic called from swiotlb_tbl_map_single → usb_get_device_descriptor → hub_port_init, indicating a DMA/IOMMU mapping issue where the target physical address (0xffff00007feff000) was inaccessible, likely due to incorrect IOMMU configuration or a hardware-level bus fault specific to the qcs615-ride platform's USB controller and SWIOTLB interaction.
3. Possible fix: This is a pre-existing platform-specific kernel crash on qcs615-ride unrelated to the PR's USB DT changes (which target Shikra platforms only). The PR modifies USB device tree nodes for shikra-iqs-evk, shikra-cqm-evk, and shikra-cqs-evk, but qcs615-ride is a separate SoC with its own device tree. The crash signature (synchronous external abort in SWIOTLB memcpy during USB enumeration) suggests a qcs615-specific IOMMU/SMMU configuration issue or hardware errata. Recommended action: (1) Verify qcs615-ride USB IOMMU domain configuration in arch/arm64/boot/dts/qcom/qcs615-ride.dts; (2) Check if SWIOTLB size is sufficient (swiotlb= kernel parameter); (3) Review qcs615 USB controller errata for known DMA access issues; (4) Test with iommu.passthrough=1 to isolate IOMMU vs hardware fault; (5) This failure should NOT block the PR merge as it is platform-specific to qcs615-ride and not introduced by the Shikra USB changes.
4. Detail analysis attachment: failed_case_job234775_2_detailed.md

  Case 3: Kernel Crash — Synchronous External Abort (Memory Access Fault)

1. Failed case: Kernel Crash — Synchronous External Abort (Memory Access Fault)
2. Root cause: The kernel panicked at 7.25s during USB device enumeration with a synchronous external abort (0x0000000096000010) in __pi_memcpy_generic while copying data via SWIOTLB bounce buffer during USB DMA mapping for a low-speed USB device (usb 1-1). The crash occurred in the USB hub worker thread attempting to get the device descriptor, indicating a hardware memory access violation during DMA buffer bounce operation.
3. Possible fix: This is a hardware-level memory access fault during USB DMA operations on qcs615-ride. The crash is not directly caused by the PR's USB DT changes (which only affect Shikra platform), but may indicate a pre-existing USB/IOMMU/SWIOTLB configuration issue on qcs615-ride that was exposed by this kernel version. Recommended actions: (1) Check if qcs615-ride USB DMA/IOMMU configuration is correct in the device tree; (2) Verify SWIOTLB buffer allocation and mapping; (3) Test with USB devices disconnected to confirm USB enumeration is the trigger; (4) Check if this failure reproduces on baseline qcom-6.18.y without the PR changes to confirm it's not PR-introduced.
4. Detail analysis attachment: failed_case_job234775_3_detailed.md

  Case 4: Kernel Crash — Synchronous External Abort during USB initialization

1. Failed case: Kernel Crash — Synchronous External Abort during USB initialization
2. Root cause: Result: Kernel Crash. The kernel panicked with a synchronous external abort (data abort exception) at 7.25 seconds into boot while the USB hub worker thread attempted to enumerate a USB device. The fault occurred in __pi_memcpy_generic called from swiotlb_bounce during DMA buffer mapping for a USB control transfer (usb_get_descriptor). The crash signature indicates an attempt to access an invalid or unmapped physical memory address (0x0000000110c51840 in x19) during SWIOTLB bounce buffer operations, suggesting either incorrect DMA address translation or a hardware-level bus fault on the qcs615-ride platform.
3. Possible fix: Revert the USB PHY driver changes for Shikra from this PR and verify USB DMA address translation on qcs615-ride. The PR introduces shikra_usb3dp_phy_cfg in drivers/phy/qualcomm/phy-qcom-qmp-usbc.c which reuses qcs615 register offsets and configuration tables. If qcs615-ride shares the same USB PHY hardware block, verify that the new PHY configuration does not break DMA coherency or IOMMU mappings. Check the SWIOTLB configuration and USB controller DMA mask settings for qcs615-ride. If the issue persists after PHY config verification, add platform-specific quirks to prevent the qcs615 USB controller from using the new Shikra PHY configuration.
4. Detail analysis attachment: failed_case_job234775_4_detailed.md

Job 234777 | SoC qcs8300-ride

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

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

  Case 1: Probe_Failure_Check — False Positive (Benign Firmware Load Failure)

1. Failed case: Probe_Failure_Check — False Positive (Benign Firmware Load Failure)
2. Root cause: The test detected a regulatory.db firmware load failure (-ENOENT) during cfg80211 initialization. This is a benign failure — cfg80211 successfully falls back to built-in regulatory rules (compiled-in X.509 certificates), and wireless functionality is unaffected. The regulatory.db file is not present in the test rootfs, which is a pre-existing test environment configuration issue, not a kernel regression.
3. Possible fix: Update the Probe_Failure_Check test to exclude benign firmware load failures. Specifically, suppress regulatory.db load failures when cfg80211 successfully loads built-in regulatory certificates (evidenced by "Loaded X.509 cert" log lines). Alternatively, package regulatory.db in the test rootfs to eliminate the warning. This is NOT a kernel bug and does NOT require a kernel fix.
4. Detail analysis attachment: failed_case_job234777_1_detailed.md

  Case 2: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: /dev/kvm device node unavailable because QCS8300-ride platform runs under Gunyah hypervisor at EL2, preventing KVM initialization (KVM also requires EL2 and cannot coexist with another hypervisor).
3. Possible fix: This is a known platform limitation, not a kernel bug. The test expectation should be updated to skip KVM tests on Gunyah-enabled platforms, or the platform firmware should be configured to boot without Gunyah if KVM functionality is required for testing.
4. Detail analysis attachment: failed_case_job234777_2_detailed.md

  Case 3: KVM_EL2_DTB — /dev/kvm device node not created

1. Failed case: KVM_EL2_DTB — /dev/kvm device node not created
2. Root cause: KVM kernel module (CONFIG_KVM=y) is compiled into the kernel but the /dev/kvm device node is not being created at runtime on the qcs8300-ride (Monaco) platform, preventing KVM functionality from being accessible to userspace despite kernel configuration being correct.
3. Possible fix: This is a pre-existing platform/kernel configuration issue, not introduced by this PR (PR Add Support for usb0 and usb1 on shikra QLI #1062 only touches USB device tree nodes for Shikra platform). The failure requires platform-specific investigation: (1) Check if KVM ARM virtualization extensions are enabled in the hypervisor/firmware for qcs8300-ride; (2) Verify that the platform's EL2 mode is accessible to Linux (not reserved by secure firmware); (3) Check dmesg for KVM initialization errors during boot (none visible in provided logs, suggesting KVM init may be silently failing or skipped); (4) Confirm that the qcs8300 SoC hardware supports ARM virtualization extensions (VHE/nVHE). No PR changes are needed — this is a platform enablement gap.
4. Detail analysis attachment: failed_case_job234777_3_detailed.md

  Case 4: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM driver failed to initialize on qcs8300-ride (Monaco) platform — CONFIG_KVM is enabled in kernel config but /dev/kvm device node was not created at runtime, indicating the KVM ARM driver did not successfully probe or the platform does not support virtualization extensions (EL2/VHE) required for KVM operation.
3. Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression (PR Add Support for usb0 and usb1 on shikra QLI #1062 contains only USB DT changes for Shikra). The qcs8300-ride platform may not have EL2 virtualization support enabled in firmware/bootloader, or the SoC variant does not support KVM. Verify: (1) bootloader enables EL2 and HVC instruction support, (2) check dmesg for "kvm" initialization messages or errors during boot, (3) confirm SoC variant supports ARM virtualization extensions. If the platform genuinely does not support KVM, mark this test as "not applicable" for qcs8300-ride in the CI test matrix.
4. Detail analysis attachment: failed_case_job234777_4_detailed.md

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

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: LAVA test runner completed all test cases successfully but did not properly signal completion to the LAVA dispatcher, causing LAVA to mark the test definition as "unfinished" and fail it with error "Marking unfinished test run as failed". The test runner printed <LAVA_TEST_RUNNER EXIT> and LAVA acknowledged "lava_test_shell seems to have completed", but the completion signal was not recognized as valid by the LAVA dispatcher.
3. Possible fix: This is a LAVA test infrastructure issue, not a kernel regression introduced by PR Add Support for usb0 and usb1 on shikra QLI #1062. The PR changes only affect Shikra platform USB device tree nodes and related bindings/drivers, which are unrelated to the qcs8300-ride platform where this test ran. Re-trigger the CI job to verify this is a transient LAVA infrastructure issue. If the issue persists, investigate the LAVA test runner completion signaling mechanism in the test definition YAML.
4. Detail analysis attachment: failed_case_job234777_5_detailed.md

---

🔎 Boot Log Comparison — PR #1062 vs qcom-6.18.y baseline

PR: #1062
Baseline branch: qcom-6.18.y
Targets compared: 9

Target	Boot lines (PR)	Boot lines (baseline)	New issues	Critical	High	Medium	Low
qcs9100-ride	1412	no baseline	11	0	0	10	1
monaco-evk	2424	no baseline	22	0	0	21	1
qcs6490-rb3gen2	1081	no baseline	15	0	0	14	1
shikra-iqs-evk	1066	no baseline	12	0	0	11	1
hamoa-evk	1641	no baseline	18	0	1	17	0
purwa-evk	1519	no baseline	36	0	1	33	2
lemans-evk	1152	no baseline	7	0	0	7	0
qcs615-ride	1039	no baseline	3	1	1	1	0
qcs8300-ride	1155	no baseline	12	0	2	10	0

⚠️ 9 target(s) have no stored baseline — all their issues are listed below but cannot be confirmed as PR-introduced without a baseline.

🔴 CRITICAL new boot issues: 136 new issue(s) across 9 target(s).

Target: qcs9100-ride

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 11 (0 critical, 0 high, 10 medium, 1 low)

🟡 ERROR (medium) ← PR symbols: failed, interrupt, names

[    3.696363][    T1] DT AEST: registered 3 AEST error source(s) from DT

Context

[    3.659951][    T1] DT AEST: node /aest/aest-processor-0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.672038][    T1] DT AEST: node /aest/aest-l3-cluster0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.684057][    T1] DT AEST: node /aest/aest-l3-cluster1: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.696363][    T1] DT AEST: registered 3 AEST error source(s) from DT
[    3.703201][    T1] clocksource: Switched to clocksource arch_sys_counter
[    3.713389][    T1] VFS: Disk quotas dquot_6.6.0
[    3.718178][    T1] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[    9.104203][  T194] qcom_eud 88e1000.eud: error -ENODEV: failed to get controller node for path 0

Context

[    9.071668][  T219] qcom-pcie 1c00000.pcie:      MEM 0x0040300000..0x005fffffff -> 0x0040300000
[    9.093392][  T219] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
[    9.103633][  T219] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    9.104203][  T194] qcom_eud 88e1000.eud: error -ENODEV: failed to get controller node for path 0
[    9.114255][  T219] qcom-pcie 1c00000.pcie: host bridge /pcie@1c00000 ranges:
[    9.115568][  T186] coresight cti_sys0: CTI initialized 0
[    9.134955][  T219] qcom-pcie 1c00000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000

🟡 ERROR (medium) ← PR symbols: supply, write, found

[   10.472710][  T220] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f

Context

[   10.417408][  T196] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@af5c000
[   10.433733][  T196] /soc@0/display-subsystem@ae00000/displayport-controller@af5c000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   10.454090][  T220] msm_dsi ae96000.dsi: supply refgen not found, using dummy regulator
[   10.472710][  T220] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[   10.472710][  T220] :39
[   10.485902][  T220] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[   10.485902][  T220] :43

🟡 ERROR (medium) ← PR symbols: supply, write, found

[   10.485902][  T220] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

Context

[   10.454090][  T220] msm_dsi ae96000.dsi: supply refgen not found, using dummy regulator
[   10.472710][  T220] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[   10.472710][  T220] :39
[   10.485902][  T220] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[   10.485902][  T220] :43
[   10.486286][  T196] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@2215c000
[   10.514226][  T196] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@22154000

🟡 ERROR (medium) ← PR symbols: write, with

[   10.621608][  T220] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f

Context

[   10.567426][  T196] /soc@0/display-subsystem@22000000/displayport-controller@22154000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/display-controller@22001000
[   10.585564][  T196] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@2215c000
[   10.602442][  T196] /soc@0/display-subsystem@22000000/displayport-controller@2215c000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/display-controller@22001000
[   10.621608][  T220] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[   10.621608][  T220] :39
[   10.634650][  T220] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[   10.634650][  T220] :43

🟡 ERROR (medium) ← PR symbols: qcom, write, with

[   10.634650][  T220] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

Context

[   10.602442][  T196] /soc@0/display-subsystem@22000000/displayport-controller@2215c000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/display-controller@22001000
[   10.621608][  T220] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[   10.621608][  T220] :39
[   10.634650][  T220] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[   10.634650][  T220] :43
[   10.740853][  T219] qcom-pcie 1c00000.pcie: PCIe Gen.3 x1 link up
[   10.747436][  T219] qcom-pcie 1c00000.pcie: PCI host bridge to bus 0000:00

🟡 ERROR (medium) ← PR symbols: failed, data, with

[   11.000213][   T73] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   10.993621][  T220] msm_dpu ae01000.display-controller: bound af54000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   10.999743][  T113] Bluetooth: hci0: QCA setup on UART is completed
[   11.000018][  T202] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.000213][   T73] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.000225][   T73] cfg80211: failed to load regulatory.db
[   11.013069][  T220] msm_dpu ae01000.display-controller: bound af5c000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   11.018384][  T113] Bluetooth: hci0: HFP non-HCI data transport is supported

🔵 FIRMWARE_FAIL (low) ← PR symbols: failed, with, read

[   11.510421][  T173] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22

Context

[   11.411064][  T220] [drm:dpu_kms_hw_init:1201] dpu hardware revision:0x80040000
[   11.425105][  T220] [drm] Initialized msm-kms 1.13.0 for 22001000.display-controller on minor 2
[   11.486088][   T95] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes
[   11.510421][  T173] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   11.532493][  T173] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   11.537540][  T220] msm_dpu 22001000.display-controller: [drm] Cannot find any crtc or sizes
[   11.557057][  T334] platform 2a300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 30

🟡 ERROR (medium) ← PR symbols: failed, with, read

[   11.532493][  T173] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22

Context

[   11.425105][  T220] [drm] Initialized msm-kms 1.13.0 for 22001000.display-controller on minor 2
[   11.486088][   T95] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes
[   11.510421][  T173] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   11.532493][  T173] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   11.537540][  T220] msm_dpu 22001000.display-controller: [drm] Cannot find any crtc or sizes
[   11.557057][  T334] platform 2a300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 30
[   11.567974][  T335] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 31

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   31.758682][  T421] EXT4-fs (sda2): orphan cleanup on readonly fs
[   31.765570][  T421] EXT4-fs (sda2): mounted filesystem 57198697-7c20-47a4-944c-71a7b61d6a7e ro with ordered data mode. Quota mode: none.
done.

Target: monaco-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 22 (0 critical, 0 high, 21 medium, 1 low)

🟡 ERROR (medium) ← PR symbols: supply, found, regulator

[    6.786280][   T75] usb usb2-port1: config error

Context

[    6.767741][  T160] pca953x 3-003d: supply vcc not found, using dummy regulator
[    6.767865][  T160] pca953x 3-003d: using no AI
[    6.776572][  T173] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 20
[    6.786280][   T75] usb usb2-port1: config error
[    6.804033][  T160] pca953x 3-003e: supply vcc not found, using dummy regulator
[    6.805791][  T173] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 21
[    6.806814][  T173] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 22

🟡 ERROR (medium) ← PR symbols: window, failed, qcom

[    7.245227][   T64] ufshcd-qcom 1d84000.ufs: error -EAGAIN: Initialization failed with error -11

Context

[    7.227633][   T63] pci 0000:00:00.0: bridge window [mem 0x40400000-0x405fffff]: assigned
[    7.233547][   T64] ufshcd-qcom 1d84000.ufs: ufshcd_verify_dev_init: NOP OUT failed -11
[    7.236034][   T63] pci 0000:00:00.0: BAR 0 [mem 0x40300000-0x40300fff]: assigned
[    7.245227][   T64] ufshcd-qcom 1d84000.ufs: error -EAGAIN: Initialization failed with error -11
[    7.251929][   T63] pci 0000:01:00.0: BAR 0 [mem 0x40400000-0x405fffff 64bit]: assigned
[    7.260951][   T64] ufshcd-qcom 1d84000.ufs: error -EAGAIN: ufshcd_pltfrm_init() failed
[    7.266375][   T75] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd

🟡 ERROR (medium) ← PR symbols: failed, qcom, assigned

[    7.260951][   T64] ufshcd-qcom 1d84000.ufs: error -EAGAIN: ufshcd_pltfrm_init() failed

Context

[    7.236034][   T63] pci 0000:00:00.0: BAR 0 [mem 0x40300000-0x40300fff]: assigned
[    7.245227][   T64] ufshcd-qcom 1d84000.ufs: error -EAGAIN: Initialization failed with error -11
[    7.251929][   T63] pci 0000:01:00.0: BAR 0 [mem 0x40400000-0x405fffff 64bit]: assigned
[    7.260951][   T64] ufshcd-qcom 1d84000.ufs: error -EAGAIN: ufshcd_pltfrm_init() failed
[    7.266375][   T75] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd
[    7.269194][   T63] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    7.277387][   T64] ufshcd-qcom 1d84000.ufs: probe with driver ufshcd-qcom failed with error -11

🟡 ERROR (medium) ← PR symbols: window, failed, qcom

[    7.277387][   T64] ufshcd-qcom 1d84000.ufs: probe with driver ufshcd-qcom failed with error -11

Context

[    7.260951][   T64] ufshcd-qcom 1d84000.ufs: error -EAGAIN: ufshcd_pltfrm_init() failed
[    7.266375][   T75] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd
[    7.269194][   T63] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    7.277387][   T64] ufshcd-qcom 1d84000.ufs: probe with driver ufshcd-qcom failed with error -11
[    7.285939][   T63] pci 0000:00:00.0:   bridge window [mem 0x40400000-0x405fffff]
[    7.285944][   T63] pci_bus 0000:00: resource 4 [io  0x0000-0xfffff]
[    7.315243][   T63] pci_bus 0000:00: resource 5 [mem 0x40300000-0x5fffffff]

🟡 ERROR (medium) ← PR symbols: qcom, device, with

[    7.873174][   T63] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[    7.833200][   T73] pcieport 0001:00:00.0: AER: enabled with IRQ 340
[    7.850539][  T215] qcom,apr 3000000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[    7.855632][   T63] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)
[    7.873174][   T63] tpm tpm0: A TPM error (256) occurred attempting the self test
[    7.880917][   T63] tpm tpm0: starting up the TPM manually
[    7.886956][  T215] qcom,apr 3000000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[    7.922797][  T180] cfg80211: Loading compiled-in X.509 certificates for regulatory database

🟡 ERROR (medium) ← PR symbols: failed, supply, found

[    7.962329][   T31] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    7.922797][  T180] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    7.946866][  T180] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    7.953953][  T180] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    7.962329][   T31] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    7.972126][   T31] cfg80211: failed to load regulatory.db
[    8.000572][  T162] at24 1-0050: supply vcc not found, using dummy regulator
[    8.013312][  T185] lt8713sx 2-004f: supply vdd not found, using dummy regulator

🟡 ERROR (medium) ← PR symbols: bits, success, failed

[    8.327172][  T300] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2

Context

[    8.310799][   T64] qcom-ethqos 23040000.ethernet: Using 36/40 bits DMA host/device width
[    8.318587][  T180] mhi mhi0: Requested to power ON
[    8.324233][  T180] mhi mhi0: Power on setup success
[    8.327172][  T300] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    8.339928][  T300] mhi mhi0: Error loading firmware: -2
[    8.346160][  T180] ath11k_pci 0000:01:00.0: failed to power up mhi: -110
[    8.347244][  T112] Bluetooth: hci0: QCA Product ID   :0x00000013

🟡 ERROR (medium) ← PR symbols: success, failed, power

[    8.339928][  T300] mhi mhi0: Error loading firmware: -2

Context

[    8.318587][  T180] mhi mhi0: Requested to power ON
[    8.324233][  T180] mhi mhi0: Power on setup success
[    8.327172][  T300] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    8.339928][  T300] mhi mhi0: Error loading firmware: -2
[    8.346160][  T180] ath11k_pci 0000:01:00.0: failed to power up mhi: -110
[    8.347244][  T112] Bluetooth: hci0: QCA Product ID   :0x00000013
[    8.353149][  T180] ath11k_pci 0000:01:00.0: failed to start mhi: -110

🟡 ERROR (medium) ← PR symbols: failed, core, with

[    8.423073][  T112] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2

Context

[    8.401087][  T180] ath11k_pci 0000:01:00.0: failed to init core: -110
[    8.403626][  T112] Bluetooth: hci0: QCA controller version 0x12110201
[    8.414610][  T112] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.423073][  T112] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.432696][  T112] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.441134][  T112] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.448702][  T112] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

🟡 ERROR (medium) ← PR symbols: failed, data, with

[    8.448702][  T112] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

Context

[    8.423073][  T112] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.432696][  T112] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.441134][  T112] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.448702][  T112] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.457995][  T112] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.466153][  T112] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.474342][  T112] Bluetooth: hci0: HFP non-HCI data transport is supported

🟡 ERROR (medium) ← PR symbols: failed, device, found

[    8.703064][  T180] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110

Context

[    8.616119][   T64] [drm] Loaded GMU firmware v3.6.1
[    8.624174][   T64] msm_dpu ae01000.display-controller: Zap shader not enabled - using SECVID_TRUST_CNTL instead
[    8.686859][   T64] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes
[    8.703064][  T180] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110
[    8.750706][  T125] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes
[   12.615484][  T255] usb 2-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[   12.677878][  T255] hub 2-1.1:1.0: USB hub found

🔵 FIRMWARE_FAIL (low) ← PR symbols: Status, Found

FmpDxe(Qualcomm System Firmware Update Driver): Failed to get the controller state.  Status = Not Found

Context

    ====================================
Selected FW GUID =: 8BF4424F-E842-409C-80BE-1418E91EF343 
  Platform = 20 
FmpDxe(Qualcomm System Firmware Update Driver): Failed to get the controller state.  Status = Not Found
SoftSKUDxe: GetChipFamily() : 145, GetChipId: 675 
SoftSKUDxeInitialize: SoftSKU not supported for this chip
MinidumpTADxe: Minidump TA loading not enabled.

🟡 ERROR (medium) ← PR symbols: failed, supply, device

[    8.238824][  T104] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    8.237515][  T176] pca953x 3-003e: supply vcc not found, using dummy regulator
[    8.237921][  T190] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[    8.238009][  T176] pca953x 3-003e: using no AI
[    8.238824][  T104] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.257267][  T189] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 24
[    8.258365][   T77] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    8.258981][  T104] cfg80211: failed to load regulatory.db

🟡 ERROR (medium) ← PR symbols: failed

[    8.330554][  T243] usb usb2-port1: config error

Context

[    8.258981][  T104] cfg80211: failed to load regulatory.db
[    8.313086][  T110] Bluetooth: hci0: QCA Product ID   :0x00000013
[    8.327312][  T110] Bluetooth: hci0: QCA SOC Version  :0x400c1211
[    8.330554][  T243] usb usb2-port1: config error
[    8.331012][  T189] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 25
[    8.333636][  T110] Bluetooth: hci0: QCA ROM Version  :0x00000201
[    8.354640][  T110] Bluetooth: hci0: QCA Patch Version:0x000038e6

🟡 ERROR (medium) ← PR symbols: failed, device, with

[    8.384351][  T110] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2

Context

[    8.370552][  T110] Bluetooth: hci0: QCA controller version 0x12110201
[    8.377286][  T110] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.382519][  T189] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 26
[    8.384351][  T110] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.396357][   T88] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)
[    8.403933][  T110] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.416388][   T88] tpm tpm0: A TPM error (256) occurred attempting the self test

🟡 ERROR (medium) ← PR symbols: failed, device, with

[    8.416388][   T88] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[    8.384351][  T110] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.396357][   T88] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)
[    8.403933][  T110] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.416388][   T88] tpm tpm0: A TPM error (256) occurred attempting the self test
[    8.419181][  T110] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.419380][  T110] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.426959][   T88] tpm tpm0: starting up the TPM manually

🟡 ERROR (medium) ← PR symbols: failed, with, self

[    8.419380][  T110] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

Context

[    8.403933][  T110] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.416388][   T88] tpm tpm0: A TPM error (256) occurred attempting the self test
[    8.419181][  T110] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.419380][  T110] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.426959][   T88] tpm tpm0: starting up the TPM manually
[    8.433567][  T110] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.433571][  T110] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)

🟡 ERROR (medium) ← PR symbols: success, failed, power

[    9.034684][  T300] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2

Context

[    8.980374][  T183] usbcore: registered new device driver onboard-usb-dev
[    9.026916][  T182] mhi mhi0: Requested to power ON
[    9.031972][  T182] mhi mhi0: Power on setup success
[    9.034684][  T300] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.047670][  T300] mhi mhi0: Error loading firmware: -2
[    9.053976][  T182] ath11k_pci 0000:01:00.0: failed to power up mhi: -110
[    9.060970][  T182] ath11k_pci 0000:01:00.0: failed to start mhi: -110

🟡 ERROR (medium) ← PR symbols: success, failed, power

[    9.047670][  T300] mhi mhi0: Error loading firmware: -2

Context

[    9.026916][  T182] mhi mhi0: Requested to power ON
[    9.031972][  T182] mhi mhi0: Power on setup success
[    9.034684][  T300] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.047670][  T300] mhi mhi0: Error loading firmware: -2
[    9.053976][  T182] ath11k_pci 0000:01:00.0: failed to power up mhi: -110
[    9.060970][  T182] ath11k_pci 0000:01:00.0: failed to start mhi: -110
[    9.067674][  T182] ath11k_pci 0000:01:00.0: failed to power up :-110

🟡 ERROR (medium) ← PR symbols: failed, ports, found

[    9.375731][  T182] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110

Context

[    9.234881][   T72] msm_dpu ae01000.display-controller: Zap shader not enabled - using SECVID_TRUST_CNTL instead
[    9.295851][   T72] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes
[    9.355945][   T37] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes
[    9.375731][  T182] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110
[    9.458693][  T188] hub 1-1:1.0: USB hub found
[    9.458976][  T183] hub 2-1:1.0: USB hub found
[    9.466776][  T188] hub 1-1:1.0: 4 ports detected

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   31.927225][  T375] EXT4-fs (sda2): orphan cleanup on readonly fs
[   31.935080][  T375] EXT4-fs (sda2): mounted filesystem 513728bc-9c18-4a66-a6fb-01735755aeed ro with ordered data mode. Quota mode: none.
done.

Target: qcs6490-rb3gen2

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 15 (0 critical, 0 high, 14 medium, 1 low)

🟡 ERROR (medium) ← PR symbols: failed, with

[    9.925817][   T25] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    9.919163][  T163] coresight etm2: CPU2: etm v4.2 initialized
[    9.925057][   T88] arm-smmu 3da0000.iommu: probing hardware configuration...
[    9.925066][   T88] arm-smmu 3da0000.iommu: SMMUv2 with:
[    9.925817][   T25] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.925867][   T25] cfg80211: failed to load regulatory.db
[    9.938851][  T163] CSCFG registered etm3
[    9.948099][   T88] arm-smmu 3da0000.iommu: 	stage 1 translation

🟡 ERROR (medium) ← PR symbols: supply, device, found

[   12.883274][  T161] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.838884][  T106] Bluetooth: hci0: QCA Patch Version:0x000024c7
[   12.868602][  T106] Bluetooth: hci0: QCA controller version 0x01100101
[   12.875798][  T106] Bluetooth: hci0: QCA Downloading qca/msbtfw11.mbn
[   12.883274][  T161] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.884892][  T231] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[   12.893695][  T161] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.947742][  T162] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)

🟡 ERROR (medium) ← PR symbols: supply, device, found

[   12.893695][  T161] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.875798][  T106] Bluetooth: hci0: QCA Downloading qca/msbtfw11.mbn
[   12.883274][  T161] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.884892][  T231] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[   12.893695][  T161] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.947742][  T162] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[   13.020870][  T274] scsi_id (274) used greatest stack depth: 11256 bytes left
[   13.038487][  T275] scsi_id (275) used greatest stack depth: 10656 bytes left

🟡 ERROR (medium) ← PR symbols: qcom, connector, device

[   13.085241][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   13.047212][   T73] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[   13.059190][  T160] CAN device driver interface
[   13.061276][   T73] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[   13.085241][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.086756][  T184] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-001c for /pmic-glink/connector@0
[   13.099007][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.142344][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 16

🟡 ERROR (medium) ← PR symbols: qcom, connector, device

[   13.099007][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   13.061276][   T73] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[   13.085241][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.086756][  T184] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-001c for /pmic-glink/connector@0
[   13.099007][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.142344][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 16
[   13.171119][  T160] spi_master spi3: will run message pump with realtime priority
[   13.191570][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 17

🔵 FIRMWARE_FAIL (low) ← PR symbols: failed, qcom, supply

[   13.203979][  T162] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2

Context

[   13.171119][  T160] spi_master spi3: will run message pump with realtime priority
[   13.191570][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 17
[   13.203661][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 18
[   13.203979][  T162] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2
[   13.212314][  T158] qcom-edp-phy aec2a00.phy: supply vdda-phy not found, using dummy regulator
[   13.231770][  T162] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2
[   13.236096][  T158] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[   13.231770][  T162] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2

Context

[   13.203661][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 18
[   13.203979][  T162] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2
[   13.212314][  T158] qcom-edp-phy aec2a00.phy: supply vdda-phy not found, using dummy regulator
[   13.231770][  T162] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2
[   13.236096][  T158] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator
[   13.253091][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 19
[   13.270169][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[   13.270169][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   13.231770][  T162] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2
[   13.236096][  T158] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator
[   13.253091][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 19
[   13.270169][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.280142][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.285978][  T160] mcp251xfd spi3.0 can0: MCP2518FD rev0.0 (-RX_INT -PLL -MAB_NO_WARN +CRC_REG +CRC_RX +CRC_TX +ECC -HD o:40.00MHz c:40.00MHz m:10.00MHz rs:10.00MHz es:0.00MHz rf:10.00MHz ef:0.00M
[   13.290430][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 20

🟡 ERROR (medium) ← PR symbols: qcom, supply, vdda

[   13.280142][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   13.236096][  T158] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator
[   13.253091][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 19
[   13.270169][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.280142][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.285978][  T160] mcp251xfd spi3.0 can0: MCP2518FD rev0.0 (-RX_INT -PLL -MAB_NO_WARN +CRC_REG +CRC_RX +CRC_TX +ECC -HD o:40.00MHz c:40.00MHz m:10.00MHz rs:10.00MHz es:0.00MHz rf:10.00MHz ef:0.00M
[   13.290430][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 20
[   13.323436][  T231] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   13.323436][  T231] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

Context

[   13.280142][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.285978][  T160] mcp251xfd spi3.0 can0: MCP2518FD rev0.0 (-RX_INT -PLL -MAB_NO_WARN +CRC_REG +CRC_RX +CRC_TX +ECC -HD o:40.00MHz c:40.00MHz m:10.00MHz rs:10.00MHz es:0.00MHz rf:10.00MHz ef:0.00M
[   13.290430][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 20
[   13.323436][  T231] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   13.325373][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 21
[   13.340239][  T231] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   13.363747][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 22

🟡 ERROR (medium) ← PR symbols: EINVAL

[   13.340239][  T231] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

Context

[   13.290430][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 20
[   13.323436][  T231] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   13.325373][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 21
[   13.340239][  T231] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   13.363747][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 22
[   13.483730][  T164] lt9611uxc 0-002b: LT9611 revision: 0x17.04.93
[   13.514717][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 23

🟡 ERROR (medium) ← PR symbols: EINVAL

[   13.546325][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   13.483730][  T164] lt9611uxc 0-002b: LT9611 revision: 0x17.04.93
[   13.514717][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 23
[   13.527769][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@11: Adding to iommu group 24
[   13.546325][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.546760][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@12: Adding to iommu group 25
[   13.556229][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.568066][  T164] lt9611uxc 0-002b: LT9611 version: 0x50

🟡 ERROR (medium) ← PR symbols: EINVAL

[   13.556229][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   13.527769][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@11: Adding to iommu group 24
[   13.546325][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.546760][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@12: Adding to iommu group 25
[   13.556229][  T231] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.568066][  T164] lt9611uxc 0-002b: LT9611 version: 0x50
[   13.568100][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@13: Adding to iommu group 26
[   13.570270][  T176] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@14: Adding to iommu group 27

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   36.628065][  T335] EXT4-fs (sda2): orphan cleanup on readonly fs
[   36.637708][  T335] EXT4-fs (sda2): mounted filesystem 698d30c1-1e68-4325-852e-0d99efa1467f ro with ordered data mode. Quota mode: none.
done.

Target: shikra-iqs-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 12 (0 critical, 0 high, 11 medium, 1 low)

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[    8.104481][  T154] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22

Context

[    8.035695][   T59] arm-smmu 59a0000.iommu: 	preserved 0 boot mappings
[    8.044833][   T59] platform 5900000.gpu: Adding to iommu group 13
[    8.090155][   T86] qcom-pcie 45e8000.pcie: supply vdda not found, using dummy regulator
[    8.104481][  T154] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    8.114095][   T86] qcom-pcie 45e8000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    8.114764][  T154] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    8.130560][  T137] mc: Linux media interface: v0.10

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[    8.114764][  T154] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22

Context

[    8.090155][   T86] qcom-pcie 45e8000.pcie: supply vdda not found, using dummy regulator
[    8.104481][  T154] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    8.114095][   T86] qcom-pcie 45e8000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    8.114764][  T154] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    8.130560][  T137] mc: Linux media interface: v0.10
[    8.148498][  T154] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    8.152562][   T86] qcom-pcie 45e8000.pcie: host bridge /soc@0/pcie@45e8000 ranges:

🟡 ERROR (medium) ← PR symbols: failed, qcom, supply

[    8.148498][  T154] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22

Context

[    8.114095][   T86] qcom-pcie 45e8000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    8.114764][  T154] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    8.130560][  T137] mc: Linux media interface: v0.10
[    8.148498][  T154] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    8.152562][   T86] qcom-pcie 45e8000.pcie: host bridge /soc@0/pcie@45e8000 ranges:
[    8.158804][  T154] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    8.168197][   T86] qcom-pcie 45e8000.pcie:       IO 0x0060200000..0x00602fffff -> 0x0000000000

🟡 ERROR (medium) ← PR symbols: failed, qcom, with

[    8.158804][  T154] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22

Context

[    8.130560][  T137] mc: Linux media interface: v0.10
[    8.148498][  T154] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    8.152562][   T86] qcom-pcie 45e8000.pcie: host bridge /soc@0/pcie@45e8000 ranges:
[    8.158804][  T154] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    8.168197][   T86] qcom-pcie 45e8000.pcie:       IO 0x0060200000..0x00602fffff -> 0x0000000000
[    8.184355][   T86] qcom-pcie 45e8000.pcie:      MEM 0x0060300000..0x0063ffffff -> 0x0060300000
[    8.222726][   T91] l2: unsupportable voltage range: 3500000-3296000uV

🟡 ERROR (medium) ← PR symbols: failed, qcom, register

[    9.693286][  T101] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    9.676950][  T130] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.684498][  T130] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.686080][  T135] /soc@0/geniqup@4ac0000/i2c@4a90000/lt9611uxd@41: Fixed dependency cycle(s) with /soc@0/display-subsystem@5e00000/dsi@5e94000
[    9.693286][  T101] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.709523][   T86] cpufreq-dt cpufreq-dt: failed register driver: -17
[    9.715822][  T101] cfg80211: failed to load regulatory.db
[    9.718992][  T161] qcom-pcie 45e8000.pcie: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G

🟡 ERROR (medium) ← PR symbols: failed, qcom, register

[    9.729919][   T86] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17

Context

[    9.709523][   T86] cpufreq-dt cpufreq-dt: failed register driver: -17
[    9.715822][  T101] cfg80211: failed to load regulatory.db
[    9.718992][  T161] qcom-pcie 45e8000.pcie: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[    9.729919][   T86] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17
[    9.753815][  T141] /soc@0/display-subsystem@5e00000/display-controller@5e01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@5e00000/dsi@5e94000
[    9.779696][  T141] /soc@0/display-subsystem@5e00000/display-controller@5e01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@5e00000/dsi@5e94000
[    9.796000][  T141] /soc@0/geniqup@4ac0000/i2c@4a90000/lt9611uxd@41: Fixed dependency cycle(s) with /soc@0/display-subsystem@5e00000/dsi@5e94000

🟡 ERROR (medium) ← PR symbols: failed, interrupt, with

[   11.106676][   T86] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110

Context

[   11.078078][  T146] irq: IRQ191: trimming hierarchy from :soc@0:interrupt-controller@f200000-1
[   11.087253][  T132] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 20
[   11.106071][  T132] platform b300000.remoteproc:glink-edge:fastrpc:compute-cb@9: Adding to iommu group 21
[   11.106676][   T86] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110
[   11.144717][  T150] Bluetooth: HCI UART driver ver 2.3
[   11.150138][  T150] Bluetooth: HCI UART protocol H4 registered
[   11.156787][  T150] Bluetooth: HCI UART protocol LL registered

🟡 ERROR (medium) ← PR symbols: failed, request_firmware, ccg_fw_update

[   11.310443][  T151] ucsi_ccg 3-0040: Direct firmware load for ccg_secondary.cyacd2 failed with error -2

Context

[   11.286943][  T151] Ak: hybrid:0
[   11.290384][  T151] ucsi_ccg 3-0040: DEVICE_MODE=0x91 row_size=256 BL_LAST=0x0001 FW1_START=2 FW2_START=258 rows_per_bank=256
[   11.302048][  T151] ucsi_ccg 3-0040: requesting firmware: ccg_secondary.cyacd2
[   11.310443][  T151] ucsi_ccg 3-0040: Direct firmware load for ccg_secondary.cyacd2 failed with error -2
[   11.320249][  T151] ucsi_ccg 3-0040: request_firmware(ccg_secondary.cyacd2) failed (-2)
[   11.328961][  T151] ucsi_ccg 3-0040: ccg_fw_update failed - -2
[   11.354573][  T151] ucsi_ccg 3-0040: probe with driver ucsi_ccg failed with error -2

🔵 FIRMWARE_FAIL (low) ← PR symbols: failed, request_firmware, ccg_fw_update

[   11.320249][  T151] ucsi_ccg 3-0040: request_firmware(ccg_secondary.cyacd2) failed (-2)

Context

[   11.290384][  T151] ucsi_ccg 3-0040: DEVICE_MODE=0x91 row_size=256 BL_LAST=0x0001 FW1_START=2 FW2_START=258 rows_per_bank=256
[   11.302048][  T151] ucsi_ccg 3-0040: requesting firmware: ccg_secondary.cyacd2
[   11.310443][  T151] ucsi_ccg 3-0040: Direct firmware load for ccg_secondary.cyacd2 failed with error -2
[   11.320249][  T151] ucsi_ccg 3-0040: request_firmware(ccg_secondary.cyacd2) failed (-2)
[   11.328961][  T151] ucsi_ccg 3-0040: ccg_fw_update failed - -2
[   11.354573][  T151] ucsi_ccg 3-0040: probe with driver ucsi_ccg failed with error -2
[   11.416514][   T91] l2: unsupportable voltage range: 3500000-3296000uV

🟡 ERROR (medium) ← PR symbols: failed, request_firmware, ccg_fw_update

[   11.354573][  T151] ucsi_ccg 3-0040: probe with driver ucsi_ccg failed with error -2

Context

[   11.310443][  T151] ucsi_ccg 3-0040: Direct firmware load for ccg_secondary.cyacd2 failed with error -2
[   11.320249][  T151] ucsi_ccg 3-0040: request_firmware(ccg_secondary.cyacd2) failed (-2)
[   11.328961][  T151] ucsi_ccg 3-0040: ccg_fw_update failed - -2
[   11.354573][  T151] ucsi_ccg 3-0040: probe with driver ucsi_ccg failed with error -2
[   11.416514][   T91] l2: unsupportable voltage range: 3500000-3296000uV
[   11.487390][  T143] Bluetooth: hci0: QCA Product ID   :0x0000000a
[   11.493972][  T143] Bluetooth: hci0: QCA SOC Version  :0x40020140

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p53

Context

[   23.093175][   T91] l2: unsupportable voltage range: 3500000-3296000uV
[   23.178252][  T208] blkid (208) used greatest stack depth: 10192 bytes left
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p53
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: while, failed, status

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p53
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   23.307562][   T91] l2: unsupportable voltage range: 3500000-3296000uV
[   23.522417][   T91] l2: unsupportable voltage range: 3500000-3296000uV
[   23.741411][   T91] l2: unsupportable voltage range: 3500000-3296000uV

Target: hamoa-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 18 (0 critical, 1 high, 17 medium, 0 low)

🟡 WATCHDOG (medium) ← PR symbols: with

[    6.972526][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.

Context

[    6.919373][    T1] usbcore: registered new interface driver usb-storage
[    6.940483][  T115] Freeing initrd memory: 61108K
[    6.949347][    T1] i2c_dev: i2c /dev entries driver
[    6.972526][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.984452][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.991514][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.996841][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium) ← PR symbols: failed, already, with

[    7.030591][  T115] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    7.017619][    T1] pstore: Registered efi_pstore as persistent store backend
[    7.025213][  T115] efivars: efivars already registered
[    7.025294][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    7.030591][  T115] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    7.038195][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    7.062177][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    7.070917][    T1] usbcore: registered new interface driver usbhid

🟡 ERROR (medium) ← PR symbols: qcom, connector, typec

[   11.560421][  T271] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led

Context

[   11.539782][  T289] /soc@0/geniqup@bc0000/i2c@b84000/typec-mux@8: Fixed dependency cycle(s) with /soc@0/phy@fdf000
[   11.551958][  T254] mc: Linux media interface: v0.10
[   11.557830][  T290] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: registered as rtc0
[   11.560421][  T271] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   11.560735][  T295] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier usb-1-ss0-sbu-mux for /pmic-glink/connector@0
[   11.561922][  T267] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier fd5000.phy for /pmic-glink/connector@0
[   11.563485][  T122] arm-smmu 3da0000.iommu: probing hardware configuration...

🟡 ERROR (medium) ← PR symbols: failed, qcom, connector

[   11.574810][  T271] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22

Context

[   11.566655][  T122] platform 3d00000.gpu: Adding to iommu group 14
[   11.566840][  T122] platform 3d6a000.gmu: Adding to iommu group 15
[   11.569127][  T289] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 2-0008 for /pmic-glink/connector@1
[   11.574810][  T271] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   11.591778][  T122] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a600000.usb for /pmic-glink/connector@0
[   11.636428][  T254] videodev: Linux video capture interface: v2.00
[   11.643211][  T252] remoteproc remoteproc0: adsp is available

🟡 ERROR (medium) ← PR symbols: assigned, device, self

[   11.828949][   T88] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[   11.824061][   T88] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   11.828654][  T122] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[   11.828674][  T122] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 2
[   11.828949][   T88] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.828952][   T88] tpm tpm0: starting up the TPM manually
[   11.831259][  T122] xhci-hcd xhci-hcd.2.auto: hcc params 0x0118ffc5 hci version 0x110 quirks 0x0000808000000810
[   11.831298][  T122] xhci-hcd xhci-hcd.2.auto: irq 241, io mem 0x0a400000

🟡 ERROR (medium) ← PR symbols: window, with, EINVAL

[   12.384705][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.351187][  T168] pci 0004:00:00.0: PCI bridge to [bus 01-ff]
[   12.358357][  T266] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   12.374029][  T168] pci 0004:00:00.0:   bridge window [io  0x100000-0x100fff]
[   12.384705][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.397786][  T168] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[   12.405139][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.414926][  T168] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]

🟡 ERROR (medium) ← PR symbols: window, EINVAL

[   12.405139][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.374029][  T168] pci 0004:00:00.0:   bridge window [io  0x100000-0x100fff]
[   12.384705][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.397786][  T168] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[   12.405139][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.414926][  T168] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   12.414979][  T168] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold
[   12.425170][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: window, type, EINVAL

[   12.425170][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.405139][  T122] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.414926][  T168] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   12.414979][  T168] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold
[   12.425170][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.434512][  T168] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint
[   12.441199][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.448271][  T168] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]

🟡 ERROR (medium) ← PR symbols: type, EINVAL

[   12.441199][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.414979][  T168] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold
[   12.425170][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.434512][  T168] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint
[   12.441199][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.448271][  T168] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]
[   12.462251][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.466430][  T168] pci 0004:01:00.0: PME# supported from D0 D3hot D3cold

🟡 ERROR (medium) ← PR symbols: type, default, EINVAL

[   12.462251][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.434512][  T168] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint
[   12.441199][  T122] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.448271][  T168] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]
[   12.462251][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.466430][  T168] pci 0004:01:00.0: PME# supported from D0 D3hot D3cold
[   12.475915][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.491637][  T168] pci 0004:01:00.0: ASPM: default states L1

🟡 ERROR (medium) ← PR symbols: window, assigned, default

[   12.475915][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.448271][  T168] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]
[   12.462251][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.466430][  T168] pci 0004:01:00.0: PME# supported from D0 D3hot D3cold
[   12.475915][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.491637][  T168] pci 0004:01:00.0: ASPM: default states L1
[   12.495482][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.500076][  T168] pci 0004:00:00.0: bridge window [mem 0x7c400000-0x7c5fffff]: assigned

🟡 ERROR (medium) ← PR symbols: window, assigned, default

[   12.495482][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.466430][  T168] pci 0004:01:00.0: PME# supported from D0 D3hot D3cold
[   12.475915][  T122] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.491637][  T168] pci 0004:01:00.0: ASPM: default states L1
[   12.495482][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.500076][  T168] pci 0004:00:00.0: bridge window [mem 0x7c400000-0x7c5fffff]: assigned
[   12.509859][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.515708][  T168] pci 0004:00:00.0: BAR 0 [mem 0x7c300000-0x7c300fff]: assigned

🟡 ERROR (medium) ← PR symbols: window, assigned, default

[   12.509859][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.491637][  T168] pci 0004:01:00.0: ASPM: default states L1
[   12.495482][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.500076][  T168] pci 0004:00:00.0: bridge window [mem 0x7c400000-0x7c5fffff]: assigned
[   12.509859][  T122] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.515708][  T168] pci 0004:00:00.0: BAR 0 [mem 0x7c300000-0x7c300fff]: assigned
[   12.515719][  T168] pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned
[   12.526219][  T122] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel

🟡 ERROR (medium) ← PR symbols: failed, device, with

[   12.718295][  T364] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   12.709577][  T257] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 32
[   12.710734][  T257] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 33
[   12.711861][  T257] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 34
[   12.718295][  T364] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   12.735619][  T337] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[   12.737909][  T364] cfg80211: failed to load regulatory.db
[   12.791724][    C0] Unknown battery technology 'LIONQCOMBAT01_07012011'

🟡 WARNING (medium) ← PR symbols: power, typec

[   12.969838][  T265] WARNING: CPU: 10 PID: 265 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   12.948014][  T285] ath12k_wifi7_pci 0004:01:00.0: Wi-Fi 7 Hardware name: wcn7850 hw2.0
[   12.956949][  T285] ath12k_wifi7_pci 0004:01:00.0: MSI vectors: 16
[   12.964335][  T265] ------------[ cut here ]------------
[   12.969838][  T265] WARNING: CPU: 10 PID: 265 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   12.982288][  T265] Modules linked in: ath12k_wifi7(+) ath12k mac80211 libarc4 snd_q6apm(+) rpmsg_ctrl panel_edp(+) apr rpmsg_char fastrpc qrtr_smd qcom_pd_mapper cfg80211 qcom_iris rfkill mhi nvme
[   12.982535][  T265]  snd_soc_lpass_wsa_macro
[   13.020365][  T285] mhi mhi0: Requested to power ON

🟠 CALL_TRACE (high)

[   13.291075][  T265] Call trace:

Context

[   13.185557][  T265] x8 : ffff800085273518 x7 : 0000000000000000 x6 : 0000000000000001
[   13.185558][  T265] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   13.283020][  T265] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   13.291075][  T265] Call trace:
[   13.294325][  T265]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   13.301218][  T265]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   13.307051][  T265]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   33.348459][  T488] EXT4-fs (sda2): orphan cleanup on readonly fs
[   33.355161][  T488] EXT4-fs (sda2): mounted filesystem 2afe7eee-2d67-4173-9b85-5b1918477db3 ro with ordered data mode. Quota mode: none.
done.

Target: purwa-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 36 (0 critical, 1 high, 33 medium, 2 low)

🟡 WATCHDOG (medium) ← PR symbols: with

[    6.362384][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.

Context

[    6.313772][    T1] usbcore: registered new interface driver usb-storage
[    6.330308][   T91] Freeing initrd memory: 60804K
[    6.343668][    T1] i2c_dev: i2c /dev entries driver
[    6.362384][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.373939][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.381003][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.386322][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium) ← PR symbols: failed, already, with

[    6.420103][   T91] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    6.407062][    T1] pstore: Registered efi_pstore as persistent store backend
[    6.414724][   T91] efivars: efivars already registered
[    6.414891][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    6.420103][   T91] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    6.427730][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    6.451686][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    6.460425][    T1] usbcore: registered new interface driver usbhid

🔵 FIRMWARE_FAIL (low) ← PR symbols: qcom, supply, regulator

[    9.326204][  T186] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16

Context

[    9.232121][  T186] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_perf_level_get_fc_force]
[    9.236057][  T186] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_clock_rates_triplet_out_of_spec]
[    9.325528][  T233] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.326204][  T186] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.334319][  T233] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[    9.344816][  T186] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.356213][  T233] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled

🔵 FIRMWARE_FAIL (low) ← PR symbols: qcom, supply, regulator

[    9.344816][  T186] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16

Context

[    9.325528][  T233] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.326204][  T186] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.334319][  T233] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[    9.344816][  T186] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.356213][  T233] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled
[    9.379246][  T245] coresight stm0: STM32 initialized
[    9.385875][  T227] mc: Linux media interface: v0.10

🟡 ERROR (medium) ← PR symbols: failed, qcom, type

[    9.520633][  T237] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led

Context

[    9.519178][  T234] platform iris_pixel.0: Adding to iommu group 17
[    9.519670][  T225] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-0008 for /pmic-glink/connector@0
[    9.520122][  T113] scsi 0:0:0:49456: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.520633][  T237] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[    9.520637][  T237] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[    9.522148][  T113] scsi 0:0:0:0: Direct-Access     KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.530102][  T227] qcom-camss acb7000.isp: Entity type for entity msm_tpg2 was not initialized!

🟡 ERROR (medium) ← PR symbols: failed, qcom, type

[    9.520637][  T237] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22

Context

[    9.519670][  T225] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-0008 for /pmic-glink/connector@0
[    9.520122][  T113] scsi 0:0:0:49456: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.520633][  T237] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[    9.520637][  T237] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[    9.522148][  T113] scsi 0:0:0:0: Direct-Access     KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.530102][  T227] qcom-camss acb7000.isp: Entity type for entity msm_tpg2 was not initialized!
[    9.540779][   T93] sd 0:0:0:0: [sda] 62470144 4096-byte logical blocks: (256 GB/238 GiB)

🟡 ERROR (medium) ← PR symbols: failed, qcom, with

[    9.552663][  T183] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host

Context

[    9.549131][   T93] sd 0:0:0:0: [sda] Write Protect is off
[    9.552568][  T183] qcom-qmp-pcie-phy 1bfc000.phy: Init sequence not available
[    9.552571][  T183] phy phy-1bfc000.phy.0: phy poweron failed --> -61
[    9.552663][  T183] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host
[    9.552670][  T183] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61
[    9.553331][   T64] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.553332][   T64] phy phy-1bd4000.phy.3: phy poweron failed --> -61

🟡 ERROR (medium) ← PR symbols: failed, qcom, with

[    9.552670][  T183] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61

Context

[    9.552568][  T183] qcom-qmp-pcie-phy 1bfc000.phy: Init sequence not available
[    9.552571][  T183] phy phy-1bfc000.phy.0: phy poweron failed --> -61
[    9.552663][  T183] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host
[    9.552670][  T183] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61
[    9.553331][   T64] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.553332][   T64] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    9.553406][   T64] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host

🟡 ERROR (medium) ← PR symbols: failed, qcom, remote

[    9.553406][   T64] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host

Context

[    9.552670][  T183] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61
[    9.553331][   T64] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.553332][   T64] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    9.553406][   T64] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.553917][   T64] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.556826][   T64] sd 0:0:0:1: [sdb] 16384 4096-byte logical blocks: (67.1 MB/64.0 MiB)
[    9.570974][   T25] remoteproc remoteproc1: remote processor cdsp is now up

🟡 ERROR (medium) ← PR symbols: failed, qcom, remote

[    9.553917][   T64] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61

Context

[    9.553331][   T64] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.553332][   T64] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    9.553406][   T64] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.553917][   T64] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.556826][   T64] sd 0:0:0:1: [sdb] 16384 4096-byte logical blocks: (67.1 MB/64.0 MiB)
[    9.570974][   T25] remoteproc remoteproc1: remote processor cdsp is now up
[    9.572654][   T64] sd 0:0:0:1: [sdb] Write Protect is off

🟡 ERROR (medium) ← PR symbols: device, with, self

[   10.970784][  T287] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[   10.925302][  T216] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae98000
[   10.936755][  T287] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   10.952606][  T216] /soc@0/display-subsystem@ae00000/displayport-controller@ae98000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   10.970784][  T287] tpm tpm0: A TPM error (256) occurred attempting the self test
[   10.983243][  T287] tpm tpm0: starting up the TPM manually
[   10.986082][  T216] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae9a000
[   11.005216][  T216] /soc@0/display-subsystem@ae00000/displayport-controller@ae9a000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000

🟡 ERROR (medium) ← PR symbols: connector, device, with

[   11.112000][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.057386][  T216] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   11.073843][  T216] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   11.091697][  T238] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 0-0008 for /pmic-glink/connector@2
[   11.112000][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.113520][  T245] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   11.121834][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.140727][  T238] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-0008 for /pmic-glink/connector@0

🟡 ERROR (medium) ← PR symbols: connector, device, with

[   11.121834][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.091697][  T238] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 0-0008 for /pmic-glink/connector@2
[   11.112000][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.113520][  T245] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   11.121834][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.140727][  T238] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-0008 for /pmic-glink/connector@0
[   11.145134][  T245] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.159981][  T245] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'

🟡 ERROR (medium) ← PR symbols: failed, connector, device

[   11.162862][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.140727][  T238] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-0008 for /pmic-glink/connector@0
[   11.145134][  T245] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.159981][  T245] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.162862][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.168260][  T158] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.178080][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.187626][  T158] cfg80211: failed to load regulatory.db

🟡 ERROR (medium) ← PR symbols: failed, with, EINVAL

[   11.168260][  T158] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   11.145134][  T245] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.159981][  T245] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.162862][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.168260][  T158] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.178080][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.187626][  T158] cfg80211: failed to load regulatory.db
[   11.198968][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: failed, with, EINVAL

[   11.178080][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.159981][  T245] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.162862][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.168260][  T158] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.178080][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.187626][  T158] cfg80211: failed to load regulatory.db
[   11.198968][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.213166][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: failed, with, EINVAL

[   11.198968][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.168260][  T158] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.178080][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.187626][  T158] cfg80211: failed to load regulatory.db
[   11.198968][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.213166][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.224423][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.234274][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: failed, assigned, EINVAL

[   11.213166][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.178080][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.187626][  T158] cfg80211: failed to load regulatory.db
[   11.198968][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.213166][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.224423][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.234274][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.235313][  T245] ath12k_wifi7_pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned

🟡 ERROR (medium) ← PR symbols: failed, assigned, with

[   11.224423][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.187626][  T158] cfg80211: failed to load regulatory.db
[   11.198968][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.213166][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.224423][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.234274][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.235313][  T245] ath12k_wifi7_pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned
[   11.244543][   T93] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel

🟡 ERROR (medium) ← PR symbols: assigned, device, with

[   11.234274][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.198968][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.213166][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.224423][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.234274][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.235313][  T245] ath12k_wifi7_pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned
[   11.244543][   T93] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   11.253552][  T245] ath12k_wifi7_pci 0004:01:00.0: enabling device (0000 -> 0002)

🟡 WARNING (medium) ← PR symbols: mode, success, typec

[   11.471738][   T93] WARNING: CPU: 3 PID: 93 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   11.340413][  T245] mhi mhi0: Power on setup success
[   11.439074][  T120] mhi mhi0: Wait for device to enter SBL or Mission mode
[   11.466267][   T93] ------------[ cut here ]------------
[   11.471738][   T93] WARNING: CPU: 3 PID: 93 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   11.483978][   T93] Modules linked in: panel_edp ath12k_wifi7(+) ath12k mac80211 libarc4 cfg80211 rfkill rpmsg_ctrl mhi apr fastrpc(+) rpmsg_char qrtr_smd(+) qcom_hamoa_ec ps883x phy_nxp_ptn3222 qc
[   11.484216][   T93]  videocc_x1p42100 sha256 mc soundwire_qcom qcom_q6v5 snd_soc_lpass_wsa_macro snd_soc_lpass_tx_macro sha1 snd_soc_lpass_va_macro qcom_sysmon qcom_common phy_snps_eusb2 libdes llc
[   11.648186][   T93] CPU: 3 UID: 0 PID: 93 Comm: kworker/u34:5 Not tainted 6.18.44-g3f68958fa3b6 #1 PREEMPT 

🟠 CALL_TRACE (high)

[   11.778854][   T93] Call trace:

Context

[   11.754715][   T93] x8 : ffff80008410b468 x7 : 0000000000000000 x6 : 0000000000000001
[   11.762761][   T93] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   11.770815][   T93] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   11.778854][   T93] Call trace:
[   11.782091][   T93]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   11.788976][   T93]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   11.794789][   T93]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium) ← PR symbols: ports, found, EINVAL

[   12.140726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.124134][   T93] hub 2-0:1.0: 2 ports detected
[   12.129754][   T93] hub 3-0:1.0: USB hub found
[   12.134358][   T93] hub 3-0:1.0: 2 ports detected
[   12.140726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.150553][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.162498][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.172339][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: ports, found, EINVAL

[   12.150553][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.129754][   T93] hub 3-0:1.0: USB hub found
[   12.134358][   T93] hub 3-0:1.0: 2 ports detected
[   12.140726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.150553][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.162498][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.172339][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.183201][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: ports, EINVAL

[   12.162498][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.134358][   T93] hub 3-0:1.0: 2 ports detected
[   12.140726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.150553][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.162498][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.172339][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.183201][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.193027][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.172339][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.140726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.150553][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.162498][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.172339][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.183201][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.193027][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.206578][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.183201][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.150553][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.162498][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.172339][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.183201][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.193027][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.206578][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.216405][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.193027][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.162498][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.172339][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.183201][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.193027][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.206578][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.216405][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.227759][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.206578][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.172339][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.183201][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.193027][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.206578][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.216405][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.227759][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.237584][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.216405][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.183201][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.193027][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.206578][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.216405][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.227759][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.237584][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.250004][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.227759][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.193027][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.206578][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.216405][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.227759][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.237584][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.250004][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.255713][  T226] ath12k_wifi7_pci 0004:01:00.0 wlP4p1s0: renamed from wlan0

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.237584][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.206578][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.216405][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.227759][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.237584][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.250004][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.255713][  T226] ath12k_wifi7_pci 0004:01:00.0 wlP4p1s0: renamed from wlan0
[   12.259881][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.250004][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.216405][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.227759][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.237584][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.250004][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.255713][  T226] ath12k_wifi7_pci 0004:01:00.0 wlP4p1s0: renamed from wlan0
[   12.259881][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.279631][   T93] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium) ← PR symbols: EINVAL

[   12.259881][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.237584][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.250004][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.255713][  T226] ath12k_wifi7_pci 0004:01:00.0 wlP4p1s0: renamed from wlan0
[   12.259881][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.279631][   T93] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   12.292847][   T93] msm_dpu ae01000.display-controller: bound ae98000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   12.305018][   T93] msm_dpu ae01000.display-controller: bound aea0000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   33.349077][  T404] EXT4-fs (sda2): orphan cleanup on readonly fs
[   33.355787][  T404] EXT4-fs (sda2): mounted filesystem 2e16df27-6eab-4d72-84b7-a63f5340d8a3 ro with ordered data mode. Quota mode: none.
done.

Target: lemans-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 7 (0 critical, 0 high, 7 medium, 0 low)

🟡 ERROR (medium) ← PR symbols: failed, interrupt, names

[    3.199553][    T1] DT AEST: registered 3 AEST error source(s) from DT

Context

[    3.163151][    T1] DT AEST: node /aest/aest-processor-0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.175228][    T1] DT AEST: node /aest/aest-l3-cluster0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.187249][    T1] DT AEST: node /aest/aest-l3-cluster1: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.199553][    T1] DT AEST: registered 3 AEST error source(s) from DT
[    3.206389][    T1] clocksource: Switched to clocksource arch_sys_counter
[    3.213898][    T1] VFS: Disk quotas dquot_6.6.0
[    3.218693][    T1] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

🟡 ERROR (medium) ← PR symbols: device, default, self

[    7.311609][   T63] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[    7.283077][  T207] Bluetooth: L2CAP socket layer initialized
[    7.303646][  T184] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    7.308569][   T63] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)
[    7.311609][   T63] tpm tpm0: A TPM error (256) occurred attempting the self test
[    7.311614][   T63] tpm tpm0: starting up the TPM manually
[    7.319237][  T207] Bluetooth: SCO socket layer initialized
[    7.319927][  T192] geni_i2c a90000.i2c: Bus frequency not specified, default to 100kHz.

🟡 ERROR (medium) ← PR symbols: failed, connector, typec

[    7.380892][  T139] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    7.362699][  T192] /connector-0: Fixed dependency cycle(s) with /soc@0/geniqup@ac0000/i2c@a90000/usb-typec@67
[    7.366253][  T184] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    7.374945][  T191] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 27
[    7.380892][  T139] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    7.400233][  T192] /soc@0/geniqup@ac0000/i2c@a90000/usb-typec@67: Fixed dependency cycle(s) with /connector-0
[    7.401120][  T139] cfg80211: failed to load regulatory.db
[    7.426112][  T192] /connector-1: Fixed dependency cycle(s) with /soc@0/geniqup@ac0000/i2c@a90000/usb-typec@47

🟡 ERROR (medium) ← PR symbols: failed, found, with

[    7.812083][  T115] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2

Context

[    7.770449][  T226] hub 1-1:1.0: USB hub found
[    7.811910][  T115] Bluetooth: hci0: QCA controller version 0x12110201
[    7.811917][  T115] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    7.812083][  T115] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    7.812096][  T115] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    7.812098][  T115] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    7.812246][  T115] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

🟡 ERROR (medium) ← PR symbols: failed, data, with

[    7.812246][  T115] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

Context

[    7.812083][  T115] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    7.812096][  T115] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    7.812098][  T115] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    7.812246][  T115] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    7.812257][  T115] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    7.812258][  T115] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    7.812260][  T115] Bluetooth: hci0: HFP non-HCI data transport is supported

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   28.843615][  T361] EXT4-fs (sda2): orphan cleanup on readonly fs
[   28.850463][  T361] EXT4-fs (sda2): mounted filesystem 7f081a84-7045-4209-949a-773694ad02be ro with ordered data mode. Quota mode: none.
done.

Target: qcs615-ride

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 3 (1 critical, 1 high, 1 medium, 0 low)

🟡 ERROR (medium) ← PR symbols: qcom, typec, limit

[    7.250109][  T111] Internal error: synchronous external abort: 0000000096000010 [#1]  SMP

Context

[    7.215696][  T187] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 19
[    7.216514][  T221] qcom-pcie 1c08000.pcie: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[    7.239062][  T187] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 20
[    7.250109][  T111] Internal error: synchronous external abort: 0000000096000010 [#1]  SMP
[    7.251066][  T187] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 21
[    7.258621][  T111] Modules linked in: qcom_edac rpmsg_char fastrpc(+) qcom_pdr_msg qrtr_smd qmi_cooling pci_pwrctrl_pwrseq qcom_spmi_temp_alarm qcom_vadc_common rtc_pm8xxx phy_package qcom_pon rfk
[    7.272180][  T187] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 22

🟠 CALL_TRACE (high)

[    7.368301][  T111] Call trace:

Context

[    7.368276][  T111] x8 : 0000000000000018 x7 : 0000000000000000 x6 : 0000000000000000
[    7.368284][  T111] x5 : ffff00007feff012 x4 : ffff000090c51852 x3 : 0000000000000001
[    7.368293][  T111] x2 : 0000000000000012 x1 : ffff000090c51840 x0 : ffff00007feff000
[    7.368301][  T111] Call trace:
[    7.368306][  T111]  __pi_memcpy_generic+0x2c/0x230 (P)
[    7.377381][  T221] pci 0000:00:00.0: Adding to iommu group 23
[    7.381706][  T111]  swiotlb_tbl_map_single+0x160/0x2c8

🔴 KERNEL_PANIC (critical) ← PR symbols: features

[    7.541774][  T111] Kernel panic - not syncing: synchronous external abort: Fatal exception

Context

[    7.417872][  T111]  ret_from_fork+0x10/0x20
[    7.417885][  T111] Code: f100405f 540000c3 a9401c26 a97f348c (a9001c06) 
[    7.417892][  T111] ---[ end trace 0000000000000000 ]---
[    7.541774][  T111] Kernel panic - not syncing: synchronous external abort: Fatal exception
[    7.541785][  T111] SMP: stopping secondary CPUs
[    7.743839][  T111] Kernel Offset: disabled
[    7.743843][  T111] CPU features: 0x100000,00426000,40046281,0400720b

Target: qcs8300-ride

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 12 (0 critical, 2 high, 10 medium, 0 low)

🟡 WARNING (medium) ← PR symbols: qcom, clocks, supply

[    5.021868][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98

Context

[    5.014942][   T85] qcom-pcie 1c00000.pci: supply vddpe-3v3 not found, using dummy regulator
[    5.021316][    T1] clk: Disabling unused clocks
[    5.021867][    T1] ------------[ cut here ]------------
[    5.021868][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98
[    5.021876][    T1] Modules linked in:
[    5.021880][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G S                  6.18.44-g3f68958fa3b6 #1 PREEMPT 
[    5.021883][    T1] Tainted: [S]=CPU_OUT_OF_SPEC

🟠 CALL_TRACE (high)

[    5.021917][    T1] Call trace:

Context

[    5.021909][    T1] x8 : ffff800082c3bbe8 x7 : 0000000000000000 x6 : 0000000000000001
[    5.021912][    T1] x5 : ffff800080b41b88 x4 : 000000000007706c x3 : 000000000007706c
[    5.021914][    T1] x2 : ffff800080b43298 x1 : 0000000000000001 x0 : 0000000000000001
[    5.021917][    T1] Call trace:
[    5.021919][    T1]  phy_mux_is_enabled+0x7c/0x98 (P)
[    5.021921][    T1]  clk_core_is_enabled+0x44/0x120
[    5.021925][    T1]  clk_disable_unused_subtree+0x88/0x258

🟡 WARNING (medium) ← PR symbols: qcom

[    5.021962][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98

Context

[    5.021942][    T1]  ret_from_fork+0x10/0x20
[    5.021945][    T1] ---[ end trace 0000000000000000 ]---
[    5.021962][    T1] ------------[ cut here ]------------
[    5.021962][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98
[    5.021965][    T1] Modules linked in:
[    5.021967][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G S      W           6.18.44-g3f68958fa3b6 #1 PREEMPT 
[    5.021970][    T1] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN

🟠 CALL_TRACE (high)

[    5.021999][    T1] Call trace:

Context

[    5.021993][    T1] x8 : ffff800082c3bbe8 x7 : 0000000000000000 x6 : 0000000000000001
[    5.021995][    T1] x5 : ffff800080b41b88 x4 : 00000000000a906c x3 : 00000000000a906c
[    5.021997][    T1] x2 : ffff800080b43298 x1 : 0000000000000001 x0 : 0000000000000001
[    5.021999][    T1] Call trace:
[    5.022000][    T1]  phy_mux_is_enabled+0x7c/0x98 (P)
[    5.022002][    T1]  clk_core_is_enabled+0x44/0x120
[    5.022004][    T1]  clk_disable_unused_subtree+0x88/0x258

🟡 ERROR (medium) ← PR symbols: failed, assigned, device

[   10.613803][  T104] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   10.573227][  T192] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   10.598338][  T192] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.605316][  T192] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.613803][  T104] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.623598][  T104] cfg80211: failed to load regulatory.db
[   10.709158][  T192] ath11k_pci 0000:01:00.0: BAR 0 [mem 0x40400000-0x405fffff 64bit]: assigned
[   10.718077][  T192] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002)

🟡 ERROR (medium) ← PR symbols: while, failed, status

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium) ← PR symbols: mode, while, failed

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   34.151498][  T366] EXT4-fs (sda2): orphan cleanup on readonly fs
[   34.158391][  T366] EXT4-fs (sda2): mounted filesystem 985e5d67-cfc5-4f20-bc82-74addca41f10 ro with ordered data mode. Quota mode: none.
done.

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.113828][  T337] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   35.080558][    T1] Segment Routing with IPv6
[   35.085419][    T1] In-situ OAM (IOAM) with IPv6
[18t[   36.108505][  T138] refgen: disabling
[   36.113828][  T337] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.124089][  T337] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.134805][  T337] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.144103][  T337] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.134805][  T337] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[18t[   36.108505][  T138] refgen: disabling
[   36.113828][  T337] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.124089][  T337] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.134805][  T337] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.144103][  T337] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.151797][  T337] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.162689][  T337] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium) ← PR symbols: mode, status, type

[   36.162689][  T337] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.134805][  T337] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.144103][  T337] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.151797][  T337] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.162689][  T337] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.172151][  T337] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
7[32766;32766H[6n8[!p]104\[0m[?7h[1G[0J[   36.523212][    T1] systemd[1]: systemd 261.2 running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA +IPE -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +
[   36.556598][    T1] systemd[1]: Detected architecture arm64.

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.589707][  T337] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.556598][    T1] systemd[1]: Detected architecture arm64.
[   36.569399][  T337] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:00:00.0
[   36.578860][  T337] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.589707][  T337] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.599021][  T337] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.606898][  T337] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   36.616299][  T337] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium) ← PR symbols: status, type, device

[   36.616302][  T337] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.599021][  T337] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.606898][  T337] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   36.616299][  T337] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.616302][  T337] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.616304][  T337] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)

[0;1;39mWelcome to [0m[1mQualcomm Linux Reference Distro 2.99+snapshot-d58a9f2dddfdeb4e74ef99929072ff6721590dc9[0m[0;1;39m![0m