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
System hung when playback failed & copy debugfs to other folder immediately on BYT nocodec. #684
@plbossart
This is a fail log collection method. We would like to copy the logs and debugfs once the test is failed. But during the test we found that the BYT will have system hang if we try to copy something at some fail case.
@xun2z can you also switch on LOCK DEBUGGING with the kernel (use kconfig menuconfig) and wait for 2 minutes after the hang. This option should print out debug statements to the console if we are deadlocked with IRQs OFF.
I tried on the latest commit: ee46ece. This issue is fixed by Ranjani's pr #708. The corresponding commit number is 68bbdac
reverted by 1238f67. The actual fix is 95dea6e
IPC will time out for a while rather than return Invalid argument the 2nd time.
This is fixed. So I think we can close this issue and reopen it when need.
Activity
plbossart commentedon Mar 4, 2019
@xun2z What are you trying to do with the copy of the debugfs folder? What is this test about?
xiulipan commentedon Mar 5, 2019
@plbossart
This is a fail log collection method. We would like to copy the logs and debugfs once the test is failed. But during the test we found that the BYT will have system hang if we try to copy something at some fail case.
plbossart commentedon Mar 19, 2019
Is anyone assigned to look into this? @mengdonglin @wenqingfu this hasn't progressed in 2 weeks.
xun2z commentedon Mar 20, 2019
I tried it on my byt nocodec. Using the linux:95b2fab5, I see the hung whenever the 2nd time I run this command, the 1st is OK.
To get the dmesg, I just use this command. Basically, It works well in fulfilling our origin purpose
aplay -Dhw:0,0 -f s24_le -r 48000 -c 2 /dev/zero; sleep 5 && sudo su -c "timeout 1 cp -rf /sys/kernel/debug/sof /tmp/"So I think we have 2 issues here
lgirdwood commentedon Mar 20, 2019
@xun2z can you also switch on LOCK DEBUGGING with the kernel (use kconfig menuconfig) and wait for 2 minutes after the hang. This option should print out debug statements to the console if we are deadlocked with IRQs OFF.
xun2z commentedon Mar 21, 2019
I tried on the latest commit: ee46ece. This issue is fixed by Ranjani's pr #708.
The corresponding commit number is 68bbdacreverted by 1238f67. The actual fix is 95dea6e
This is fixed. So I think we can close this issue and reopen it when need.
Using the old version, I still cannot return from hang after waiting a few minutes.enabled "Debug Lockups and Hangs", I can return to normal.
dmesg.txt
lockdep.txt
lockdep_chains.txt
lockdep_stats.txt
PM: core: keep irq flags in device_pm_check_callbacks()