Skip to content

[BUG] dai_config IPC timeout on TGLU_RVP_NOCODEC when arecord #4164

Closed

Description

@XiaoyunWu6666

Describe the bug
When running check-capture on TGLU_RVP_NOCODEC ,fread failed in logger_read when arecording

To Reproduce
TPLG=sof-tgl-nocodec-ci.tplg ~/sof-test/test-case/check-capture.sh -d 1 -l 1 -r 50

Environment
Kernel Branch: topic/sof-dev
Kernel Commit: aae5bcfa
SOF Branch: main
SOF Commit: ea5d9be
TPLG=sof-tgl-nocodec-ci.tplg
Device:TGLU_RVP_NOCODEC [jf-tglu-rvp-nocodec-1]

Screenshots or console output
image

dmesg log
image

For more detailed log, please refer to http://sof-ci.sh.intel.com/#/result/planresultdetail/3874?model=TGLU_RVP_NOCODEC&testcase=check-capture-50rounds

Activity

  1. changed the title [-][BUG] soc_pcm_hw_params and dpcm_fe_dai_hw_params failed on TGLU_RVP_NOCODEC when arecord[/-] [+][BUG] dai_config IPC timeout on TGLU_RVP_NOCODEC when arecord[/+] on May 11, 2021
  2. added
    TGLApplies to Tiger Lake
    multicoreIssues observed when not only core#0 is used.
    on May 11, 2021
  3. slawblauciak commented on May 11, 2021

    @slawblauciak
    Collaborator

    Can you please check if #4089 is effective against this issue? Thanks

  4. XiaoyunWu6666 commented on May 11, 2021

    @XiaoyunWu6666
    ContributorAuthor

    This issue happens on ADLP_RVP_NOCODEC in May10's daily,plz refer to
    http://sof-ci.sh.intel.com/#/result/planresultdetail/3868?model=ADLP_RVP_NOCODEC&testcase=check-capture-3rounds
    will check whether #4089 works ASAP

  5. added this to the v1.8 milestone on May 11, 2021
  6. keyonjie commented on May 12, 2021

    @keyonjie
    Contributor

    looks this is a driver regression, it pass on May 9th daily but failed on May 10th.

  7. XiaoyunWu6666 commented on May 12, 2021

    @XiaoyunWu6666
    ContributorAuthor

    #4089 is effective against this issue. [tested on ubuntu@sh-tglu-rvp-nocodec-02]
    It can fix 3 cases that failed on TGLU_RVP_NOCODEC on May 9th.

  8. lgirdwood commented on May 12, 2021

    @lgirdwood
    Member

    looks this is a driver regression, it pass on May 9th daily but failed on May 10th.

    IPC timeouts are FW crashes.

  9. XiaoyunWu6666 commented on May 13, 2021

    @XiaoyunWu6666
    ContributorAuthor
  10. keyonjie commented on May 13, 2021

    @keyonjie
    Contributor

    looks this is a driver regression, it pass on May 9th daily but failed on May 10th.

    IPC timeouts are FW crashes.

    Yes, maybe FW change on 10th lead to this?
    Anyway, the PR #4089 will fix it.

  11. lgirdwood commented on May 20, 2021

    @lgirdwood
    Member

    @XiaoyunWu6666 is this now fixed with recent kernel updates and on stable-v1.8 branch ?

  12. XiaoyunWu6666 commented on May 21, 2021

    @XiaoyunWu6666
    ContributorAuthor

    @XiaoyunWu6666 is this now fixed with recent kernel updates and on stable-v1.8 branch ?

    Yes , it is

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

    ADLApplies to Alder Lake platformTGLApplies to Tiger LakebugSomething isn't working as expectedmulticoreIssues observed when not only core#0 is used.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions