Skip to content

ci: skip qrb2210-rb1 in the mainline and linux-next LAVA tests - #553

Draft
Christopher Obbard (obbardc) wants to merge 1 commit into
qualcomm-linux:mainfrom
obbardc:wip/obbardc/lava-disable-rb1-mainline-next
Draft

ci: skip qrb2210-rb1 in the mainline and linux-next LAVA tests#553
Christopher Obbard (obbardc) wants to merge 1 commit into
qualcomm-linux:mainfrom
obbardc:wip/obbardc/lava-disable-rb1-mainline-next

Conversation

@obbardc

Copy link
Copy Markdown
Contributor

qrb2210-rb1 never reaches a login prompt on the mainline kernel: as adsprpcd.service and adsprpcd_audiopd.service start, fastrpc fails an mmap for the aDSP:

qcom,fastrpc-cb [...]:fastrpc:compute-cb@3: mem mmap error, fd 11,
vaddr ffff9dc10000, size 262144
qcom_q6v5_pas ab00000.remoteproc: fatal error received: SFR Init:
wdog or kernel error suspected.
remoteproc remoteproc1: crash detected in adsp: type fatal error

The SoC then hard resets with no panic and no call trace. That repeats for the timeout the minimal-boot action allows, so the login-action times out and the job is marked as Incomplete.

See https://lava.infra.foundries.io/scheduler/job/356726 for a sample job.

Exclude the board from both runs until the aDSP side is fixed. The qcom-next runs still cover qrb2210-rb1.

Link: #424

qrb2210-rb1 never reaches a login prompt on the mainline kernel: as
adsprpcd.service and adsprpcd_audiopd.service start, fastrpc fails an
mmap for the aDSP:

  qcom,fastrpc-cb [...]:fastrpc:compute-cb@3: mem mmap error, fd 11,
    vaddr ffff9dc10000, size 262144
  qcom_q6v5_pas ab00000.remoteproc: fatal error received: SFR Init:
    wdog or kernel error suspected.
  remoteproc remoteproc1: crash detected in adsp: type fatal error

The SoC then hard resets with no panic and no call trace. That repeats
for the timeout the minimal-boot action allows, so the login-action
times out and the job is marked as Incomplete.

See https://lava.infra.foundries.io/scheduler/job/356726 for a sample
job.

Exclude the board from both runs until the aDSP side is fixed. The
qcom-next runs still cover qrb2210-rb1.

Link: qualcomm-linux#424
Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
lava_report_test_results_externally: false
lava_boards_exclude: '["glymur-crd", "qcs615-ride", "qcs8300-ride", "lemans-evk"]'
# qrb2210-rb1 doesn't boot with mainline, only qcom-next; see
# https://github.com/qualcomm-linux/qcom-deb-images/issues/424

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wasn't sure whether to create a new issue about this or reuse the existing issue.

@lool

Copy link
Copy Markdown
Contributor

Christopher Obbard (@obbardc) this is qualcomm/fastrpc#371

I didn't get the chance to upload this fix, I was kind of hoping to get qualcomm/fastrpc#372 reviewed so that I could upload both patches on top of 1.0.6 to 4 repos (forky, trixie + QLI overlays).

@github-actions

Copy link
Copy Markdown

Test Results

  7 files  ±0   21 suites  ±0   15m 37s ⏱️ ±0s
 21 tests ±0   19 ✅ ±0  0 💤 ±0  2 ❌ ±0 
184 runs  ±0  182 ✅ ±0  0 💤 ±0  2 ❌ ±0 

For more details on these failures, see this check.

Results for commit 5d4ee88. ± Comparison against base commit 260a69f.

@github-actions

Copy link
Copy Markdown

@obbardc

Copy link
Copy Markdown
Contributor Author

Christopher Obbard (Christopher Obbard (@obbardc)) this is qualcomm/fastrpc#371

I didn't get the chance to upload this fix, I was kind of hoping to get qualcomm/fastrpc#372 reviewed so that I could upload both patches on top of 1.0.6 to 4 repos (forky, trixie + QLI overlays).

Sure, I think it makes sense to create an issue in qcom-deb-images so we can track the issue, then close this "useless" PR, what do you think?

@lool

Copy link
Copy Markdown
Contributor

Sure, I think it makes sense to create an issue in qcom-deb-images so we can track the issue, then close this "useless" PR, what do you think?

Totally, I agree an issue here makes sense, time will tell if we end up picking up this PR or closing it without merging :)

@obbardc

Copy link
Copy Markdown
Contributor Author

This should have been fixed with latest fastrpc package upload but it still seems to be failing. Should probbaly convert this to an issue as a next step.

@obbardc

Copy link
Copy Markdown
Contributor Author

Created #572 to track this better.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants