Skip to content

ICL firmware boot errors #2380

Closed
Closed

Description

@plbossart

We really need to solve this, this keeps polluting CI results:

https://sof-ci.01.org/sofpr/PR3296/build6981/devicetest/

kernel: [  730.773915] sof-audio-pci 0000:00:1f.3: FW Poll Status: reg=0x80000000 successful
kernel: [  730.773938] sof-audio-pci 0000:00:1f.3: FW Poll Status: reg=0x3010e0e successful
kernel: [  731.073971] sof-audio-pci 0000:00:1f.3: FW Poll Status: reg=0x6000010 timedout
kernel: [  731.073992] sof-audio-pci 0000:00:1f.3: unknown ROM status value 06000010
kernel: [  731.073998] sof-audio-pci 0000:00:1f.3: error: status = 0x00000000 panic = 0x00000000
kernel: [  731.074030] sof-audio-pci 0000:00:1f.3: error: extended rom status: 0x6000010 0x0 0x0 0x0 0x0 0x0 0x2001182 0x0
kernel: [  731.074036] sof-audio-pci 0000:00:1f.3: unknown ROM status value 06000010

Also seen on 02_01_TestPtpSimpleLoopbackMasterPlayback48000Hz32b32b8ch firmware tests
https://sof-ci.01.org/sof-pr-viewer/#/build/PR3296/build5404075

Activity

  1. ranj063 commented on Aug 24, 2020

    @ranj063
    Collaborator

    @plbossart I dont think this a kernel issue. The driver does the right thing. It is more of a CI issue where it needs to realize that firmware boot can take more than 1 iteration.

  2. ranj063 commented on Aug 24, 2020

    @ranj063
    Collaborator

    @plbossart I dont think this a kernel issue. The driver does the right thing. It is more of a CI issue where it needs to realize that firmware boot can take more than 1 iteration.

    sof-test issue related to this: thesofproject/sof-test#340

  3. plbossart commented on Aug 24, 2020

    @plbossart
    MemberAuthor

    @ranj063 I can flip the argument and ask why the kernel flags an error when it should only complain when the last iteration fails.
    The intermediate errors should really be warnings. It's not the job of CI scripts to translate error/warning levels, the kernel should do a better job here.

  4. xiulipan commented on Aug 25, 2020

    @xiulipan

    @ranj063 Agreed with @plbossart why we should print an error message when this actually is not an error.
    PS: I also see same issue on CML these days, seems some change will make the FW boot retry happen more often.

  5. fredoh9 commented on Aug 25, 2020

    @fredoh9
    Collaborator

    related PR is #2382

  6. added
    CMLApplies to Comet Lake platform
    ICLApplies to Icelake platform
    P1Blocker bugs or important features
    dmesgIssues related to kernel dmesg (diagnostic message)
    on Aug 31, 2020
  7. mengdonglin commented on Aug 31, 2020

    @mengdonglin

    @xiulipan is revising CI filter to check the new dmesg.

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

    CMLApplies to Comet Lake platformICLApplies to Icelake platformP1Blocker bugs or important featuresdmesgIssues related to kernel dmesg (diagnostic message)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions