You are not logged in.
Oh boy...
So, the update from 5.15.17 to latest linux-lts 5.15.24 welcomed me with NFS not working anymore, probably due to this:
[ 38.722487] FS-Cache: Loaded
[ 38.748413] RPC: Registered named UNIX socket transport module.
[ 38.748417] RPC: Registered udp transport module.
[ 38.748418] RPC: Registered tcp transport module.
[ 38.748418] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 38.780905] FS-Cache: Netfs 'nfs' registered for caching
[ 38.786945] Key type dns_resolver registered
[ 39.009325] NFS: Registering the id_resolver key type
[ 39.009344] Key type id_resolver registered
[ 39.009346] Key type id_legacy registered
[ 39.011828] FS-Cache: Duplicate cookie detected
[ 39.011834] FS-Cache: O-cookie c=00000003 [p=00000002 fl=222 nc=0 na=1]
[ 39.011838] FS-Cache: O-cookie d=0000000001ed7707{NFS.server} n=00000000fb1f11b6
[ 39.011842] FS-Cache: O-key=[16] '040000000200000002000801c0a8000a'
[ 39.011853] FS-Cache: N-cookie c=00000004 [p=00000002 fl=2 nc=0 na=1]
[ 39.011855] FS-Cache: N-cookie d=0000000001ed7707{NFS.server} n=00000000417936fb
[ 39.011857] FS-Cache: N-key=[16] '040000000200000002000801c0a8000a'So, this is a show stopper, can't mount my NAS. I downgraded to 5.15.17 only in order to find out that my dkms modules don't work anymore.
This is apparently because of the gcc upgrade:
# sudo dkms install --no-depmod vboxhost/6.1.32_OSE -k 5.15.17-1-lts
Building module:
cleaning build area...
make -j32 KERNELRELEASE=5.15.17-1-lts -C /usr/lib/modules/5.15.17-1-lts/build M=/var/lib/dkms/vboxhost/6.1.32_OSE/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.15.17-1-lts (x86_64)
Consult /var/lib/dkms/vboxhost/6.1.32_OSE/build/make.log for more information.
# head -20 /var/lib/dkms/vboxhost/6.1.32_OSE/build/make.log
DKMS make.log for vboxhost-6.1.32_OSE for kernel 5.15.17-1-lts (x86_64)
Tue 22 Feb 10:30:38 CET 2022
make: Entering directory '/usr/lib/modules/5.15.17-1-lts/build'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc (GCC) 11.1.0
You are using: gcc (GCC) 11.2.0
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxnetadp/VBoxNetAdp.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxdrv/SUPDrvGip.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxnetflt/VBoxNetFlt.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxnetflt/SUPR0IdcClientComponent.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxnetflt/SUPR0IdcClient.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.32_OSE/build/vboxdrv/SUPDrvTracer.o
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.soCannot easily downgrade gcc either:
# yay -U gcc-11.1.0-3-x86_64.pkg.tar.zst gcc-libs-11.1.0-3-x86_64.pkg.tar.zst
loading packages...
warning: downgrading package gcc (11.2.0-3 => 11.1.0-3)
warning: downgrading package gcc-libs (11.2.0-3 => 11.1.0-3)
resolving dependencies...
looking for conflicting packages...
Package (2) Old Version New Version Net Change
gcc 11.2.0-3 11.1.0-3 -5.29 MiB
gcc-libs 11.2.0-3 11.1.0-3 -1.44 MiB
Total Installed Size: 273.79 MiB
Net Upgrade Size: -6.72 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring [##############################################################################################] 100%
(2/2) checking package integrity [##############################################################################################] 100%
(2/2) loading package files [##############################################################################################] 100%
(2/2) checking for file conflicts [##############################################################################################] 100%
error: failed to commit transaction (conflicting files)
gcc: /usr/include/libiberty/ansidecl.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/demangle.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/dyn-string.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/fibheap.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/floatformat.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/hashtab.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/libiberty.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/objalloc.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/partition.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/safe-ctype.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/sort.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/splay-tree.h exists in filesystem (owned by binutils)
gcc: /usr/include/libiberty/timeval-utils.h exists in filesystem (owned by binutils)
gcc: /usr/lib/libiberty.a exists in filesystem (owned by binutils)
Errors occurred, no packages were upgraded.This sucks big time, I depend on asus-wmi-sensors-dkms-git in order to see temps.
What the heck do I know when this fs cache thing is going to be fixed?
I still have the old compiled modules lying around in /var/lib/dkms/. Can I install them manually somehow?
This did not succeed:
# cp -a /.snapshots/13325/snapshot/lib/modules/5.15.17-1-lts/updates/dkms/asus-wmi-sensors.ko.zst /lib/modules/5.15.17-1-lts/updates/dkms/And BTW is kde-cli-tools mandatory? I didn't upgrade it because of file conflicts with kdebase-runtime and now find myself in a KDE without desktop icons/wallpaper.
Last edited by tcn (2022-02-22 10:00:58)
Offline
The best way to fix this now with a downgrade of just the kernel is to actually recompile the older kernel with the new toolchain, you could leverage the ABS for that: https://wiki.archlinux.org/title/Arch_Build_System
If you actually want to work for and help with/test for a fix for the actual bug see: https://bbs.archlinux.org/viewtopic.php?id=274259
For the secondary question, it's the other way around, kde-cli-tools is necessary and kdebase-runtime doesn't exist anymore since quite a while and is an old KDE4 relict remove it, while you are at it check for other orphans: https://wiki.archlinux.org/title/System … d_packages
On checking whether you might be able to use a different intermediate kernel that ticks all the relevant boxes, apparently there's a potential bugfix release in testing you could try: https://archlinux.org/packages/testing/ … linux-lts/
Last edited by V1del (2022-02-22 10:21:44)
Offline
The best way to fix this now with a downgrade of just the kernel is to actually recompile the older kernel with the new toolchain, you could leverage the ABS for that: https://wiki.archlinux.org/title/Arch_Build_System
Good news: looks like there's stock support for my kraken now \o/ (only since 5.13!) and I don't depend on liquidtux-dkms-git anymore:
"New drivers:
- Driver for NZXT Kraken X42/X52/X62/X72"
https://cdn.kernel.org/pub/linux/kernel … geLog-5.13
https://www.kernel.org/doc/html/latest/ … aken2.html
Still depend on asus-wmi-sensors-dkms-git, though :\
On checking whether you might be able to use a different intermediate kernel that ticks all the relevant boxes, apparently there's a potential bugfix release in testing you could try: https://archlinux.org/packages/testing/ … linux-lts/
Yeah, when between .17 and .24 did the update to gcc 11.2 occur?
Will give the testing version a shot, but not today anymore.
Last edited by tcn (2022-02-22 10:48:27)
Offline
The update did first fully appear with .24 though there were relevant rebuilds (identified by the -2 in the pkgrel) for .23 and .22 but not sure whether those ever landed on stable or were just on testing.
Offline
Looks like -2 is already in stable. Is it confirmed to be a fix or still the attempt of one?
Offline
Be part of the solution and test it, since you are affected. I don't use NFS so I can't give you clear information here, according to the linked bug report it is fixed for at least the person reporting the issue.
Offline