Summary: | [BDW]igt/gem_exec_faulting_reloc/{normal,no-prefault} fail | ||||||
---|---|---|---|---|---|---|---|
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: | XOrg git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Guo Jinxian
2013-12-02 05:39:20 UTC
Atm gpu reset doesn't work on bdw. Can you please recheck that the system isn't dead already? Please re-run the test directly after boot-up, without X or anything having run before. execbuf really shouldn't fail like this ... I rechecked on -nightly commit 2a9f23d82a79d2785429aba43b02683abf103c0b, run the test after reboot directly, the system isn't dead indeed (In reply to comment #2) > I rechecked on -nightly commit 2a9f23d82a79d2785429aba43b02683abf103c0b, run > the test after reboot directly, the system isn't dead indeed So even after a fresh boot it fails with the exact same error? The big question is whether it still fails in gem_execbuf. Please retest with latest IGT Retested on latest IGT(commit 8ac7b93b218af1544988331cd68c69ba4102c29f), this bug still failed. [root@x-bdw01 tests]# ./gem_exec_faulting_reloc Test assertion failure function gem_execbuf, file drmtest.c:558: Failed assertion: ret == 0 Subtest normal: FAIL Test assertion failure function gem_execbuf, file drmtest.c:558: Failed assertion: ret == 0 Subtest no-prefault: FAIL Update test result on IGT commit(3c5423b9a74fe056cae1fce41fd3ad16584e9c8d), the test is passed, thanks. [root@x-bdw01 tests]# ./gem_exec_faulting_reloc Subtest normal: SUCCESS Subtest no-prefault: SUCCESS test passed on IGT commit(3c5423b9a74fe056cae1fce41fd3ad16584e9c8d) 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.