Reboot after hibernate failed to restore to previous session.

[John Schmitt]

Using maxcpus=1 in your grub command line is an ugly work-around, I agree.

However, if your machine is waking up from sleep or hibernate, using
maxcpus=1 on your grub command line is going to apply only until your
frozen system image (that is, the image of your running kernel that was
running on all CPUs) is loaded and run.  That is my understanding of the
mechanism.  The bug appears to be in the process of unfreezing your system
image with multiple processors.


On Tue, Apr 14, 2015 at 12:39 PM, Heinz Diehl <htd+ml at fritha.org> wrote:

> On 14.04.2015, jd1008 wrote:
>
> > So, use maxcpus=1 during first boot and 2nd boot?
>
> The machine is a quadcore XEON, reducing it to a single-core is not really
> something I want.
>
> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20150414/9bc088ba/attachment.html>