UP squared 6000 board fails to bring up audio on v2023dev3

Affected images versions

not relevant (explain why)
see the table below (list the build id and the apt or ostree deployment of the tested images in the appropriate cells)

Type	Arch	v2023dev3
minimal/fixedfunction	amd64	20220822.1240
minimal/fixedfunction	armhf
minimal/fixedfunction	arm64
target/hmi	amd64	20220822.1240
target/hmi	armhf
target/hmi	arm64
basesdk	amd64
sdk	amd64
nfs	amd64
nfs	armhf
nfs	arm64
lxc	amd64
lxc	armhf
lxc	arm64
image-builder
package-source-builder

To find the build id and the variant type you can:

derive it from the image name
- for instance, with the apertis_ostree_v2022pre-fixedfunction-amd64-uefi_20211031.0425.img.gz image the build id is 20211031.0425, the variant is fixedfunction the deployment type is ostree
obtain it from /etc/os-release using the BUILD_ID and VARIANT_ID keys

Unaffected images versions

all versions up to XXX (replace XXX with the build id of the most recent Apertis images where this bug cannot be reproduced)
not relevant (explain why)
v2020 (explain why)
v2021 (explain why)
v2022 (explain why)

Testcase

The link to the testcase on https://qa.apertis.org/ if the bug was found during a testing round

Steps to reproduce

Ordered list detailing every step so other developers can reproduce the issue. Include hardware which you used.

Expected result

Explain (at least briefly) what result you expected.

Actual result

Explain the actual result observed after the execution steps. Paste any error output here between code block back-quotes. For long text contents (over 1000 lines) it is better to attach a file by using the button in the right corner. If adding comments on the log is required create a new snippet and add the link to it here.

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

always
✅ often, but not always
rarely

Impact of bug

How severe is the bug? Does it render an image unbootable? Is it a security issue? Does it prevent specific applications from working? What is the impact? Does this bug affect a critical component? Does it cause something else to not work? How often is the bug likely to be found by a user? For example, every boot or once per year?

Attachments

Add further information about the environment in the form of attachments here. Attach plain text files from log output (from journalctl, systemctl, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.

Screenshots and videos are usually useful for graphic issues.

Root cause

describe in one line what caused the issue to give a hint to product teams whether they may be impacted or not

$ sudo dmesg | grep sof
[    0.389423] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.389424] software IO TLB: mapped [mem 0x0000000067c0b000-0x000000006bc0b000] (64MB)
[   13.849342] sof-audio-pci-intel-tgl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[   13.849354] sof-audio-pci-intel-tgl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[   13.849372] sof-audio-pci-intel-tgl 0000:00:1f.3: enabling device (0000 -> 0002)
[   13.849716] sof-audio-pci-intel-tgl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[   14.669089] sof-audio-pci-intel-tgl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[   14.679243] sof-audio-pci-intel-tgl 0000:00:1f.3: use msi interrupt mode
[   16.129835] sof-audio-pci-intel-tgl 0000:00:1f.3: No SoundWire machine driver found
[   16.129842] sof-audio-pci-intel-tgl 0000:00:1f.3: hda codecs found, mask 5
[   16.129845] sof-audio-pci-intel-tgl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[   16.129854] sof-audio-pci-intel-tgl 0000:00:1f.3: DMICs detected in NHLT tables: 4
[   16.233540] sof-audio-pci-intel-tgl 0000:00:1f.3: firmware: direct-loading firmware intel/sof/community/sof-ehl.ri
[   16.233564] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 1:7:0-47d07
[   16.233568] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:19:1
[   16.233581] sof-audio-pci-intel-tgl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[   19.323405] sof-audio-pci-intel-tgl 0000:00:1f.3: error: cl_copy_fw: timeout HDA_DSP_SRAM_REG_ROM_STATUS read
[   19.335024] sof-audio-pci-intel-tgl 0000:00:1f.3: ------------[ DSP dump start ]------------
[   19.344466] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware download failed
[   19.352146] sof-audio-pci-intel-tgl 0000:00:1f.3: fw_state: SOF_FW_BOOT_IN_PROGRESS (2)
[   19.361117] sof-audio-pci-intel-tgl 0000:00:1f.3: extended rom status:  0x80000012 0x2c 0x0 0x0 0x0 0x0 0x25401c8 0x0
[   19.372978] sof-audio-pci-intel-tgl 0000:00:1f.3: ------------[ DSP dump end ]------------
[   19.382276] sof-audio-pci-intel-tgl 0000:00:1f.3: Failed to start DSP
[   19.389476] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to boot DSP firmware -110
[   19.449382] sof-audio-pci-intel-tgl 0000:00:1f.3: error: hda_dsp_core_reset_enter: timeout on HDA_DSP_REG_ADSPCS read
[   19.461260] sof-audio-pci-intel-tgl 0000:00:1f.3: error: dsp core reset failed: core_mask 1
[   19.470876] sof-audio-pci-intel-tgl 0000:00:1f.3: error: sof_probe_work failed err: -110

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @sagar @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T9191

Edited Aug 23, 2022 by Apertis CI robot