[Bug 92435] New: [BSW][Linux]: GPU hang observed during S4 exit
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Oct 12 02:15:09 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=92435
Bug ID: 92435
Summary: [BSW][Linux]: GPU hang observed during S4 exit
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: vijayakannanx.ayyathurai at intel.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: badex.appalanaidu at intel.com, girish.ks at intel.com,
intel-gfx-bugs at lists.freedesktop.org,
raju.rajakumar at intel.com,
vijayakannanx.ayyathurai at intel.com
i915 platform: BSW/CHT
Created attachment 118835
--> https://bugs.freedesktop.org/attachment.cgi?id=118835&action=edit
GPU_hang_dmesg_log
System Environment
==================
Board - Braswell M/D RVP
CPU - BSW D0 stepping CHERRY TRAIL QDF: K6XC
Bios - BSW_SPI_Quad_R12_Config1_Production_BRASWEL_X64_R_X087_00_ME-2.0.1.2087
KSC - 1.08
Software stack:
===============
Kernel - (4.3-rc3) from
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Bug detailed description
========================
GPU hang observed during S4 exit. Drm is the cause for it.
Expected Result
=============
GPU hang should not come during the S4 exit.
Actual Result
===========
GPU hang is observed during S4 exit.
Reproduce Steps:
===============
1. Execute command as root:
echo disk > /sys/power/state
2. Wait for 80 seconds
3. Resume with keyboard/power button
4. Observe the GPU hang in the dmesg.
dmesg cut:
==========
[238772.956521] [drm] stuck on render ring
[238772.956527] [drm] stuck on bsd ring
[238772.956529] [drm] stuck on blitter ring
[238772.956530] [drm] stuck on video enhancement ring
[238772.976029] [drm] GPU HANG: ecode 8:0:0x7ebcfd38, reason: Ring hung,
action: reset
More details in the detailed log in the attachment.
Attachments:
===========
1. log_gpu_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/20151012/822963ce/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list