Ask Your Question

Fedora 22 not shutting down after hibernate

asked 2016-04-17 07:51:52 -0500

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

Hello everyone,

I have my fedora 22 installation running for quite some time and the hibernation-feature has been working over many kernel-updates. Since a few weeks, I can not hibernate correctly:

I want to hibernate the PC, it shuts down the current session. The screen goes blank, the second monitor switches off and it splashes something about an IRQ-vector it cannot find.

Then, the screen goes blank again and it remains like this for hours - blank screen, running, not responding to any inputs; it does not shut down the pc as it should.

My options are forcing the shutdown by holding the power-button pressed or pressing the reset-button.

Beside that problem, the resume from that hibernation sometimes works, sometimes does not.

My attempts so far were folling the instructions in the first answer to this post: - probably the same way I configured the hibernation in the first place. I can only guess, the problem is not the resume but the hibernate / shutdown.

Thanks in advance for any help or suggestions!

Edit - this is the log of a hibernate-(pc not shutting down)-(push reset button)-sucessfully resume-sequence (sorry, cannot attach as file, because I need more than 60 points): click me!

edit retag flag offensive close merge delete


Please have a look at your syslog, namely using journalctl -b -1 and scrolling to the end. You might want to paste them here.

genodeftest gravatar imagegenodeftest ( 2016-04-17 10:32:23 -0500 )edit

bump Any suggestions? Here ist a nother journalctl -b -0 -output from the minute, I hibernated this morning and the pc did not shut down:

Thanks in advance again

sponki gravatar imagesponki ( 2016-04-21 11:56:35 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2016-05-15 18:21:21 -0500

sponki gravatar image

Some time passed and my machine was update to kernel 4.4.8-200 in the meantime and luckily, the bug disappeared. Sadly, I can not tell, which update really fixed it, because I did not test it for some weeks.

One interesting thing is now, that my journalctl -b -0-logs read like this:

May 15 03:40:30 NetworkManager[1229]: <info> sleep requested (sleeping: no enabled: yes)

May 15 03:40:30 NetworkManager[1229]: <info> sleeping...

May 15 03:40:30 NetworkManager[1229]: <info> NetworkManager state is now ASLEEP

May 15 03:40:30 systemd[1]: Reached target Sleep.

May 15 03:40:30 systemd[1]: Starting Sleep.

May 15 03:40:30 systemd[1]: Starting Hibernate...

May 15 03:40:30 kernel: PM: Hibernation mode set to 'platform'

May 15 03:40:30 systemd-sleep[3957]: Suspending system...

May 15 10:26:20 kernel: PM: Syncing filesystems ... done.

May 15 10:26:20 kernel: Freezing user space processes ... (elapsed 0.667 seconds) done.

The difference here is, that there is no more fingerprint-authentication-demon starting up, but to be honest, that output is really very messy. Anyway, maybe it helps.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2016-04-17 07:51:52 -0500

Seen: 265 times

Last updated: May 15 '16