Skip to content

Stress Test: repetitive unloading and reloading driver can cause kernel panic on BYT using nocodec topology #46

Closed

Description

@zhuqingliang

Run soft/kmod_scripts/sof_bootloop.sh that repetitively unloads and reloads driver can cause kernel panic on BYT using nocodec topology.

description:
After 61 cycles ,prompt 'Removing sof_acpi_dev , Killed"
lsmod | grep sof :
sof_acpi_dev 16384 -1
snd_sof_intel_bdw 20480 1 sof_acpi_dev
...
...

System Environment:
sof-v4.14 : 2879223
sof: d696d8f
soft: a25f4b0
using test-ssp2-mclk-0-I2S-volume-s16le-s16le-48k-19200k-nocodec.tplg

reproduce steps:
./sof_bootloop.sh

log:
boot_59.boot.log
boot_60.boot.log
boot_61.boot.log
boot_62.boot.log
rmbox-t.log

Activity

  1. plbossart commented on Aug 8, 2018

    @plbossart
    Member

    Can you clarify why I see this log in the dmesg files:
    [ 210.916884] rt5651 i2c-10EC5651:00: Device with ID register 0xffff8c2d is not rt5651

    This means you are not in nodec mode, you are using the ACPI ID to probe the codec. Or you must use the force-nocodec kconfig?

  2. changed the title [-]Stress Test: run `soft/kmod_scripts/sof_bootloop.sh` cause kernel panic on BYT using nocodec topology[/-] [+]Stress Test: repetitive unloading and reloading driver can cause kernel panic on BYT using nocodec topology[/+] on Sep 11, 2018
  3. changed the title [-]Stress Test: repetitive unloading and reloading driver can cause kernel panic on BYT using nocodec topology[/-] [+]Stress Test: repetitive unloading and reloading driver can cause kernel panic[/+] on Sep 12, 2018
  4. changed the title [-]Stress Test: repetitive unloading and reloading driver can cause kernel panic[/-] [+]Stress Test: repetitive unloading and reloading driver can cause kernel panic on BYT using nocodec topology[/+] on Sep 12, 2018
  5. added
    P3Low-impact bugs or features
    and removed
    P2Critical bugs or normal features
    on Sep 18, 2018
  6. mengdonglin commented on Sep 18, 2018

    @mengdonglin

    Stress test on driver unload/reload is not priority atm.

    @lyakh it seem PR #130 still need to fix some check patch error. Please notify validation here when the PR is merged. Thanks!

  7. 19 remaining items

  8. wenqingfu commented on Mar 20, 2019

    @wenqingfu

    from the last few days' regression report, I think it can conclude it's fixed. Thank you for following up with this bug, @juimonen

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 platformP3Low-impact bugs or featuresbugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions