dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101768] [HSW] [IGT] kms_cursor_legacy@flip-vs-cursor-busy-crc-* produces a GPU hang
Date: Tue, 05 Sep 2017 19:39:45 +0000	[thread overview]
Message-ID: <bug-101768-502-DVBS9GfFyD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101768-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 4152 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101768

--- Comment #2 from Hector Velazquez <hector.franciscox.velazquez.suriano@intel.com> ---
The following tests show new FAIL on HSW 

Tests List:

igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic
igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-legacy


======================================
        Output
======================================

(kms_cursor_legacy:5828) igt-debugfs-DEBUG: CRC mismatch at index 0: 0x87acf6a4
!= 0xcdacf93b
(kms_cursor_legacy:5828) igt-debugfs-CRITICAL: Test assertion failure function
igt_assert_crc_equal, file igt_debugfs.c:325:
(kms_cursor_legacy:5828) igt-debugfs-CRITICAL: Failed assertion: !mismatch
(kms_cursor_legacy:5828) igt-core-INFO: Stack trace:
(kms_cursor_legacy:5828) igt-core-INFO:   #0 [__igt_fail_assert+0x101]
(kms_cursor_legacy:5828) igt-core-INFO:   #1 [igt_assert_crc_equal+0x5d]
(kms_cursor_legacy:5828) igt-core-INFO:   #2 [flip_vs_cursor_busy_crc+0x3d5]
(kms_cursor_legacy:5828) igt-core-INFO:   #3 [__real_main1411+0x12aa]
(kms_cursor_legacy:5828) igt-core-INFO:   #4 [main+0x33]
(kms_cursor_legacy:5828) igt-core-INFO:   #5 [__libc_start_main+0xf1]
(kms_cursor_legacy:5828) igt-core-INFO:   #6 [_start+0x29]
(kms_cursor_legacy:5828) igt-core-INFO:   #7 [<unknown>+0x29]
****  END  ****
Stack trace:
  #0 [__igt_fail_assert+0x101]
  #1 [igt_assert_crc_equal+0x5d]
  #2 [flip_vs_cursor_busy_crc+0x3d5]
  #3 [__real_main1411+0x12aa]
  #4 [main+0x33]
  #5 [__libc_start_main+0xf1]
  #6 [_start+0x29]
  #7 [<unknown>+0x29]
Subtest flip-vs-cursor-busy-crc-atomic: FAIL (9.852s)
(kms_cursor_legacy:5828) igt-core-DEBUG: Exiting with status code 99


This is my configuration:

======================================
        Graphic stack
======================================

Component: drm
    tag: libdrm-2.4.81-52-g05a830d
    commit: 05a830d382382905d87b55af90aa109fb76e4c16

Component: cairo
    tag: 1.15.6-30-gc29db4f
    commit: c29db4f0de52727406a8b62f4da9a382084b5a79

Component: intel-gpu-tools
    tag: intel-gpu-tools-1.19-234-g490b386
    commit: 490b386ae36d393cdea514882a2437c6e964c13f

Component: piglit
    tag: piglit-v1
    commit: dab15137044c34023b1a843e72e781b03b17548b

======================================
             Software
======================================
kernel version              : 4.13.0-drm-tip-ww36-commit-9dd459e+
hostname                    : gfx-desktop
architecture                : x86_64
os version                  : Ubuntu 16.10
os codename                 : yakkety
kernel driver               : i915
bios revision               : 4.6
bios release date           : 03/02/2017
hardware acceleration       : disabled
swap partition              : enabled on (/dev/sda3)

======================================
        Graphic drivers
======================================
libdrm                      : 2.4.83
cairo                       : 1.15.9
intel-gpu-tools (tag)       : intel-gpu-tools-1.19-234-g490b386
intel-gpu-tools (commit)    : 490b386

======================================
             Hardware
======================================
platform                   : Haswell-Nuc
motherboard id             : D54250WYK
form factor                : Desktop
cpu family                 : Core i5
cpu family id              : 6
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])
memory ram                 : 1.83 GB
max memory ram             : 16 GB
cpu thread                 : 4
cpu core                   : 2
cpu model                  : 69
cpu stepping               : 1
socket                     : Socket LGA1150
signature                  : Type 0, Family 6, Model 69, Stepping 1
hard drive                 : 223GiB (240GB)
current cd clock frequency : 450000 kHz
maximum cd clock frequency : 450000 kHz
displays connected         : DP-1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5057 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-09-05 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 16:14 [Bug 101768] [HSW] [IGT] kms_cursor_legacy@flip-vs-cursor-busy-crc-* produces a GPU hang bugzilla-daemon
2017-07-12 16:15 ` bugzilla-daemon
2017-09-05 19:39 ` bugzilla-daemon [this message]
2017-09-05 19:40 ` bugzilla-daemon
2017-09-05 19:41 ` bugzilla-daemon
2017-09-05 19:41 ` bugzilla-daemon
2017-09-19  9:25 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101768-502-DVBS9GfFyD@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox