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.
Ran in to an issue with 5.13.0 today. I runs fine except for one issue that is forcing me back to 5.12.x (14 right now).
This desktop is running 5.13.0, my laptop was running 5.12.12. I update my laptop via NFS shares on the desktop, mounting those shares on the laptop fails with:
Code:
mount.nfs: requested NFS version or transport protocol is not supported
Rebooting the desktop to back to 5.12.14, the mount succeeds.
Same applies when mounting the reverse, laptop 5.13.0, desktop 5.12.14, attempting to mount a share on the laptop from the desktop fails. Reverting back to 5.12.12 on the laptop, the mount succeeds.
Both desktop and laptop running 5.13.0, mounts in either direction fail with same error.
Both desktop and laptop are now running 5.12.14 with no issues in mounting shares.
Ran in to an issue with 5.13.0 today. I runs fine except for one issue that is forcing me back to 5.12.x (14 right now).
This desktop is running 5.13.0, my laptop was running 5.12.12. I update my laptop via NFS shares on the desktop, mounting those shares on the laptop fails with:
Code:
mount.nfs: requested NFS version or transport protocol is not supported
Rebooting the desktop to back to 5.12.14, the mount succeeds.
Same applies when mounting the reverse, laptop 5.13.0, desktop 5.12.14, attempting to mount a share on the laptop from the desktop fails. Reverting back to 5.12.12 on the laptop, the mount succeeds.
Both desktop and laptop running 5.13.0, mounts in either direction fail with same error.
Both desktop and laptop are now running 5.12.14 with no issues in mounting shares.
It's been reported and I think there's a patch for regression.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,018
Rep:
Quote:
Originally Posted by chrisretusn
Ran in to an issue with 5.13.0 today. I runs fine except for one issue that is forcing me back to 5.12.x (14 right now).
This desktop is running 5.13.0, my laptop was running 5.12.12. I update my laptop via NFS shares on the desktop, mounting those shares on the laptop fails with:
Code:
mount.nfs: requested NFS version or transport protocol is not supported
Rebooting the desktop to back to 5.12.14, the mount succeeds.
Same applies when mounting the reverse, laptop 5.13.0, desktop 5.12.14, attempting to mount a share on the laptop from the desktop fails. Reverting back to 5.12.12 on the laptop, the mount succeeds.
Both desktop and laptop running 5.13.0, mounts in either direction fail with same error.
Both desktop and laptop are now running 5.12.14 with no issues in mounting shares.
Thank you. This is the first useful information about 5.13.0 kernel.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,167
Original Poster
Rep:
Year 2021, Round 44.
Another batch of updates has been scheduled for release on Wednesday, 7 July 2021, at approximately 11:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
I can't tell from the following if the fix for the nfs problem, as pointed out by board member chrisretusn (see post #3558, above), will be included in this round or if it is has been queued up for the next update (and I don't see a 5.13.1-rc2, yet).
Greg KH on Mon Jul 05 2021 at 08:41:46 EST, replying to a post by a Thomas B, made on Mon Jul 05 2021 at 08:22:30 EST
Quote:
> This one should be added too:
>
> From 66d9282523b3228183b14d9f812872dd2620704d Mon Sep 17 00:00:00 2001
> From:
> Date: Mon, 28 Jun 2021 16:02:19 +0100
> Subject: [PATCH] mm/page_alloc: Correct return value of populated elements
> if
> bulk array is populated
>
>
> to unbreak nfs in 5.13 series ...
>
> the cause and fix is confirmed in several threads both on lkml and stable@
Just got to doing the update today - last updated Jun 23.
Slackware64 -current with kernel 5.13.0 from testing working fine, after update from 5.12.12. Never any problems with any of the 5.12.x that I upgraded to (I missed a couple.)
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,167
Original Poster
Rep:
Year 2021, Round 45.
Another batch of updates has been scheduled for release on Sunday, 11 July 2021, at approximately 13:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Saturday (depending on your time zone).
5.13.1 built and running fine. Never had the nfs problem though so can't verify it is fixed.
I've been without Internet for two days. I just finished by upgrades the NFS problem has been fixed upgrading my laptop 5.12.14 off the NFS share on this desktop 5.13.1.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
