Bug 88819

Summary: [BSW]igt/gem_persistent_relocs/forked-interruptible-faulting-reloc-thrashing sporadically fails
Product: DRI Reporter: lu hua <huax.lu>
Component: DRM/IntelAssignee: 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: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description lu hua 2015-01-27 03:12:34 UTC 
Created attachment 112870 [details]
dmesg

==System Environment==
--------------------------
Regression:  not sure

no-working platforms: BSW

==kernel==
--------------------------
drm-intel-nightly/67e9eb08a3b967b1ac6b7ec4588a93a2cb030cae
commit 67e9eb08a3b967b1ac6b7ec4588a93a2cb030cae
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Jan 23 17:04:55 2015 +0100

    drm-intel-nightly: 2015y-01m-23d-16h-04m-34s UTC integration manifest

==Bug detailed description==
-----------------------------
It fails on BSW with -nightly kernel. Fail rate: 1/4

output:
IGT-Version: 1.9-gfa94e01 (x86_64) (Linux: 3.19.0-rc5_drm-intel-nightly_67e9eb_20150126+ x86_64)
(gem_persistent_relocs:4363) ioctl-wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ioctl_wrappers.c:437:
(gem_persistent_relocs:4363) ioctl-wrappers-CRITICAL: Failed assertion: ret == 0
(gem_persistent_relocs:4363) ioctl-wrappers-CRITICAL: Last errno: 22, Invalid argument
child 3 died with signal 10, User defined signal 1
Subtest forked-interruptible-faulting-reloc-thrashing: FAIL (2.883s)

==Reproduce steps==
---------------------------- 
1. ./gem_persistent_relocs --run-subtest forked-interruptible-faulting-reloc-thrashing
Comment 1 lu hua 2015-05-28 08:18:53 UTC 
Test on the latest drm-intel-nightly kernel 10 cycles, it works well. Close it.
Comment 2 lu hua 2015-05-28 08:19:08 UTC 
Verified.Fixed.
Comment 3 Elizabeth 2017-10-06 14:31:49 UTC 
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.