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.
Same here, random and I have to pkill the program.
I have an i7-10750H
The light on my computer would stay on it through out it. My computer wasn't running hard. It just was unresponsive for a bit. I could move my mouse. On run level 3 I was upgrading with slackpkg, the upgrade package part took forever instead of seconds. I switched to ondemand (defaults to powersave i believe) and it works much better. I'm using the "intel_cpufreq" driver. The problem is still there. I don't know what the issue is. I briefly went back to 5.19.17 (except for the kernel headers) and the issue was still there so I went back to 6.1.X. I suppose I owe kernel 6.1 an apology. I upped "/sys/devices/system/cpu/intel_pstate/min_perf_pct" a little bit and now my computer is much more responsive.
On my machine this makes the minimum frequency 1.87 GHz. It says "current policy: frequency should be within 1.87 GHz and 3.90 GHz." Otherwise the min freq would be 1.60 Ghz.
Not sure if this counts but in 6.2-rc8 schedutil works without hickups under (minor) stress e.g compiling kernel or other software.
Note (random)
heh I got windows 10 icon on the system that never booted to windows. That is good actually
Thanks for the information! Originally I was certain it was schedutil but now I have no idea. I just know under it recently my computer would have bouts of very slow opening programs, loading webpages, etc. After further investigation, maybe I shouldn't have brought this up in this thread.
I used to have Windows 10 on this computer but I got tired of reinstalling it! The problem I've had reminds me of Windows except the computer is doing pretty much nothing while in Windows it would be grunting and making all kinds of noises (fan spinning rapidly) as it struggled to open up a program.
Had a soft lockup on 6.1.12, not tainted, & can't repeat it on 6.1.11.
What locks up: Xorg, mouse, keyboard, all frozen.
What does not freeze: network, disk, power button, all works.
Power button does "init 0" after short delay as usual, but after this lockup: nouveau framebuffer display becomes corrupt.
Expected text on shutdown, becomes corrupt/unreadable colored garbage output on top of the screen.
Thought it might be the recent Xorg patch fault at first, but can't seem to repeat the thing on previous kernel 6.1.11.
I think that it is important to inform at least what CPU is involved. It seems that there is more issues related to AMD than Intel.
Ryzen5, but it's more likely realtek audio/ nouveau video that triggered it.
Don't care anymore really, lost the will to fix unstable stuff, seems completely futile at this point.
I'll just drop 6.1 kernels, got 14.2 installed for multimedia anyway, no big deal.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,154
Original Poster
Rep:
Year 2023, Round 11.
Another batch of updates has been scheduled for release on Wednesday, 22 February 2023, at approximately 13:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by RadicalDreamer
The light on my computer would stay on it through out it. My computer wasn't running hard. It just was unresponsive for a bit. I could move my mouse. On run level 3 I was upgrading with slackpkg, the upgrade package part took forever instead of seconds. I switched to ondemand (defaults to powersave i believe) and it works much better. I'm using the "intel_cpufreq" driver. The problem is still there. I don't know what the issue is. I briefly went back to 5.19.17 (except for the kernel headers) and the issue was still there so I went back to 6.1.X. I suppose I owe kernel 6.1 an apology. I upped "/sys/devices/system/cpu/intel_pstate/min_perf_pct" a little bit and now my computer is much more responsive.
On my machine this makes the minimum frequency 1.87 GHz. It says "current policy: frequency should be within 1.87 GHz and 3.90 GHz." Otherwise the min freq would be 1.60 Ghz.
Thanks for the information! Originally I was certain it was schedutil but now I have no idea. I just know under it recently my computer would have bouts of very slow opening programs, loading webpages, etc. After further investigation, maybe I shouldn't have brought this up in this thread.
I used to have Windows 10 on this computer but I got tired of reinstalling it! The problem I've had reminds me of Windows except the computer is doing pretty much nothing while in Windows it would be grunting and making all kinds of noises (fan spinning rapidly) as it struggled to open up a program.
Does anyone experience random reboots with kernel 5.15.94 (on Slackware64 15.0)? I remember this computer of mine doing so with various kernels in the past, but the 5.15.x series have been quite stable so far, up until 5.15.94. The machine barely lasts an hour when left idle. I will probably try switching to a custom 6.x kernel, but I wonder if I am the only one. This is an Intel Core i5-8500T machine.
Generic Kernel Version 6.1.13.kjh is running fine on my Slackware64 15.0 + Multilib LapTop.
No CVE References were found for 6.1.13, 5.15.95, 5.10.169, 5.4.232, 4.19.273 or 4.14.306, but as always, do check the ChangeLogs for other security-related fixes.
rebuilding kernel was something that I wanted to suggest as clearly suspicious option was long in use in Slackware kernel though not sure why.
Kernel is huge and weed out all options that aren't necessary is impossible including developer settings. If not for (unrelated) issues with booting your kernel, this option would happily be turned on until forever.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.