Bug 92473 - [HSW] kms_flip some sub-tests causes crash
Summary: [HSW] kms_flip some sub-tests causes crash
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Luis Botello
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-15 17:13 UTC by Humberto Israel Perez Rodriguez
Modified: 2017-03-31 22:48 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features: display/DP


Attachments
dmesg.log (124.04 KB, text/plain)
2015-10-15 17:13 UTC, Humberto Israel Perez Rodriguez
no flags Details
GPU_crash_dump_file.log (25 bytes, text/plain)
2015-10-15 17:13 UTC, Humberto Israel Perez Rodriguez
no flags Details
i915_error_state.log (25 bytes, text/plain)
2015-10-15 17:13 UTC, Humberto Israel Perez Rodriguez
no flags Details
Xorg.log (17.61 KB, text/plain)
2015-10-15 17:14 UTC, Humberto Israel Perez Rodriguez
no flags Details
Zip file with latest logs (67.96 KB, text/plain)
2016-01-06 22:04 UTC, Elio
no flags Details
dmesg_low_resolution (249.80 KB, text/plain)
2016-01-06 22:06 UTC, Elio
no flags Details
dmesg_high_resolution_dp.txt (249.97 KB, text/plain)
2016-01-06 22:07 UTC, Elio
no flags Details
xorg log (17.36 KB, text/plain)
2016-01-06 22:07 UTC, Elio
no flags Details

Description Humberto Israel Perez Rodriguez 2015-10-15 17:13:21 UTC
Created attachment 118894 [details]
dmesg.log

Kernel <drm-intel-testing-2015-10-10>


==Bug detailed description==
--------------------------------------------------
kms_flip some sub-tests causes crash

==Attachments==
--------------------------------------------------
dmesg.log
i915_error_state.log
GPU_crash_dump_file.log
Xorg.log


==Steps to reproduce==
--------------------------------------------------
run any of the following sub-tests :

<%blt-flip-vs-panning%>
<%flip-vs-panning%>
<%render-flip-vs-panning%>
<%flip-vs-panning-vs-hang-interruptible%>
<%flip-vs-panning-interruptible%>
<%blt-flip-vs-panning-interruptible%>
<%flip-vs-panning-interruptible%>
<%flip-vs-panning-vs-hang%>

e.g : gem_mmap_gtt --run-subtest flip-vs-panning-vs-hang 


==Actual results==
--------------------------------------------------
the subtests causes crash

==Expected results==
--------------------------------------------------
The subtests must pass


==Hardware configuration==
--------------------------------------------------

-- Platform: --
Processor: Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz
Motherboard : D54250WYK
Memory : 8GB

-- Software --
Linux distribution: Ubuntu 14.04.03 LTS 64Bits
BIOS: 4.6


==Test Environment==
--------------------------------------------------
kernel: 4.3.0-rc4-drm-intel-testing-2015-10-10
xorg-server-1.17.2
libdrm-2.4.65
xf86-video-intel-2.99.917
mesa-11.0.2
libva-1.6.1
intel-driver-1.6.1
cairo-1.14.2
IGT Version : 1.12-g1f9e055

Command output :
----------------------------------------------------
$kms_flip --run-subtest blt-flip-vs-panning
IGT-Version: 1.12-g1f9e055 (x86_64) (Linux: 4.3.0-rc4-drm-intel-testing-2015-10-10-ww41+ x86_64)
Using monotonic timestamps
Beginning blt-flip-vs-panning on crtc 21, connector 32
  3840x2160 30 3840 4016 4104 4400 2160 2168 2178 2250 0x9 0x48 297000
.........
blt-flip-vs-panning on crtc 21, connector 32: PASSED

Beginning blt-flip-vs-panning on crtc 25, connector 32
  3840x2160 30 3840 4016 4104 4400 2160 2168 2178 2250 0x9 0x48 297000
..........
blt-flip-vs-panning on crtc 25, connector 32: PASSED

Beginning blt-flip-vs-panning on crtc 29, connector 32
Received signal SIGBUS.
Subtest blt-flip-vs-panning: CRASH (22.108s)

real    0m22.391s
user    0m0.428s
sys     0m2.004s
Comment 1 Humberto Israel Perez Rodriguez 2015-10-15 17:13:35 UTC
Created attachment 118895 [details]
GPU_crash_dump_file.log
Comment 2 Humberto Israel Perez Rodriguez 2015-10-15 17:13:50 UTC
Created attachment 118896 [details]
i915_error_state.log
Comment 3 Humberto Israel Perez Rodriguez 2015-10-15 17:14:06 UTC
Created attachment 118897 [details]
Xorg.log
Comment 4 Elio 2015-10-16 14:06:55 UTC
Adding more sub-test failing on BYT
kms_flip@2x-blt-wf_vblank-vs-modeset-interruptible
kms_flip@2x-wf_vblank-vs-modeset-interruptible
kms_flip_tiling@flip-to-y-tiled
Comment 5 cprigent 2015-10-19 08:59:20 UTC
BYT environment:
Baytrail-M
Hardware
Platform: Toshiba Satellite C55t
Processor Intel(R) Celeron(R) CPU  N2820  @ 2.13GHz
Software
Linux distribution: Ubuntu 14.04 LTS 64Bits
BIOS: 1.10
kernel: 4.3.0-rc4-drm-intel-testing-2015-10-10
Comment 6 Chris Wilson 2015-10-28 19:05:11 UTC
Note that the attached dmesg.log doesn't correspond with the command output.
Comment 7 cprigent 2015-11-29 09:50:49 UTC
Humberto,
Could check the log attached.
Thanks.
Comment 8 Elio 2016-01-05 22:05:48 UTC
The mentioned test are working without problems
BYT environment:
Baytrail-M
Hardware
Platform: Toshiba Satellite C55t
Processor Intel(R) Celeron(R) CPU  N2820  @ 2.13GHz
Software
Linux distribution: Ubuntu 15.10 LTS 64Bits
BIOS: 1.10
kernel: 4.4.0-rc6-drm-intel-nightly-2015-10-10
commit 0417da5e6f56078d87d366d5f959f8290ae9d16d
IGT= intel-gpu-tools-1.13
Cairo=1.15.2
Intel-Driver= 1.6.2.pre2
xf86= 2.99.917-524-g8e98751
libva=libva-1.6.2.pre3
xorg-server=xorg-server-1.18.0
drm=libdrm-2.4.65
mesa=mesa-11.1.0

Subtests were tested in different ways (from script and test) individually without problem. 

I decide to stress the system running a 100 times cycle over the same test in order to catch the failure but it didn't appear.

Deleting BYT platform from bug header.
Comment 9 Elio 2016-01-06 22:03:17 UTC
The problem is present in HSW platform with following configuration **JUST HAPPENS WITH 4k RESOLUTION*** the test passes with  Lower resolution.
kernel: 4.4.0-rc6-drm-intel-nightly-2015-10-10
commit 0417da5e6f56078d87d366d5f959f8290ae9d16d
IGT= intel-gpu-tools-1.13
Cairo=1.15.2
Intel-Driver= 1.6.2.pre2
xf86= 2.99.917-524-g8e98751
libva=libva-1.6.2.pre3
xorg-server=xorg-server-1.18.0
drm=libdrm-2.4.65
mesa=mesa-11.1.0

Attaching Xorg.logs
Dmesg and Output.log
Comment 10 Elio 2016-01-06 22:04:14 UTC
Created attachment 120840 [details]
Zip file with latest logs
Comment 11 Elio 2016-01-06 22:06:21 UTC
Created attachment 120841 [details]
dmesg_low_resolution
Comment 12 Elio 2016-01-06 22:07:10 UTC
Created attachment 120842 [details]
dmesg_high_resolution_dp.txt
Comment 13 Elio 2016-01-06 22:07:33 UTC
Created attachment 120843 [details]
xorg log
Comment 14 yann 2017-03-17 15:18:58 UTC
(In reply to Elio from comment #13)
> Created attachment 120843 [details]
> xorg log

Elio, Humberto please re-test with latest kernel and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce.
Comment 15 Luis Botello 2017-03-31 22:48:03 UTC
Issue is not seen anymore with the latest config on HSW:

======================================
             Software
======================================
kernel version            : 4.11.0-rc1-drm-tip-qa-ww11-commit-2cb1288+
architecture              : x86_64
os version                : Ubuntu 16.10
os codename               : yakkety
kernel driver             : i915
bios revision             : 4.6

======================================
        Graphic drivers
======================================
modesetting               : modesetting_drv.so
xorg-xserver              : 1.18.4
libdrm                    : 2.4.75
vaapi (intel-driver)      : Intel i965 driver for Intel(R) Haswell Mobile - 1.8.0.pre1 (1.8.0.pre1)
cairo                     : 1.15.4
xserver                   : X.Org X Server 1.19.2
intel-gpu-tools (tag)     : intel-gpu-tools-1.18
intel-gpu-tools (commit)  : bb97a05

======================================
             Hardware
======================================
platform                  : HSW-Nuc
motherboard id            : D54250WYK
form factor               : Desktop
cpu family                : Core i5
cpu information           : Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz
gpu card                  : Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])


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.