How to debug hibernate-wakeup problem in 17.10?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












In 17.04, hibernate worked good. Now since 17.10 the PC does not come up after hibernation. Something starts, but the screens stays black and the keyboard lights do not go on. /var/log/syslog is empty for that time, nothing is logged. Suspend works.
How can I further debug this to find out what it could be?



(PC with Asus mainboard and Intel i7 CPU, Ubuntu 17.10, kernel 4.13.0-37)










share|improve this question

























    up vote
    0
    down vote

    favorite












    In 17.04, hibernate worked good. Now since 17.10 the PC does not come up after hibernation. Something starts, but the screens stays black and the keyboard lights do not go on. /var/log/syslog is empty for that time, nothing is logged. Suspend works.
    How can I further debug this to find out what it could be?



    (PC with Asus mainboard and Intel i7 CPU, Ubuntu 17.10, kernel 4.13.0-37)










    share|improve this question























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      In 17.04, hibernate worked good. Now since 17.10 the PC does not come up after hibernation. Something starts, but the screens stays black and the keyboard lights do not go on. /var/log/syslog is empty for that time, nothing is logged. Suspend works.
      How can I further debug this to find out what it could be?



      (PC with Asus mainboard and Intel i7 CPU, Ubuntu 17.10, kernel 4.13.0-37)










      share|improve this question













      In 17.04, hibernate worked good. Now since 17.10 the PC does not come up after hibernation. Something starts, but the screens stays black and the keyboard lights do not go on. /var/log/syslog is empty for that time, nothing is logged. Suspend works.
      How can I further debug this to find out what it could be?



      (PC with Asus mainboard and Intel i7 CPU, Ubuntu 17.10, kernel 4.13.0-37)







      hibernate wakeup






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 17 at 17:19









      jms

      464515




      464515




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          1
          down vote













          After installing kernel 4.16.0-041600rc5-generic it worked.



          I went to http://kernel.ubuntu.com/~kernel-ppa/mainline/
          and changed into the directory v4.16-rc5/.
          From there I downloaded



          linux-headers-4.16.0-041600rc5_4.16.0-041600rc5.201803112130_all.deb
          linux-headers-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb
          linux-image-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb


          and did



          sudo dpkg -i linux-*





          share|improve this answer






















          • I updated the answer
            – jms
            Mar 17 at 20:47










          • Last two steps would be rm linux-* and reboot.
            – WinEunuuchs2Unix
            Mar 20 at 17:48

















          up vote
          0
          down vote













          All of this works well for me for hibernating to file, thanks for the instructions! In my case I also had to get the latest stable kernel for hibernate to file to work, i.e. Ubuntu 17.10 and a dell xps 9370, I had to upgrade the kernel to 4.16.0rc



          Note that if hibernating to file, you still have to do the whole filefrag stuff to copy the physical_offset to the etc/default/grub file,e.g. GRUB_CMD_LINUX_DEFAULT="quiet splash resume=swap_file_deb_partition resume_offset=physical_offset_as_filefrag_says" and then do not forget to run sudo update-grup and reboot for changes to take effect!






          share|improve this answer




















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "89"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1016797%2fhow-to-debug-hibernate-wakeup-problem-in-17-10%23new-answer', 'question_page');

            );

            Post as a guest






























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote













            After installing kernel 4.16.0-041600rc5-generic it worked.



            I went to http://kernel.ubuntu.com/~kernel-ppa/mainline/
            and changed into the directory v4.16-rc5/.
            From there I downloaded



            linux-headers-4.16.0-041600rc5_4.16.0-041600rc5.201803112130_all.deb
            linux-headers-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb
            linux-image-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb


            and did



            sudo dpkg -i linux-*





            share|improve this answer






















            • I updated the answer
              – jms
              Mar 17 at 20:47










            • Last two steps would be rm linux-* and reboot.
              – WinEunuuchs2Unix
              Mar 20 at 17:48














            up vote
            1
            down vote













            After installing kernel 4.16.0-041600rc5-generic it worked.



            I went to http://kernel.ubuntu.com/~kernel-ppa/mainline/
            and changed into the directory v4.16-rc5/.
            From there I downloaded



            linux-headers-4.16.0-041600rc5_4.16.0-041600rc5.201803112130_all.deb
            linux-headers-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb
            linux-image-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb


            and did



            sudo dpkg -i linux-*





            share|improve this answer






















            • I updated the answer
              – jms
              Mar 17 at 20:47










            • Last two steps would be rm linux-* and reboot.
              – WinEunuuchs2Unix
              Mar 20 at 17:48












            up vote
            1
            down vote










            up vote
            1
            down vote









            After installing kernel 4.16.0-041600rc5-generic it worked.



            I went to http://kernel.ubuntu.com/~kernel-ppa/mainline/
            and changed into the directory v4.16-rc5/.
            From there I downloaded



            linux-headers-4.16.0-041600rc5_4.16.0-041600rc5.201803112130_all.deb
            linux-headers-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb
            linux-image-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb


            and did



            sudo dpkg -i linux-*





            share|improve this answer














            After installing kernel 4.16.0-041600rc5-generic it worked.



            I went to http://kernel.ubuntu.com/~kernel-ppa/mainline/
            and changed into the directory v4.16-rc5/.
            From there I downloaded



            linux-headers-4.16.0-041600rc5_4.16.0-041600rc5.201803112130_all.deb
            linux-headers-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb
            linux-image-4.16.0-041600rc5-generic_4.16.0-041600rc5.201803112130_amd64.deb


            and did



            sudo dpkg -i linux-*






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Mar 17 at 20:48









            Zanna

            48.1k13120228




            48.1k13120228










            answered Mar 17 at 17:24









            jms

            464515




            464515











            • I updated the answer
              – jms
              Mar 17 at 20:47










            • Last two steps would be rm linux-* and reboot.
              – WinEunuuchs2Unix
              Mar 20 at 17:48
















            • I updated the answer
              – jms
              Mar 17 at 20:47










            • Last two steps would be rm linux-* and reboot.
              – WinEunuuchs2Unix
              Mar 20 at 17:48















            I updated the answer
            – jms
            Mar 17 at 20:47




            I updated the answer
            – jms
            Mar 17 at 20:47












            Last two steps would be rm linux-* and reboot.
            – WinEunuuchs2Unix
            Mar 20 at 17:48




            Last two steps would be rm linux-* and reboot.
            – WinEunuuchs2Unix
            Mar 20 at 17:48












            up vote
            0
            down vote













            All of this works well for me for hibernating to file, thanks for the instructions! In my case I also had to get the latest stable kernel for hibernate to file to work, i.e. Ubuntu 17.10 and a dell xps 9370, I had to upgrade the kernel to 4.16.0rc



            Note that if hibernating to file, you still have to do the whole filefrag stuff to copy the physical_offset to the etc/default/grub file,e.g. GRUB_CMD_LINUX_DEFAULT="quiet splash resume=swap_file_deb_partition resume_offset=physical_offset_as_filefrag_says" and then do not forget to run sudo update-grup and reboot for changes to take effect!






            share|improve this answer
























              up vote
              0
              down vote













              All of this works well for me for hibernating to file, thanks for the instructions! In my case I also had to get the latest stable kernel for hibernate to file to work, i.e. Ubuntu 17.10 and a dell xps 9370, I had to upgrade the kernel to 4.16.0rc



              Note that if hibernating to file, you still have to do the whole filefrag stuff to copy the physical_offset to the etc/default/grub file,e.g. GRUB_CMD_LINUX_DEFAULT="quiet splash resume=swap_file_deb_partition resume_offset=physical_offset_as_filefrag_says" and then do not forget to run sudo update-grup and reboot for changes to take effect!






              share|improve this answer






















                up vote
                0
                down vote










                up vote
                0
                down vote









                All of this works well for me for hibernating to file, thanks for the instructions! In my case I also had to get the latest stable kernel for hibernate to file to work, i.e. Ubuntu 17.10 and a dell xps 9370, I had to upgrade the kernel to 4.16.0rc



                Note that if hibernating to file, you still have to do the whole filefrag stuff to copy the physical_offset to the etc/default/grub file,e.g. GRUB_CMD_LINUX_DEFAULT="quiet splash resume=swap_file_deb_partition resume_offset=physical_offset_as_filefrag_says" and then do not forget to run sudo update-grup and reboot for changes to take effect!






                share|improve this answer












                All of this works well for me for hibernating to file, thanks for the instructions! In my case I also had to get the latest stable kernel for hibernate to file to work, i.e. Ubuntu 17.10 and a dell xps 9370, I had to upgrade the kernel to 4.16.0rc



                Note that if hibernating to file, you still have to do the whole filefrag stuff to copy the physical_offset to the etc/default/grub file,e.g. GRUB_CMD_LINUX_DEFAULT="quiet splash resume=swap_file_deb_partition resume_offset=physical_offset_as_filefrag_says" and then do not forget to run sudo update-grup and reboot for changes to take effect!







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 20 at 11:13









                user2003706

                1




                1



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1016797%2fhow-to-debug-hibernate-wakeup-problem-in-17-10%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    GRUB: Fatal! inconsistent data read from (0x84) 0+xxxxxx

                    What makes Checkinstall packages not suitable for distribution?

                    Running the scala interactive shell from the command line