Bug 64898 - [3.9.3]igt/gem_tiling_max_stride core dumped
Summary: [3.9.3]igt/gem_tiling_max_stride core dumped
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
: 65557 (view as bug list)
Depends on:
Reported: 2013-05-23 08:32 UTC by lu hua
Modified: 2015-05-13 07:28 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Description lu hua 2013-05-23 08:32:32 UTC
System Environment:
Platform:         Pineview/Ironlake/Sandybridge/Ivybridge/Haswell
Kernel: (linux-3.9.y)4bb08696fab71294c8f1c134a21be9159f82ba08

Bug detailed description:
It core dumped on 3.9.3 kernel.
It also happens on 3.8.2 kernel(commit:19b00d2dc9bedf0856e366cb7b9c7733ded659e4)

gem_tiling_max_stride: gem_tiling_max_stride.c:58: do_test_invalid_tiling: Assertion `ret == -1 && (*__errno_location ()) == 22' failed.
Aborted (core dumped)

[   57.687223] [drm:i915_driver_open],
[   57.687236] [drm:intel_crtc_set_config], [CRTC:3] [FB:40] #connectors=1 (x y) (0 0)
[   57.687240] [drm:intel_modeset_stage_output_state], [CONNECTOR:12:HDMI-A-1] to [CRTC:3]
[   57.687242] [drm:intel_crtc_set_config], [CRTC:5] [NOFB]
[   57.687244] [drm:intel_modeset_stage_output_state], [CONNECTOR:12:HDMI-A-1] to [CRTC:3]
[   57.687245] [drm:intel_crtc_set_config], [CRTC:7] [NOFB]
[   57.687246] [drm:intel_modeset_stage_output_state], [CONNECTOR:12:HDMI-A-1] to [CRTC:3]
[   57.687251] [drm:i915_driver_open],
[   57.712782] [drm:intel_crtc_set_config], [CRTC:3] [FB:40] #connectors=1 (x y) (0 0)
[   57.712787] [drm:intel_modeset_stage_output_state], [CONNECTOR:12:HDMI-A-1] to [CRTC:3]
[   57.712789] [drm:intel_crtc_set_config], [CRTC:5] [NOFB]
[   57.712790] [drm:intel_modeset_stage_output_state], [CONNECTOR:12:HDMI-A-1] to [CRTC:3]
[   57.712792] [drm:intel_crtc_set_config], [CRTC:7] [NOFB]
[   57.712793] [drm:intel_modeset_stage_output_state], [CONNECTOR:12:HDMI-A-1] to [CRTC:3]

Reproduce steps:
1. ./gem_tiling_max_stride
Comment 1 Daniel Vetter 2013-05-23 09:00:47 UTC
Can you please test whether backporting

commit fe48d8de34eeaefb2c71dab68ea7c236f06e5877
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Tue Apr 9 20:09:13 2013 +0300

    drm/i915: Reject fence stride=0 on gen4+

fixes the test-failure?
Comment 2 lu hua 2013-05-24 05:54:39 UTC
It works well on drm-intel-fixes and drm-intel-next-queued kernel.
3a062478308187d4b4d0ef546a16e66852d03489 fixed this issue on drm-intel-next-queued branch.
commit 3a062478308187d4b4d0ef546a16e66852d03489
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Tue Apr 9 11:45:05 2013 +0300

    drm/i915: Increase max fence pitch limit to 256KB on IVB+

    BSpec contains several scattered notes which state that the maximum
    fence stride was increased to 256KB on IVB.

    Testing on real hardware agrees.

    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Comment 3 Chris Wilson 2013-05-24 13:28:33 UTC
I don't regard stride==0 failure as a stable candidate, it should just result in corruption and nothing more.
Comment 4 Daniel Vetter 2013-05-24 19:41:26 UTC
Yeah, agreed that do not need to backport the patch. So closing as wontfix (for 3.9 and older at least).
Comment 5 lu hua 2013-06-09 05:20:22 UTC
*** Bug 65557 has been marked as a duplicate of this bug. ***

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.