Bug 1069418 - Reboot or Shutdown (Power Off) do not work.
Summary: Reboot or Shutdown (Power Off) do not work.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-25 00:57 UTC by sangu
Modified: 2014-02-25 08:43 UTC (History)
11 users (show)

Fixed In Version: 3.13.1-27.fc21.noarch
Clone Of:
Environment:
Last Closed: 2014-02-25 08:43:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Reboot and Shutdown (Power Off) is hang (455.30 KB, image/jpeg)
2014-02-25 00:57 UTC, sangu
no flags Details

Description sangu 2014-02-25 00:57:55 UTC
Created attachment 867216 [details]
Reboot and Shutdown (Power Off) is hang

Description of problem:
( 1 of 3) A stop Job is runnning  for User Manager for 42_
--- Long Term -- ( About 1 Minute?)
(skip)
[OK]...
[OK]...
[OK] Reached target Shutdown.
---
HANG

Version-Release number of selected component (if applicable):
208-14.fc21.x86_64

How reproducible:
always

Steps to Reproduce:
1. Click shutdown or Reboot button in gnome-shell
2.
3.

Actual results:


Expected results:


Additional info:
selinux-policy-3.13.1-26.fc21.noarch
kernel-3.14.0-0.rc3.git0.1.fc21.x86_64

# dmesg | grep systemd
[    0.862463] systemd[1]: systemd 208 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
[    0.862581] systemd[1]: Running in initial RAM disk.
[    0.862607] systemd[1]: Set hostname to <localhost>.
[    0.862910] random: systemd urandom read with 15 bits of entropy available
[    0.890335] systemd[1]: Expecting device dev-disk-by\x2duuid-ef61b88c\x2d32f1\x2d4a48\x2db691\x2d5f0a78d26355.device...
[    0.890367] systemd[1]: Expecting device dev-disk-by\x2duuid-04bf3756\x2dcd2a\x2d4111\x2d882b\x2d6664d33173c7.device...
[    0.890387] systemd[1]: Expecting device dev-disk-by\x2duuid-930f6155\x2d3f71\x2d4a39\x2d8177\x2d573732082a1a.device...
[    0.890405] systemd[1]: Starting -.slice.
[    0.890667] systemd[1]: Created slice -.slice.
[    0.890692] systemd[1]: Starting System Slice.
[    0.890810] systemd[1]: Created slice System Slice.
[    0.890829] systemd[1]: Starting Slices.
[    0.890846] systemd[1]: Reached target Slices.
[    0.890862] systemd[1]: Starting Timers.
[    0.890878] systemd[1]: Reached target Timers.
[    0.890895] systemd[1]: Starting Journal Socket.
[    0.891022] systemd[1]: Listening on Journal Socket.
[    0.891232] systemd[1]: Starting dracut cmdline hook...
[    0.891829] systemd[1]: Starting Journal Service...
[    0.892529] systemd[1]: Started Journal Service.
[    0.904595] systemd-journald[139]: Vacuuming done, freed 0 bytes
[    1.073650] systemd-udevd[245]: starting version 208
[    1.168829] systemd-udevd[251]: renamed network interface eth0 to enp2s0
[    3.129948] systemd-journald[139]: Received SIGTERM
[    3.819934] systemd[1]: Successfully loaded SELinux policy in 207.612ms.
[    3.951280] systemd[1]: RTC configured in localtime, applying delta of 540 minutes to system time.
[    3.998169] systemd[1]: Relabelled /dev and /run in 35.772ms.
[    5.072284] systemd-readahead[385]: Bumped block_nr parameter of 8:0 to 20480. This is a temporary hack and should be removed one day.
[    5.592504] systemd-journald[398]: Vacuuming done, freed 0 bytes
[    6.228649] systemd-udevd[420]: starting version 208
[   14.916217] systemd-journald[398]: Received request to flush runtime journal from PID 1
[   15.233244] systemd-journald[398]: File /var/log/journal/1d6c0776def0448e9f708cb1a1a29af1/system.journal corrupted or uncleanly shut down, renaming and replacing.
[   16.521817] systemd[1]: mcelog.service: control process exited, code=exited status=203
[   16.541781] systemd[1]: Unit mcelog.service entered failed state.

Comment 1 sangu 2014-02-25 06:38:14 UTC
After Updating selinux-policy-3.13.1-27.fc21.noarch, this issue does not happen.


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