Summary: | intel-gpu-tools: kms tests returning TIMEOUT | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Tiago Vignatti <tiago.vignatti> | ||||
Component: | DRM/Intel | Assignee: | Thomas Wood <thomas.wood> | ||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | daniel, intel-gfx-bugs, przanoni, thomas.wood, tiago.vignatti | ||||
Version: | unspecified | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Tiago Vignatti
2014-10-31 21:12:23 UTC
The timeout results are likely to be caused by a problem reading the pipe CRC values that are used in these tests. The skip results are due to subsequent subtests being skipped after a timeout. The CRC timeout issue is fixed in more recent kernel versions. The kms_flip test result may be a different issue. Can you attach gdb to the process and get a backtrace to determine where the process is blocked? Here's where kms_flip is blocking: https://gist.githubusercontent.com/tiagovignatti/4a0073c0cb6744429548/raw/63b8d5cd73c61369bf20425970e7b8b1192d4bec/gistfile1.txt Besides, what kernel version (or commits?) precisely fixed that CRC timeout issue? Thanks for checking Thomas. Created attachment 109228 [details] [review] tests/kms_flip: add a timeout for the nonblocking-read This patch prevents kms_flip/nonblocking-read from blocking indefinitely by introducing a timeout. Please test and confirm whether it fixes the issue with kms_flip. (In reply to Thomas Wood from comment #3) > This patch prevents kms_flip/nonblocking-read from blocking indefinitely by > introducing a timeout. Please test and confirm whether it fixes the issue > with kms_flip. It doesn't fix my real issue, but now at least it's not blocking indefinitely: https://gist.github.com/anonymous/21b75f7709dbec38b4a5 The blocking issue in kms_flip is fixed by commit f6aa80c (tests/kms_flip: add a timeout for the nonblocking-read test) and the issue with the subtests skipping after the a timeout is fixed by commit ebab9f0 (lib: only skip subsequent tests if a timeout occurs outside of a subtest). The causes of both the timeout issues are fixed in more recent kernel versions. Closing resolved+fixed after more than two years. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.