@mfoley

I looked through this thread, but did not see this mentioned - are you using Plasma (Wayland) or Plasma (X11)? Have you noticed any difference between the two with respect to freezes?

I have a box with an old GTX 950 running nouveau that cannot run Plasma Wayland, but the intel graphics (i915) on the i7 4790K on the same box has no problems running Wayland. The GTX 950 runs fine with Plasma (X11).

1 members found this post helpful.

Just a quick update. I just compiled 5.15.0 this morning and have had no freezes so far. I am using X11 with XFCE and the MESA Iris driver. I'll leave my machine running over the next week and see how it pans out. That being said, last night I upgraded to the latest current kernel, 5.14.15, left my machine on overnight and found it frozen in the morning.

The latest current kernel is 5.15.0.

Aha, wasn't there yet last night but good to know, thanks. Anyway been working fine for a whole day so it seems these GPU issues I've been having have been addressed by this new kernel series.

I had some minor to moderate freezes in Chrome after moving to slackware64-current 5.14.15 generic kernel with the new preemption code and all the switches flipped. Two Chrome tabs died on separate occasions (new behavior). A third time it eventually came back to life. And several times the Chrome Bookmark Manager screen couldn't scroll to the top of a bookmarks list. The latter condition always cleared after a few seconds/trys.

I have Intel i915 grahics.

But it's a new day and that 5.14.15 kernel is gone, never to return, so we'll see how it goes.

I didn't get that prolonged blank screen during the 5.15.0 boot that people speak of. I run LILO at low resolution, vga=normal, so that's how the initial kernel boot-up scroll goes, then it blanks out for a second or two before switching to 1920x1080. I never got frame buffer settings to work in LILO on this machine, though I did not try very hard.

I have not. That might make a difference, but wouldn't be a configuration I'd want to run with, so it doesn't really matter if that would work and opening up the box, yanking a card, etc. is not worth the effort. The occasional restart of KDE/XFCE is less trouble.
See my post #168 in this thread. With NVIDIA drivers I only get two monitors. To get 4 I need to run XINERAMA which is too old to run Firefox and LibreOffice, and gave me crashes when moving windows or browser tabs. nouveau runs 4 monitors, no problem (well, aside from the freezes mentioned in this thread).

I upgraded to 5.14.15 one week ago. At first, I got freezes about once a day, sometimes up to 3 a day, but not so bad as to induce me to revert to a previous version. For the heck of it, I decided to swap out my Logitech wireless keyboard/mouse and use a wired keyboard/mouse. In the past 5 days I only had one freeze. Not sure if this means anything yet. Need more time. I've been upgrading monthly and I'll probably wait until the end of the month before upgrading to the 5.15.x kernel.

Still had problems in the end for me, both with 5.15.0 and 5.15.1. However this time, my monitor still gets a video signal (so I see frozen XFCE mice) whereas it wasn't the case with the 5.10.x and 5.14.x series. Even tried disabling i915 power saving to no avail. So back on 5.4.x for now.

I tried kernel 5.15 recently, compiling it myself using the config file in -current. Of my 4 computers (2 desktops, 2 laptops) 3 work well, but the last one, an Asus TP200SA with Intel graphics, gets a black screen after suspend (for a brief moment one can see the rectangular mouse cursor -- as in the framebuffer screen). Kernels 5.4 and 5.10 were running fine on this device. For the moment, I am back to 5.4.

I have been using X11, but based on your question I just tried Wayland this evening. What a mess! First off, I lost two of the 4 monitors. The mouse was VERY unresponsive (slow). I tried to "Leave" but got an error that the Greeting had crashed. In the end, I had to reboot from an ssh login. When I came back up and logged in with X11 my active monitor was changed, so I had to change it back. I did some searching on "Wayland Full", but that doesn't seem worth the risk.
That's interesting. My setup pretty much always "gets a video signal", as you say, even with past kernel versions. When I've "frozen" and ssh in and do a VM savestate, the image of the VM persists on the screen even though VBox is no longer running. Likewise if I "killall firefox". It stops running, but the image is still there. I believe that's what you mean. When I freeze up like this, the mouse moves for a while, but buttons do nothing. In short order, the mouse also stops moving. What usually works for me is to ssh in remotely (from my Android phone, in fact), su to root and do 'init 3' followed by 'init 4' shortly thereafter when the screens all go back to text mode.

I've noticed fewer freeze-ups with a wired mouse/keyboard ... until this evening when I had two freezes in a row within an hour. Both times while composing a Thunderbird email. I've updated Thunderbird; we'll see!

In my case the machine was no longer accessible via the network so I couldn't even SSH into it.

UPDATE: I just updated to 5.15.2 and it seems to be fine. Uptime is now close to 22 hours without a single hitch.

1 members found this post helpful.

I upgraded to 5.15.12 from 5.15.6 5 days ago. 5.16.6 wasn't too bad, about one freeze a week. 5.15.12 sucketh! At least one and up to 3 freezes a day; sometimes back-to-back (within minutes). In none of the cases was VirtualBox running. Just in case, I always shut that down when finished with Windows. Sometimes it seemed to freeze when I switch to the screen having Firefox, but not consistent and not enough freeze samples to conclude anything there. Sometimes the monitors break up into a jigsaw puzzle of random screen "squares" that flicker when I move the mouse, but nothing is clickable and the mouse eventually stops. Sometime the freeze happens with nothing going on and with me away from the computer for a couple of hours. In this case I'll notice that the time display on the sleep-screen is well behind the actual time and not updating. I hope this eventually gets fixed!

1 members found this post helpful.

As I reported in the kernel thread, while running 5.15.12 and streaming video, I was twice thrown back to the prompt (init 3). That has not been a problem with 5.16-rc7 or -rc8.

Just now upgraded from 5.15.12 to 5.15.18. I have only been running this for a couple of hours, so no feedback yet on freeze issues. I do have a question though. I noticed that /etc/slackpkg/mirrors has a lot more slackware64-15.0 sites listed. Should I now start using e.g. https://mirrors.slackware.com/slackw...ckware64-15.0/ instead of https://mirrors.slackware.com/slackw...re64-current/?

Not yet, 15.0 mirrors won't be up until after slackware 15 has been officially released.

Well, I thought this freeze issue was finally nailed, but today it froze up hard while composing a message in Thunderbird. ssh'ing in and doing init3/init 4 didn't reset the desktop; had to shutdown -r. Still, it ran without freezes since my last post 6 days ago, which is a record. I guess I'll have to keep my 14.1 systems going until this gets fixed and the VirtualBox crashing when checking for updates is fixed. There is a new kernel out 5.15.19. Maybe ...?
"Alien Pastures" sent an email on Thursday (2022-02-03), subject: "Slackware 15.0 has been released on 2022-02-02". So, is it official now?