Bug 1047396 - Fedora doesn't power off
Summary: Fedora doesn't power off
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-30 23:07 UTC by dontbother
Modified: 2014-01-06 14:30 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-06 14:30:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
sudo dmidecode > dmidecode.txt (20.39 KB, text/plain)
2014-01-01 23:50 UTC, dontbother 		no flags Details
lspci -vvvv > lspci.txt (15.24 KB, text/plain)
2014-01-01 23:51 UTC, dontbother 		no flags Details
View All

Description dontbother 2013-12-30 23:07:53 UTC 
Description of problem:
Fedora 20 (clean install) sometimes doesn't poweroff.
Logout is done and the computer freezes at filled (blue) Fedora logo.

Version-Release number of selected component (if applicable):
20

How reproducible:
random

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
power off

Additional info:
Comment 1 Michele Baldessari 2014-01-01 18:24:52 UTC 
What machine is this? Can you attach the output of "dmidecode" and "lspci -vvvv" to this BZ please?

What's the kernel version? (output of 'uname -a')

Thanks,
Michele
Comment 2 dontbother 2014-01-01 23:49:58 UTC 
Linux localhost.localdomain 3.12.5-302.fc20.x86_64 #1 SMP Tue Dec 17 20:42:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Comment 3 dontbother 2014-01-01 23:50:47 UTC 
Created attachment 844311 [details]
sudo dmidecode > dmidecode.txt
Comment 4 dontbother 2014-01-01 23:51:22 UTC 
Created attachment 844312 [details]
lspci -vvvv > lspci.txt
Comment 5 Michele Baldessari 2014-01-02 07:12:12 UTC 
Hi,

it's an Asus. This should be fixed with 3.12.6. You can either wait for the
official update to come or take it from updates-testing.

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