Ubuntu desktop hangs occasionally during regular use












3















Ubuntu 16.04 has been hanging on me ~1x per day. This happens when I am in the middle of web browsing or using a desktop application, not when booting. When it does, the mouse pointer will still move freely, but clicking or keystrokes have no effect on my system until I do a hard reboot.



What is the best way for me to debug this?



Here is some information:



selah@selah-Precision-Tower-5810:~$ uname -a
Linux selah-Precision-Tower-5810 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


Also, in case it is relevant, I have a "very big" monitor, a Dell 42" at 3840x2160 resolution.



selah@selah-Precision-Tower-5810:~$ lspci | grep VGA
03:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K2200] (rev a2)




UPDATE:



Following Artyom's advice I found the following message in my error logs:



Apr 27 09:47:25 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Apr 27 09:47:29 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Apr 27 09:47:33 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]


Which has let me to this bug which describes similar behavior:
https://bugs.freedesktop.org/show_bug.cgi?id=93629










share|improve this question

























  • What do you mean 'hang' what comes to mind is a windows 95 computer in a noose.

    – Ubuntu User
    Jan 20 '17 at 21:14











  • I did in fact question whether I should use 'hang' or 'freeze'. After checking this out I chose 'hang'. cyberlink.com/support/faq-content.do?id=14592

    – Selah
    Jan 20 '17 at 21:35






  • 2





    You need Nvidia proprietary drivers for better performance.

    – user589808
    Jan 21 '17 at 0:14











  • Trying this using these instructions: webupd8.org/2016/06/…

    – Selah
    Feb 15 '17 at 17:01











  • Ahhhh nvidea-375 messed up Ubuntu 16.04 real bad!! Lead to much crashing and mysterious blinking. Had to use recovery mode from previous kernel version in order to uninstall.

    – Selah
    Feb 15 '17 at 21:46


















3















Ubuntu 16.04 has been hanging on me ~1x per day. This happens when I am in the middle of web browsing or using a desktop application, not when booting. When it does, the mouse pointer will still move freely, but clicking or keystrokes have no effect on my system until I do a hard reboot.



What is the best way for me to debug this?



Here is some information:



selah@selah-Precision-Tower-5810:~$ uname -a
Linux selah-Precision-Tower-5810 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


Also, in case it is relevant, I have a "very big" monitor, a Dell 42" at 3840x2160 resolution.



selah@selah-Precision-Tower-5810:~$ lspci | grep VGA
03:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K2200] (rev a2)




UPDATE:



Following Artyom's advice I found the following message in my error logs:



Apr 27 09:47:25 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Apr 27 09:47:29 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Apr 27 09:47:33 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]


Which has let me to this bug which describes similar behavior:
https://bugs.freedesktop.org/show_bug.cgi?id=93629










share|improve this question

























  • What do you mean 'hang' what comes to mind is a windows 95 computer in a noose.

    – Ubuntu User
    Jan 20 '17 at 21:14











  • I did in fact question whether I should use 'hang' or 'freeze'. After checking this out I chose 'hang'. cyberlink.com/support/faq-content.do?id=14592

    – Selah
    Jan 20 '17 at 21:35






  • 2





    You need Nvidia proprietary drivers for better performance.

    – user589808
    Jan 21 '17 at 0:14











  • Trying this using these instructions: webupd8.org/2016/06/…

    – Selah
    Feb 15 '17 at 17:01











  • Ahhhh nvidea-375 messed up Ubuntu 16.04 real bad!! Lead to much crashing and mysterious blinking. Had to use recovery mode from previous kernel version in order to uninstall.

    – Selah
    Feb 15 '17 at 21:46
















3












3








3








Ubuntu 16.04 has been hanging on me ~1x per day. This happens when I am in the middle of web browsing or using a desktop application, not when booting. When it does, the mouse pointer will still move freely, but clicking or keystrokes have no effect on my system until I do a hard reboot.



What is the best way for me to debug this?



Here is some information:



selah@selah-Precision-Tower-5810:~$ uname -a
Linux selah-Precision-Tower-5810 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


Also, in case it is relevant, I have a "very big" monitor, a Dell 42" at 3840x2160 resolution.



selah@selah-Precision-Tower-5810:~$ lspci | grep VGA
03:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K2200] (rev a2)




UPDATE:



Following Artyom's advice I found the following message in my error logs:



Apr 27 09:47:25 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Apr 27 09:47:29 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Apr 27 09:47:33 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]


Which has let me to this bug which describes similar behavior:
https://bugs.freedesktop.org/show_bug.cgi?id=93629










share|improve this question
















Ubuntu 16.04 has been hanging on me ~1x per day. This happens when I am in the middle of web browsing or using a desktop application, not when booting. When it does, the mouse pointer will still move freely, but clicking or keystrokes have no effect on my system until I do a hard reboot.



What is the best way for me to debug this?



Here is some information:



selah@selah-Precision-Tower-5810:~$ uname -a
Linux selah-Precision-Tower-5810 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


Also, in case it is relevant, I have a "very big" monitor, a Dell 42" at 3840x2160 resolution.



selah@selah-Precision-Tower-5810:~$ lspci | grep VGA
03:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K2200] (rev a2)




UPDATE:



Following Artyom's advice I found the following message in my error logs:



Apr 27 09:47:25 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Apr 27 09:47:29 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Apr 27 09:47:33 selah-Precision-Tower-5810 kernel: nouveau 0000:03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]


Which has let me to this bug which describes similar behavior:
https://bugs.freedesktop.org/show_bug.cgi?id=93629







16.04 crash video-driver






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 6 at 19:02









kenorb

4,36613953




4,36613953










asked Jan 20 '17 at 21:04









SelahSelah

96511426




96511426













  • What do you mean 'hang' what comes to mind is a windows 95 computer in a noose.

    – Ubuntu User
    Jan 20 '17 at 21:14











  • I did in fact question whether I should use 'hang' or 'freeze'. After checking this out I chose 'hang'. cyberlink.com/support/faq-content.do?id=14592

    – Selah
    Jan 20 '17 at 21:35






  • 2





    You need Nvidia proprietary drivers for better performance.

    – user589808
    Jan 21 '17 at 0:14











  • Trying this using these instructions: webupd8.org/2016/06/…

    – Selah
    Feb 15 '17 at 17:01











  • Ahhhh nvidea-375 messed up Ubuntu 16.04 real bad!! Lead to much crashing and mysterious blinking. Had to use recovery mode from previous kernel version in order to uninstall.

    – Selah
    Feb 15 '17 at 21:46





















  • What do you mean 'hang' what comes to mind is a windows 95 computer in a noose.

    – Ubuntu User
    Jan 20 '17 at 21:14











  • I did in fact question whether I should use 'hang' or 'freeze'. After checking this out I chose 'hang'. cyberlink.com/support/faq-content.do?id=14592

    – Selah
    Jan 20 '17 at 21:35






  • 2





    You need Nvidia proprietary drivers for better performance.

    – user589808
    Jan 21 '17 at 0:14











  • Trying this using these instructions: webupd8.org/2016/06/…

    – Selah
    Feb 15 '17 at 17:01











  • Ahhhh nvidea-375 messed up Ubuntu 16.04 real bad!! Lead to much crashing and mysterious blinking. Had to use recovery mode from previous kernel version in order to uninstall.

    – Selah
    Feb 15 '17 at 21:46



















What do you mean 'hang' what comes to mind is a windows 95 computer in a noose.

– Ubuntu User
Jan 20 '17 at 21:14





What do you mean 'hang' what comes to mind is a windows 95 computer in a noose.

– Ubuntu User
Jan 20 '17 at 21:14













I did in fact question whether I should use 'hang' or 'freeze'. After checking this out I chose 'hang'. cyberlink.com/support/faq-content.do?id=14592

– Selah
Jan 20 '17 at 21:35





I did in fact question whether I should use 'hang' or 'freeze'. After checking this out I chose 'hang'. cyberlink.com/support/faq-content.do?id=14592

– Selah
Jan 20 '17 at 21:35




2




2





You need Nvidia proprietary drivers for better performance.

– user589808
Jan 21 '17 at 0:14





You need Nvidia proprietary drivers for better performance.

– user589808
Jan 21 '17 at 0:14













Trying this using these instructions: webupd8.org/2016/06/…

– Selah
Feb 15 '17 at 17:01





Trying this using these instructions: webupd8.org/2016/06/…

– Selah
Feb 15 '17 at 17:01













Ahhhh nvidea-375 messed up Ubuntu 16.04 real bad!! Lead to much crashing and mysterious blinking. Had to use recovery mode from previous kernel version in order to uninstall.

– Selah
Feb 15 '17 at 21:46







Ahhhh nvidea-375 messed up Ubuntu 16.04 real bad!! Lead to much crashing and mysterious blinking. Had to use recovery mode from previous kernel version in order to uninstall.

– Selah
Feb 15 '17 at 21:46












2 Answers
2






active

oldest

votes


















2





+50









Enable persistent logging



sudo mkdir /var/log/journal


Reboot



Make sure persistent logging is enabled by browsing /var/log/journal and checking if a random named directory exists.



After the incident



List system boots



sudo journalctl --list-boots


Extract the boot with the incident



sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe > /tmp/errorlog


or just



sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe


Inspect the log.






share|improve this answer

































    0














    This is the bug of Nouveau video driver (kernel extension). For details, check the bugs at bugs.freedesktop.org or at GitLab, especially: #93629, #99900 and #100567 (which are related to SCHED_ERROR/CTXSW_TIMEOUT).



    To debug the freeze, you can use Magic SysRq key, for example:





    • Alt-SysRq-9 - Set the console log level to 9 to show more of kernel messages


    • Alt-SysRq-w - Display list of blocked (D state) tasks


    • Alt-SysRq-l - Shows a stack backtrace for all active CPUs.


    • Alt-SysRq-t - Output a list of current tasks and their information to the console


    • Alt-SysRq-p - Output the current registers and flags to the console


    • Alt-SysRq-q - Display all active high-resolution timers and clock sources.


    • Alt-SysRq-m - Output current memory information to the console


    Other things to try during freeze:




    • Reset the nice level of all high-priority and real-time tasks by hitting Alt-SysRq-n.

    • Try changing graphic mode into console by Control-Alt-0 (you can use numbers from 0 to 9).

    • Kill all processes on the current virtual console (can kill X) by hitting Alt-SysRq-k.

    • Perform a system crash (if it is configured) by Alt-SysRq-c.


    If nothing works, you should perform a safe reboot by Alt-SysRq-REISUB, which is:





    • Alt-SysRq-R: UnRaw (take control of keyboard back from X).


    • Alt-SysRq-E: tErminate (send SIGTERM to all processes).


    • Alt-SysRq-I: kIll (send SIGKILL to all processes, forcing them to terminate immediately).


    • Alt-SysRq-S: Sync all mounted filesystems (flush data to disk).


    • Alt-SysRq-U: Unmount (remount all filesystems in read-only mode),


    • Alt-SysRq-B: immediately reBoot the system.



      Note: If above hard reboot combination won't work, the freeze could be caused by defected hardware, not video drivers.




    After reboot, check your kern.log for details, especially call traces generated by above kernel commands. This can help to find the right bug report for it, and find the solution. Check the following kern.log example.



    You can check the latest crash log by:



    journalctl -b -1 # Then hit Shift-G to jump to the end.


    Suggested solution:




    • Upgrade your Ubuntu and kernel to the latest version.

    • If problem repeats, the workaround is to install NVIDIA drivers, which replaces Nouveau video driver.






    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',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      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%2f874307%2fubuntu-desktop-hangs-occasionally-during-regular-use%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      2





      +50









      Enable persistent logging



      sudo mkdir /var/log/journal


      Reboot



      Make sure persistent logging is enabled by browsing /var/log/journal and checking if a random named directory exists.



      After the incident



      List system boots



      sudo journalctl --list-boots


      Extract the boot with the incident



      sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe > /tmp/errorlog


      or just



      sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe


      Inspect the log.






      share|improve this answer






























        2





        +50









        Enable persistent logging



        sudo mkdir /var/log/journal


        Reboot



        Make sure persistent logging is enabled by browsing /var/log/journal and checking if a random named directory exists.



        After the incident



        List system boots



        sudo journalctl --list-boots


        Extract the boot with the incident



        sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe > /tmp/errorlog


        or just



        sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe


        Inspect the log.






        share|improve this answer




























          2





          +50







          2





          +50



          2




          +50





          Enable persistent logging



          sudo mkdir /var/log/journal


          Reboot



          Make sure persistent logging is enabled by browsing /var/log/journal and checking if a random named directory exists.



          After the incident



          List system boots



          sudo journalctl --list-boots


          Extract the boot with the incident



          sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe > /tmp/errorlog


          or just



          sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe


          Inspect the log.






          share|improve this answer















          Enable persistent logging



          sudo mkdir /var/log/journal


          Reboot



          Make sure persistent logging is enabled by browsing /var/log/journal and checking if a random named directory exists.



          After the incident



          List system boots



          sudo journalctl --list-boots


          Extract the boot with the incident



          sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe > /tmp/errorlog


          or just



          sudo journalctl -b caf0524a1d394ce0bdbcff75b94444fe


          Inspect the log.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 6 at 15:30









          Zanna

          50.6k13134241




          50.6k13134241










          answered Feb 15 '17 at 17:42









          ArtyomArtyom

          1,0281724




          1,0281724

























              0














              This is the bug of Nouveau video driver (kernel extension). For details, check the bugs at bugs.freedesktop.org or at GitLab, especially: #93629, #99900 and #100567 (which are related to SCHED_ERROR/CTXSW_TIMEOUT).



              To debug the freeze, you can use Magic SysRq key, for example:





              • Alt-SysRq-9 - Set the console log level to 9 to show more of kernel messages


              • Alt-SysRq-w - Display list of blocked (D state) tasks


              • Alt-SysRq-l - Shows a stack backtrace for all active CPUs.


              • Alt-SysRq-t - Output a list of current tasks and their information to the console


              • Alt-SysRq-p - Output the current registers and flags to the console


              • Alt-SysRq-q - Display all active high-resolution timers and clock sources.


              • Alt-SysRq-m - Output current memory information to the console


              Other things to try during freeze:




              • Reset the nice level of all high-priority and real-time tasks by hitting Alt-SysRq-n.

              • Try changing graphic mode into console by Control-Alt-0 (you can use numbers from 0 to 9).

              • Kill all processes on the current virtual console (can kill X) by hitting Alt-SysRq-k.

              • Perform a system crash (if it is configured) by Alt-SysRq-c.


              If nothing works, you should perform a safe reboot by Alt-SysRq-REISUB, which is:





              • Alt-SysRq-R: UnRaw (take control of keyboard back from X).


              • Alt-SysRq-E: tErminate (send SIGTERM to all processes).


              • Alt-SysRq-I: kIll (send SIGKILL to all processes, forcing them to terminate immediately).


              • Alt-SysRq-S: Sync all mounted filesystems (flush data to disk).


              • Alt-SysRq-U: Unmount (remount all filesystems in read-only mode),


              • Alt-SysRq-B: immediately reBoot the system.



                Note: If above hard reboot combination won't work, the freeze could be caused by defected hardware, not video drivers.




              After reboot, check your kern.log for details, especially call traces generated by above kernel commands. This can help to find the right bug report for it, and find the solution. Check the following kern.log example.



              You can check the latest crash log by:



              journalctl -b -1 # Then hit Shift-G to jump to the end.


              Suggested solution:




              • Upgrade your Ubuntu and kernel to the latest version.

              • If problem repeats, the workaround is to install NVIDIA drivers, which replaces Nouveau video driver.






              share|improve this answer






























                0














                This is the bug of Nouveau video driver (kernel extension). For details, check the bugs at bugs.freedesktop.org or at GitLab, especially: #93629, #99900 and #100567 (which are related to SCHED_ERROR/CTXSW_TIMEOUT).



                To debug the freeze, you can use Magic SysRq key, for example:





                • Alt-SysRq-9 - Set the console log level to 9 to show more of kernel messages


                • Alt-SysRq-w - Display list of blocked (D state) tasks


                • Alt-SysRq-l - Shows a stack backtrace for all active CPUs.


                • Alt-SysRq-t - Output a list of current tasks and their information to the console


                • Alt-SysRq-p - Output the current registers and flags to the console


                • Alt-SysRq-q - Display all active high-resolution timers and clock sources.


                • Alt-SysRq-m - Output current memory information to the console


                Other things to try during freeze:




                • Reset the nice level of all high-priority and real-time tasks by hitting Alt-SysRq-n.

                • Try changing graphic mode into console by Control-Alt-0 (you can use numbers from 0 to 9).

                • Kill all processes on the current virtual console (can kill X) by hitting Alt-SysRq-k.

                • Perform a system crash (if it is configured) by Alt-SysRq-c.


                If nothing works, you should perform a safe reboot by Alt-SysRq-REISUB, which is:





                • Alt-SysRq-R: UnRaw (take control of keyboard back from X).


                • Alt-SysRq-E: tErminate (send SIGTERM to all processes).


                • Alt-SysRq-I: kIll (send SIGKILL to all processes, forcing them to terminate immediately).


                • Alt-SysRq-S: Sync all mounted filesystems (flush data to disk).


                • Alt-SysRq-U: Unmount (remount all filesystems in read-only mode),


                • Alt-SysRq-B: immediately reBoot the system.



                  Note: If above hard reboot combination won't work, the freeze could be caused by defected hardware, not video drivers.




                After reboot, check your kern.log for details, especially call traces generated by above kernel commands. This can help to find the right bug report for it, and find the solution. Check the following kern.log example.



                You can check the latest crash log by:



                journalctl -b -1 # Then hit Shift-G to jump to the end.


                Suggested solution:




                • Upgrade your Ubuntu and kernel to the latest version.

                • If problem repeats, the workaround is to install NVIDIA drivers, which replaces Nouveau video driver.






                share|improve this answer




























                  0












                  0








                  0







                  This is the bug of Nouveau video driver (kernel extension). For details, check the bugs at bugs.freedesktop.org or at GitLab, especially: #93629, #99900 and #100567 (which are related to SCHED_ERROR/CTXSW_TIMEOUT).



                  To debug the freeze, you can use Magic SysRq key, for example:





                  • Alt-SysRq-9 - Set the console log level to 9 to show more of kernel messages


                  • Alt-SysRq-w - Display list of blocked (D state) tasks


                  • Alt-SysRq-l - Shows a stack backtrace for all active CPUs.


                  • Alt-SysRq-t - Output a list of current tasks and their information to the console


                  • Alt-SysRq-p - Output the current registers and flags to the console


                  • Alt-SysRq-q - Display all active high-resolution timers and clock sources.


                  • Alt-SysRq-m - Output current memory information to the console


                  Other things to try during freeze:




                  • Reset the nice level of all high-priority and real-time tasks by hitting Alt-SysRq-n.

                  • Try changing graphic mode into console by Control-Alt-0 (you can use numbers from 0 to 9).

                  • Kill all processes on the current virtual console (can kill X) by hitting Alt-SysRq-k.

                  • Perform a system crash (if it is configured) by Alt-SysRq-c.


                  If nothing works, you should perform a safe reboot by Alt-SysRq-REISUB, which is:





                  • Alt-SysRq-R: UnRaw (take control of keyboard back from X).


                  • Alt-SysRq-E: tErminate (send SIGTERM to all processes).


                  • Alt-SysRq-I: kIll (send SIGKILL to all processes, forcing them to terminate immediately).


                  • Alt-SysRq-S: Sync all mounted filesystems (flush data to disk).


                  • Alt-SysRq-U: Unmount (remount all filesystems in read-only mode),


                  • Alt-SysRq-B: immediately reBoot the system.



                    Note: If above hard reboot combination won't work, the freeze could be caused by defected hardware, not video drivers.




                  After reboot, check your kern.log for details, especially call traces generated by above kernel commands. This can help to find the right bug report for it, and find the solution. Check the following kern.log example.



                  You can check the latest crash log by:



                  journalctl -b -1 # Then hit Shift-G to jump to the end.


                  Suggested solution:




                  • Upgrade your Ubuntu and kernel to the latest version.

                  • If problem repeats, the workaround is to install NVIDIA drivers, which replaces Nouveau video driver.






                  share|improve this answer















                  This is the bug of Nouveau video driver (kernel extension). For details, check the bugs at bugs.freedesktop.org or at GitLab, especially: #93629, #99900 and #100567 (which are related to SCHED_ERROR/CTXSW_TIMEOUT).



                  To debug the freeze, you can use Magic SysRq key, for example:





                  • Alt-SysRq-9 - Set the console log level to 9 to show more of kernel messages


                  • Alt-SysRq-w - Display list of blocked (D state) tasks


                  • Alt-SysRq-l - Shows a stack backtrace for all active CPUs.


                  • Alt-SysRq-t - Output a list of current tasks and their information to the console


                  • Alt-SysRq-p - Output the current registers and flags to the console


                  • Alt-SysRq-q - Display all active high-resolution timers and clock sources.


                  • Alt-SysRq-m - Output current memory information to the console


                  Other things to try during freeze:




                  • Reset the nice level of all high-priority and real-time tasks by hitting Alt-SysRq-n.

                  • Try changing graphic mode into console by Control-Alt-0 (you can use numbers from 0 to 9).

                  • Kill all processes on the current virtual console (can kill X) by hitting Alt-SysRq-k.

                  • Perform a system crash (if it is configured) by Alt-SysRq-c.


                  If nothing works, you should perform a safe reboot by Alt-SysRq-REISUB, which is:





                  • Alt-SysRq-R: UnRaw (take control of keyboard back from X).


                  • Alt-SysRq-E: tErminate (send SIGTERM to all processes).


                  • Alt-SysRq-I: kIll (send SIGKILL to all processes, forcing them to terminate immediately).


                  • Alt-SysRq-S: Sync all mounted filesystems (flush data to disk).


                  • Alt-SysRq-U: Unmount (remount all filesystems in read-only mode),


                  • Alt-SysRq-B: immediately reBoot the system.



                    Note: If above hard reboot combination won't work, the freeze could be caused by defected hardware, not video drivers.




                  After reboot, check your kern.log for details, especially call traces generated by above kernel commands. This can help to find the right bug report for it, and find the solution. Check the following kern.log example.



                  You can check the latest crash log by:



                  journalctl -b -1 # Then hit Shift-G to jump to the end.


                  Suggested solution:




                  • Upgrade your Ubuntu and kernel to the latest version.

                  • If problem repeats, the workaround is to install NVIDIA drivers, which replaces Nouveau video driver.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Jan 13 at 19:54

























                  answered Jan 6 at 18:39









                  kenorbkenorb

                  4,36613953




                  4,36613953






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f874307%2fubuntu-desktop-hangs-occasionally-during-regular-use%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Quarter-circle Tiles

                      build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

                      Mont Emei