This looks to be from commit 0f8ede1b8c4cb845c53072d7e49d71ca24a61ced upstream.

Since we build with CONFIG_HIBERNATION, it does the weird WARN thing now.  We'll look into this but I'm not sure there's going to be a great resolution.

Actually, this looks to have been fixed by commit 65fe935dd2387a4faf15314c73f5e6d31ef0217e in the tip tree.  That hasn't quite hit Linus' tree yet, but I suspect it will sometime next week.

(In reply to Josh Boyer from comment #2)
> Actually, this looks to have been fixed by commit
> 65fe935dd2387a4faf15314c73f5e6d31ef0217e in the tip tree.  That hasn't quite
> hit Linus' tree yet, but I suspect it will sometime next week.

Thanks for the update and thanks for looking into it!

This has now showed up in Fedora 24 with 4.7.2-200.fc24.x86_64 update that came through updates testing today.

(In reply to Bill from comment #4)
> This has now showed up in Fedora 24 with 4.7.2-200.fc24.x86_64 update that
> came through updates testing today.

Confirmed, same issue here with this exact same kernel version on F24.

I have not faced it with 4.7.2-200.fc24.x86_64 (installed from updates-testing), but with 4.7.2-201 (installed using koji download-build), this error came up.

I'm using Fedora 24 and after 4.7.2 kernel update this error came up

This isn't a bug or warning per se. The Fedora devs have chosen to build the kernel with CONFIG_HIBERNATION, as noted above. 

We can learn from the LKML, the kernel developers prioritized CONFIG_RANDOMIZE_BASE over CONFIG_HIBERNATION to improve security. The kernel team recommends DISABLING hibernation by default AND passing "nokaslr" on the kernel command line. 

The kernel patch produces the message reported: 

-#ifdef CONFIG_HIBERNATION
-	if (!cmdline_find_option_bool("kaslr")) {
-		debug_putstr("KASLR disabled by default...\n");
-		goto out;

If my understanding is correct, the Fedora devs may want to disable hibernation by default and give users the option of modifying the kernel command line. According to LKML, implementing kASLR will improve security

(In reply to SteveCr48 from comment #8)
> This isn't a bug or warning per se. The Fedora devs have chosen to build the
> kernel with CONFIG_HIBERNATION, as noted above. 
> 
> We can learn from the LKML, the kernel developers prioritized
> CONFIG_RANDOMIZE_BASE over CONFIG_HIBERNATION to improve security. The
> kernel team recommends DISABLING hibernation by default AND passing
> "nokaslr" on the kernel command line. 
> 
> The kernel patch produces the message reported: 
> 
> -#ifdef CONFIG_HIBERNATION
> -	if (!cmdline_find_option_bool("kaslr")) {
> -		debug_putstr("KASLR disabled by default...\n");
> -		goto out;
> 
> If my understanding is correct, the Fedora devs may want to disable
> hibernation by default and give users the option of modifying the kernel
> command line. According to LKML, implementing kASLR will improve security

That's inaccurate.  As I said in comment #2, the issue is fixed.  It is now in Linus' tree but didn't make the 4.7.y kernel.  The options are to wait for 4.8.y or to backport the patch that fixes it.

(In reply to Bill from comment #4)
> This has now showed up in Fedora 24 with 4.7.2-200.fc24.x86_64 update that
> came through updates testing today.

Getting this issue with 4.7.2-201.fc24.x86_64

Also loading the previous kernel versions from grub gets me an error "Oops something went wrong"

Just installed some pending updates this morning which started this issue. Everything was working fine before then.

(In reply to Joseph McMurray from comment #10)
> (In reply to Bill from comment #4)
> > This has now showed up in Fedora 24 with 4.7.2-200.fc24.x86_64 update that
> > came through updates testing today.
> 
> Getting this issue with 4.7.2-201.fc24.x86_64
> 
> Also loading the previous kernel versions from grub gets me an error "Oops
> something went wrong"
> 
> Just installed some pending updates this morning which started this issue.
> Everything was working fine before then.

Disregard the later half of that comment. That is something separate.

Confirmed with 4.7.2-201.fc24.x86_64 on two different laptops

Some information for the F24 users on how this is going to be officially tackled would be nice. As far as I can see, there are at least a couple of options including:

* re-configuring the kernel command line -- is this then being done by updates to the respective packages?

* back-porting the changes from https://patchwork.kernel.org/patch/9199367/ to 4.7.* kernels and building new kernel packages

* leave the choice up to the users, potentially having all their kernels producing warnings at boot time -- should provide some kind of mini-how-to then

Any statements?

Now in Fedora 23 as well.  4.7.2-101.fc23.x86_64 landed on September 04.

This message "kaslr disabled: 'kaslr not on cmdline (hiberation selected)" has appeared after the laptop got a sudden switched of because the battery.
I thought it was because of this, I am using SSD.
I am using F24.
Waiting for a new kernel update.

Same problem on a DELL Optiplex 790 but not on my Dell Optiplex 760, Asus notebook and HP Pavilion x360 II.

For those not using hibernation, adding "nohibernate" to the kernel append line does make the KASLR disabled message go away.

yep! Same problem in Fedora 24(Kernel Version:  4.7.2_201)

kernel-4.7.3-200.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f9d5f8f03f

kernel-4.7.3-100.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-91fb402c7f

I confirm, the message is present on my F23 system after the update to 4.7.2-201.fc23.x86_64

kernel-4.7.3-100.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-91fb402c7f

I confirm this situation in a virtual machine. My machine virtual
is virtualbox for windows (version 5.0.26 r108824 - 64 bit) running
Fedora 23 - 64 bit with kernel 4.7.2-101.fc23.x86_64. After of
message "kaslr disabled: 'kaslr' not on cmdline (hiberation selected)",
the system is frozen and does not allow start Session in my account.

(In reply to Matthias31 from comment #17)
> For those not using hibernation, adding "nohibernate" to the kernel append
> line does make the KASLR disabled message go away.

For me on 4.7.2-101.fc23.x86_64 adding "nohibernate" didn't, but adding "kaslr" did.

kernel-4.7.3-200.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f9d5f8f03f

Installed kernel 4.7.3-200.fc24 from updates testing and I can confirm that the problem is resolved for me,.

kernel-4.7.3-200.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

kernel-4.7.3-100.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

A quick question.  What do ordinary folk do when this has wiped out their Fedora?

My screen flashes for a while trying to start Gnome display manager.

So again.... What do folk that can't access their system do to update so it works?
sent from my iPhone.

(In reply to Ernst from comment #29)
> A quick question.  What do ordinary folk do when this has wiped out their
> Fedora?
> 
> My screen flashes for a while trying to start Gnome display manager.
> 
> So again.... What do folk that can't access their system do to update so it
> works?
> sent from my iPhone.

1. This issue surely didn't wipe out anyone's Fedora.
2. If your system doesn't boot, try to select an older kernel or a rescue kernel on boot.
3. go to a tty (Ctrl+Alt+F3 for example) and try to log in from there. Can you access the syslog (journalctl)? There should be some useful info there.
4. Put your question on ask.fedoraproject.org, the fedora forums or on https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/ . If you know what you're doing, file a bug here on this bugzilla instead.

I'm running Fedora 24 on VirtualBox. I updated my kernel to kernel-4.7.3-200.fc24.x86_64 but the the system still crashes before it can start Gnome. Adding kaslr, nokaslr, or nohibernate doesn't help. The last kernel that works is kernel-4.6.7-300.fc24.x86_64. I can't get a syslog because I can't switch to a TTY after the crash, and after rebooting with the working kernel, the boot syslog gets updated with the successful boot.

This issue is not related to anything than a single print message. If you are having any other issue please open a separate bugzilla.

(In reply to Laura Abbott from comment #32)
> This issue is not related to anything than a single print message. If you
> are having any other issue please open a separate bugzilla.

You're right, sorry about that. I figured it might still be related to this issue based on Comment 29. For what it's worth, the issue I was is fixed by updating Virtual Box and the Guest Additions: http://unix.stackexchange.com/questions/309076/fedora-24-kernel-4-7-2-201-crash-on-boot-once-virtualbox-guest-additions-have