Upgrade Warning -- kernel 5.13.3-1 may break networking

[Carnophage]

OK, it's been a while since I had to debug such issues, does anyone have any hints where to look - what can affect modules loaded at OS start, any kernel/systemd/boot flags that might make things more verbose?

[unklarer]

There seems to be no loading of the modules with the 5.13's here either.
lsmod | grep vfat has no output
Manually via dolphin it tells me:

Beim Zugriff auf ,,98,6 GiB Festplatte" ist ein Fehler aufgetreten, die Meldung lautet: Die angegebene Operation ist fehlgeschlagen: Error mounting system-managed device /dev/sda6: unknown filesystem type 'vfat'

also mount /dev/sda6 /mnt says that.

this and this does not help.

[cs]

Hello again,

unfortunately my problems persist with the updated kernel:

Code Auswählen Erweitern

Linux x13-cord 5.13.3-3-siduction-amd64 #1 SMP PREEMPT siduction 5.13-3.2 (2021-07-20) x86_64 GNU/Linux

I still cannot use my external usb sound card.

And yes: I have luks encrypted data partition and cache.

[jure]

Again, not reproducable.

ANd btw, what does happen, if you modprobe nfs?

manually modprobe nfs and modprobe nfsv4 works and I can mount the NAS nfs sahres.

But the modules are not loaded automaticlly, what they do with the former kernels.

[cs]

Zitat von: cs am Gestern um 06:46:54

    Hello,

    unfortunately, with kernel 5.13.3-2 my external Sound Card Steinberg UR22C no longer works. (It didn't work with 5.13.3-1 either, but it did work flawlessly with kernel 5.12).

    uname -r

    5.13.3-2-siduction-amd64

    dmesg gives me the following error output:

    ] xhci_hcd 0000:05:00.0: firmware: failed to load renesas_usb_fw.mem (-2)
    [    1.259457] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
    [    1.259466] xhci_hcd 0000:05:00.0: Direct firmware load for renesas_usb_fw.mem failed with error -2

See Bugreport on lkml

https://lkml.org/lkml/2021/7/16/794

Please excuse my ingenuity: Can I fix this myself?

Guess I'd have du build my own kernel including the fix found under https://lkml.org/lkml/2021/7/16/794

I don't trust myself building kernels ...

[towo]

That lkml report has nothing to do with your problem.
No clue why micha7 points to it.

[devil]

Please excuse my ingenuity: Can I fix this myself?

Just use 5,12.x until the problem is sorted out. Up to now it is pretty mysterious, but in time we will get to the bottom of it.

[jure]

manually modprobe nfs and modprobe nfsv4 works and I can mount the NAS nfs sahres.

But the modules are not loaded automatically, what they do with the former kernels.

no improvement with 5.13.4-1 in relation to nfs modules not loaded

[towo]

Automatic module loading is not a kernel job, it's the job for the system, here especialy systemd.

[jure]

yes, but why are these modules not loaded only with kernel 5.13...up to 5.12 I have had no problems - hmm

[towo]

I don't know, all modules are there. The config between 5.12 and 5.13 has nothing deactivated, which would prevent modules from load.
I would also like to ask you, if you can test the linked iso, if it is working.

[jure]

I have shortly tested the iso, it works so far, network/internet is up. But of course I couldn't test if nfs modules would be loaded,  because there are no mounted shares ... but on my system I have no problems with network, only with nfs (modules) with Kernel 5.13...

[towo]

Any messages in

Code Auswählen Erweitern

journalctl -b | grep -i nfs
?

[jure]

fresh reboot with 5.13.4-1

journalctl -b | grep -i nfs
Jul 20 22:17:46 siductionbox systemd[1]: Dependency failed for RPC security service for NFS server.
Jul 20 22:17:46 siductionbox systemd[1]: Dependency failed for RPC security service for NFS client and server.
Jul 20 22:17:46 siductionbox systemd[1]: Reached target NFS client services.
Jul 20 22:17:47 siductionbox systemd[1]: Starting Preprocess NFS configuration...
Jul 20 22:17:47 siductionbox systemd[1]: nfs-config.service: Succeeded.
Jul 20 22:17:47 siductionbox systemd[1]: Finished Preprocess NFS configuration.
Jul 20 22:18:03 siductionbox mount[1955]: mount.nfs4: No such device
Jul 20 22:18:03 siductionbox mount[1966]: mount.nfs4: No such device
Jul 20 22:18:08 siductionbox mount[2503]: mount.nfs4: No such device
Jul 20 22:18:08 siductionbox mount[2506]: mount.nfs4: No such device
Jul 20 22:18:08 siductionbox mount[2509]: mount.nfs4: No such device

then after modprobe nfs and nfsv4

Jul 20 22:18:49 siductionbox kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jul 20 22:18:49 siductionbox kernel: FS-Cache: Netfs 'nfs' registered for caching
Jul 20 22:18:53 siductionbox kernel: NFS: Registering the id_resolver key type

edit:
fresh reboot with 5.12.17-1 - nfs modules are loaded and shares are mounted automatically.

journalctl -b | grep -i nfs
Jul 20 22:25:11 siductionbox kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jul 20 22:25:12 siductionbox systemd[1]: Starting Preprocess NFS configuration...
Jul 20 22:25:12 siductionbox systemd[1]: nfs-config.service: Succeeded.
Jul 20 22:25:12 siductionbox systemd[1]: Finished Preprocess NFS configuration.
Jul 20 22:25:12 siductionbox systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Jul 20 22:25:12 siductionbox systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Jul 20 22:25:12 siductionbox systemd[1]: Reached target NFS client services.
Jul 20 22:25:32 siductionbox kernel: FS-Cache: Netfs 'nfs' registered for caching
Jul 20 22:25:32 siductionbox kernel: NFS: Registering the id_resolver key type

[towo]

Can you paste

Code Auswählen Erweitern

inxi -S -xxx

please, all involved in that thread schould do that, if not already done.

And btw, i would like to see the fstab from the systems with the failures.