You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Stress Test: repetitive unloading and reloading driver can cause kernel panic on BYT using nocodec topology #46
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
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
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
Activity
plbossart commentedon Aug 8, 2018
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?
[-]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[/+][-]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[/+][-]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[/+]mengdonglin commentedon Sep 18, 2018
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!
19 remaining items
wenqingfu commentedon Mar 20, 2019
from the last few days' regression report, I think it can conclude it's fixed. Thank you for following up with this bug, @juimonen
doc: fix documentation about UIO_MEM_LOGICAL using
drm/kfd: fix a system crash issue during GPU recovery
net: ftgmac100: Fix crash when removing driver
powerpc/stacktrace: Fix spurious "stale" traces in raise_backtrace_ipi()
Merge pull request thesofproject#46 from namjaejeon/cifsd-for-next
kernel/locking: Add context to ww_mutex_trylock()
ipmi: Fix UAF when uninstall ipmi_si and ipmi_msghandler module
selftests/bpf: Avoid skipping certain subtests
sched/debug: Show the registers of 'current' in dump_cpu_task()
perf, hw_breakpoint: Fix use-after-free if perf_event_open() fails
mm/hugetlb: let vma_offset_start() to return start
drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL
team: prevent adding a device which is already a team device lower