-
Notifications
You must be signed in to change notification settings - Fork 133
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
[FEATURE] driver should limit FW crash reports to single reports #2890
Comments
The SNR isn't going to be fundamentally better if we remove the crash information, the ASoC core will continue doing a lot of error handling and throw repeated IPC errors. You would e.g. still get this as a result
|
Agree ALSA/ASoC will keep sending new IPC but a simple flag is enough to say "FW is dead, lets not keep dumping the same IPC registers and FW stack trace to dmesg" TBH, this is where we should be trying to recover FW and doing a D0 -> D3 -> D0 cycle. |
some day we'll finally work on #1675 |
@plbossart fwiw, I've asked @ujfalusi to look at this log fix and also the FW #1675 when he's waiting on his aux bus review comments. |
@ujfalusi I think this is already implemented? Can we close this? |
@plbossart, I think this can be closed, we keep the dumps at bay now. |
Currently if the FW crashes we get multiple copies of the crash dump in dmesg (i.e. one dump per tried IPC). Kernel should limit this to one dump until next FW boot. i.e. today we have poor dmesg SNR as dmesg can overflow with the same message
The text was updated successfully, but these errors were encountered: