Skip to content

Firmware boot failure after unloading and reloading driver #124

Closed

Description

@ZhendanYang

Summary:
run the "soft/kmod_scripts/sof_bootone.sh" script, that means do the module reload one time, but boot failed on APL, BYT and CNL.

Environment:
kernel: sof-dev 64cf3e3

Log on APL:
boot_fail.log

Activity

  1. added
    bugSomething isn't working
    P1Blocker bugs or important features
    on Sep 11, 2018
  2. changed the title [-]Firmware unload and reload failed on APL, BYT and CNL[/-] [+]Firmware boot failure after unloading and reloading driver[/+] on Sep 12, 2018
  3. added
    BYTApplies to Baytrail platform
    APLApplies to ApolloLake platform
    CNLApplies to Cannonlake
    on Sep 12, 2018
  4. mengdonglin commented on Sep 13, 2018

    @mengdonglin

    @lyakh could you help to check this issue?

  5. removed
    APLApplies to ApolloLake platform
    CNLApplies to Cannonlake
    on Sep 18, 2018
  6. lyakh commented on Sep 20, 2018

    @lyakh
    Collaborator

    @ZhendanYang could you please point out where in the attached log the failure is seeing? Also, on which specific platforms / test boards and with which topology configurations has it been possible to reproduce this?

  7. lgirdwood commented on Sep 20, 2018

    @lgirdwood
    Member

    @lyakh Looks like an earlier PM failure is breaking things.

    [  264.573413] sof-audio sof-audio: tplg: complete pipeline PIPELINE.1.SSP0.OUT id 5
    [  264.573422] sof-audio sof-audio: ipc tx: 0x30130000
    [  264.573471] sof-audio sof-audio: ipc tx succeeded: 0x30130000
    [  264.573494] sof-audio sof-audio: error: failed to enter PM idle -11
    [  264.573571] sof-nocodec sof-nocodec: snd-soc-dummy-dai <-> SSP0 Pin mapping ok
    [  264.573588] sof-nocodec sof-nocodec: snd-soc-dummy-dai <-> SSP1 Pin mapping ok
    
  8. 5 remaining items

  9. removed
    P1Blocker bugs or important features
    on Oct 10, 2018
  10. mengdonglin commented on Dec 11, 2018

    @mengdonglin

    @stevyan @markyang Could you help to check if this issue is gone with fixing of #144 by #311?

  11. markyang commented on Dec 12, 2018

    @markyang

    Summary:
    This issue cannot be reproduced on BYT with ALC5651 using the build on Dec 7.
    There is no Kernel Panic, both arecord and aplay worked fine.

    Test steps:
    kmod_scripts/sof_bootone.sh
    arecord -Dhw:0,0 -c2 -fS16_LE -vv -i ~/mytest.wav #OK
    aplay -Dhw:0,0 -c2 -fS16_LE -vv -i ~/mytest.wav #OK

    Test env:
    sof master: b5d6c71 #Dec 7
    kernel sof-dev: a71221d #Dec 7
    tplg: test-ssp2-mclk-0-I2S-volume-s16le-s16le-48k-19200k-codec.tplg

  12. added a commit that references this issue on May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BYTApplies to Baytrail platformP2Critical bugs or normal featuresbugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions