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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,041
Original Poster
Rep:
According to this,
Quote:
Re: [PATCH 5.11 000/342] 5.11.20-rc1 review
From: Greg Kroah-Hartman
Date: Tue May 11 2021 - 09:35:59 EST
.......It might be due to 79fcd446e7e1 ("drm/amdgpu: Fix memory leak") which I
have reverted from 5.12 and 5.11 queues now and pushed out a -rc2. If
you could test those to verify this or not, that would be great.
thanks,
greg k-h
there should be a second round of release candidates for the 5.11 and 5.12 series,
but they have yet to be posted.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,041
Original Poster
Rep:
Year 2021, Round 33.
Another batch of updates has been scheduled for release on Friday, 14 May 2021, at approximately 14:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Thursday (depending on your time zone).
Just did the usually uneventful thrice a week ritual bump to 5.10.37 with generic & same mkinitrd params going back many an upgrade. Instead of a < 1 min boot, it was ~ 30 min. udevd seemed to be hunting for nonexistent prey. Revert to 5.10.36 & all is OK plus 5.12.4 from testing is a champ. Anyone else observing this behavior?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.