-
Notifications
You must be signed in to change notification settings - Fork 45
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
Catch firmware errors #1075
Catch firmware errors #1075
Conversation
There are a LOT of ERRORs in stable-v2.2 https://sof-ci.01.org/softestpr/PR1075/build537/devicetest/index.html , about half the tests have some. They all seem to be this timeout:
Should it really be at the ERROR level? In one sample context:
|
cavs25 https://sof-ci.01.org/softestpr/PR1075/build536/devicetest/index.html and MTL https://sof-ci.ostc.intel.com/#/result/planresultdetail/28422 show both the same, Most error messages seem be this timeout
|
New run, same results.
|
This comment was marked as outdated.
This comment was marked as outdated.
test run on 2023-07-18 No change in stable-v2.2 https://sof-ci.01.org/softestpr/PR1075/build629/devicetest/index.html cavs2.5 https://sof-ci.01.org/softestpr/PR1075/build630/devicetest/index.html and in MTL https://sof-ci.01.org/softestpr/PR1075/build631/devicetest/index.html Same errors all around. September 19th, no change in: |
This comment was marked as outdated.
This comment was marked as outdated.
SOFCI TEST |
cavs https://sof-ci.01.org/softestpr/PR1075/build129/devicetest/index.html has some new type of error:
cavs25 https://sof-ci.01.org/softestpr/PR1075/build753/devicetest/index.html is from the old build service and very old (sept 2023) MTL https://sof-ci.01.org/softestpr/PR1075/build128/devicetest/index.html has plenty of FW errors but unfortunately no logs, dunno why. stable-v2.2 has underruns https://sof-ci.01.org/softestpr/PR1075/build130/devicetest/index.html and suspend/resume failures, otherwise mostly OK. |
SOFCI TEST EDIT, now blocked by (among others): |
cavs https://sof-ci.01.org/softestpr/PR1075/build269/devicetest/index.html has the "ignoring blob" errors in NOCODEC and not much else I could find. Same thing with ACE https://sof-ci.01.org/softestpr/PR1075/build270/devicetest/index.html stable-v2.2 https://sof-ci.01.org/softestpr/PR1075/build271/devicetest/index.html seems to have many underruns |
@marc-hb, the underruns looks like to be coming from pause/resume tests only, right? All logs contains that I can see via CI (2023-09-04 is the oldest) |
I think you might be right. The rest in https://sof-ci.01.org/softestpr/PR1075/build269/devicetest/index.html seems to be In any case stable-v2.2 is obviously not the priority. I'd really like to enable this for Zephyr. |
Dropping logs is bad but it should not be fatal in itself. This ERROR is one of the last remaining one, see thesofproject/sof-test#1075 (comment) Signed-off-by: Marc Herbert <marc.herbert@intel.com>
SOFCI TEST EDIT: MTL https://sof-ci.01.org/softestpr/PR1075/build327/devicetest/index.html is 100% green! CAVS https://sof-ci.01.org/softestpr/PR1075/build328/devicetest/index.html has only one device available but it's all green. LNL https://sof-ci.01.org/softestpr/PR1075/build326/devicetest/index.html has one unrelated device PM runtime misconfiguration. stable-v2.2 still has a lot of dtrace dropped logs errors https://sof-ci.01.org/softestpr/PR1075/build325/devicetest/index.html |
Internal Intel issue 448. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
At last. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
4a1e6da
to
2825652
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, let's merge this now
MTL https://sof-ci.01.org/softestpr/PR1075/build331/devicetest/index.html 100% green. stable-v2.2 100% (cause not catching errors yet) https://sof-ci.01.org/softestpr/PR1075/build332/devicetest/index.html LNL has a couple of known issues already listed above CAVS https://sof-ci.01.org/softestpr/PR1075/build330/devicetest/index.html had only one MODEL available but it's all green. |
Dropping logs is bad but it should not be fatal in itself. This ERROR is one of the last remaining one, see thesofproject/sof-test#1075 (comment) Also switch to the "etrace" and stop using the DMA trace when it's already saturated. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Dropping logs is bad but it should not be fatal in itself. This ERROR is one of the last remaining errors in stable-v2.2, see thesofproject/sof-test#1075 (comment) Also switch to the "etrace": drop the dubious recursion and stop using the DMA trace when it's already saturated. Disclaimer: this was (successfully) tested only on stable-v2.2, see Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Dropping logs is bad but it should not be fatal in itself. This ERROR is one of the last remaining errors in stable-v2.2, see thesofproject/sof-test#1075 (comment) Also switch to the "etrace": drop the dubious recursion and stop using the DMA trace when it's already saturated. Disclaimer: this was (successfully) tested only on stable-v2.2, see thesofproject#9036 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Dropping logs is bad but it should not be fatal in itself. This ERROR is one of the last remaining errors in stable-v2.2, see thesofproject/sof-test#1075 (comment) Also switch to the "etrace": drop the dubious recursion and stop using the DMA trace when it's already saturated. Disclaimer: this was (successfully) tested only on stable-v2.2, see #9036 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Dropping logs is bad but it should not be fatal in itself. This ERROR is one of the last remaining errors in stable-v2.2, see thesofproject/sof-test#1075 (comment) Also switch to the "etrace": drop the dubious recursion and stop using the DMA trace when it's already saturated. Disclaimer: this was (successfully) tested only on stable-v2.2, see thesofproject#9036 Signed-off-by: Marc Herbert <marc.herbert@intel.com> (cherry picked from commit bb31696)
Dropping logs is bad but it should not be fatal in itself. This ERROR is one of the last remaining errors in stable-v2.2, see thesofproject/sof-test#1075 (comment) Also switch to the "etrace": drop the dubious recursion and stop using the DMA trace when it's already saturated. Disclaimer: this was (successfully) tested only on stable-v2.2, see #9036 Signed-off-by: Marc Herbert <marc.herbert@intel.com> (cherry picked from commit bb31696)
Dropping logs is bad but it should not be fatal in itself. This ERROR is one of the last remaining errors in stable-v2.2, see thesofproject/sof-test#1075 (comment) Also switch to the "etrace": drop the dubious recursion and stop using the DMA trace when it's already saturated. Disclaimer: this was (successfully) tested only on stable-v2.2, see thesofproject#9036 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Final PR at last.
EDIT: "final" except for stable-v2.2; followup in:
See commit messages.
For a (lot of) context see
... and all the links from there.
cc: