After most recent kernel update (4.15.0-44-generic) my tablet freezes whenever plugged into docking station












29















I performed the most recent kernel update on my Dell 5290 2-in-1 earlier today. But moments after I plug it into its docking station, the screen flickers, blanks and freezes. The only item left on the screen is the mouse pointer, and it is stuck.



If I leave the tablet not plugged in, it runs just fine. It seems to be the docking station that triggers the freeze.



That said, I can log into the tablet via ssh even with the screen frozen. So the system is still running. But if I try to reboot the tablet via the reboot command, nothing appears to happen. sudo reboot -f will reboot the system, while sudo reboot will not.



Any ideas where I should start looking to identify this problem?










share|improve this question




















  • 1





    What happens if you hold Shift while booting and within GRUB select the old kernel from before you updated?

    – Kristopher Ives
    Jan 29 at 8:41






  • 3





    It took me a while, but I finally got it to boot to 4.15.0-43-generic. This kernel is not freezing. I'll run it all night to be sure, but it's survived much longer than 4.15.0-44-generic has ever lasted on my tablet.

    – Ryan Budney
    Jan 29 at 8:49













  • I've escalated the question to a bug report: bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795

    – Ryan Budney
    Jan 29 at 16:44











  • Although it's possibly unrelated, I've been having problems with my desktop computer and this new kernel, as well. Getting strange wifi cut-outs. It's telling me my printer isn't accepting jobs. And it's starting to refuse basic file operations -- getting errors with the copy operation.

    – Ryan Budney
    Jan 29 at 20:34
















29















I performed the most recent kernel update on my Dell 5290 2-in-1 earlier today. But moments after I plug it into its docking station, the screen flickers, blanks and freezes. The only item left on the screen is the mouse pointer, and it is stuck.



If I leave the tablet not plugged in, it runs just fine. It seems to be the docking station that triggers the freeze.



That said, I can log into the tablet via ssh even with the screen frozen. So the system is still running. But if I try to reboot the tablet via the reboot command, nothing appears to happen. sudo reboot -f will reboot the system, while sudo reboot will not.



Any ideas where I should start looking to identify this problem?










share|improve this question




















  • 1





    What happens if you hold Shift while booting and within GRUB select the old kernel from before you updated?

    – Kristopher Ives
    Jan 29 at 8:41






  • 3





    It took me a while, but I finally got it to boot to 4.15.0-43-generic. This kernel is not freezing. I'll run it all night to be sure, but it's survived much longer than 4.15.0-44-generic has ever lasted on my tablet.

    – Ryan Budney
    Jan 29 at 8:49













  • I've escalated the question to a bug report: bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795

    – Ryan Budney
    Jan 29 at 16:44











  • Although it's possibly unrelated, I've been having problems with my desktop computer and this new kernel, as well. Getting strange wifi cut-outs. It's telling me my printer isn't accepting jobs. And it's starting to refuse basic file operations -- getting errors with the copy operation.

    – Ryan Budney
    Jan 29 at 20:34














29












29








29


8






I performed the most recent kernel update on my Dell 5290 2-in-1 earlier today. But moments after I plug it into its docking station, the screen flickers, blanks and freezes. The only item left on the screen is the mouse pointer, and it is stuck.



If I leave the tablet not plugged in, it runs just fine. It seems to be the docking station that triggers the freeze.



That said, I can log into the tablet via ssh even with the screen frozen. So the system is still running. But if I try to reboot the tablet via the reboot command, nothing appears to happen. sudo reboot -f will reboot the system, while sudo reboot will not.



Any ideas where I should start looking to identify this problem?










share|improve this question
















I performed the most recent kernel update on my Dell 5290 2-in-1 earlier today. But moments after I plug it into its docking station, the screen flickers, blanks and freezes. The only item left on the screen is the mouse pointer, and it is stuck.



If I leave the tablet not plugged in, it runs just fine. It seems to be the docking station that triggers the freeze.



That said, I can log into the tablet via ssh even with the screen frozen. So the system is still running. But if I try to reboot the tablet via the reboot command, nothing appears to happen. sudo reboot -f will reboot the system, while sudo reboot will not.



Any ideas where I should start looking to identify this problem?







18.04 kernel dell tablet charging






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 11 at 17:02









Zanna

51.2k13139242




51.2k13139242










asked Jan 29 at 7:42









Ryan BudneyRyan Budney

294412




294412








  • 1





    What happens if you hold Shift while booting and within GRUB select the old kernel from before you updated?

    – Kristopher Ives
    Jan 29 at 8:41






  • 3





    It took me a while, but I finally got it to boot to 4.15.0-43-generic. This kernel is not freezing. I'll run it all night to be sure, but it's survived much longer than 4.15.0-44-generic has ever lasted on my tablet.

    – Ryan Budney
    Jan 29 at 8:49













  • I've escalated the question to a bug report: bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795

    – Ryan Budney
    Jan 29 at 16:44











  • Although it's possibly unrelated, I've been having problems with my desktop computer and this new kernel, as well. Getting strange wifi cut-outs. It's telling me my printer isn't accepting jobs. And it's starting to refuse basic file operations -- getting errors with the copy operation.

    – Ryan Budney
    Jan 29 at 20:34














  • 1





    What happens if you hold Shift while booting and within GRUB select the old kernel from before you updated?

    – Kristopher Ives
    Jan 29 at 8:41






  • 3





    It took me a while, but I finally got it to boot to 4.15.0-43-generic. This kernel is not freezing. I'll run it all night to be sure, but it's survived much longer than 4.15.0-44-generic has ever lasted on my tablet.

    – Ryan Budney
    Jan 29 at 8:49













  • I've escalated the question to a bug report: bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795

    – Ryan Budney
    Jan 29 at 16:44











  • Although it's possibly unrelated, I've been having problems with my desktop computer and this new kernel, as well. Getting strange wifi cut-outs. It's telling me my printer isn't accepting jobs. And it's starting to refuse basic file operations -- getting errors with the copy operation.

    – Ryan Budney
    Jan 29 at 20:34








1




1





What happens if you hold Shift while booting and within GRUB select the old kernel from before you updated?

– Kristopher Ives
Jan 29 at 8:41





What happens if you hold Shift while booting and within GRUB select the old kernel from before you updated?

– Kristopher Ives
Jan 29 at 8:41




3




3





It took me a while, but I finally got it to boot to 4.15.0-43-generic. This kernel is not freezing. I'll run it all night to be sure, but it's survived much longer than 4.15.0-44-generic has ever lasted on my tablet.

– Ryan Budney
Jan 29 at 8:49







It took me a while, but I finally got it to boot to 4.15.0-43-generic. This kernel is not freezing. I'll run it all night to be sure, but it's survived much longer than 4.15.0-44-generic has ever lasted on my tablet.

– Ryan Budney
Jan 29 at 8:49















I've escalated the question to a bug report: bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795

– Ryan Budney
Jan 29 at 16:44





I've escalated the question to a bug report: bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795

– Ryan Budney
Jan 29 at 16:44













Although it's possibly unrelated, I've been having problems with my desktop computer and this new kernel, as well. Getting strange wifi cut-outs. It's telling me my printer isn't accepting jobs. And it's starting to refuse basic file operations -- getting errors with the copy operation.

– Ryan Budney
Jan 29 at 20:34





Although it's possibly unrelated, I've been having problems with my desktop computer and this new kernel, as well. Getting strange wifi cut-outs. It's telling me my printer isn't accepting jobs. And it's starting to refuse basic file operations -- getting errors with the copy operation.

– Ryan Budney
Jan 29 at 20:34










3 Answers
3






active

oldest

votes


















5














This problem has been solved in 4.15.0-45-generic. Running these commands can fix the issue:



sudo apt-get update
sudo apt-get dist-upgrade





share|improve this answer


























  • I still have this problem with kernel version is 4.15.0-46-generic on ubuntu 16.04 Link to my question is: askubuntu.com/questions/1125107/…

    – kalmanIsAGameChanger
    Mar 19 at 14:58



















15














Same story here, using a XPS 15 99560 and a TB16 dock.



The only solution found for now is to revert to 4.15.0-43, using the Advanced boot options in GRUB.



Link to the kernel changelog. Link to the launchpad discussion where you can follow the evolution.



EDIT : fixed in 4.15.0-45



* External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"





share|improve this answer





















  • 1





    I confirm GRUB -> Advanced options -> booting with kernel 4.15.0.-43 got things back to work as before.

    – Gondy
    Jan 30 at 14:38





















2














This kinda happens also to me, with my Surface Pro 3, when I boot it attached to the docking station.



I can boot the device, but as soon as I log in, I get a kernel bug NULL pointer deference error. Which turns the display black and locks up all input. Network is still working though.



If I boot the device and login without docking station, it works. I can attach the docking station afterwards.



I've reported my issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813796






share|improve this answer






















    protected by Thomas Ward Jan 29 at 20:08



    Thank you for your interest in this question.
    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



    Would you like to answer one of these unanswered questions instead?














    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    5














    This problem has been solved in 4.15.0-45-generic. Running these commands can fix the issue:



    sudo apt-get update
    sudo apt-get dist-upgrade





    share|improve this answer


























    • I still have this problem with kernel version is 4.15.0-46-generic on ubuntu 16.04 Link to my question is: askubuntu.com/questions/1125107/…

      – kalmanIsAGameChanger
      Mar 19 at 14:58
















    5














    This problem has been solved in 4.15.0-45-generic. Running these commands can fix the issue:



    sudo apt-get update
    sudo apt-get dist-upgrade





    share|improve this answer


























    • I still have this problem with kernel version is 4.15.0-46-generic on ubuntu 16.04 Link to my question is: askubuntu.com/questions/1125107/…

      – kalmanIsAGameChanger
      Mar 19 at 14:58














    5












    5








    5







    This problem has been solved in 4.15.0-45-generic. Running these commands can fix the issue:



    sudo apt-get update
    sudo apt-get dist-upgrade





    share|improve this answer















    This problem has been solved in 4.15.0-45-generic. Running these commands can fix the issue:



    sudo apt-get update
    sudo apt-get dist-upgrade






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Feb 11 at 17:03









    Zanna

    51.2k13139242




    51.2k13139242










    answered Feb 4 at 7:46









    HuseyinHuseyin

    4871925




    4871925













    • I still have this problem with kernel version is 4.15.0-46-generic on ubuntu 16.04 Link to my question is: askubuntu.com/questions/1125107/…

      – kalmanIsAGameChanger
      Mar 19 at 14:58



















    • I still have this problem with kernel version is 4.15.0-46-generic on ubuntu 16.04 Link to my question is: askubuntu.com/questions/1125107/…

      – kalmanIsAGameChanger
      Mar 19 at 14:58

















    I still have this problem with kernel version is 4.15.0-46-generic on ubuntu 16.04 Link to my question is: askubuntu.com/questions/1125107/…

    – kalmanIsAGameChanger
    Mar 19 at 14:58





    I still have this problem with kernel version is 4.15.0-46-generic on ubuntu 16.04 Link to my question is: askubuntu.com/questions/1125107/…

    – kalmanIsAGameChanger
    Mar 19 at 14:58













    15














    Same story here, using a XPS 15 99560 and a TB16 dock.



    The only solution found for now is to revert to 4.15.0-43, using the Advanced boot options in GRUB.



    Link to the kernel changelog. Link to the launchpad discussion where you can follow the evolution.



    EDIT : fixed in 4.15.0-45



    * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
    - SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"





    share|improve this answer





















    • 1





      I confirm GRUB -> Advanced options -> booting with kernel 4.15.0.-43 got things back to work as before.

      – Gondy
      Jan 30 at 14:38


















    15














    Same story here, using a XPS 15 99560 and a TB16 dock.



    The only solution found for now is to revert to 4.15.0-43, using the Advanced boot options in GRUB.



    Link to the kernel changelog. Link to the launchpad discussion where you can follow the evolution.



    EDIT : fixed in 4.15.0-45



    * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
    - SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"





    share|improve this answer





















    • 1





      I confirm GRUB -> Advanced options -> booting with kernel 4.15.0.-43 got things back to work as before.

      – Gondy
      Jan 30 at 14:38
















    15












    15








    15







    Same story here, using a XPS 15 99560 and a TB16 dock.



    The only solution found for now is to revert to 4.15.0-43, using the Advanced boot options in GRUB.



    Link to the kernel changelog. Link to the launchpad discussion where you can follow the evolution.



    EDIT : fixed in 4.15.0-45



    * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
    - SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"





    share|improve this answer















    Same story here, using a XPS 15 99560 and a TB16 dock.



    The only solution found for now is to revert to 4.15.0-43, using the Advanced boot options in GRUB.



    Link to the kernel changelog. Link to the launchpad discussion where you can follow the evolution.



    EDIT : fixed in 4.15.0-45



    * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
    - SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 12 at 17:14

























    answered Jan 29 at 10:45









    KriegalexKriegalex

    25616




    25616








    • 1





      I confirm GRUB -> Advanced options -> booting with kernel 4.15.0.-43 got things back to work as before.

      – Gondy
      Jan 30 at 14:38
















    • 1





      I confirm GRUB -> Advanced options -> booting with kernel 4.15.0.-43 got things back to work as before.

      – Gondy
      Jan 30 at 14:38










    1




    1





    I confirm GRUB -> Advanced options -> booting with kernel 4.15.0.-43 got things back to work as before.

    – Gondy
    Jan 30 at 14:38







    I confirm GRUB -> Advanced options -> booting with kernel 4.15.0.-43 got things back to work as before.

    – Gondy
    Jan 30 at 14:38













    2














    This kinda happens also to me, with my Surface Pro 3, when I boot it attached to the docking station.



    I can boot the device, but as soon as I log in, I get a kernel bug NULL pointer deference error. Which turns the display black and locks up all input. Network is still working though.



    If I boot the device and login without docking station, it works. I can attach the docking station afterwards.



    I've reported my issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813796






    share|improve this answer




























      2














      This kinda happens also to me, with my Surface Pro 3, when I boot it attached to the docking station.



      I can boot the device, but as soon as I log in, I get a kernel bug NULL pointer deference error. Which turns the display black and locks up all input. Network is still working though.



      If I boot the device and login without docking station, it works. I can attach the docking station afterwards.



      I've reported my issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813796






      share|improve this answer


























        2












        2








        2







        This kinda happens also to me, with my Surface Pro 3, when I boot it attached to the docking station.



        I can boot the device, but as soon as I log in, I get a kernel bug NULL pointer deference error. Which turns the display black and locks up all input. Network is still working though.



        If I boot the device and login without docking station, it works. I can attach the docking station afterwards.



        I've reported my issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813796






        share|improve this answer













        This kinda happens also to me, with my Surface Pro 3, when I boot it attached to the docking station.



        I can boot the device, but as soon as I log in, I get a kernel bug NULL pointer deference error. Which turns the display black and locks up all input. Network is still working though.



        If I boot the device and login without docking station, it works. I can attach the docking station afterwards.



        I've reported my issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813796







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 29 at 16:50









        CorbenCorben

        263




        263

















            protected by Thomas Ward Jan 29 at 20:08



            Thank you for your interest in this question.
            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



            Would you like to answer one of these unanswered questions instead?



            Popular posts from this blog

            MongoDB - Not Authorized To Execute Command

            How to fix TextFormField cause rebuild widget in Flutter

            in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith