After upgrading my kernel to 5.2.1, I have problems shutting down or rebooting the system. The distro is Gentoo, with 64-bit Linux 5.2.1 and systemd-241-r4 and the card is 1050 Ti with 4GB of VRAM. I’m using KDE plasma with sddm as the graphical login manager. The system works fine inside plasma, but when I click on reboot or shut down, X is killed, the initial virtual console 1 is displayed (it shows the systemd messages upon booting), but the screen is frozen. I cannot Ctrl+Alt+F2 (or other console) and Ctrl+Alt+Del does nothing. The system is not locked up, since I can ping it from another PC. It might shutdown eventually, but it will take several minutes. I had to use the SysRq key to reboot the system a couple of itmes.
The previous 5.1.16 kernel worked fine with the same drivers (tried both 430.26 and 430.34). It seems that the nvidia drivers is the source of the problem, since I logged inside a virtual console, killed X, unloaded all nvidia(_drm, _modeset) modules and issued a shutdown command, which worked instantly.
I can provide more details if needed or send the output from nvidia-bug-report.
I somehow thought he workds for Nvidia. No luck I guess, is any Nvidia developer watching these forum threads…?
The system is not frozen or locked up. If I choose to logout instead of shutdown, you can ssh to it normally. It’s just that the first screen console (the modeset screen) is stuck there and pressing Ctrl+Alt+F does nothing. If I wait long enough (eg. 3-4 minutes), the system will shut down (or logoff) eventually.
I had to revert back to 5.1.18, since this is rather annoying.
A kernel regression/bug/new internal behavior/new behavior in regard to your HW configuration - in this case bisect will help, though it’s an arduous task.
Some other package you’ve updated in the meantime you’ve totally forgotten about
Some reconfiguration of your userspace (systemd, login manager, kernel systemctl parameters, etc.)
A compiler issue (this happens quite rarely) or weird compilation flags (e.g. Gentoo users love to over-optimize their kernels by using some experimental compilation flags)
Something else entirely.
Considering you’re the only one with this issue so far, you’re on your own.
I’d recommend using off-the-shelf distros which come with precompiled components - a lot fewer chances of hitting the issues like your. At least if you hit them, there’ll be other users who could chime in and help debug the problem.
I have the same problem, my system is Arch Linux with the following packages
My system has
Intel I7 9700k
Gigabyte Z390 Aorus Elite
Nvidia 2070 RTX (ROG Strix)
In my case the GDM process is being kept alive by the Xorg session, which in turn is being kept alive by the nvidia driver. I managed to capture a journalctl log with a stack trace from the nvidia driver
Also this problem does not occur on Ubuntu 18.04 installed on the same machine (Ubuntu with default kernel and latest 430.34 drivers).
For more information, I made a GDM bug report with further details here https://gitlab.gnome.org/GNOME/gdm/issues/503
I have this problem since kernel 5.1.* (which is the first kernel I tested on this relatively new PC). That log is from kernel 5.2.1, but the problem persists with latest 5.2.3. As stated in my previous post, this does not happen on Ubuntu 18.04 with default kernel and latest nvidia drivers (430.34), so this makes me think it’s a kernel regression.
Tomorrow I’ll test the LTS kernel which is on 4.19.61, to see if it is a recent regression.
If I am not mistaken, you had uploaded bug report and kernel config file on bug which you raised and I tried with same config but not able to replicate issue yet.
I updated same in the bug and you should have been received notification.
I am currently looking for system with processor i5 or i7 and will try to repro again, will keep updated on the same.
Hi amrits, yes I opened the bug some time ago. I posted a comment here, because for some reason, I couldn’t post a comment there today, the system wouldn’t accept it. I’ve sent you by private message a link to the video showing the issue with the latest kernel and nvidia drivers.
What bothers me is that -in my case- the problem exists with kernel 5.2 only. Unfortunately, 5.1 is EOL and the latest LTS kernel is 4.19, so I’m stuck with either 4.19 or 5.2 (but having to use SysRq key to reboot the system).