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.
Thanks for the information.
I can understand how such problems can occur in a development kernel, but how does this happen with stable LTS kernels?
Is no one watching the store?
Last edited by cwizardone; 12-10-2023 at 11:15 AM.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,018
Rep:
Quote:
Originally Posted by cwizardone
Within eight hours of installing 6.6.5, this box spontaneously rebooted itself three times. Sometimes I think it is my wireless keyboard as it seems to happen when scrolling down a web page using either the down arrow or the touch pad.
Regardless, it hasn't happened with 6.7-rc2, which has been rock solid. OTOH, 6.7-rc3 was a dog and I didn't build 6.7-rc4. Maybe I'll try 6.7-rc5, when it is released later today.
I don't see this issue neither with 6.1.66. nor 6.6.5
Quote:
Originally Posted by Petri Kaukasoina
6.6.5 doesn't work so well here. System shutdown hangs in '/etc/rc.d/rc.inet1 stop', in gateway_down (/sbin/ip -4 route show). REISUB needed.
I don't shut down much, so I noticed the problem first when hibernating did not work, 2 user space processes refused to freeze: NetworkManager and ntpd.
It worked ok after I downgraded net/wireless/core.h and net/wireless/nl80211.c to the versions from kernel 6.6.4.
(I have RTL8723BE Wireless Network Adapter, using rtl8723be module.)
The offending commit:
Code:
commit 4a7e92551618f3737b305f62451353ee05662f57
Author: Johannes Berg <johannes.berg@intel.com>
Date: Mon Nov 6 23:17:16 2023 +0100
wifi: cfg80211: fix CQM for non-range use
commit 7e7efdda6adb385fbdfd6f819d76bc68c923c394 upstream.
My prior race fix here broke CQM when ranges aren't used, as
the reporting worker now requires the cqm_config to be set in
the wdev, but isn't set when there's no range configured.
Rather than continuing to special-case the range version, set
the cqm_config always and configure accordingly, also tracking
if range was used or not to be able to clear the configuration
appropriately with the same API, which was actually not right
if both were implemented by a driver for some reason, as is
the case with mac80211 (though there the implementations are
equivalent so it doesn't matter.)
Also, the original multiple-RSSI commit lost checking for the
callback, so might have potentially crashed if a driver had
neither implementation, and userspace tried to use it despite
not being advertised as supported.
Maybe 6.1.66 exhibits the same problem, as it also includes this commit.
I was not able to reproduce this behavior running 6.1.66 or 6.6.5. On the other hand looks like affected is distro with systemd. However I have Intel Wi-Fi 6 AX210/AX211/AX411 not Realtek so maybe hardware matters
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,163
Original Poster
Rep:
Year 2023, Round 62
Another batch of updates has been scheduled for release on Wednesday, 13 December 2023, at approximately 18:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Only Pat knows, but I can't help but think that since we have a brand new shiny LTS kernel and Plasma 5 heading towards EOL, 15.1 should at least be on the horizon soon. The only thing left I can think of is the switch to Grub from lilo/elilo, but I am not sure if that is coming with 15.1 or 16.0.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.