Summary: | [IVB/HSW/BYT]Some subcases of igt/gem_exec_parse fails | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Guo Jinxian <jinxianx.guo> | ||||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||||
Version: | unspecified | ||||||||||
Hardware: | Other | ||||||||||
OS: | All | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Guo Jinxian
2014-05-08 08:39:10 UTC
Created attachment 98667 [details]
dmesg on fixes branch
This is known to be broken on -fixes. Please only reopen if there are failures with gem_exec_param on byt on -nightly. Created attachment 104602 [details] dmesg (In reply to comment #2) > This is known to be broken on -fixes. Please only reopen if there are > failures with gem_exec_param on byt on -nightly. Test failed on latest -nightly(da31e7c60be217316278a055dd3f91c33913270f) on byt-m root@x-bytm02:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_exec_parse IGT-Version: 1.7-geda904c (x86_64) (Linux: 3.16.0_drm-intel-nightly_da31e7_20140814+ x86_64) Subtest basic-allowed: SUCCESS Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest basic-rejected: FAIL Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest registers: FAIL Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest bitmasks: FAIL Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest batch-without-end: FAIL Subtest cmd-crossing-page: SUCCESS Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest oacontrol-tracking: FAIL This bug is able to reproduce on IVB and HSW platforms. [root@x-ivb9 tests]# ./gem_exec_parse IGT-Version: 1.7-g5c7bcb1 (x86_64) (Linux: 3.16.0_drm-intel-nightly_da31e7_20140814_debug+ x86_64) Subtest basic-allowed: SUCCESS Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest basic-rejected: FAIL Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest registers: FAIL Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest bitmasks: FAIL Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest batch-without-end: FAIL Subtest cmd-crossing-page: SUCCESS Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 == -22 Subtest oacontrol-tracking: FAIL It works well on -nightly kernel. It also happens on -fixes kernel(commit f114040e3ea6e0737) run ./gem_exec_parse --run-subtest registers output: IGT-Version: 1.8-gbba1cd0 (x86_64) (Linux: 3.18.0-rc1_drm-intel-fixes_f11404_20141021_debug+ x86_64) Test assertion failure function exec_batch, file gem_exec_parse.c:135: Failed assertion: __gem_execbuf(fd, &execbuf) == expected_ret error: 0 != -22 Subtest registers: FAIL (0.000s) If it works well on -nightly it was probably fixed already. Feel free to reopen if it still happens. pass on BYT/HSW/IVB with nightly latest baranch: d2a1764437d8b4c30948704ff6c64e4bbfd1df7c(2015-01-20) change state to verified. Closing old verified. |
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.