-
Notifications
You must be signed in to change notification settings - Fork 59
verify-kernel-kernel-log: skip ADL platforms #786
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
Conversation
Rationale in thesofproject#740 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Having plaforms still under development in PR testing is already a stretch, let's not push it too far. The kernel boot logs should still be availble. This will avoid recurring issues like thesofproject#767, - *ERROR* bcs'0 reset request timed out: {request: 00000001, RESET_CTL: https://sof-ci.01.org/sofpr/PR4777/build10384/devicetest/?model=ADLP_RVP_SDW&testcase=verify-kernel-boot-log - [ 3.262181] kernel: cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) in daily tests, Others in 9ba1215, etc. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
seen at Also spotted: |
|
In https://sof-ci.01.org/softestpr/PR786/build899/devicetest , |
fredoh9
left a comment
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.
Good idea
|
This cpufreq warnings are ADLP new CPU specific errors. I upgraded the new CPU on one ADLP-RVP-SDW(sh-adlp-rvp-sdw-02) and one ADLP-RVP-NOCODEC(sh-adlp-rvp-nocodec-02) yesterday and the warnings started after that. |
|
When I begged to catch all kernel errors and exclude specific ones a couple years ago, many people said "it's not going to work, too many random kernel errors especially with new platforms". We had to exclude many USB and other errors[*] but it mostly worked... except for new platforms indeed like ADL that keep spitting new random errors every time there is a kernel upgrade, or BIOS upgrade, or hardware upgrade, then the error goes away on the next upgrade and is replaced by new one(s). But no one ever cleans up our giant We can remove this SKIP around the time the products are out. Note even with the SKIP the kernel logs are still collected and available. [*] https://github.com/thesofproject/sof-test/issues?q=+label%3A%22area%3Anon-audio+Failure%22+ - 70 issues+PRs |
|
Let's see if we can revert this the next time we have a big kernel "backmerge" |
Maybe one error has gone but here's the first ADL platform and daily run I looked at : 10402?model=ADLP_BRYA_SDW&testcase=verify-kernel-boot-log Start Time: 2022-02-21 22:27:31 UTC Still too much of a mess... What would we get from failing this test all the time? |
2 commits:
You really want to review the commits separately