Created attachment 107702 [details] 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.
Hello Ville, Does this issue has the same root cause as S4: https://bugs.freedesktop.org/show_bug.cgi?id=84903 Thanks.
Sorry Does this issue has the same root cause as S3 issue: https://bugs.freedesktop.org/show_bug.cgi?id=84903
Verified 2014_11_06 drm-intel-nightly branch kernel: [root@x-bsw01 ~]# cat /proc/cmdline BOOT_IMAGE=kernels//nightly_parents/2014_11_06/drm-intel-nightly/0642a51748ff46a 205cf2a3fc45ba18cc92c9bda/bzImage_x86_64 root=/dev/sda4 hostname=x-bsw01 modules _path=kernels//nightly_parents/2014_11_06/drm-intel-nightly/0642a51748ff46a205cf 2a3fc45ba18cc92c9bda/modules_x86_64/lib/modules/3.18.0-rc3_drm-intel-nightly_064 2a5_20141106+ acpi_rsdp=0x7b71d014 kexec_jump_back_entry=0xe84a9118 S4 issue has been fixed, S4 can successfully enter and resume by press power button, and there is no error message in dmesg, so close this bug as fixed.
Created attachment 109992 [details] s4-fail-dmesg
(In reply to wendy.wang from comment #4) > Created attachment 109992 [details] > s4-fail-dmesg There is no error or backtrace in here. Can you please explain why you reopened this. Also you've confirmed in comment #3 that it works. If it's broken now that's likely a new bug (and a regressions). If that's the case please reset this bug back to verified and open a new bug to track this regression.
Closing old verified.
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.