System Environment: -------------------------- Kernel: (drm-intel-fixes)a65851af59387146a28a928c3e7bb17dabc5db72 Bug detailed description: ----------------------------- It aborted on pineview,ironlake,sandybridge,ivybridge and haswell. It happens on drm-intel-fixes and drm-intel-next-queued kernel.It is new case for I-G-T. igt/prime_self_import/with_one_bo also aborted. output: prime_self_import: prime_self_import.c:75: check_bo: Assertion `memcmp(ptr1, ptr2, (16*1024)) == 0' failed. Aborted (core dumped) dmesg: [ 116.978664] [drm:i915_driver_open], [ 116.978679] [drm:intel_crtc_set_config], [CRTC:3] [FB:30] #connectors=1 (x y) (0 0) [ 116.978684] [drm:intel_modeset_stage_output_state], [CONNECTOR:18:HDMI-A-3] to [CRTC:3] [ 116.978686] [drm:intel_crtc_set_config], [CRTC:5] [NOFB] [ 116.978688] [drm:intel_modeset_stage_output_state], [CONNECTOR:18:HDMI-A-3] to [CRTC:3] [ 116.978694] [drm:i915_driver_open], [ 116.978699] [drm:i915_driver_open], [ 116.978704] [drm:i915_driver_open], [ 117.000724] [drm:intel_crtc_set_config], [CRTC:3] [FB:30] #connectors=1 (x y) (0 0) [ 117.000730] [drm:intel_modeset_stage_output_state], [CONNECTOR:18:HDMI-A-3] to [CRTC:3] [ 117.000733] [drm:intel_crtc_set_config], [CRTC:5] [NOFB] [ 117.000735] [drm:intel_modeset_stage_output_state], [CONNECTOR:18:HDMI-A-3] to [CRTC:3] Reproduce steps: ---------------------------- 1. ./prime_self_import --run-subtest with_two_bos
Dave Airlie merged the prime refcount fixes into drm-next, which is now included in drm-intel-nightly. Note that dinq/drm-intel-fixes does not yet have the patches, since it's a drm upstream issue.
(In reply to comment #1) > Dave Airlie merged the prime refcount fixes into drm-next, which is now > included in drm-intel-nightly. Note that dinq/drm-intel-fixes does not yet > have the patches, since it's a drm upstream issue. I tested latest nightly kernel, this case worked very well, I verified here.
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.