Created attachment 127824 [details] dmesg.log Bug description ======================================= Fedora 32bits kernel 4.8.4-200.fc24.i686+PAE is not able to resume from hibernate, after send the platform to S4 / hibernate looks like that the platforms is not able to enter to S4 because the post code remains in "0004" and never shutdown completly how does it happen in Fedora 64bits Note : this bug does not appears in Fedora 64bit with kernel 4.5.5-300-fc24.x86_64 Steps to reproduce ======================================= 1. Install Fedora 24 32bits 2. Go to hibernate with either of the following commands : # rtcwake -s 60 -m disk # echo disk > /sys/power/state 3. if you try with the second command try to wake up the platform pushing any key / if you try with the first command wait 60 seconds Expected behavior ======================================= The platforms must resume from S4 / hibernate Actual result ======================================= After the step 3 the platform does not resume from S4 / hibernate Software configuration ============================================ Linux OS : Fedora 32Bit Kernel version : 4.8.4-200.fc24.i686+PAE Bios revision : 144.10 Bios release date : 06/27/2016 KSC revision : 1.15 Hardware information ============================================ Platform : BXT-P Motherboard model : BroxtonP Motherboard type : NOTEBOOK Hand Held Motherboard manufacturer : IntelCorp. CPU family : Other CPU information : 06/5c GPU Card : Intel Corporation Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Integrated Graphics Controller (rev 0a) (prog-if 00 [VGA controller]) Memory ram : 8 GB Maximum memory ram allowed : 16 GB CPU thread : 4 CPU core : 4 Attachments =========================================== dmesg.log, which containg the log when the platforms try to enter to S4 state Additional information =========================================== in order to send the platform to S3 (suspend) / S4 (hibernate) you have to enable it in the grub in the following way : 1. $ dmesg | grep -i "swap on" # to know where is your swap partition example : /dev/mapper/fedora-swap 2. add the following parameter in the file /etc/default/grub resume=/dev/mapper/fedora-swap add it at the end of the line : GRUB_CMDLINE_LINUX= 3. update the grub : grub2-mkconfig -o /boot/grub2/grub.cfg this a common issue in Fedora, for more detail information please read the following article : https://fedoraproject.org/wiki/Common_F24_bugs#Hibernation_doesn.27t_work_from_a_standard_install Please correct me if i am placing this issue in the wrong component, thanks i915_error_state = no error state collected cat /sys/class/drm/card0/error = no error state collected
This issue is also seen on Ubuntu 32 bits an all the platforms, with the following config: Software information ============================================ Kernel version : 4.8.0-27-generic Linux distribution : Ubuntu 16.10 Architecture : 64-bit Kernel driver in use : i915 Bios revision : 144.10 Bios release date : 06/27/2016 KSC revision : 1.6
the issue still occurs with the following configuration on SKL ====================================== Software ====================================== kernel version : 4.8.0-34-generic architecture : x86_64 os version : Ubuntu 16.10 os codename : yakkety kernel driver : i915 bios revision : 5.6 bios release date : 09/29/2016 ====================================== Graphic drivers ====================================== mesa : 12.0.3 xorg-xserver : 1.18.4 libva : 1.7.3-2 vaapi (intel-driver) : 1.7.3 intel-gpu-tools : 1.16-1 xserver-xorg-video-intel :2:2.99.917-git20160706
Hi, Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org. To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default). Sorry about the noise!
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.