[Bug 84902] New: [BSW] System fail to enter hibernation with error message after load i915 driver
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Oct 11 01:03:36 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=84902
Bug ID: 84902
Summary: [BSW] System fail to enter hibernation with error
message after load i915 driver
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: wendy.wang at intel.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 107702
--> https://bugs.freedesktop.org/attachment.cgi?id=107702&action=edit
dmesg log file
==System Environment==
--------------------------
Regression: No.
It's first run tests on BSW
Non-working platforms: BSW
==kernel==
--------------------------
origin/drm-intel-nightly:
BOOT_IMAGE=kernels//nightly_parents/2014_10_11/drm-intel-nightly/ea4bec8e96ea8b33b49a7892c1c7f20041a56da6/bzImage_x86_64
root=/dev/sda4 drm.debug=0xe
modules_path=kernels//nightly_parents/2014_10_11/drm-intel-nightly/ea4bec8e96ea8b33b49a7892c1c7f20041a56da6/modules_x86_64/lib/modules/3.17.0_drm-intel-nightly_ea4bec_20141011+
acpi_rsdp=0x7b729014 kexec_jump_back_entry=0x5434a8e8
==Bug detailed description==
-----------------------------
With i915 driver loaded the fail symptom as below:
1. 1st cycle to execute "echo disk > /sys/power/state"
2. test machine will enter S4 successfully, then automatically resume back from
S4.
3. Second time to try "echo disk > /sys/power/state", system will fail to enter
into S4 with dmesge error:"
[ 90.753796] [drm] stuck on blitter ring
[ 90.776392] [drm] GPU HANG: ecode 2:0xfffffffe, reason: Ring hung, action:
reset
[ 90.780688] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 90.785052] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 90.789480] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 90.793974] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 90.798527] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 90.803502] i915 0000:00:02.0: GEM idle failed, resume might fail
[ 90.805296] drm/i915: Resetting chip after gpu hang
[ 90.812746] pci_pm_freeze(): i915_pm_freeze+0x0/0x34 [i915] returns -11
[ 90.817418] dpm_run_callback(): pci_pm_freeze+0x0/0xb5 returns -11
[ 90.822089] call 0000:00:02.0+ returned -11 after 5851154 usecs
[ 90.826773] PM: Device 0000:00:02.0 failed to freeze async: error -11
"
4. Disable i915 driver and system can enter S4 successfully both at the 1st or
2nd cycle.
--
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/20141011/6d0a922b/attachment.html>
More information about the intel-gfx-bugs
mailing list