Upgrade from 5.22.1 to 5.22.2 killed my system
Page 1 of 1 (15 posts)
Tags:
None
Registered Member 
|
Hi.
About 1 week ago, I updated my system (which had been working beautifully for years under KDE Neon). Immediately after the update, my system started displaying all kinds of strangeness. At first, I thought it was my network, because none of my network shares were accessible, and network monitor was complaining. After trying to figure this out by poking around the system, I found it would lock up after about 2-3 minutes. During this 2-3 minute grace period, I would be subjected to all manner of weirdness on the KDE interface... stacatto mouse movements... artifacts on the screens, failure to paint windows properly, etc. After some trouble-shooting I found that the network was not my problem. Very mysteriously, during my trouble-shooting of this issue, the network stopped complaining... but instead, I was getting CPU stalling behaviours that would continuously complain... and nvidia card errors on my VTs... it was very difficutl to see these things and trouble-shoot them because my grace period before lockup seemed to be getting shorter and shorter. Eventually, I removed all the nvidia elements from the system... no more stalling CPUs... but the system was still exhibiting all the same bizarre behaviors that would always wind up with lockups... but now within a couple seconds of login. During the week, I'd apply any updates that came my way, in hopes that it would fix this issue. It didn't. I reinstalled the Nvidia drivers. It didn't seem to either help or hinder the situation... I disabled compositing on the desktop... this bought a few minutes again before lockup -- but all the same really weird behaviors were still occurring in the interface (mentioned above), with the new addition that the keyboard would stop sending input (mouse still worked, but I couldn't type anything into a field on the screen). I also lost the ability to view my VTs somewhere along the way. Now, before people start suggesting this is hardware -- I've already ruled that out by booting to alternate USB/DVD media and by booting to the previous KDE Neon/Ubuntu kernel. Using the previous kernel, I cannot get a good resolution, because it isn't loading the nvidia driver -- but the system is stable, with no complaints of any kind. This problem seems to relate to the kernel itself, or the nvidia driver's goodness of fit with the 5.8 kernel. I've tried logging in using the wayland option, just to see if this helped. Of course, it didn't. I imagine there are some other hoops I have to jump through for that to work right... but I'm not interested in that right now. I have plenty of empty hard disk space, and plenty of memory. My video card is an nvidia GTX 970, using the 460 proprietary driver. I had been using the PPA driver for a long time now, but currently I'm on the mainstream, Ubuntu driver as part of this trouble-shooting process. I appreciate any help. Thanks. My CPU:
Here is some of the latest babel from my syslog:
|
|
Registered Member
|
5.22.3 came out today.... It fixed everything.
|
|
Registered Member
|
I spoke too soon. It seemed to work for a little while there... now it is locking up all the time... make no sense to me... Here I am again on the previous kernel, and things are working fine (except for my nvidia drivers -- I'm working in 600x800 resolution). Going to the new kernel kills the stability of my system...
|
|
Registered Member
|
Hi!
To get to know what is causing the issues, you could have a look at the changes at kernel.org or at first look at `journalctl -b -xep err` to get the error relevant error messages. If your system runs with nvidia drivers, be sure not to choose wayland and stay on Xserver as display server. |
|
Registered Member
|
This is exceedingly difficult to do, since it typically locks up within seconds now after booting. However, I did get it to fire off once, and it only kicked out the same things I have already listed in my post above: namely the stalled CPU. I tried to get it into a text file so I could reboot to the old kernel and post it exactly, but it just is not stable enough... but I assure you, it is information that is only redundant to what I posted in the logs. The lock ups are as strange as ever... the mouse will move across the screen, but most things are not clickable... the things I can click usually fail to manifest on the screen.. sometimes I can see the window dimensions, but the window never paints... instead it retains whatever would have been behind it within those dimensions... almost as if it is a carbon-copy of what is beneath it. When this happens, the window is not moveable. The 'x' button is still there and I can click it, but nothing happens. I cannot access VTs, and I cannot reboot the system. I have to do a hard reset. I have pulled the pc apart and reset everything physically -- and gave it a good clean-out while I was at it... even though I'm confident this isn't hardware related. Again, booting to the old kernel works fine. I am not using wayland, I'm sure of that. Any assistance is appreciated. Thank you. |
|
Registered Member
|
Depending on your bootloader¹ you can stop booting before SDDM starts enabling «text». For systemd there are some options like: systemd.log_level=debug and/or systemd.unit=multi-user.target or systemd.unit=rescue As I do not know grub2 that much, I'd try using multi-user first: On the grub-screen choose the latest kernel and press 'e'. The kernel command line with 'quiet splash' or similar must be carefully changed. Remove quiet and splash to see more messages and insert systemd.unit=multi-user.target instead. Then press F10 to continue boot with these settings. You should now have a fully working systemd (without gui). Login and get the informations as usual, saving them to a file² for the current log or just the errors including the last logs. The messages above are cut off and do not show the system start which (hopefully) contains more information. You could also log `journalctl -k` (basically the further dmesg command). ¹,²:
2 → e.g. `journalctl -b > ~/informations`, use >> instead of > to append to a file |
|
Registered Member
|
Hi, yeah, that is essentially what I'm doing. But there are no problems (and hence no error output) when I don't have the gui up, so journalctl gives me nothing. |
|
Registered Member
|
And if you manually start an XServer after startup?
|
|
Registered Member
|
I just tried starting X manually... and it is even worse... cannot even get past the giant "K" splash screen before plasma desktop loads.
For S's and G's I installed fluxbox, to see if it would fare any better. It did not. It exhibited the same behavior. As much as I'd like to know what is going on here, I'm thinking it is time for a reinstall... |
|
Registered Member
|
If X and wayland get stuck with every user (you should create a clean one to test) there could be an issue with the graphical stack. For this you could compare the modules loaded into the kernel with `lsmod`. Perhaps it is a driver issue. What graphic card(s) do you use? Are there any acpi(d)-errors?
will show the graphic card and drivers. |
|
Registered Member
|
I just downloaded a fresh copy of the KDE neon installation media. The same exact problems are present with the the live boot of the installation media itself. If I boot to nomodeset, it works, but the resolution is terrible (as one might expect).
I downloaded a copy of Manjaro, and did the same -- works perfectly, even with the proprietary drivers. It seems pretty clear to me that this is a bug, it just isn't biting very many people. I think it is a hardware + kernel version + nvidia module issue. The current Manjaro installation media is on kernel 5.10, and uses the nvidia drivers 4.65. I can try what you suggest, but given that it is a stock install, and that it happens even with the installation media, this reeks of a bug. I will post one, then try to delve a little deeper. The problem is, I've already lost a few weeks with this, and I need this to work. I don't know how much time I can put into this... Time is a just a scarce commodity these days (which is why this system is kde neon and not Gentoo!). |
|
Registered Member
|
I cannot do this under kernel 5.8 due to the instability... but here is the output under kernel 5.4:
|
|
Registered Member
|
Try to switch to nouveau, your card seems to be working mostly → https://nouveau.freedesktop.org/FeatureMatrix.html
|
|
Registered Member
|
I appreciate your input, but I I do not want to switch to nouveau. I prefer the proprietary driver.
|
|
Registered Member
|
Then you can just try the dkms-driver or the default one.
|
Page 1 of 1 (15 posts)
Bookmarks
Who is online
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft
