Skip to content

[BUG] alsabat test failed with 821Hz on IPC4 nocodec platforms #7285

Closed

Description

@keqiaozhang

Describe the bug
This issue only happened on IPC4 nocodec platform with 821Hz sine wav. From the waveform, there's a glitch and it seems that one sample point is inverted. No such issue with 599 or 997 Hz

image

To Reproduce
~/sof-test/test-case/check-alsabat.sh -p hw:sofnocodec,0 -c hw:sofnocodec,0 -C 2 -F 821

Reproduction Rate
100%

Environment

  1. Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
    • Kernel: tip sof-dev
    • SOF: main
  2. Name of the topology file
    • Topology: sof-tgl-nocodec.tplg sof-adl-nocodec.tplg
  3. Name of the platform(s) on which the bug is observed.
    • Platform: TGL/ADL IPC4 nocodec platforms

Activity

  1. added
    bugSomething isn't working as expected
    TGLApplies to Tiger Lake
    ADLApplies to Alder Lake platform
    IPC4Issues observed with IPC4 (same IPC as Windows)
    on Mar 16, 2023
  2. changed the title [-][BUG] alsabat test failed on IPC4 nocodec platforms[/-] [+][BUG] alsabat test failed with 821Hz on IPC4 nocodec platforms[/+] on Mar 16, 2023
  3. keqiaozhang commented on Mar 16, 2023

    @keqiaozhang
    CollaboratorAuthor

    We have a duplicate, internal issue 379

  4. lgirdwood commented on Mar 17, 2023

    @lgirdwood
    Member

    The sine frequency should make no difference to the result, is the glitch periodic or just random in position/channel ?

  5. added
    I2SApplies to I2S bus for codec connection
    on Mar 20, 2023
  6. keqiaozhang commented on Mar 20, 2023

    @keqiaozhang
    CollaboratorAuthor

    The sine frequency should make no difference to the result, is the glitch periodic or just random in position/channel ?

    Just random in position/channel, no rules.

  7. added
    P1Blocker bugs or important features
    on Mar 21, 2023
  8. lgirdwood commented on Mar 21, 2023

    @lgirdwood
    Member

    @singalsu how can we make the CI testing more clever to reject glitches on the USB testing HW ?

  9. singalsu commented on Mar 23, 2023

    @singalsu
    Collaborator

    @singalsu how can we make the CI testing more clever to reject glitches on the USB testing HW ?

    I'm making a proposal for additional glitch detector with Octave to check the alsabat recording, since alsabat may miss some issues. The test is for measuring presence of a test frequency, not really to find poor audio or glitches. But it will also support ignore of start ramp that can now trigger alsabat. If it works we can relax a bit alsabat and rely more on the additional test.

  10. lrudyX commented on Mar 24, 2023

    @lrudyX

    @keqiaozhang we need IPC logs with payloads to reproduce with FW tests, could you prepare?

  11. juimonen commented on Mar 28, 2023

    @juimonen

    anyone able to replicate this locally? I just can't reproduce in my upx...

  12. keqiaozhang commented on Mar 29, 2023

    @keqiaozhang
    CollaboratorAuthor

    anyone able to replicate this locally? I just can't reproduce in my upx...

    I did a quick check on TGL-UP and ADLP-RVP nocodec devices, it seems that this issue no longer exists on these 2 platforms.

  13. lgirdwood commented on Mar 29, 2023

    @lgirdwood
    Member

    ok, pls close when happy its not in daily test.

  14. keqiaozhang commented on Mar 30, 2023

    @keqiaozhang
    CollaboratorAuthor

    This issue no longer exists in CI, closing this bug.

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

Metadata

Metadata

Assignees

Labels

ADLApplies to Alder Lake platformI2SApplies to I2S bus for codec connectionIPC4Issues observed with IPC4 (same IPC as Windows)P1Blocker bugs or important featuresTGLApplies to Tiger Lakearea:alsa-batbugSomething isn't working as expected

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions