[SOLVED] Occasional system freeze after the latest update in Slackware64 --curent
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
That thing described in first post, I get this sometimes on 64bit 14.2 (nouveau driver) happens with or without network, idle or not doesn't matter.
Pretty sure it's the kernel because it did not happen before 4.14.199 but happens often since 4.14.200 up to 4.14.212
Might be unrelated, but when it freeze I mount the rootfs on another system and check the log where I found something like this every time:
Code:
[ 3449.357] Using O_TMPFILE
[ 3449.993] Using O_TMPFILE
[ 3450.680] Using O_TMPFILE
[ 3451.475] Using O_TMPFILE
[ 3456.282] Using O_TMPFILE
[ 5964.443] Using O_TMPFILE
[ 8468.462] Using O_TMPFILE
[ 8469.022] Using O_TMPFILE
[ 8469.630] Using O_TMPFILE
[ 8470.318] Using O_TMPFILE
[ 8474.240] Using O_TMPFILE
I first tried the proprietary driver, but it didn't help. I still had both screen glitching and occasional freezing (screen and keyboard freeze, fan goes wild).
Next, I uninstalled the proprietary, switched back to the nouveau driver and decided to wait for the next kernel upgrade. After the upgrade to 5.10.3, both glitching and freezing disappeared (or at least didn't appear in the next several hours of testing). If anything changes (hopefully it won't) I'll let you know, but everything looks OK now.
exactly what i did too on both laptop and desktop (each having a second screen connected to it)
Ok, it happened again. In somewhat more than a day of testing, there were no screen glitches, but it still freezes occasionally (just experienced the first one with 5.10.3), just less frequent than before I upgraded to 5.10.3. So, it's not really solved yet.
Ok I have the same issue as you. Lockup to point where keyboard is non-resposive. I noticed I can still ssh into the box so I did this and see:
** Xorg (attached screenshot)
Happened several times (always with Firefox)
-- after first it prompted me to start clean (fresh install 5.10.2 current / update to 5.10.3) [saved backup]
-- still happens clean install (only added i3 wm) (but did get Lockup in xfce and fluxbox too.)
My current theory is Firefox related. (running Konqueror as I type to see if it happens here)
-- randomness of the issue makes it hard to be too sure
Ok I have the same issue as you. Lockup to point where keyboard is non-resposive. I noticed I can still ssh into the box so I did this and see:
** Xorg (attached screenshot)
Happened several times (always with Firefox)
-- after first it prompted me to start clean (fresh install 5.10.2 current / update to 5.10.3) [saved backup]
-- still happens clean install (only added i3 wm) (but did get Lockup in xfce and fluxbox too.)
My current theory is Firefox related. (running Konqueror as I type to see if it happens here)
-- randomness of the issue makes it hard to be too sure
Good point, thanks! I also suspected that it has something to do with Firefox. Every time it happened here, it was while using Firefox. However, it was the same Firefox version I was using before the kernel was upgraded (without any problems), so I forgot about that possibility, but the combination between the two might be the problem. The new kernel version is going to be up in a couple of days I think, and I hope the new release of Firefox will happen soon.
Every time it happened here, it was while using Firefox.
Now that I think about it, the two times it happened last week with the 5.10.2 kernel, I was also using Firefox. I had several other applications running on other workspaces, but the actual freezes occurred while I was on Firefox’s window.
Now that I think about it, the two times it happened last week with the 5.10.2 kernel, I was also using Firefox. I had several other applications running on other workspaces, but the actual freezes occurred while I was on Firefox’s window.
Same here. I've had my system lock up three times now. Twice with 5.10.2 and once with 5.10.3.
The CUDA toolkit is included in the proprietary NVIDIA driver.
I've installed slackware64-current (from alienbob's iso repo for current) on 3 machines this last month, no freezes.
One laptop was pure integrated, no problems.
Another one intel + nvidia, so I fiddled a bit with bumblebee but it seems blacklisting i915 and NVIDIA proprietary was the way to go for that one (worked fine ran Dark Sould 3 and WoW:Shadowlands with fps capped at 144 same as my screen hertz).
The desktop however (gtx1080ti + intel 7700K) didnt work with the "long lived" drivers but the "short lived" drivers seems to be working great so far!
If you are having any problems with current and NVIDIA I can recommend to try the short-lived drivers especially if you recently upgraded kernel and have problems.
honestly, i dont think it is related to firefox. I believe it to be just a coincidence as firefox use also video-accelerator; however, in my system, it happens also when i move windows between screen or most often completely random (for example yesterday it crashed as soon as i woke the system from sleep by simply moving the mouse even with a single screen, although i didnt lose the keyboard so i could ctrl+alt+del to log out and log back in).
Disabling firefox video accelerator has stopped firefox to be able to stream some in-browser video but, for example the gliching still persists here as soon as i enable the second screen (i have been only with one screen for over a week now to decrease the glitching but the system crash it's always an incognito).
I still bet on linux kernel/gcc compiler and nvidia kernel/driver
edit: i opened a thread here if anyone wishes to peak for hints and suggestions
honestly, i dont think it is related to firefox. I believe it to be just a coincidence as firefox use also video-accelerator; however, in my system, it happens also when i move windows between screen or most often completely random (for example yesterday it crashed as soon as i woke the system from sleep by simply moving the mouse even with a single screen, although i didnt lose the keyboard so i could ctrl+alt+del to log out and log back in).
Disabling firefox video accelerator has stopped firefox to be able to stream some in-browser video but, for example the gliching still persists here as soon as i enable the second screen (i have been only with one screen for over a week now to decrease the glitching but the system crash it's always an incognito).
I still bet on linux kernel/gcc compiler and nvidia kernel/driver
edit: i opened a thread here if anyone wishes to peak for hints and suggestions
I've had this before on stable systems and just either disabled the auto settings or just disabling hardware acceleration overall.
I've had this before on stable systems and just either disabled the auto settings or just disabling hardware acceleration overall.
Ok i have some interesting findings!
if you xwmconfig in to XFCE, no glitching, no crashes, no need to blacklist anything, no need of proprietary drivers and no need to disable hardware acceleration, both screens are magnificently working as they should.
I change back to KDE and glitching starts immediately.
Now, i am not a developer and/or a tech guru, just a mediocrely educated person who understands that 2+2 equals 4; so, if one 2 is the same hardware and the other 2 is the X desktop it cannot be 4 in one case and 3 or 5 in the other case.
Am i missing something about the new KDE Plasma that differs from xfce (in terms of video resources)?
Am i missing something about the new KDE Plasma that differs from xfce (in terms of video resources)?
One potential area of investigation could be the compositing settings (System Settings>Display and Screen>Compositor: based on rough translation from French).
There, you can modify rendering engine, vsync and other parameters related to graphics. I'm no graphics hardware specialist but looking at various forums, it looks like some settings might create instability for some hardware/kernel combinations.
if you xwmconfig in to XFCE, no glitching, no crashes, no need to blacklist anything, no need of proprietary drivers and no need to disable hardware acceleration, both screens are magnificently working as they should.
I change back to KDE and glitching starts immediately.
Now, i am not a developer and/or a tech guru, just a mediocrely educated person who understands that 2+2 equals 4; so, if one 2 is the same hardware and the other 2 is the X desktop it cannot be 4 in one case and 3 or 5 in the other case.
Am i missing something about the new KDE Plasma that differs from xfce (in terms of video resources)?
Just to mention that I use fluxbox, so it's not necessarily KDE-related.
Another thing is that the problem persists no matter if I use nouveau or proprietary NVIDIA driver.
Since 5.10.3 I don't see screen glitching anymore but it still freezes from time to time, and always while using Firefox. Btw, I agree about the Firefox and hardware acceleration, that sounds like a good explanation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
