Test environment: platform: Broadwell Kernel_version: 3.13.6 Libdrm: (master)libdrm-2.4.52 Mesa: (10.1) mesa-10.1 Xserver: (server-1.15-branch)xorg-server-1.15.0 Xf86_video_intel: (master)2.99.910 Cairo: (master)1.12.6 Libva: 1.3.0.pre1 Libva_intel_driver: 1.3.0.pre1 Description: 1. enter command to hibernate system # echo disk > /sys/power/state 2. There are some error message on screen, and system seems goes to power off after more than 10 seconds. Error message please see attached hibernate_error_msg.jpg 3. Press power button, ther's call trace appear on screen, and cannot enter into OS. Call trace message please see attached resume_error_call_trace1.jpg and resume_error_call_trace2.jpg
Created attachment 96333 [details] shows error message when hibernate
Created attachment 96334 [details] Call trace message when resume
Created attachment 96335 [details] Whole screen of call trace appear
There is some confusion here. The original message says the kernel is 3.13.6. The first screenshot is 3.13.6. The last screenshot shows 3.14.0-rc6. The middle is TBD. Neither of these are the latest drm-intel-nightly. Can you please retest with the latest drm-intel-nightly?
Making the prio lower since hibernate isn't as important as suspend and other power features. FWIW, I cannot get my machine to resume at the moment. Can you confirm this is still a bug for you?
Created attachment 100069 [details] dmesg System unable into S4 on one BDW device. dmesg: St[ 291.611991] PM: Syncing filesystems ... arting Security done. Auditing Service[ 291.700673] Freezing user space processes ... ... S(elapsed 0.001 seconds) tarting Tell Plydone.mouth To Write O ut Runtime Data.[ 291.855087] PM: Preallocating image memory... .. Stdone (allocated 89831 pages) arting Recreate [ 292.095222] PM: Allocated 359324 kbytes in 0.12 seconds (2994.36 MB/s) Volatile Files a[ 292.191487] Freezing remaining freezable tasks ... nd Directories..(elapsed 0.001 seconds) . [ OK done. ] Started Se[ 292.332652] Suspending console(s) (use no_console_suspend to debug) curi And CallTrace on other BDW device, please check the dmesg in attachment.
Can you please try to reproduce with i915 module not loaded?
(In reply to comment #7) > Can you please try to reproduce with i915 module not loaded? Disable i915 module failed: 1. boot the kernel with parameter "i915.modeset=0" 2. lsmod still found i915 was loaded. [root@x-bdw01 ~]# lsmod|grep i915 i915 723492 2 video 11899 1 i915 button 4261 1 i915 drm_kms_helper 27762 1 i915 drm 208656 2 i915,drm_kms_helper 3. Failed to remove module with commands below, and unable to find which module used i915 module. [root@x-bdw01 ~]# rmmod i915 rmmod: ERROR: Module i915 is in use [root@x-bdw01 ~]# modprobe -r i915 modprobe: FATAL: Module i915 is in use.
(In reply to comment #8) > (In reply to comment #7) > > Can you please try to reproduce with i915 module not loaded? > > Disable i915 module failed: > 1. boot the kernel with parameter "i915.modeset=0" > 2. lsmod still found i915 was loaded. > > [root@x-bdw01 ~]# lsmod|grep i915 > i915 723492 2 > video 11899 1 i915 > button 4261 1 i915 > drm_kms_helper 27762 1 i915 > drm 208656 2 i915,drm_kms_helper > > 3. Failed to remove module with commands below, and unable to find which > module used i915 module. > > [root@x-bdw01 ~]# rmmod i915 > rmmod: ERROR: Module i915 is in use > [root@x-bdw01 ~]# modprobe -r i915 > modprobe: FATAL: Module i915 is in use. Remove snd_hda_intel module the remove i915, the module is able to remove. After remove i915 module, the device is able into S4.
Please retest on current drm-intel-nightly.
The test was blocked by bug 82340, the device reboot when resume form S4
Fix for #82340 has landed on -fixes and -nightly. Could you please retest with latest -nightly? Thanks, Rodrigo.
The Calltrace unable to reproduce on latest -nightly(7101d84020f63f1da7e0c5d021cdd6be4d515de5)
Closing Verified+Fixed.
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.