-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG][Multi-core] MTL RVP hangs when core1 & core2 are used simultaneously #7705
Comments
Same on main branch? |
@RanderWang checked this today with our validation and we have good results when core1 & core2 are used simultaneously. |
Thanks! As you know, driver doesn't touch core1 & core2, which are maintained by FW. SOC team is checking the scan dump. I will share you the finding |
@abonislawski We got the reply from SOC team and you are in the loop. Do you have any idea ? Thanks! |
the scandump show DSP0 and DSP2 are issuing exclusive read to L2SRAM address 0x400ED940. however the transaction is not seen at fabric-to-L2SRAM interface. question: are these valid program counter: DSP0 = 0x4006 600C, DSP2 = 0x400E CE82 |
@RanderWang it looks fine. To see exactly what's under it we need to check files from this fw build. |
@abonislawski yes, the address is for log_buffer for this scan dump. I disable log but make no effect on 005 branch. I tested main branch last week, but to my surprise this bug doesn't happen on latest main branch ! |
@abonislawski Can you give education about "program counter: DSP0 = 0x4006 600C, DSP2 = 0x400E CE82". As I know dsp address is based on 0xa0002000, why it is 0x400xxxxx? Thanks! |
0xAxxxxx is cached alias |
@abonislawski no issue on latest main branch. The issue was fixed or workaround by e2d0d1
This is proved that our SOC team reported that DSP0 and DSP2 are issuing exclusive read to L2SRAM address 0x400ED940 (log_buffer). |
|
@nashif the problem is not on the FW side, please assign the right person to issue |
Fixed with latest zephyr version, @RanderWang can you check? |
fixed |
Describe the bug
MTL RVP hangs when core1 & core2 are used simultaneously. We need to rescue the MTL RVP by cold boot.
To Reproduce
Do two streams playback on core1 & core2
Reproduction Rate
100%
Environment
We created internal bug 15013565662 and ask for help from SOC team
The text was updated successfully, but these errors were encountered: