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.
FWIW: Just built and installed the 6.8.0 kernel. It is early yet, but so far, so good.
6.8.0 ran almost fine for me, I always test new kernel releases with a sleep and resume test a few times and run some games. I kept getting this message spaming my logs and dmesg output.
Code:
[drm] scheduler comp_1.0.1 is not ready, skipping
I had hundreds of those lines in the course of in hour testing the new kernel and a sight but noticeable slowdown in desktop performance.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,124
Original Poster
Rep:
Thanks for the heads up.
As I don't own or use a laptop/notebook I haven't seen any problems, as of the moment, with the 6.8.0 kernel on this box.
The 6.6.20 kernel worked just fine for me, but there were two spontaneous reboots with 6.6.21.
Last edited by cwizardone; 03-11-2024 at 08:48 PM.
I'm using a desktop atm, I just find running a couple suspend/resume cycles on new kernels tends to be the best way to stress the kernel OOTB and if the system does come out of suspend without any gotchas that usually means the kernel is going to be relatively bug free on my system(s). It's just a one part of anecdata and one part ritual that I have been using for the last few years.
And most of the time when the test fails and couple kernel point releases fixes the issue(s).
After retesting kernel 6.8.0 I noticed my Windows partition wasn't getting mounted at boot and also I could not mount it manually so I make oldconfig the kernel config from 6.7.x again and found that the new kernel option
Code:
BLK_DEV_WRITE_MOUNTED
needed to be enabled. After a recompile the partition showed up again. Just a heads up for those that use the FUSE NTFS-3g driver with the new kernels.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,124
Original Poster
Rep:
Year 2024, Round 15
Another batch of updates has been scheduled for release on Friday, 15 March 2024, at approximately 16:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Thursday (depending on your time zone).
6.8.1 seems to be specifically addressing another CPU vulnerability, in Intel Atoms this time. I'm building it now, but I don't have an Atom so to be honest, I'm not sure why I'm bothering to do so.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 931
Rep:
Quote:
Originally Posted by cwizardone
FWIW: The problem returned with the 6.6.17 kernel and continues with the 6.6.18 and 6.6.19 kernels.
Edit in: The "blackout" is now 9 seconds with the 6.6.20 kernel.
This seems an intermittent problem across kernel releases.
I was running 6.7.2 kernel (Slackware 15.0) with "only" 2 seconds, it's acceptable.
Now with 6.8.1 the 6 seconds blackout is back.
6 seconds for us "computer guys" is long enough to be irritating.
Anything more than 10 seconds is an eternity.
This is with NVidia driver 535.154.05, but it doesn't matter.
The blackout happens with any version.
IIRC it happens with nouveau too.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.