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.
linux-6.2.1 will co-exist with the most recent Nvidia driver as long as I do not log out of a KDE session. When I log out, I never return to a terminal, and I have to ssh into the box to reboot it. Linux-6.0.18 works well enough for me until Nvidia gets its house in order.
I have no idea what is causing my issue. I believe I unfairly libeled schedutil. It is random, whatever it is. I boot and I experience it immediately while trying to open up applications. Then I reboot and it is gone.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by RadicalDreamer
I have no idea what is causing my issue. I believe I unfairly libeled schedutil. It is random, whatever it is. I boot and I experience it immediately while trying to open up applications. Then I reboot and it is gone.
In my case when disk (nvme) was accessed and cpu was used, system froze for a few sec (~3s). This is the first time for since very long (years) so maybe this is nothing but it felt like OS from 90' - early 00'.
This is not what you observe of course.
I have no idea what is causing my issue. I believe I unfairly libeled schedutil. It is random, whatever it is. I boot and I experience it immediately while trying to open up applications. Then I reboot and it is gone.
Did you upgrade latest bios for your board?
In 2022, I've seen some stability issues, similar to what you posted, and then gigabyte shipped an update which fixed most of it.
In my case when disk (nvme) was accessed and cpu was used, system froze for a few sec (~3s). This is the first time for since very long (years) so maybe this is nothing but it felt like OS from 90' - early 00'.
This is not what you observe of course.
Exactly the same here (with both 6.1 & 6.2). I especially notice it when I install pkg from SBo (not during the build, but when the package is installed)
I just tested with kernel linux-next (2023-02-25), the freeze seems to have disappeared for now
EDIT: the freeze appeared again when I launched Telegram for the first time ...
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by marav
Exactly the same here (with both 6.1 & 6.2). I especially notice it when I install pkg from SBo (not during the build, but when the package is installed)
I just tested with kernel linux-next (2023-02-25), the freeze seems to have disappeared for now
EDIT: the freeze appeared again when I launched Telegram for the first time ...
This is bad.. I wonder how come that developers did not notice and fix this issue right away.
I re-compiled 6.1.14 and 6.2.1 with CPUFreq Performance
I re-compiled 6.1.14 and 6.2.1 with CPUFreq Performance
Why recompile? /etc/default/cpufreq:
Code:
# To select a particular CPU governor option for /etc/rc.d/rc.cpufreq,
# uncomment the line below and edit it to select your choice:
#SCALING_GOVERNOR=ondemand
Or you can try different values, for example:
Code:
# /etc/rc.d/rc.cpufreq
Enabled CPU frequency scaling governor: ondemand
# /etc/rc.d/rc.cpufreq performance
Enabled CPU frequency scaling governor: performance
# To select a particular CPU governor option for /etc/rc.d/rc.cpufreq,
# uncomment the line below and edit it to select your choice:
#SCALING_GOVERNOR=ondemand
Or you can try different values, for example:
Code:
# /etc/rc.d/rc.cpufreq
Enabled CPU frequency scaling governor: ondemand
# /etc/rc.d/rc.cpufreq performance
Enabled CPU frequency scaling governor: performance
+ if you want to switch amd-pstate <-> acpi-cpufreq
acpi-cpufreq is loaded by default
just add "amd_pstate=passive" in the kernel command line to use amd-pstate
Did you upgrade latest bios for your board?
In 2022, I've seen some stability issues, similar to what you posted, and then gigabyte shipped an update which fixed most of it.
HP hasn't updated my bios since 2015. My next computer will be prebuilt! I didn't update for a couple of weeks this year. I know I updated around Feb 1st. A new mozj was added, an older one was removed, and I installed the 6.1.8 kernel. I noticed it right away after the update. I noticed I forgot to install-new and did so, I rebooted, and it went away. I initially thought it was the new kernel. I downgraded my kernel back to 5.19 and it was still there so I was wrong! I have an install of Slackware 15 on the same computer and it hasn't had any problems.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
