Bug 1213216 - Failure to turn off / suspend or hibernate computer
Summary: Failure to turn off / suspend or hibernate computer
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-20 04:27 UTC by Bastián Díaz
Modified: 2018-10-17 18:38 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
lshw output (32.07 KB, text/plain)
2015-04-20 04:27 UTC, Bastián Díaz
no flags Details

Description Bastián Díaz 2015-04-20 04:27:42 UTC
Created attachment 1016208 [details]
lshw output

Description of problem:
This seems to be a common problem in new equipment. I understand that hibernation and to a lesser extent the suspension malfunction, but the equipment off is a basic functionality.
Also I have noticed that the laptop does not respond well to power settings: No screen dims after a period of inactivity, the screen brightness responds slowly and the screen takes a few seconds off after resume.

Version-Release number of selected component (if applicable):
-Gnome 3.16.1
-Fedora 22 (rawhide)
-Acer Aspire E11 | ES1-111M-C6NR
-Laptop with support UEFI used in legacy mode / Touchpad in basic mode from bios setup.
-Kernel: Linux 4.0.0-1.fc22.i686

How reproducible:
Always

Steps to Reproduce:
1.Select the menu system
2.Select Off / suspension

Actual results:
The computer closes applications and shows the logo (fedora), then maintained well without doing anything else. Unfortunately there are to force shutdown.

Expected results:
The computer off smoothly.
The computer is suspended and resumed smoothly.

Note: It really is very complex choose the components to report an error. Please, if I have erred address the problem to the right place. Thank you.

Comment 1 Michael Proto 2015-04-23 15:47:35 UTC
I can confirm this under the x86_64 architecture as well.

Version-Release number of selected component (if applicable):
-XFCE 4.12
-Fedora 22 beta, XFCE spin
-Acer Aspire E11 | ES1-111M-C40S
-UEFI BIOS in legacy mode
-Kernel: Linux 4.0.0-0.rc5.git4.1.fc22.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Select the menu system
2.Select Off  or Reboot

Actual results:
Selecting shutdown or reboot leads to a brief display of the fedora logo then a blank screen and hard-freeze where the only option is to hold the power button for 5 seconds.

Expected results:
System powers-off or reboots successfully.

Comment 2 prateek.1.kohli 2015-06-06 08:53:25 UTC
I am facing exactly this same issue.

Comment 3 Neil 2015-06-28 05:37:52 UTC
Same issue 
-Fedora 22
-Cinnamon 2.6.7
-Bios: Insyde F.66
-kernel-4.0.5-300.fc22.x86_64

Comment 4 Neil 2015-07-02 22:07:50 UTC
(In reply to Bastián Díaz from comment #0)
> Note: It really is very complex choose the components to report an error.
> Please, if I have erred address the problem to the right place. Thank you.

I don't think is a kernel bug, even if it is, we should look if dracut is doing alright since dracut is in charge of turning off the system.

Comment 5 Michael Proto 2015-07-31 16:02:07 UTC
I have some additional information on this. The freeze seems to happen at the very last part of shutdown, after the root filesystem is unmounted. When following https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_troubleshooting if I set "rd.break=pre-shutdown rd.break=shutdown" I can get to and utilize both the pre-shutdown and shutdown shells just fine before the freeze. It is only after I exit the shutdown dracut shell that it freezes. Further there are only 2 additional lines on screen before the freeze after exiting the shutdown dracut shell:

[  188.323327] kvm: exiting hardware virtualization
[  188.824993] r8169 0000:03:00.0: System wakeup enabled by ACPI

Comment 6 Bastián Díaz 2015-08-26 19:20:29 UTC
Note: This is a specific bug related "legacy bios".

I installed more RAM to my computer (8GB), and then reinstall Fedora 22 64bit with UEFI boot.

Surprisingly, all previously detected bugs are not presented with this configuration. (the computer shuts down, suspend, hibernate and restart correctly).

I recommend it to other users who have this problem, use the 64bit version of fedora with UEFI boot.

Note: If you have an Acer computer and after installing fedora, the message "No bootable device" appears, you must rename the "fedora" folder to "Windows Boot Manager" (/boot/efi partition).
With this, the partition will be recognized by the system and boot properly.

Thanks


Note You need to log in before you can comment on or make changes to this bug.