Skip to content
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

kmod-load-unload fails to recognise an underlying kernel error #473

Closed
lyakh opened this issue Oct 26, 2020 · 4 comments
Closed

kmod-load-unload fails to recognise an underlying kernel error #473

lyakh opened this issue Oct 26, 2020 · 4 comments
Labels
state:ping-for-close Will be closed if submitter is not responsive type:bug Something doesn't work as expected

Comments

@lyakh
Copy link
Contributor

lyakh commented Oct 26, 2020

As described in thesofproject/linux#2535 a kmod-load-unload test failed with "dsp is not suspended after 15s" and it failed to identify the underlying kernel error.

@aiChaoSONG
Copy link

@lyakh before starting test, we will wait DSP to suspend, if you see the dsp is not suspended after 15s, that means we have issues.
Previous error may cause the DSP keeps alive.

@lyakh
Copy link
Contributor Author

lyakh commented Nov 2, 2020

@aiChaoSONG exactly, an IPC timeout causes

sof-audio-pci 0000:00:1f.3: error: ipc timed out for 0x40010000 size 76
sof-audio-pci 0000:00:1f.3: info: preventing DSP entering D3 state to preserve context

I understand that, but I think, that that should be identified and printed by test scripts. Usually our test scripts do grep dmesg for error messages, so it would be trivial for them and more useful for developers to see the actual error instead of just a timeout entering suspend

@lyakh lyakh added the type:bug Something doesn't work as expected label Nov 10, 2020
@mengdonglin mengdonglin added the state:ping-for-close Will be closed if submitter is not responsive label Jan 27, 2021
@marc-hb
Copy link
Collaborator

marc-hb commented Jan 27, 2021

@lyakh can you still reproduce this? There's been a number of changes in sof-test since you filed it.
Also appreciate if you can provide detailed reproduction steps.

Is the problem the lack of kernel log check? Just to make sure we understand each other.

@mengdonglin
Copy link
Contributor

mengdonglin commented Apr 14, 2021

Close as no response for a long time, assuming this issue cannot be reproduced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:ping-for-close Will be closed if submitter is not responsive type:bug Something doesn't work as expected
Projects
None yet
Development

No branches or pull requests

5 participants