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 5835 times)

Offline jure

  • User
  • Posts: 635
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #60 on: 2021/07/20, 22:50:21 »
Quote
inxi -S -xxx
System:    Host: siductionbox Kernel: 5.13.4-1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
           Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 wm: kwin_x11 dm: LightDM 1.26.0 Distro: Debian GNU/Linux 11 (bullseye)
           base: Debian GNU/Linux 11 (bullseye)

edit:

and the entries in fstab related to my nfs problem are like this, and this has been working except with 5.13...
Quote
192.168.2.60:/volume1/software    /media/software-nas  nfs4  noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd
.idle-timeout=1min 0 0
« Last Edit: 2021/07/20, 22:56:20 by jure »
Gruss Juergen

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.638
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #61 on: 2021/07/20, 23:03:37 »
Why you have

Code: [Select]
timeo=14,x-systemd.idle-timeout=1min
that looks wrong to me.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline michaa7

  • User
  • Posts: 2.193
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #62 on: 2021/07/20, 23:11:45 »
Quote
$ inxi -S -xxx
System:    Host: neutower Kernel: 5.12.16-1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Fluxbox 1.3.5
           dm: SDDM Distro: siduction 18.2.0 Patience - xorg - (201803080008) base: Debian GNU/Linux 11 (bullseye)


Quote
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=655268bd-541f-4863-a960-951dc0cdcb46 /              ext4    defaults,noatime 0 1

LABEL=v64       /var    ext4    defaults,noatime        0       2
LABEL=debarch   /var/cache/apt/archives ext4    defaults,noatime        0       2
LABEL=aptc      /var/cache/apt-cacher-ng        ext4    defaults,noatime        0       2

LABEL=h1601     /home   ext4     defaults,noatime       0       2

LABEL=musik     /dtn/musik      ext4    defaults,noatime        0       0
#LABEL=musik2     /dtn/musik2      ext4    defaults,noatime        0       0
LABEL=vid       /dtn/vid        ext4    defaults,noatime        0       0
LABEL=soft_alt /dtn/soft_alt        ext4    defaults,noatime        0       0
LABEL=archiv    /dtn/archiv     ext4    defaults,noatime        0       0
LABEL=rec       /dtn/rec        ext4    defaults,noatime        0       0

... and my external USB-TV-Card does not work with kernel 5.13.x
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline jure

  • User
  • Posts: 635
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #63 on: 2021/07/20, 23:14:42 »
to be honest, I don`t know exactly - but this did not make problems up to now, and after manually loading the nfs modules and mount -a (only with 5.13..), all nfs shares are mounted.
With 5.12.. and earlier everything is done automatically as expected.
Gruss Juergen

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.638
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #64 on: 2021/07/20, 23:23:00 »
Code: [Select]
... and my external USB-TV-Card does not work with kernel 5.13.xAnd that secret card is?
It has worked with 5.12?
ANd other problems around?
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline michaa7

  • User
  • Posts: 2.193
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #65 on: 2021/07/20, 23:39:46 »
Code: [Select]
... and my external USB-TV-Card does not work with kernel 5.13.xAnd that secret card is?

Quote
Bus 001 Device 003: ID 2040:0265 Hauppauge WinTV-dualHD DVB

It has worked with 5.12?

Sure. I didn't mention it because otherwise I would not blame 5.13.x ...
ANd other problems around?
No other problems except the "Failed" messages during boot regarding rpc and ELF. And wmmixer shows only (the active-) one of three sound cards (see above).
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.638
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #66 on: 2021/07/20, 23:49:41 »
Any USB related error in dmesg or journal?
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline Carnophage

  • User
  • Posts: 38
    • http://carnophage.wordpress.com
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #67 on: 2021/07/20, 23:55:45 »
Code: [Select]
System:    Host: hal9001 Kernel: 5.12.17-1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0
           tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
           Distro: siduction 14.1.0 Indian Summer - nox - (201411230419) base: Debian GNU/Linux 11 (bullseye)

Code: [Select]
#UUID=02B26D08B26D0191                      /disks/disk1part1     ntfs   auto,users,ro,dmask=0022,fmask=0133,nls=utf8                                                 0  0
UUID=e565e8ab-2c84-4b3d-9d8e-faef717c4aea  /                     ext4   defaults,relatime,errors=remount-ro 0  1
/dev/mapper/home                           /home                 ext4   defaults,relatime   0  2
jarvis:/volume1/download                   /mnt/download-jarvis  nfs4   noauto,nofail,x-systemd.automount,x-systemd.device-timeout=10,x-systemd.idle-timeout=5min  0  0

And journal with some debug flags
Code: [Select]
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=onhttps://gist.github.com/carno/d24c5b9990a6605567d718c141d7850f

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.638
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #68 on: 2021/07/21, 01:07:31 »
Jure

I have now installed a Debian Bullseye, like you.
Then i have changed the sources to unstable, added siduction extra and fixes repos.
Then i have done a dist-upgrade and installed the siduction kernel.
After reboot, all is working as expected, my nfs mounts from fstab are mounted correctly, no errors suring boot.
I'm out of ideas, where your problems are.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline michaa7

  • User
  • Posts: 2.193
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #69 on: 2021/07/21, 01:28:53 »
Any USB related error in dmesg or journal?

none.

And according to dmesg the TV card is found:

from dmesg:
Quote
[    2.068080] usb 5-6: new high-speed USB device number 3 using ehci-pci
[    2.198143] usb 5-6: New USB device found, idVendor=2040, idProduct=0265, bcdDevice= 1.00
[    2.198153] usb 5-6: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    2.198157] usb 5-6: Product: dualHD
[    2.198160] usb 5-6: Manufacturer: HCW

Quote
lsusb
Bus 005 Device 003: ID 2040:0265 Hauppauge WinTV-dualHD DVB
...

with journalctl I am not sure what the normal behaviour is: It seems the system ***continously*** tries to resett some USB devices which causes journalctl to never stop. I have to abort it. Many massages like:


THe cable is not bad, works fine with kernel 5.12.16
Quote
Jul 16 11:25:15 neutower kernel: usb 5-6: new high-speed USB device number 3 using ehci-pci
Jul 16 11:25:15 neutower kernel: usb 5-6: New USB device found, idVendor=2040, idProduct=0265, bcdDevice= 1.00
Jul 16 11:25:15 neutower kernel: usb 5-6: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Jul 16 11:25:15 neutower kernel: usb 5-6: Product: dualHD
Jul 16 11:25:15 neutower kernel: usb 5-6: Manufacturer: HCW
Jul 16 11:25:15 neutower kernel: usb 5-6: SerialNumber: 0013969171
Jul 16 11:25:15 neutower kernel: usb 5-5.1: new low-speed USB device number 4 using ehci-pci
Jul 16 11:25:15 neutower kernel: usb 5-5.1: New USB device found, idVendor=093a, idProduct=2521, bcdDevice= 1.00
Jul 16 11:25:15 neutower kernel: usb 5-5.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
Jul 16 11:25:15 neutower kernel: usb 5-5.1: Product: USB OPTICAL MOUSE
Jul 16 11:25:15 neutower kernel: input: USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1/5-5.1:1.0/0003:093A:2521.0001/input/input3
Jul 16 11:25:15 neutower kernel: hid-generic 0003:093A:2521.0001: input,hidraw0: USB HID v1.11 Mouse [USB OPTICAL MOUSE] on usb-0000:00:1d.7-5.1/input0
Jul 16 11:25:16 neutower mtp-probe[345]: checking bus 5, device 3: "/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-6"
Jul 16 11:25:16 neutower mtp-probe[352]: checking bus 5, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1"
Jul 16 11:25:19 neutower kernel: usbcore: registered new interface driver em28xx
Jul 16 11:25:19 neutower kernel: rc rc0: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:1d.7/usb5/5-6/5-6:1.0/rc/rc0
Jul 16 11:25:19 neutower kernel: input: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:1d.7/usb5/5-6/5-6:1.0/rc/rc0/input14
Jul 16 12:13:16 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 12:13:16 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 12:13:16 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
...
Jul 16 17:28:10 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 17:28:11 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:28:11 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:28:22 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 17:28:22 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:28:23 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:28:29 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 17:28:29 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:28:29 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:28:48 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 17:28:48 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:28:48 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:28:52 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 17:28:52 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:28:52 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
...
Jul 16 17:40:51 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 17:40:51 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
...
Jul 16 17:42:42 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 17:42:42 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
...
Jul 16 17:46:49 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 17:46:49 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:46:50 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:46:53 neutower kernel: usb 5-5.1: reset low-speed USB device number 4 using ehci-pci
Jul 16 17:46:53 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:46:53 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:47:01 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:01 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:02 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:02 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:02 neutower kernel: usb 5-5-port1: Cannot enable. Maybe the USB cable is bad?
Jul 16 17:47:02 neutower kernel: usb 5-5-port1: cannot disable (err = -71)
Jul 16 17:47:02 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:03 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:03 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:03 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:03 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:03 neutower kernel: usb 5-5-port1: Cannot enable. Maybe the USB cable is bad?
Jul 16 17:47:04 neutower kernel: usb 5-5-port1: cannot disable (err = -71)
Jul 16 17:47:04 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:04 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:04 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:05 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:05 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:05 neutower kernel: usb 5-5-port1: Cannot enable. Maybe the USB cable is bad?
Jul 16 17:47:05 neutower kernel: usb 5-5-port1: cannot disable (err = -71)
Jul 16 17:47:06 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:06 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:06 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:06 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:06 neutower kernel: usb 5-5-port1: cannot reset (err = -71)
Jul 16 17:47:06 neutower kernel: usb 5-5-port1: Cannot enable. Maybe the USB cable is bad?
Jul 16 17:47:07 neutower kernel: usb 5-5-port1: cannot disable (err = -71)
Jul 16 17:47:07 neutower kernel: usb 5-5-port1: cannot disable (err = -71)
Jul 16 17:48:18 neutower kernel: usb 5-5: USB disconnect, device number 2
Jul 16 17:48:18 neutower kernel: usb 5-5.1: USB disconnect, device number 4
Jul 16 17:48:18 neutower kernel: usb 3-1: new full-speed USB device number 2 using uhci_hcd
Jul 16 17:48:18 neutower kernel: usb 3-1: device descriptor read/64, error -71
Jul 16 17:48:18 neutower kernel: usb 3-1: device descriptor read/64, error -71
Jul 16 17:48:19 neutower kernel: usb 3-1: new full-speed USB device number 3 using uhci_hcd
Jul 16 17:48:19 neutower kernel: usb 3-1: device descriptor read/64, error -71
Jul 16 17:48:19 neutower kernel: usb 3-1: device descriptor read/64, error -71
Jul 16 17:48:19 neutower kernel: usb usb3-port1: attempt power cycle
Jul 16 17:48:19 neutower kernel: usb 3-1: new full-speed USB device number 4 using uhci_hcd
Jul 16 17:48:20 neutower kernel: usb 3-1: device not accepting address 4, error -71
Jul 16 17:48:20 neutower kernel: usb 3-1: new full-speed USB device number 5 using uhci_hcd
Jul 16 17:48:20 neutower kernel: usb 3-1: device not accepting address 5, error -71
Jul 16 17:48:20 neutower kernel: usb usb3-port1: unable to enumerate USB device
Jul 16 17:48:23 neutower kernel: usb 5-5: new high-speed USB device number 6 using ehci-pci
Jul 16 17:48:23 neutower kernel: usb 5-5: device not accepting address 6, error -71
Jul 16 17:48:24 neutower kernel: usb 5-5: new high-speed USB device number 7 using ehci-pci
Jul 16 17:48:24 neutower kernel: usb 5-5: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice= 9.01
Jul 16 17:48:24 neutower kernel: usb 5-5: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Jul 16 17:48:24 neutower kernel: usb 5-5: Product: USB2.0 Hub
Jul 16 17:48:24 neutower kernel: hub 5-5:1.0: USB hub found
Jul 16 17:48:24 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5
Jul 16 17:48:24 neutower kernel: usb 5-5.1: new low-speed USB device number 8 using ehci-pci
Jul 16 17:48:24 neutower kernel: usb 5-5.1: New USB device found, idVendor=093a, idProduct=2521, bcdDevice= 1.00
Jul 16 17:48:24 neutower kernel: usb 5-5.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
Jul 16 17:48:24 neutower kernel: usb 5-5.1: Product: USB OPTICAL MOUSE
Jul 16 17:48:24 neutower kernel: input: USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1/5-5.1:1.0/0003:093A:2521.0002/input/input15
Jul 16 17:48:24 neutower kernel: hid-generic 0003:093A:2521.0002: input,hidraw0: USB HID v1.11 Mouse [USB OPTICAL MOUSE] on usb-0000:00:1d.7-5.1/input0
Jul 16 17:48:24 neutower mtp-probe[105291]: checking bus 5, device 8: "/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1"
Jul 16 17:48:24 neutower upowerd[3575]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1
Jul 16 17:48:24 neutower mtp-probe[105304]: checking bus 5, device 8: "/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-5/5-5.1"
Jul 16 17:48:26 neutower kernel: usb 5-5: USB disconnect, device number 7

will compare with 5.12.16 .... moment ...

EDIT:

I don't have those error messages in 5.12.16

n8

« Last Edit: 2021/07/21, 01:41:33 by michaa7 »
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline cs

  • User
  • Posts: 89
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #70 on: 2021/07/21, 09:50:08 »
Here we go:

inxi -S -xxx

Quote
System:    Host: x13-cord Kernel: 5.13.4-1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: KDE Plasma 5.22.3
           tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: siduction 18.3.0 Patience - kde - (202007152027)
           base: Debian GNU/Linux 11 (bullseye)

dmesg errors

Quote
[    1.216770] piix4_smbus 0000:00:14.0: SMBus region 0xb20 already in use!

Quote
[    1.227068] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[    1.227093] xhci_hcd 0000:05:00.0: Direct firmware load for renesas_usb_fw.mem failed with error -2
[    1.227096] xhci_hcd 0000:05:00.0: request_firmware failed: -2

Quote
[   11.765529] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-63.ucode (-2)
[   11.765539] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-63.ucode failed with error -2
[   11.766780] iwlwifi 0000:03:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-62.ucode
[   11.766799] iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver
[   11.766815] iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[   11.767246] iwlwifi 0000:03:00.0: loaded firmware version 62.49eeb572.0 cc-a0-62.ucode op_mode iwlmvm
[   11.767281] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)

Quote
[   12.020878] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517

Quote
[   12.865444] bluetooth hci0: firmware: failed to load intel/ibt-20-0-0.sfi (-2)

Quote
[   14.517915] usbcore: registered new interface driver snd-usb-audio
[   15.199490] BUG: kernel NULL pointer dereference, address: 0000000000000000
[   15.199500] #PF: supervisor instruction fetch in kernel mode
[   15.199504][   15.199490] BUG: kernel NULL pointer dereference, address: 0000000000000000
[   15.199500] #PF: supervisor instruction fetch in kernel mode
[   15.199504] #PF: error_code(0x0010) - not-present page
[   15.199509] PGD 0 P4D 0
[   15.199515] Oops: 0010 [#1] PREEMPT SMP NOPTI
[   15.199520] CPU: 7 PID: 3906 Comm: tpacpi-bat Tainted: G           O      5.13.4-1-siduction-amd64 #1 siduction 5.13-4
[   15.199527] Hardware name: LENOVO 20UGS00800/20UGS00800, BIOS R1CET63W(1.32 ) 04/09/2021
[   15.199531] RIP: 0010:0x0
[   15.199541] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   15.199544] RSP: 0018:ffffc90001d23e98 EFLAGS: 00010246
[   15.199549] RAX: 0000000000000000 RBX: ffff888104eea600 RCX: 0000000000000001
[   15.199553] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff88811ff54300
[   15.199557] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   15.199560] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   15.199563] R13: ffffffffffffffea R14: ffff88811ff54300 R15: 0000000000000000
[   15.199567] FS:  00007fd49c79d280(0000) GS:ffff8883ff7c0000(0000) knlGS:0000000000000000
[   15.199572] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   15.199576] CR2: ffffffffffffffd6 CR3: 000000011ddee000 CR4: 0000000000350ee0
[   15.199580] Call Trace:
[   15.199584]  proc_reg_llseek+0x45/0x80
[   15.199594]  ksys_lseek+0x7d/0xb0
[   15.199601]  do_syscall_64+0x61/0x80
[   15.199609]  ? syscall_exit_to_user_mode+0x12/0x40
[   15.199614]  ? do_syscall_64+0x6e/0x80
[   15.199620]  ? asm_exc_page_fault+0x8/0x30
[   15.199625]  ? exit_to_user_mode_prepare+0x1d/0x1d0
[   15.199633]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   15.199641] RIP: 0033:0x7fd49c9b1647
[   15.199646] Code: ff ff ff ff c3 66 0f 1f 44 00 00 48 8b 15 79 99 00 00 f7 d8 64 89 02 b8 ff ff ff ff eb b8 0f 1f 44 00 00 b8 08 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 51 99 00 00 f7 d8 64 89 02 48
[   15.199652] RSP: 002b:00007ffe95d5c5f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
[   15.199657] RAX: ffffffffffffffda RBX: 0000556041235e80 RCX: 00007fd49c9b1647
[   15.199661] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000003
[   15.199664] RBP: 0000556042a2bfd0 R08: 00007ffe95d5c5a0 R09: 00000000ffffffff
[   15.199667] R10: 00007fd49c997b80 R11: 0000000000000246 R12: 0000556042a0b2a0
[   15.199671] R13: 00007ffe95d5c7f0 R14: 0000556042a0b3f0 R15: 0000556042adc4e0
[   15.199677] Modules linked in: acpi_call(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cmac bnep cpufreq_userspace cpufreq_conservative cpufreq_powersave binfmt_misc snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc btusb btrtl btbcm btintel bluetooth snd_soc_dmic snd_acp3x_rn snd_acp3x_pdm_dma intel_rapl_msr snd_soc_core snd_compress snd_pcm_dmaengine ac97_bus intel_rapl_common iwlmvm snd_ctl_led snd_hda_codec_realtek mac80211 edac_mce_amd libarc4 snd_hda_codec_generic snd_hda_codec_hdmi iwlwifi snd_hda_intel nls_utf8 snd_intel_dspcfg kvm_amd snd_hda_codec thinkpad_acpi joydev nls_cp437 snd_hda_core snd_hwdep vfat kvm fat snd_rn_pci_acp3x nvram pcspkr serio_raw wmi_bmof platform_profile snd_pcm irqbypass k10temp snd_pci_acp3x cfg80211 ledtrig_audio snd_timer tpm_tis tpm_tis_core ucsi_acpi snd typec_ucsi soundcore tpm ipmi_devintf roles typec rfkill ac rng_core ipmi_msghandler evdev acpi_cpufreq
[   15.199788]  vmwgfx msr parport_pc ppdev lp parport fuse configfs sunrpc ip_tables x_tables hid_microsoft raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod hid_generic amdgpu iommu_v2 gpu_sched i2c_algo_bit rtsx_pci_sdmmc drm_ttm_helper mmc_core ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci r8169 xhci_pci_renesas psmouse realtek rtsx_pci drm mdio_devres i2c_piix4 xhci_hcd ehci_pci mfd_core ehci_hcd libphy wmi battery video i2c_scmi i2c_designware_platform i2c_designware_core button
[   15.199885] CR2: 0000000000000000
[   15.199890] ---[ end trace 90e12b0725640ad2 ]---
[   15.199894] RIP: 0010:0x0
[   15.199901] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   15.199905] RSP: 0018:ffffc90001d23e98 EFLAGS: 00010246
[   15.199909] RAX: 0000000000000000 RBX: ffff888104eea600 RCX: 0000000000000001
[   15.199913] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff88811ff54300
[   15.199917] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   15.199920] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   15.199924] R13: ffffffffffffffea R14: ffff88811ff54300 R15: 0000000000000000
[   15.199927] FS:  00007fd49c79d280(0000) GS:ffff8883ff7c0000(0000) knlGS:0000000000000000
[   15.199932] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   15.199936] CR2: ffffffffffffffd6 CR3: 000000011ddee000 CR4: 0000000000350ee0

Quote
[   19.180129] show_signal_msg: 25 callbacks suppressed
[   19.180137] pipewire-media-[8341]: segfault at 50 ip 0000000000000050 sp 00007ffe0b3288b8 error 14 in pipewire-media-session[5587ab55d000+1a000]

The external sound card that does not work with kernel 5.13 but does with kernel 5.12:

lsusb

Quote
Bus 006 Device 010: ID 0499:172f Yamaha Corp. Steinberg UR22C

Offline jure

  • User
  • Posts: 635
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #71 on: 2021/07/21, 10:46:08 »
hi towo

thx for your efforts !

the question for me is, why is systemd reporting these problems after reboot only with 5.13..  and then nfs mounting fails > mount.nfs4: No such device

what does that mean "Dependency failed for RPC security service for NFS client and server"

Quote
journalctl -b | grep -i nfs
Jul 21 09:58:53 siductionbox systemd[1]: Dependency failed for RPC security service for NFS client and server.
Jul 21 09:58:53 siductionbox systemd[1]: Dependency failed for RPC security service for NFS server.
Jul 21 09:58:53 siductionbox systemd[1]: Reached target NFS client services.
Jul 21 09:58:54 siductionbox systemd[1]: Starting Preprocess NFS configuration
Jul 21 09:58:54 siductionbox systemd[1]: nfs-config.service: Succeeded.
Jul 21 09:58:54 siductionbox systemd[1]: Finished Preprocess NFS configuration.
Jul 21 09:59:11 siductionbox mount[1946]: mount.nfs4: No such device
...


No dependency error after booting with 5.12... and nfs mounts are done without problems
Here "kernel: RPC: Registered tcp NFSv4.1 backchannel transport module." is in first place (which is missing when booting with 5.13...) and then "Starting Preprocess NFS configuration."
Quote
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


Gruss Juergen

Offline titan

  • User
  • Posts: 273
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #72 on: 2021/07/21, 12:20:12 »
With today's kernel I also get the RPC error  but more importantly

Failed to mount  /boot/efi      with error message does not recognise VFAT file system.

I don't know if this is linked to other error

Dependency failed for local file systems
failed to mount Arbitrary Executable File Format File System

It still boots OK into  5.12.17-1

Offline unklarer

  • User
  • Posts: 675
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #73 on: 2021/07/21, 13:16:21 »
For me, the dilemma with kernel's 5.13 also persists. Where I also agree with towo that this is not due to the kernel. With me desktop system:

Code: [Select]
inxi -Sxxx
System:    Host: sidukde Kernel: 5.12.17-1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
           Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 wm: kwin_x11 dm: LightDM 1.26.0
           Distro: siduction 16.1.0 Patience - kde - (201702251051) base: Debian GNU/Linux 11 (bullseye)

Code: [Select]
# <file system>                           <mount point>  <type>  <options>  <dump>  <pass>
UUID=045398f2-dfbc-4cc5-99c5-dca098051969 swap           swap    defaults,noatime,nofail 0       0
UUID=ef032757-1572-40fc-902f-1264499961a4 /              ext4    defaults,noatime 0       1
UUID=C61C-895C                            /media/DATEN   vfat    auto,nofail,uid=1000,gid=1000,rw,quiet,umask=0000,shortname=mixed,iocharset=utf8   0    0   
UUID=6EDE-B072                            /media/Distris vfat    noauto,nofail,uid=1000,gid=1000,rw,quiet,umask=0000,shortname=mixed,iocharset=utf8   0    0


The only noticeable thing is that all users involved here use an older installation, which was kept up to date in the years until today.

In contrast, the Farewell-Test installation on a laptop of mine has no errors, although a vfat file system must also be mounted there!

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.206
    • Land of the Buckeye
Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
« Reply #74 on: 2021/07/21, 13:20:00 »
Regarding the problem of USB thumb drive not mounting, I made a small discovery that may be relevant to other problems with the 5.13 series of kernels. This problem still exists with the new kernel 5.13.4-1, which I installed.

The vfat module is correctly built and saved in the correct location under /lib/modules/. But the module is not loaded at boot time. This can cause, for example, a failure to mount /boot/efi, as well as a failure to mount a USB thumb drive.  Here is the evidence:

Code: [Select]
root@Hibiscus:/home/don# /sbin/modinfo vfat
filename:       /lib/modules/5.13.4-1-siduction-amd64/kernel/fs/fat/vfat.ko
author:         Gordon Chaffee
description:    VFAT filesystem support
license:        GPL
alias:          fs-vfat
depends:        fat
retpoline:      Y
intree:         Y
name:           vfat
vermagic:       5.13.4-1-siduction-amd64 SMP preempt mod_unload modversions
 
root@Hibiscus:/home/don# lsmod | grep vfat
root@Hibiscus:/home/don#

I also checked the igb module, but it is loaded after boot, so the networking issue is something else.
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO