[Bug 73639] New: [PNV]igt/kms_flip/flip-vs-modeset-vs-hang fails with <3>[ 82.711938] [drm:i915_reset] *ERROR* Reset not implemented, but ignoring error for simulated gpu hangs
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jan 14 18:28:40 PST 2014
https://bugs.freedesktop.org/show_bug.cgi?id=73639
Priority: medium
Bug ID: 73639
CC: intel-gfx-bugs at lists.freedesktop.org
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: [PNV]igt/kms_flip/flip-vs-modeset-vs-hang fails with
<3>[ 82.711938] [drm:i915_reset] *ERROR* Reset not
implemented, but ignoring error for simulated gpu
hangs
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: huax.lu at intel.com
Hardware: All
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
Created attachment 92105
--> https://bugs.freedesktop.org/attachment.cgi?id=92105&action=edit
dmesg
System Environment:
--------------------------
Platform: Pineview
Kernel: (drm-intel-fixes)09f2344d0896eb458a639b922224c7a202c11599
Bug detailed description:
-------------------------
It fails with <3>[ 82.711938] [drm:i915_reset] *ERROR* Reset not implemented,
but ignoring error for simulated gpu hangs. It always fails on Pineview with
-fixes kernel. It doesn't happen on -nightly and -queued kernel.
no error state collected in /sys/class/drm/card0/error
Following cases also have this issue:
igt/kms_flip/flip-vs-modeset-vs-hang-interruptible
igt/kms_flip/flip-vs-panning-vs-hang
igt/kms_flip/flip-vs-panning-vs-hang-interruptible
output:
IGT-Version: 1.5-g1552aa2 (i686) (Linux:
3.13.0-rc7_drm-intel-fixes_09f234_20140114+ i686)
Using monotonic timestamps
Beginning flip-vs-modeset-vs-hang on crtc 4, connector 5
1024x600 60 1024 1048 1184 1438 600 603 604 628 0xa 0x48 54200
........
flip-vs-modeset-vs-hang on crtc 4, connector 5: PASSED
Subtest flip-vs-modeset-vs-hang: SUCCESS
Reproduce steps:
----------------
1. ./kms_flip --run-subtest flip-vs-modeset-vs-hang
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140115/e4947101/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list