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
[BUG] FW status on IPC timeout in test 07_05_TestKdDmicD0ix16000Hz16b16b2ch #4929
I believe this error message actually doesn't impact the KD functionality?
This is for the KPB history buffer allocation, when fails we will retry with smaller size and the request is from LPSRAM where we have 64KB only on TGL. So I think we actually should always see this but the allocation eventually succeed so no impact in functionality. @mrajwa FYI.
Hi @keyonjie
I misled you during bugscrub - it looks like we have another problem here (some timeout). @kkarask is checking that. We will make an update later.
changed the title [-][BUG] ERROR failed to alloc 0x2ea00 bytes zone 0x3 caps 0x8 flags 0x0 in test 07_05_TestKdDmicD0ix16000Hz16b16b2ch[/-][+][BUG] FW status on IPC timeout in test 07_05_TestKdDmicD0ix16000Hz16b16b2ch[/+]on Nov 2, 2021
Exception TimeoutError occurred at 'C:\work\KK\cavs_scripts-py\utilities\ipc_driver.py':603
FW status on IPC timeout after 5.0 seconds:
0x00000005 0x00000000 0x00004000
Looks we are quite lack of KWD coverage in our CI now, check-keyword-detection.sh event can't run on any of our 29 daily models, @keqiaozhang@aiChaoSONG@mengdonglin FYI.
Without that, we don't have this PM_GATE IPC validation at all, need to re-enable that and debug what happens here, with the latest main.
Activity
lgirdwood commentedon Oct 27, 2021
@kkarask can you bisect. There has not been any memory updates this week, but a few weeks back there was some updates merged. @keyonjie fyi.
kkarask commentedon Oct 28, 2021
Bisect done.
Last working commit: 5b4ea83
First bad commit: bec163c
keyonjie commentedon Nov 2, 2021
I believe this error message actually doesn't impact the KD functionality?
This is for the KPB history buffer allocation, when fails we will retry with smaller size and the request is from LPSRAM where we have 64KB only on TGL. So I think we actually should always see this but the allocation eventually succeed so no impact in functionality. @mrajwa FYI.
keyonjie commentedon Nov 2, 2021
BTW @marc-hb the filter feature is very annoying here that it kills useful logs for us:
"Suppressed 19 similar messages: block %d base 0x%x size %d"
marc-hb commentedon Nov 2, 2021
We can discuss turning TRACE_FILTERING_ADAPTIVE off by default as long as that change is:
Even before discussing it, anyone can submit a draft PR that turns it off just to get test results and more verbose logs.
bkokoszx commentedon Nov 2, 2021
Hi @keyonjie
I misled you during bugscrub - it looks like we have another problem here (some timeout). @kkarask is checking that. We will make an update later.
[-][BUG] ERROR failed to alloc 0x2ea00 bytes zone 0x3 caps 0x8 flags 0x0 in test 07_05_TestKdDmicD0ix16000Hz16b16b2ch[/-][+][BUG] FW status on IPC timeout in test 07_05_TestKdDmicD0ix16000Hz16b16b2ch[/+]kkarask commentedon Nov 2, 2021
@keyonjie There is timeout on IPC:
Exception TimeoutError occurred at 'C:\work\KK\cavs_scripts-py\utilities\ipc_driver.py':603
FW status on IPC timeout after 5.0 seconds:
0x00000005 0x00000000 0x00004000
when test passed with working commit there is a response from that IPC:
The error: ERROR failed to alloc 0x2ec00 bytes zone 0x3 caps 0x8 flags 0x0 was not the real reason test failed, so I change the title
marc-hb commentedon Nov 2, 2021
Just to be sure: the bisect result is still the same?
kkarask commentedon Nov 3, 2021
@marc-hb yes, bisect result is still the same with reproduction rate 100%.
lgirdwood commentedon Nov 11, 2021
@keyonjie any update ?
keyonjie commentedon Nov 18, 2021
Looks we are quite lack of KWD coverage in our CI now, check-keyword-detection.sh event can't run on any of our 29 daily models, @keqiaozhang @aiChaoSONG @mengdonglin FYI.
Without that, we don't have this PM_GATE IPC validation at all, need to re-enable that and debug what happens here, with the latest main.
wszypelt commentedon Jan 2, 2023
issue does not occur
Tested FW hash: 4943aaa