Skip to content

[BUG][JSL] Failed to load firmware on JSL #4916

New issue
New issue
Closed
Closed
[BUG][JSL] Failed to load firmware on JSL#4916
Labels
JSLApplies to Jasper Lake platformP1Blocker bugs or important featuresSigningApplies to code signing of firmwarebugSomething isn't working as expectedchromeChromebooks or ChromeOS

Description

@yangxiaohua2009
yangxiaohua2009
opened on Oct 26, 2021

Describe the bug
The sof DSP failed to boot and the dmesg shows FW Poll Status: reg[0x80000]=0x80000012 timedout on JSL.
The problem looks like #2888 but the error code is different.

To Reproduce
Select to use sof on JSL.

Reproduction Rate
10/10

Expected behavior
DSP firmware boots normally and the start-up process goes on.

Impact
firmware boot failure.

Environment

  1. Kernel: 5.14.7
  2. SOF: 1:9:0-fa857
  3. Platform: JSL

Screenshots or console output
[ 6.833291] sof-audio-pci-intel-icl 0000:00:1f.3: FW Poll Status: reg[0x80000]=0x80000012 timedout
[ 6.833296] sof-audio-pci-intel-icl 0000:00:1f.3: error: cl_copy_fw: timeout HDA_DSP_SRAM_REG_ROM_STATUS read
[ 6.833824] sof-audio-pci-intel-icl 0000:00:1f.3: FW Poll Status: reg[0x160]=0x140000 successful
[ 6.833866] sof-audio-pci-intel-icl 0000:00:1f.3: unknown ROM status value 80000012
[ 6.833888] sof-audio-pci-intel-icl 0000:00:1f.3: error: extended rom status: 0x80000012 0x2c 0x0 0x0 0x0 0x0 0x2100186 0x0
[ 6.833890] sof-audio-pci-intel-icl 0000:00:1f.3: error: load fw failed ret: -110
[ 6.833917] sof-audio-pci-intel-icl 0000:00:1f.3: error: failed to reset DSP
[ 6.833919] sof-audio-pci-intel-icl 0000:00:1f.3: error: failed to boot DSP firmware -110
[ 6.884371] sof-audio-pci-intel-icl 0000:00:1f.3: FW Poll Status: reg[0x4]=0x1d003c timedout
[ 6.884375] sof-audio-pci-intel-icl 0000:00:1f.3: error: hda_dsp_core_reset_enter: timeout on HDA_DSP_REG_ADSPCS read
[ 6.884378] sof-audio-pci-intel-icl 0000:00:1f.3: error: dsp core reset failed: core_mask 1
[ 6.884658] sof-audio-pci-intel-icl 0000:00:1f.3: error: sof_probe_work failed err: -110

dmesg2.log

Activity

  1. yangxiaohua2009
    added
    bugSomething isn't working as expected
    on Oct 26, 2021
  2. mengdonglin
    added
    SigningApplies to code signing of firmware
    on Oct 26, 2021

  3. keqiaozhang commented on Oct 26, 2021

    @keqiaozhang
    keqiaozhang
    on Oct 26, 2021
    Collaborator

    I found the same issue on ADLP chrome laptop. Our device is running with UbuntuOS, so I tested with latest kernel/sof-dev+ sof/master branch. This is not the key error and I have added i915.force_probe=46a8 to grub boot option.

    [  808.144710] usbcore: deregistering interface driver snd-usb-audio
[  813.840373] rt5682 i2c-10EC5682:00: Using default DAI clk names: rt5682-dai-wclk, rt5682-dai-bclk
[  814.791377] sof-audio-pci-intel-tgl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[  814.791625] sof-audio-pci-intel-tgl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[  814.798107] sof-audio-pci-intel-tgl 0000:00:1f.3: use msi interrupt mode
[  814.812529] sof-audio-pci-intel-tgl 0000:00:1f.3: hda codecs found, mask 4
[  814.812673] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 1:8:0-9a35f
[  814.812675] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:18:0
[  814.812682] sof-audio-pci-intel-tgl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[  814.829361] usbcore: registered new interface driver snd-usb-audio
[  815.716850] sof-audio-pci-intel-tgl 0000:00:1f.3: error: cl_dsp_init: timeout HDA_DSP_SRAM_REG_ROM_STATUS read
[  815.716873] sof-audio-pci-intel-tgl 0000:00:1f.3: ------------[ DSP dump start ]------------
[  815.716880] sof-audio-pci-intel-tgl 0000:00:1f.3: Boot iteration failed: 3/3
[  815.716886] sof-audio-pci-intel-tgl 0000:00:1f.3: fw_state: SOF_FW_BOOT_IN_PROGRESS (2)
[  815.716916] sof-audio-pci-intel-tgl 0000:00:1f.3: extended rom status:  0x6000021 0x0 0x0 0x0 0x0 0x0 0x256051f 0x0
[  815.716921] sof-audio-pci-intel-tgl 0000:00:1f.3: ------------[ DSP dump end ]------------
[  815.716946] sof-audio-pci-intel-tgl 0000:00:1f.3: error: dsp init failed after 3 attempts with err: -110
[  815.717036] sof-audio-pci-intel-tgl 0000:00:1f.3: Failed to start DSP
[  815.717042] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to boot DSP firmware -110
[  815.769469] sof-audio-pci-intel-tgl 0000:00:1f.3: error: hda_dsp_core_reset_enter: timeout on HDA_DSP_REG_ADSPCS read
[  815.769485] sof-audio-pci-intel-tgl 0000:00:1f.3: error: dsp core reset failed: core_mask 1
[  815.770376] sof-audio-pci-intel-tgl 0000:00:1f.3: error: sof_probe_work failed err: -110

    Full dmesg is attached:
    dmesg.txt

  4. keqiaozhang
    added
    ADLApplies to Alder Lake platform
    chromeChromebooks or ChromeOS
    JSLApplies to Jasper Lake platform
    P1Blocker bugs or important features
    on Oct 26, 2021

  5. mengdonglin commented on Oct 26, 2021

    @mengdonglin
    mengdonglin
    on Oct 26, 2021
    Collaborator

    @yangxiaohua2009 Can you clone https://github.com/thesofproject/sof-bin/? Please try 2 firmware binaries:

    • 1st one is v1.9.x/sof-v1.9/intel-signed/sof-jsl.ri. It's signed by Intel production key.
    • 2nd one is v1.9.x/sof-v1.9/community/sof-jsl.ri It's signed by SOF community key.

    @keqiaozhang I feel the problem you observe on ADL-P Chrome book may be a different one. There is no "W Poll Status: reg[0x80000]=0x80000012" in your test. Can you please try adl-002 debug-signed FW release?

  6. plbossart commented on Oct 26, 2021

    @plbossart
    plbossart
    on Oct 26, 2021
    Member

    @yangxiaohua2009 are you using a JSL device with ES8336? We've got a similar report here thesofproject/linux#3210 of the same problem (EDIT closed as duplicate of #4916)

    @keqiaozhang @mengdonglin I don't think we should add ADL information here, this cannot be the same issue and I don't think it's a Chrome problem either.

  7. keqiaozhang commented on Oct 27, 2021

    @keqiaozhang
    keqiaozhang
    on Oct 27, 2021
    Collaborator

    @keqiaozhang I feel the problem you observe on ADL-P Chrome book may be a different one. There is no "W Poll Status: reg[0x80000]=0x80000012" in your test. Can you please try adl-002 debug-signed FW release?

    yes, I have tried adl-002 debug-signed firmware binary, same one which chrome team is using, but this issue is still there.
    I checked with Sathya yesterday, he also checked the coreboot image(except ubuntu payload) provide by Meera, adl-002 debug-signed firmware can be loaded with that coreboot under ChromeOS, so it seems like not a coreboot issue but something related to our driver or firmware.

  8. keqiaozhang commented on Oct 27, 2021

    @keqiaozhang
    keqiaozhang
    on Oct 27, 2021
    Collaborator

    @keqiaozhang @mengdonglin I don't think we should add ADL information here, this cannot be the same issue and I >don't think it's a Chrome problem either.

    Sure, I will file a new bug to track the issue on ADLP and remove the adlp information form this bug.

  9. keqiaozhang commented on Oct 27, 2021

    @keqiaozhang
    keqiaozhang
    on Oct 27, 2021
    Collaborator

    A new bug #4923 has been filed to track the issue on ADLP.

  10. keqiaozhang
    removed
    ADLApplies to Alder Lake platform
    on Oct 27, 2021

  11. plbossart commented on Nov 5, 2021

    @plbossart
    plbossart
    on Nov 5, 2021
    Member

    @lgirdwood @mwasko this problem was reproduced by @hli25, it would appear the firmware was signed either with the wrong key, wrong masks or wrong CSE tools.

  12. mwasko commented on Nov 8, 2021

    @mwasko
    mwasko
    on Nov 8, 2021
    Contributor

    @plbossart the JSL 1.9 FW signature looks ok, but I will take a closer look on that

  13. 4 remaining items

  14. plbossart commented on Nov 15, 2021

    @plbossart
    plbossart
    on Nov 15, 2021
    Member

    @tomty89 thanks for testing, much appreciated.

    the latest code we have to support Intel platforms with the ES83316 device is here: thesofproject/linux#3107
    You would need to pick this branch and install a custom kernel.

    If you can give it a try and report your findings in thesofproject/linux#2955 that would be great.

  15. tomty89 commented on Nov 15, 2021

    @tomty89
    tomty89
    on Nov 15, 2021

    @plbossart I already did (please see the linked comment above to see what exactly I've applied), and the result is above -- I get an analog alsa device, but no sound actually coming out (other than the pops mentioned).

  16. plbossart commented on Nov 15, 2021

    @plbossart
    plbossart
    on Nov 15, 2021
    Member

    @plbossart I already did (please see the linked comment above to see what exactly I've applied), and the result is above -- I get an analog alsa device, but no sound actually coming out (other than the pops mentioned).

    @hli25 did you get audible sound on the JSL platform you tested, if yes can you share the alsamixer settings used?

  17. hli25 commented on Nov 17, 2021

    @hli25
    hli25
    on Nov 17, 2021

    @plbossart I already did (please see the linked comment above to see what exactly I've applied), and the result is above -- I get an analog alsa device, but no sound actually coming out (other than the pops mentioned).

    @hli25 did you get audible sound on the JSL platform you tested, if yes can you share the alsamixer settings used?

    Please try to set "DAC" to 100 via alsamixser @tomty89

  18. tomty89 commented on Nov 17, 2021

    @tomty89
    tomty89
    on Nov 17, 2021

    Nope, it doesn't help (it's 100 by default anyway). And toggling/adjusting other mixer controls doesn't seem to help either. Btw I don't know if it's expected but there's no master volume control. There are only the Headphone and Speaker switches and the Headphone Mixer volume control (and a bunch of other whatsoever).

  19. lgirdwood commented on Nov 17, 2021

    @lgirdwood
    lgirdwood
    on Nov 17, 2021
    Member

    @tomty89 can you run amixer contents during playback and paste the output here, it could be we are missing one mixer control setting.

  20. tomty89 commented on Nov 19, 2021

    @tomty89
    tomty89
    on Nov 19, 2021 · Hidden as off-topic

  21. marc-hb commented on Nov 19, 2021

    @marc-hb
    marc-hb
    on Nov 19, 2021
    Collaborator

    Please go to thesofproject/linux#2955 or file a different bug for problems happening after loading the firmware.

  22. marc-hb commented on Nov 19, 2021

    @marc-hb
    marc-hb
    on Nov 19, 2021
    Collaborator

    v1.9.2 has been merged in sof-bin.git

    /sof/tools/sof_ri_info/sof_ri_info.py -v sof-bin/v1.9.x/sof-v1.9.2/intel-signed/sof-jsl.ri | grep -A1 Modulus
./sof-bin/v1.9.x/sof-v1.9.2/intel-signed/sof-jsl.ri
      Modulus size (dwords) 64
        6f e4 d5 c9 52 f4 01 c1 ... f8 7c b0 09 09 c2 a3 cc (Other)

    All older intel-signed/sof-jsl.ri files had been signed with the (ICL Intel prod key)

  23. lgirdwood
    added a commit that references this issue on Nov 21, 2021

    sof_ri_info: add JSL Intel prod key to list of known keys

    2c208b5

  24. olidietzel commented on Dec 6, 2021

    @olidietzel
    olidietzel
    on Dec 6, 2021 · Hidden as off-topic
  25. marc-hb
    closed this as completedon Dec 6, 2021

  26. plbossart commented on Dec 6, 2021

    @plbossart
    plbossart
    on Dec 6, 2021
    Member

    Chuwi Hi10 Go, jsl Celeron N4500, KDE Neon unstable with signed Debian 5.16rc3 Kernel

    try thesofproject/linux#3107 and file a separate issue if this doesn't work for you.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    JSLApplies to Jasper Lake platformP1Blocker bugs or important featuresSigningApplies to code signing of firmwarebugSomething isn't working as expectedchromeChromebooks or ChromeOS

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions