Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: Upgrade Warning -- kernel 5.13.3-1 may break networking  (Read 4165 times)

Online charlyheinz

  • User
  • Posts: 35
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #30 on: 2021/07/20, 11:10:00 »
after DU and  kernelupdate (5.13.3-2-siduction-amd64) this morning everything is working properly:
Audio is working as expected, even with an scarlett USB- Interface too.
Network is running with a LAN- printer, internet-connection and NAS.
Quote
uname -r
5.13.3-2-siduction-amd64
aplay -l
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC898 Analog [ALC898 Analog]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: PCH [HDA Intel PCH], Gerät 1: ALC898 Digital [ALC898 Digital]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 2: NVidia [HDA NVidia], Gerät 3: HDMI 0 [HDMI 0]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 2: NVidia [HDA NVidia], Gerät 7: HDMI 1 [HDMI 1]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 2: NVidia [HDA NVidia], Gerät 8: HDMI 2 [HDMI 2]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 2: NVidia [HDA NVidia], Gerät 9: HDMI 3 [HDMI 3]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 2: NVidia [HDA NVidia], Gerät 10: HDMI 4 [HDMI 4]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 2: NVidia [HDA NVidia], Gerät 11: HDMI 5 [HDMI 5]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 2: NVidia [HDA NVidia], Gerät 12: HDMI 6 [HDMI 6]
  Sub-Geräte: 1/1

Offline Carnophage

  • User
  • Posts: 36
    • http://carnophage.wordpress.com
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #31 on: 2021/07/20, 11:58:36 »
Can someone of you, who have problems test that iso:

http://testbuilds.siduction.org/plasma/siduction-future-plasma-amd64-latest.iso

???

I want to know, if a clean setup wit kernel 5.13.x is working for you.

In my case, wifi works without issues when booted on the same laptop from this iso on a pendrive.
And systemctl --failed only shows fll-xdm.service

Interesting. Any particular set of logs/checks would help to narrow down the problem?
« Last Edit: 2021/07/20, 12:19:28 by Carnophage »

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.152
    • Land of the Buckeye
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #32 on: 2021/07/20, 12:24:48 »
This morning I installed the new 5.13.3-3.  It seems that networking and usb mounts are still a problem.  To compare kernels:

NETWORKING

With 5.13.3-3:

Code: [Select]
● networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2021-07-20 05:59:54 EDT; 4min 17s ago
       Docs: man:interfaces(5)
    Process: 835 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
   Main PID: 835 (code=exited, status=1/FAILURE)
        CPU: 27ms

Jul 20 05:59:53 Hibiscus systemd[1]: Starting Raise network interfaces...
Jul 20 05:59:54 Hibiscus ifup[929]: add bridge failed: Package not installed
Jul 20 05:59:54 Hibiscus ifup[925]: run-parts: /etc/network/if-pre-up.d/bridge exited with return code 1
Jul 20 05:59:54 Hibiscus ifup[835]: ifup: failed to bring up br0
Jul 20 05:59:54 Hibiscus systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Jul 20 05:59:54 Hibiscus systemd[1]: networking.service: Failed with result 'exit-code'.
Jul 20 05:59:54 Hibiscus systemd[1]: Failed to start Raise network interfaces.


With 5.12.16-1:

Code: [Select]
● networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
     Active: active (exited) since Tue 2021-07-20 06:12:13 EDT; 5min ago
       Docs: man:interfaces(5)
    Process: 848 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
   Main PID: 848 (code=exited, status=0/SUCCESS)
      Tasks: 4 (limit: 38416)
     Memory: 7.0M
        CPU: 233ms
     CGroup: /system.slice/networking.service
             └─6171 /sbin/dhclient -4 -v -i -pf /run/dhclient.br0.pid -lf /var/lib/dhcp/dhclient.br0.leases -I -df /var/l>

Jul 20 06:12:13 Hibiscus dhclient[6171]: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 5
Jul 20 06:12:13 Hibiscus ifup[6171]: DHCPOFFER of 10.120.31.129 from 10.120.31.47
Jul 20 06:12:13 Hibiscus ifup[6171]: DHCPREQUEST for 10.120.31.129 on br0 to 255.255.255.255 port 67
Jul 20 06:12:13 Hibiscus dhclient[6171]: DHCPOFFER of 10.120.31.129 from 10.120.31.47
Jul 20 06:12:13 Hibiscus dhclient[6171]: DHCPREQUEST for 10.120.31.129 on br0 to 255.255.255.255 port 67
Jul 20 06:12:13 Hibiscus dhclient[6171]: DHCPACK of 10.120.31.129 from 10.120.31.47
Jul 20 06:12:13 Hibiscus ifup[6171]: DHCPACK of 10.120.31.129 from 10.120.31.47
Jul 20 06:12:13 Hibiscus dhclient[6171]: bound to 10.120.31.129 -- renewal in 36777 seconds.
Jul 20 06:12:13 Hibiscus ifup[6171]: bound to 10.120.31.129 -- renewal in 36777 seconds.
Jul 20 06:12:13 Hibiscus systemd[1]: Finished Raise network interfaces.


USB Thumb Drive:

With 5.13.3-3:

Code: [Select]
[  417.695521] usb 2-8: new high-speed USB device number 5 using xhci_hcd
[  417.822444] usb 2-8: New USB device found, idVendor=0781, idProduct=5583, bcdDevice= 1.00
[  417.822467] usb 2-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  417.822473] usb 2-8: Product: Ultra Fit
[  417.822477] usb 2-8: Manufacturer: SanDisk
[  417.822480] usb 2-8: SerialNumber: 4C530001221215119072
[  417.834073] usb-storage 2-8:1.0: USB Mass Storage device detected
[  417.834285] scsi host16: usb-storage 2-8:1.0
[  417.834346] usbcore: registered new interface driver usb-storage
[  417.835147] usbcore: registered new interface driver uas
[  418.846896] scsi 16:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
[  418.847201] sd 16:0:0:0: Attached scsi generic sg5 type 0
[  418.847471] sd 16:0:0:0: [sdd] 121438208 512-byte logical blocks: (62.2 GB/57.9 GiB)
[  418.848365] sd 16:0:0:0: [sdd] Write Protect is off
[  418.848371] sd 16:0:0:0: [sdd] Mode Sense: 43 00 00 00
[  418.848815] sd 16:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  418.900849]  sdd: sdd1
[  418.915645] sd 16:0:0:0: [sdd] Attached SCSI removable disk

But when I try to mount it:

Code: [Select]
[  423.783096] FAT-fs (sdd1): codepage cp437 not found
[  433.719133] FAT-fs (sdd1): codepage cp437 not found
[  446.726158] FAT-fs (sdd1): codepage cp437 not found


With 5.12.16-1:

Code: [Select]
[   72.590184] usb 2-7: new high-speed USB device number 5 using xhci_hcd
[   72.717133] usb 2-7: New USB device found, idVendor=0781, idProduct=5583, bcdDevice= 1.00
[   72.717145] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   72.717151] usb 2-7: Product: Ultra Fit
[   72.717155] usb 2-7: Manufacturer: SanDisk
[   72.717159] usb 2-7: SerialNumber: 4C530001221215119072
[   72.732302] usb-storage 2-7:1.0: USB Mass Storage device detected
[   72.732418] scsi host16: usb-storage 2-7:1.0
[   72.732484] usbcore: registered new interface driver usb-storage
[   72.733220] usbcore: registered new interface driver uas
[   73.765853] scsi 16:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
[   73.766481] sd 16:0:0:0: Attached scsi generic sg5 type 0
[   73.766720] sd 16:0:0:0: [sdd] 121438208 512-byte logical blocks: (62.2 GB/57.9 GiB)
[   73.767660] sd 16:0:0:0: [sdd] Write Protect is off
[   73.767668] sd 16:0:0:0: [sdd] Mode Sense: 43 00 00 00
[   73.768039] sd 16:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   73.818268]  sdd: sdd1
[   73.819433] sd 16:0:0:0: [sdd] Attached SCSI removable disk

and then I can mount it.

I don't understand the issue with my network bridge -- "Package not installed."  Is there something new with bridged networks?
« Last Edit: 2021/07/20, 12:52:50 by dibl »
Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO, 2@WD2003FZEX in BTRFS

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.538
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #33 on: 2021/07/20, 13:19:58 »
Dibl, what i do not understand, why your system is using ifupdown still?
And your USB problem seems even not kernel related.

Here:

Code: [Select]
[Di Jul 20 13:21:54 2021] usb 1-3: new high-speed USB device number 2 using xhci_hcd
[Di Jul 20 13:21:54 2021] usb 1-3: New USB device found, idVendor=ffff, idProduct=5678, bcdDevice= 2.00
[Di Jul 20 13:21:54 2021] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Di Jul 20 13:21:54 2021] usb 1-3: Product: Disk 2.0
[Di Jul 20 13:21:54 2021] usb 1-3: Manufacturer: USB
[Di Jul 20 13:21:54 2021] usb 1-3: SerialNumber: 9207316297209129120
[Di Jul 20 13:21:55 2021] usb-storage 1-3:1.0: USB Mass Storage device detected
[Di Jul 20 13:21:55 2021] scsi host2: usb-storage 1-3:1.0
[Di Jul 20 13:21:55 2021] usbcore: registered new interface driver usb-storage
[Di Jul 20 13:21:55 2021] usbcore: registered new interface driver uas
[Di Jul 20 13:21:56 2021] scsi 2:0:0:0: Direct-Access     VendorCo ProductCode      2.00 PQ: 0 ANSI: 4
[Di Jul 20 13:21:56 2021] sd 2:0:0:0: Attached scsi generic sg2 type 0
[Di Jul 20 13:21:56 2021] sd 2:0:0:0: [sdc] 61440000 512-byte logical blocks: (31.5 GB/29.3 GiB)
[Di Jul 20 13:21:56 2021] sd 2:0:0:0: [sdc] Write Protect is off
[Di Jul 20 13:21:56 2021] sd 2:0:0:0: [sdc] Mode Sense: 03 00 00 00
[Di Jul 20 13:21:56 2021] sd 2:0:0:0: [sdc] No Caching mode page found
[Di Jul 20 13:21:56 2021] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[Di Jul 20 13:21:56 2021]  sdc: sdc1 sdc2
[Di Jul 20 13:21:56 2021] sd 2:0:0:0: [sdc] Attached SCSI removable disk

Code: [Select]
pmount /dev/sdc2
/dev/sdc2 on /media/sdc2 type vfat (rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1005,fmask=0177,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,quiet,utf8,errors=remount-ro,user)

Code: [Select]
towo@lenovo:~$ uname -a
Linux lenovo 5.13.3-3-siduction-amd64 #1 SMP PREEMPT siduction 5.13-3.2 (2021-07-20) x86_64 GNU/Linux
« Last Edit: 2021/07/20, 13:28:08 by towo »
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.152
    • Land of the Buckeye
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #34 on: 2021/07/20, 13:34:06 »
Quote from: towo
...why your system is using ifupdown still?

Hmmmmm. Well, I built this system in 2014, and I have kept it updated, but if something didn't break, then I didn't change it. I use bridge-utils -- does it pull in ifupdown?  Can I purge ifupdown with no damage to the bridge?
Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO, 2@WD2003FZEX in BTRFS

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.538
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #35 on: 2021/07/20, 13:39:58 »
I can't remember, ifupdown was obsolete since a long time.
Nowdays my Network here is configured with systemd-networkd. There is have configured my bridge for qemu.

But, ifupdown is not the case for your usb problems, which i can't reproduce here on my 3 systems, i have available.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.152
    • Land of the Buckeye
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #36 on: 2021/07/20, 13:48:24 »
Here is my interface configuration, which works good for kernels before 5.13.3:

Code: [Select]
# The loopback network interface
auto lo br0
iface lo inet loopback

iface enp6s0 inet dhcp

# Bridge setup
iface br0 inet dhcp
   bridge_ports enp6s0


I found the guidance to change to systemd-networkd here:  https://wiki.debian.org/SystemdNetworkd

I will give that a try.

Is there anything special to know to configure the bridge?   Thanks!
Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO, 2@WD2003FZEX in BTRFS

Offline jure

  • User
  • Posts: 615
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #37 on: 2021/07/20, 13:52:02 »
also with kernel 5.13.3-3 my nfs shares are not mounted. When try it manually I got

Code: [Select]
mount -t nfs 192.168.2.60:/volume1/daten /media/daten-nas/
mount.nfs: No such device

As I said, no problems with earlier kernels than 5.13....


Edit
network also still with ifup/down: with 5.13.3-3
Code: [Select]
systemctl status networking.service
● networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
     Active: active (exited) since Tue 2021-07-20 13:27:31 CEST; 25min ago
       Docs: man:interfaces(5)
    Process: 913 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
   Main PID: 913 (code=exited, status=0/SUCCESS)
      Tasks: 4 (limit: 18983)
     Memory: 114.7M
        CPU: 266ms
     CGroup: /system.slice/networking.service
             └─1014 /sbin/dhclient -4 -v -i -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhcp/dhclient6.eth0.leases >

Jul 20 13:27:29 siductionbox ifup[1014]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jul 20 13:27:29 siductionbox dhclient[1014]: DHCPOFFER of 192.168.2.25 from 192.168.2.1
Jul 20 13:27:29 siductionbox ifup[1014]: DHCPOFFER of 192.168.2.25 from 192.168.2.1
Jul 20 13:27:29 siductionbox ifup[1014]: DHCPREQUEST for 192.168.2.25 on eth0 to 255.255.255.255 port 67
Jul 20 13:27:29 siductionbox dhclient[1014]: DHCPREQUEST for 192.168.2.25 on eth0 to 255.255.255.255 port 67
Jul 20 13:27:29 siductionbox dhclient[1014]: DHCPACK of 192.168.2.25 from 192.168.2.1
Jul 20 13:27:29 siductionbox ifup[1014]: DHCPACK of 192.168.2.25 from 192.168.2.1
Jul 20 13:27:31 siductionbox dhclient[1014]: bound to 192.168.2.25 -- renewal in 336141 seconds.
Jul 20 13:27:31 siductionbox ifup[1014]: bound to 192.168.2.25 -- renewal in 336141 seconds.
Jul 20 13:27:31 siductionbox systemd[1]: Finished Raise network interfaces.



« Last Edit: 2021/07/20, 13:58:06 by jure »
Gruss Juergen

Offline michaa7

  • User
  • Posts: 2.150
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #38 on: 2021/07/20, 13:52:26 »
Quote
I want to know, if a clean setup wit kernel 5.13.x is working for you.

I booted fromiso:

Seems to work, but there was one red "Failed" message during boot, which I could not read because it scolled by too fast. I tried three times. ;-). Didn't show up in dmesg or journalctl.

Regarding the errors on my main installation:
I found all the rpc errors on my installation with the *working* kernel 5.12.16, too. So they seem unrelated to the malfunction.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.538
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #39 on: 2021/07/20, 13:57:34 »
I even followed a howto from the net.
Here is my config:

Code: [Select]
cat /etc/systemd/network/eth.network
[Match]
Name=enp*
[Network]
Bridge=bri0

Code: [Select]
cat /etc/systemd/network/bridge.network
[Match]
Name=bri0
[Network]
Gateway=192.168.178.1
Address=192.168.178.10/24
LinkLocalAddressing=no
IPv6AcceptRA=false

Code: [Select]
cat /etc/systemd/network/bridge.netdev
[NetDev]
Name=bri0
Kind=bridge

That setting i use since long time without any problem.
Installed i have here:

bridge-utils
uml-utilities

In qemu the i set

Code: [Select]
USERID=towo
INTERFACE=$(sudo /usr/bin/tunctl -b -u $USERID -t tap2)
sudo brctl addif bri0 $INTERFACE
sudo ip link set "$INTERFACE" master "bri0" up

All is working fine since ages. No Problems here, even with lernel 5.14-rc2.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.538
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #40 on: 2021/07/20, 13:59:59 »
Quote
I found all the rpc errors on my installation with the *working* kernel 5.12.16, too. So they seem unrelated to the malfunction.

They shouldn't! And they do not show on all my systems here, no matter, which kernel i use here.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline Carnophage

  • User
  • Posts: 36
    • http://carnophage.wordpress.com
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #41 on: 2021/07/20, 14:12:20 »
So in my case, it looks like there is quite a big difference between loaded modules between 5.12 and 5.13 (attached, sorted for easier diffing) + paste from iso http://paste.debian.net/hidden/2d48cf05

Manually loading iwlmvm results in wifi interface showing up, but it has some issues with password, didn't have time to debug it further for now.

Offline michaa7

  • User
  • Posts: 2.150
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #42 on: 2021/07/20, 14:27:57 »
New Kernel 5.13.3-3

Still rpc and ELF failed warnings during boot, but all (I need) is working.

wmmixer finds only one of three sound cards (which may be is a progress as I had to configure all three soundcards, because otherwise it would pick the first soundcard it founds ... which may not be the one actually used. Now with kernel 5.13.x only the active one shows up in wmmixer (although it is configured for all three soundcards) which so far seems ok, but not sure ....)

Obvioulsly I have sound with 5.13.3-3 which was lacking with 5.13.1-2.

Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline jure

  • User
  • Posts: 615
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #43 on: 2021/07/20, 14:38:13 »
Quote from: Carnophage
So in my case, it looks like there is quite a big difference between loaded modules between 5.12 and 5.13...

the same here, with 5.13.3.. no nfs* modules are loaded, with 5.12.... there are nfs, nfsv4, nfs_ssc

So in my case - no nfs modules no nfs mount ..
Gruss Juergen

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.538
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #44 on: 2021/07/20, 14:47:05 »
Code: [Select]
towo@lenovo:~$ lsmod | grep nfs
nfsv4                 868352  0
nfs                   405504  1 nfsv4
lockd                 106496  1 nfs
fscache               401408  1 nfs
sunrpc                630784  6 nfsv4,auth_rpcgss,lockd,rpcsec_gss_krb5,nfs

Again, not reproducable.

ANd btw, what does happen, if you modprobe nfs?
« Last Edit: 2021/07/20, 14:52:15 by towo »
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.