Siduction Forum

Siduction Forum => Upgrade Warnings (DE / EN) => Topic started by: dibl on 2021/07/19, 13:00:45

Title: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/19, 13:00:45

On a system that was fully updated as of Saturday, the following full-upgrade breaks networking:

Code: [Select]
Calculating upgrade...
The following NEW packages will be installed:
  linux-headers-5.13.3-1-siduction-amd64 linux-image-5.13.3-1-siduction-amd64
The following packages will be upgraded:
  gimp gimp-data ipp-usb libbabl-0.1-0 libgegl-0.4-0 libgegl-common libgimp2.0
  libnspr4 libnss3 linux-headers-siduction-amd64 linux-image-siduction-amd64
11 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.

The system that it breaks is this:

Code: [Select]
System:    Kernel: 5.12.17-1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.20.5
          Distro: siduction 13.2.1 December - kde - (201401272125)
Machine:  Type: Desktop System: ASUS product: All Series v: N/A serial: <filter>
          Mobo: ASUSTeK model: Z87-WS v: Rev 1.xx serial: <filter> BIOS: American Megatrends v: 2004 date: 06/05/2014
CPU:      Info: Quad Core model: Intel Core i7-4770 bits: 64 type: MT MCP L2 cache: 8 MiB
          Speed: 2780 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 2780 2: 2781 3: 2781 4: 2783 5: 2782 6: 2785
          7: 2783 8: 2781
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 460.84
          Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa
          resolution: 1366x768~60Hz
          OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 460.84
Audio:    Device-1: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel
          Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX] driver: snd_hda_intel
          Sound Server: ALSA v: k5.12.17-1-siduction-amd64
Network:  Device-1: Intel I210 Gigabit Network driver: igb
          IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
          Device-2: Intel I210 Gigabit Network driver: igb
          IF: enp9s0 state: down mac: <filter>
          IF-ID-1: br0 state: up speed: 1000 Mbps duplex: unknown mac: <filter>
Drives:    Local Storage: total: 2.27 TiB used: 957.53 GiB (41.1%)
          ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
          ID-2: /dev/sdb vendor: Western Digital model: WD1000DHTZ-04N21V0 size: 931.51 GiB
          ID-3: /dev/sdc vendor: Western Digital model: WD1000DHTZ-04N21V0 size: 931.51 GiB
Partition: ID-1: / size: 55.77 GiB used: 14.62 GiB (26.2%) fs: ext4 dev: /dev/sda1
          ID-2: /home size: 401.45 GiB used: 84.27 GiB (21.0%) fs: ext4 dev: /dev/sda3
Swap:      ID-1: swap-1 type: partition size: 1024 MiB used: 0 KiB (0.0%) dev: /dev/sda2
Sensors:  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 29 C
          Fan Speeds (RPM): N/A gpu: nvidia fan: 42%
Info:      Processes: 279 Uptime: 9m Memory: 31.3 GiB used: 2 GiB (6.4%) Shell: Bash inxi: 3.3.01

I assume the problem is with the new kernel, as rebooting into 5.12.17-1 restores full function of the system.
Title: Re: Upgrade Warning -- kernel 5.3.13-1 may break networking
Post by: towo on 2021/07/19, 13:12:28
More info needed!
There is no change in the config for Intel Gigabit Devices.
Title: Re: Upgrade Warning -- kernel 5.3.13-1 may break networking
Post by: dibl on 2021/07/19, 13:24:39
More info needed!

Hi towo -- can you give me a diagnostic tip -- what output would you like to see?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/19, 13:43:10
Maybe 

dmesg | egrep -i "net|igb|intel"
jounralctl -b | egrep -i "net|igb|intel"

i have no clue at the moment.

It works here without problem.


Code: [Select]
~
towo@Defiant> inxi -Sn -xxx
System:    Host: Defiant Kernel: 5.13.3-1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: KDE Plasma 5.22.3
           tk: Qt 5.15.2 info: plank wm: kwin_x11 dm: SDDM Distro: siduction 18.3.0 Patience - kde - (202010061355)
           base: Debian GNU/Linux 11 (bullseye)
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: e000 bus ID: 03:00.0
           chip ID: 8086:1539 class ID: 0200
           IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: 04:92:26:c0:3e:9f
           IF-ID-1: bri0 state: up speed: 1000 Mbps duplex: unknown mac: 56:20:6b:b0:49:0d
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 on 2021/07/19, 14:44:20
Hi,

with this kernel I have problems, too. Network is working, though.

There are alsa problems (only one of three sound cards (on-board, hdmi on graphic-card, sb-live) found) and a bunch of "failed" messages during boot, but no sound at all.



Quote
$ dmesg | egrep -i "failed"
[    5.328067] systemd[1]: run-rpc_pipefs.mount: Failed with result 'exit-code'.
[    5.328416] systemd[1]: Failed to mount RPC Pipe File System.
[    5.328941] systemd[1]: Dependency failed for RPC security service for NFS server.
[    5.335633] systemd[1]: rpc-svcgssd.service: Job rpc-svcgssd.service/start failed with result 'dependency'.
[    5.335654] systemd[1]: Dependency failed for RPC security service for NFS client and server.
[    5.336256] systemd[1]: rpc-gssd.service: Job rpc-gssd.service/start failed with result 'dependency



Quote
$ journalctl -b | egrep -i "failed"
Jul 19 14:31:35 neutower systemd[1]: run-rpc_pipefs.mount: Failed with result 'exit-code'.
Jul 19 14:31:35 neutower systemd[1]: Failed to mount RPC Pipe File System.
Jul 19 14:31:35 neutower systemd[1]: Dependency failed for RPC security service for NFS server.
Jul 19 14:31:35 neutower systemd[1]: rpc-svcgssd.service: Job rpc-svcgssd.service/start failed with result 'dependency'.
Jul 19 14:31:35 neutower systemd[1]: Dependency failed for RPC security service for NFS client and server.
Jul 19 14:31:35 neutower systemd[1]: rpc-gssd.service: Job rpc-gssd.service/start failed with result 'dependency'.
Jul 19 14:31:36 neutower systemd-udevd[321]: controlC2: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 2' failed with exit code 99.
Jul 19 14:31:42 neutower systemd[1]: proc-sys-fs-binfmt_misc.mount: Failed with result 'exit-code'.
Jul 19 14:31:42 neutower systemd[1]: Failed to mount Arbitrary Executable File Formats File System.
Jul 19 14:31:47 neutower alsactl[643]: alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -2
Jul 19 14:31:49 neutower connmand[646]: Failed to flush table 'filter': Invalid argument
Jul 19 14:31:49 neutower connmand[646]: Failed to flush table 'mangle': Invalid argument
Jul 19 14:31:49 neutower connmand[646]: Failed to flush table 'nat': Invalid argument
Jul 19 14:31:50 neutower udisksd[678]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Jul 19 14:31:50 neutower connmand[646]: Failed to open RFKILL control device
Jul 19 14:31:50 neutower udisksd[678]: Failed to load the 'mdraid' libblockdev plugin
Jul 19 14:31:51 neutower apachectl[697]: Action 'start' failed.
Jul 19 14:31:51 neutower systemd[1]: apache2.service: Failed with result 'exit-code'.
Jul 19 14:31:51 neutower systemd[1]: Failed to start The Apache HTTP Server.
Jul 19 14:31:55 neutower pipewire[2300]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Jul 19 14:32:04 neutower systemd-xdg-autostart-generator[2343]: stat() failed on /home/mh/.config/autostart/jami-gnome.desktop, ignoring: No such file or directory
Jul 19 14:32:04 neutower systemd-xdg-autostart-generator[2343]: stat() failed on /home/mh/.config/autostart/padevchooser.desktop, ignoring: No such file or directory
Jul 19 14:32:04 neutower systemd-xdg-autostart-generator[2343]: stat() failed on /home/mh/.config/autostart/automount-open.desktop, ignoring: No such file or directory
Jul 19 14:32:04 neutower systemd-xdg-autostart-generator[2343]: stat() failed on /home/mh/.config/autostart/gnome-ring.desktop, ignoring: No such file or directory
Jul 19 14:32:04 neutower pipewire[2345]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Jul 19 14:32:20 neutower dbus-daemon[645]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Jul 19 14:32:20 neutower pulseaudio[2346]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)


I re-booted several times between good and problematic kernel. Always the same.


kernel 5.12.16.1 working fine, no "failed" messages during boot with the excepion of the failing apache server, which can be ignored as it's an ***unrelated*** config problem which exists for some time.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/19, 14:47:51
I didn't see anything suspicious in the dmesg output. The journalctl output is attached -- I do not understand everything I see there -- it may have a clue.

Here is a second issue -- a known good USB thumb drive will not mount in any of the USB ports on this system, while running the 5.13.3-1 kernel.  But again, there is no problem with the 5.12.17-1. 
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/19, 15:12:54
Here is the dmesg output -- maybe I missed something.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/19, 15:13:33
At the moment i'm a bit of loose. Have to think about. 
I can't reproduce any of your problems on my system.
I even use NFS shares, but the system does not work as NFS server.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/19, 15:42:56
I ran michaa7's journalctl command -- output attached. You can see many failures, including parts of the file system.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: whistler_mb on 2021/07/19, 16:21:22
On my PC, a USB 3 PCIe card no longer works.

Code: [Select]
kernel: xhci_hcd 0000:06:00.0: firmware: failed to load renesas_usb_fw.mem (-2)

Jul 19 15:54:52 Tuxovo kernel: xhci_hcd 0000:06:00.0: request_firmware failed: -2

This problem already exists under kernel 5.12.17. With 5.12.16 the card still works.

I have found an entry at LKLM.org.
https://lkml.org/lkml/2021/7/17/327 (https://lkml.org/lkml/2021/7/17/327)
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/19, 18:11:27
I have added the patch from your link to 5.13.
Test, if it is working.

For dibl's problem at the moment i'm out of ideas.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/19, 18:37:32
With kernel 5.13.3-1-siduction-amd64 and 5.13.3-2-siduction-amd64 my network nfs mounts are not mounted. No problems with 5.12.17-1 and former kernels.

Inter-/Intranet is working ...

Quote
System:    Host: siductionbox Kernel: 5.13.3-2-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) 
Network:  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK P8 series driver: r8169 v: kernel 
          port: d000 bus ID: 03:00.0 chip ID: 10ec:8168 class ID: 0200 
          IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 08:60:6e:73:6e:ea



Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs on 2021/07/19, 18: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
[    1.259469] xhci_hcd 0000:05:00.0: request_firmware failed: -2


[   11.941623] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-63.ucode (-2)

[   11.943596] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)

[   12.265364] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
[   12.265431] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517


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

[  15.367506] BUG: kernel NULL pointer dereference, address: 0000000000000000
[  15.367518] #PF: supervisor instruction fetch in kernel mode
[  15.367521] #PF: error_code(0x0010) - not-present page
[  15.367524] PGD 0 P4D 0
[  15.367528] Oops: 0010 [#1] PREEMPT SMP NOPTI
[  15.367533] CPU: 6 PID: 3836 Comm: tpacpi-bat Tainted: G          O      5.13.3-2-siduction-amd64 #1 siduction 5.13-3.1
[  15.367538] Hardware name: LENOVO 20UGS00800/20UGS00800, BIOS R1CET63W(1.32 ) 04/09/2021
[  15.367540] RIP: 0010:0x0
[  15.367550] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[  15.367552] RSP: 0018:ffffc900017b3ed0 EFLAGS: 00010246
[  15.367556] RAX: 0000000000000000 RBX: ffff8881050d6fc0 RCX: 0000000000000001
[  15.367559] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff888110826a00
[  15.367561] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[  15.367563] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[  15.367565] R13: ffffffffffffffea R14: ffff888110826a00 R15: 0000000000000000
[  15.367568] FS:  00007fea36791280(0000) GS:ffff8883ff780000(0000) knlGS:0000000000000000
[  15.367572] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  15.367574] CR2: ffffffffffffffd6 CR3: 000000012035a000 CR4: 0000000000350ee0
[  15.367577] Call Trace:
[  15.367581]  proc_reg_llseek+0x45/0x80
[  15.367589]  ksys_lseek+0x7d/0xb0
[  15.367595]  do_syscall_64+0x61/0x80
[  15.367601]  ? asm_exc_page_fault+0x8/0x30
[  15.367607]  ? exit_to_user_mode_prepare+0x1d/0x1d0
[  15.367614]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[  15.367619] RIP: 0033:0x7fea369a5647
[  15.367623] 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.367627] RSP: 002b:00007ffe2038d9b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
[  15.367631] RAX: ffffffffffffffda RBX: 0000555c0695ee80 RCX: 00007fea369a5647
[  15.367633] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000003
[  15.367635] RBP: 0000555c07caefd0 R08: 00007ffe2038d960 R09: 00000000ffffffff
[  15.367638] R10: 00007fea3698bb80 R11: 0000000000000246 R12: 0000555c07c8e2a0
[  15.367640] R13: 00007ffe2038dbb0 R14: 0000555c07c8e3f0 R15: 0000555c07d62750
[  15.367646] 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 btusb mc btrtl btbcm btintel bluetooth snd_acp3x_rn snd_acp3x_pdm_dma snd_soc_dmic snd_soc_core snd_compress intel_rapl_msr snd_pcm_dmaengine ac97_bus snd_ctl_led iwlmvm intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi mac80211 snd_hda_intel snd_intel_dspcfg edac_mce_amd libarc4 snd_hda_codec snd_hda_core iwlwifi kvm_amd snd_hwdep nls_utf8 joydev nls_cp437 kvm thinkpad_acpi snd_pcm vfat serio_raw irqbypass nvram pcspkr platform_profile k10temp snd_rn_pci_acp3x snd_pci_acp3x fat cfg80211 snd_timer ledtrig_audio wmi_bmof ucsi_acpi tpm_tis snd typec_ucsi tpm_tis_core soundcore ipmi_devintf roles tpm ipmi_msghandler rfkill ac rng_core typec evdev acpi_cpufreq
[  15.367724]  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 rtsx_pci_sdmmc mmc_core iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt r8169 fb_sys_fops xhci_pci xhci_pci_renesas realtek psmouse drm i2c_piix4 rtsx_pci mdio_devres xhci_hcd mfd_core ehci_pci ehci_hcd libphy wmi battery video i2c_designware_platform i2c_scmi i2c_designware_core button
[  15.367781] CR2: 0000000000000000
[  15.367784] ---[ end trace 2bb0e3aaadd96c86 ]---
[  15.367787] RIP: 0010:0x0
[  15.367790] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[  15.367792] RSP: 0018:ffffc900017b3ed0 EFLAGS: 00010246
[  15.367795] RAX: 0000000000000000 RBX: ffff8881050d6fc0 RCX: 0000000000000001
[  15.367798] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff888110826a00
[  15.367800] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[  15.367802] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[  15.367804] R13: ffffffffffffffea R14: ffff888110826a00 R15: 0000000000000000
[  15.367806] FS:  00007fea36791280(0000) GS:ffff8883ff780000(0000) knlGS:0000000000000000
[  15.367809] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  15.367812] CR2: ffffffffffffffd6 CR3: 000000012035a000 CR4: 0000000000350ee0
[  15.437114] BUG: kernel NULL pointer dereference, address: 0000000000000000
[  15.437123] #PF: supervisor instruction fetch in kernel mode
[  15.437126] #PF: error_code(0x0010) - not-present page
[  15.437130] PGD 0 P4D 0
[  15.437134] Oops: 0010 [#2] PREEMPT SMP NOPTI
[  15.437139] CPU: 11 PID: 4124 Comm: tpacpi-bat Tainted: G      D    O      5.13.3-2-siduction-amd64 #1 siduction 5.13-3.1
[  15.437145] Hardware name: LENOVO 20UGS00800/20UGS00800, BIOS R1CET63W(1.32 ) 04/09/2021
[  15.437148] RIP: 0010:0x0
[  15.437156] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[  15.437159] RSP: 0018:ffffc90001d7fe38 EFLAGS: 00010246
[  15.437163] RAX: 0000000000000000 RBX: ffff8881050d6fc0 RCX: 0000000000000002
[  15.437166] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff88810979c500
[  15.437169] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[  15.437171] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[  15.437173] R13: ffffffffffffffea R14: ffff88810979c500 R15: 0000000000000000
[  15.437176] FS:  00007fb00c84b280(0000) GS:ffff8883ff8c0000(0000) knlGS:0000000000000000
[  15.437180] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  15.437183] CR2: ffffffffffffffd6 CR3: 000000012023a000 CR4: 0000000000350ee0
[  15.437186] Call Trace:
[  15.437189]  proc_reg_llseek+0x45/0x80
[  15.437198]  ksys_lseek+0x7d/0xb0
[  15.437203]  do_syscall_64+0x61/0x80
[  15.437210]  ? handle_mm_fault+0xcb/0x2a0
[  15.437217]  ? exc_page_fault+0x1d8/0x770
[  15.437221]  ? asm_exc_page_fault+0x8/0x30
[  15.437227]  ? exit_to_user_mode_prepare+0x1d/0x1d0
[  15.437233]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[  15.437241] RIP: 0033:0x7fb00ca5f647
[  15.437246] 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.437251] RSP: 002b:00007ffcad8a3fb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
[  15.437256] RAX: ffffffffffffffda RBX: 000055dbc1a76e80 RCX: 00007fb00ca5f647
[  15.437260] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000003
[  15.437262] RBP: 000055dbc2d93fd0 R08: 00007ffcad8a3f60 R09: 00000000ffffffff
[  15.437265] R10: 00007fb00ca45b80 R11: 0000000000000246 R12: 000055dbc2d732a0
[  15.437267] R13: 00007ffcad8a41b0 R14: 000055dbc2d733f0 R15: 000055dbc2e39c70
[  15.437275] 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 btusb mc btrtl btbcm btintel bluetooth snd_acp3x_rn snd_acp3x_pdm_dma snd_soc_dmic snd_soc_core snd_compress intel_rapl_msr snd_pcm_dmaengine ac97_bus snd_ctl_led iwlmvm intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi mac80211 snd_hda_intel snd_intel_dspcfg edac_mce_amd libarc4 snd_hda_codec snd_hda_core iwlwifi kvm_amd snd_hwdep nls_utf8 joydev nls_cp437 kvm thinkpad_acpi snd_pcm vfat serio_raw irqbypass nvram pcspkr platform_profile k10temp snd_rn_pci_acp3x snd_pci_acp3x fat cfg80211 snd_timer ledtrig_audio wmi_bmof ucsi_acpi tpm_tis snd typec_ucsi tpm_tis_core soundcore ipmi_devintf roles tpm ipmi_msghandler rfkill ac rng_core typec evdev acpi_cpufreq
[  15.437377]  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 rtsx_pci_sdmmc mmc_core iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt r8169 fb_sys_fops xhci_pci xhci_pci_renesas realtek psmouse drm i2c_piix4 rtsx_pci mdio_devres xhci_hcd mfd_core ehci_pci ehci_hcd libphy wmi battery video i2c_designware_platform i2c_scmi i2c_designware_core button
[  15.437437] CR2: 0000000000000000
[  15.437439] ---[ end trace 2bb0e3aaadd96c87 ]---
[  15.437442] RIP: 0010:0x0
[  15.437446] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[  15.437448] RSP: 0018:ffffc900017b3ed0 EFLAGS: 00010246
[  15.437451] RAX: 0000000000000000 RBX: ffff8881050d6fc0 RCX: 0000000000000001
[  15.437453] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff888110826a00
[  15.437456] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[  15.437458] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[  15.437460] R13: ffffffffffffffea R14: ffff888110826a00 R15: 0000000000000000
[  15.437463] FS:  00007fb00c84b280(0000) GS:ffff8883ff8c0000(0000) knlGS:0000000000000000
[  15.437466] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  15.437468] CR2: ffffffffffffffd6 CR3: 000000012023a000 CR4: 0000000000350ee0
[  17.100720] r8169 0000:02:00.0 enp2s0f0: Link is Up - 1Gbps/Full - flow control rx/tx
[  17.100748] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0f0: link becomes ready
[  19.072277] systemd-journald[563]: File /var/log/journal/18272a50cbd5449d89f77beec425efdc/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[  19.382372] Bluetooth: RFCOMM TTY layer initialized
[  19.382384] Bluetooth: RFCOMM socket layer initialized
[  19.382395] Bluetooth: RFCOMM ver 1.11
[  20.254681] show_signal_msg: 23 callbacks suppressed
[  20.254686] pipewire-media-[8369]: segfault at 21d ip 00007f58947f6cba sp 00007ffec642a670 error 4 in libasound.so.2.0.0[7f58947d1000+8d000]
[  20.254698] Code: b4 da 06 00 e8 d7 a8 fd ff 0f 1f 80 00 00 00 00 41 54 53 48 83 ec 08 48 85 ff 0f 84 bb 00 00 00 48 89 fb 48 8b bf a8 01 00 00 <8b> b7 cc 01 00 00 85 f6 75 3c 48 8b 83 98 01 00 00 48 8b 40 38 48
[  37.727646] EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 on 2021/07/19, 19:01:07
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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/19, 19:32:03
With kernel 5.13.3-1-siduction-amd64 and 5.13.3-2-siduction-amd64 my network nfs mounts are not mounted. No problems with 5.12.17-1 and former kernels.

Inter-/Intranet is working ...
How you mount your nfs shares?
I have no problems with nfs mount.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage on 2021/07/19, 20:02:01
No wifi here on 5.13, in my case wifi connection is not even listed in `ip a`

Code: [Select]
System:    Host: hal9001 Kernel: 5.12.17-1-siduction-amd64 x86_64 bits: 64 Desktop: Xfce 4.16.0
           Distro: siduction 14.1.0 Indian Summer - nox - (201411230419)
Machine:   Type: Laptop System: LENOVO product: 20BS006BPB v: ThinkPad X1 Carbon 3rd serial: 
           Mobo: LENOVO model: 20BS006BPB v: SDK0E50510 WIN serial:  UEFI [Legacy]: LENOVO
           v: N14ET54W (1.32 ) date: 03/19/2020
Battery:   ID-1: BAT0 charge: 36.0 Wh condition: 36.5/50.0 Wh (73%)
CPU:       Info: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP L2 cache: 4 MiB
           Speed: 798 MHz min/max: 500/3000 MHz Core speeds (MHz): 1: 798 2: 1224 3: 871 4: 1030
Graphics:  Device-1: Intel HD Graphics 5500 driver: i915 v: kernel
           Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev resolution: 2560x1440~60Hz
           OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 21.1.5
Audio:     Device-1: Intel Broadwell-U Audio driver: snd_hda_intel
           Device-2: Intel Wildcat Point-LP High Definition Audio driver: snd_hda_intel
           Sound Server: ALSA v: k5.12.17-1-siduction-amd64
Network:   Device-1: Intel Ethernet I218-V driver: e1000e
           IF: eth0 state: down mac: 54:ee:75:46:0c:9c
           Device-2: Intel Wireless 7265 driver: iwlwifi
           IF: wlan0 state: up mac: 60:57:18:e2:49:ba
           IF-ID-1: docker0 state: down mac: 02:42:a6:bb:eb:4f
           IF-ID-2: wwan0 state: down mac: 9a:d7:fd:67:25:7c
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
           Report: ID: hci0 state: down address: 60:57:18:E2:49:BE
Drives:    Local Storage: total: 238.47 GiB used: 36.45 GiB (15.3%)
           ID-1: /dev/sda vendor: Samsung model: MZNTE256HMHP-000L7 size: 238.47 GiB
Partition: ID-1: / size: 49.09 GiB used: 17.7 GiB (36.0%) fs: ext4 dev: /dev/sda2
           ID-2: /home size: 184.18 GiB used: 18.76 GiB (10.2%) fs: ext4 dev: /dev/dm-0
Swap:      Alert: No Swap data was found.
Sensors:   System Temperatures: cpu: 40.0 C mobo: 0.0 C
           Fan Speeds (RPM): cpu: 0
Info:      Processes: 209 Uptime: 4m Memory: 7.48 GiB used: 1.82 GiB (24.3%) Shell: Bash inxi: 3.3.01
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/19, 20:26:43
With kernel 5.13.3-1-siduction-amd64 and 5.13.3-2-siduction-amd64 my network nfs mounts are not mounted. No problems with 5.12.17-1 and former kernels.

Inter-/Intranet is working ...
How you mount your nfs shares?
I have no problems with nfs mount.
since years - for example
Code: [Select]
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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/19, 21:01:45
That's my entry in fstab


Code: [Select]
192.168.178.50:volume1/Daten     /mnt/Daten    nfs4      noauto,x-systemd.automount,x-systemd.idle-timeout=300,rw,user   0  0
It's working fine on all my machines, which i have available.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/19, 21:39:38
At all with problems, you all use encrypted drives?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/19, 21:56:33
No encrypted drive, but a LUKS encrypted file, opened with zulucrypt-gui. Did not test it with 5.13.3-1, but I will.

EDIT:  Encrypted file opens correctly.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage on 2021/07/19, 22:01:21
At all with problems, you all use encrypted drives?
I have an encrypted /home, but / is not encrypted.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: whistler_mb on 2021/07/19, 22:15:58
I have added the patch from your link to 5.13.
Test, if it is working.

For dibl's problem at the moment i'm out of ideas.
Thanks towo, it's working.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/19, 22:24:34
no encryption here and no problems with my nfs mounts, except with the 5.13.3...er kernel
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 on 2021/07/19, 22:34:23
no encryption used
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/20, 00:15:17
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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/20, 00:23:01
@towo, I think this needs to be installed on "bare metal", and not on a VM.  Correct?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/20, 00:28:07
It needs not to be installed, i want to know, if that "clean" live system does make the same problems like the install.
So it would be enaugh to boot the live medium.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: orinoco on 2021/07/20, 00:50:25
Hello,
I have problems with a USB3 PCIe-card and onboard-sound. Maybe a firmware problem?

Code: [Select]
Jul 19 22:51:48 jake kernel: ^[[0;1;39mxhci_hcd 0000:03:00.0: firmware: failed to load renesas_usb_fw.mem (-2)
Jul 19 22:51:48 jake kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mxhci_hcd 0000:03:00.0: Direct firmware load for renesas_usb$
Jul 19 22:51:48 jake kernel: ^[[0;1;39mxhci_hcd 0000:03:00.0: request_firmware failed: -2
Jul 19 22:51:48 jake kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mxhci_hcd: probe of 0000:03:00.0 failed with error -2
Jul 19 22:51:50 jake kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185msnd_hda_intel: probe of 0000:01:00.1 failed with error -2
Jul 19 22:51:50 jake kernel: ^[[0;1;39mhdaudio hdaudioC0D0: Unable to bind the codec
Linux jake 5.13.3-1-siduction-amd64 #1 SMP PREEMPT siduction 5.13-3 (2021-07-19) x86_64 GNU/Linux
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/20, 02:15:13
I booted the new Live ISO on the same hardware as I previously reported:

Code: [Select]
System:
  Kernel: 5.13.1-2-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.22.3
  Distro: siduction 21.1.99 Future - plasma - (202107121639)
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A serial: <filter>
  Mobo: ASUSTeK model: Z87-WS v: Rev 1.xx serial: <filter>
  BIOS: American Megatrends v: 2004 date: 06/05/2014
CPU:
  Info: Quad Core model: Intel Core i7-4770 bits: 64 type: MT MCP L2 cache: 8 MiB
  Speed: 927 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 927 2: 2534 3: 927
  4: 914 5: 825 6: 824 7: 867 8: 880
Graphics:
  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nouveau v: kernel
  Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting
  unloaded: fbdev,vesa resolution: 1366x768~60Hz
  OpenGL: renderer: NV117 v: 4.3 Mesa 21.2.0-devel
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel
  Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX]
  driver: snd_hda_intel
  Sound Server: ALSA v: k5.13.1-2-siduction-amd64
Network:
  Device-1: Intel I210 Gigabit Network driver: igb
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I210 Gigabit Network driver: igb
  IF: enp9s0 state: down mac: <filter>
Drives:
  Local Storage: total: 2.27 TiB used: 398.9 MiB (0.0%)
  ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
  ID-2: /dev/sdb vendor: Western Digital model: WD1000DHTZ-04N21V0 size: 931.51 GiB
  ID-3: /dev/sdc vendor: Western Digital model: WD1000DHTZ-04N21V0 size: 931.51 GiB
Partition:
  ID-1: / size: 28.17 GiB used: 398.9 MiB (1.4%) fs: overlay source: ERR-102
Swap:
  Alert: No Swap data was found.
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 29.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 224 Uptime: 11m Memory: 31.3 GiB used: 1.37 GiB (4.4%) Shell: Bash
  inxi: 3.3.01

The output files from dmesg, systemctl, and journalctl are attached.  There was a message in the boot output about fll-xdg.service, so I got an output for that one from systemctl.  Networking works. The only thing that didn't work "out of the box" is audio, and I am sure that could be fixed if I took the time -- pulseaudio is always a little tricky on this hardware, but it will always work once I get the configuration correct. It's kind of complicated ....

Code: [Select]
siducer@siduction:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC1150 Analog [ALC1150 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC1150 Digital [ALC1150 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

USB thumb drive mounts as expected.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: titan on 2021/07/20, 09:16:33
After du this morning I can't log in at all with latest kernel just in emergency mode, control -D has no effect I can run journalctl -xb but only errors I can see (in red) are failed to mount RPC  and complaints about missing /bin/plymouth . I can't boot system so don't know if there are issues with network, sound or USB as others have reported. reverted to previous kernel all is working fine.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: charlyheinz 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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage 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?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl 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?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo 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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl 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?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo 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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl 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!
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure 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.



Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo 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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo 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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage 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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 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.

Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure 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 ..
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo 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?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage on 2021/07/20, 15:55:05
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?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: unklarer on 2021/07/20, 16:02:38
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:
Quote
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 (https://unix.stackexchange.com/questions/638038/boot-efi-failed-to-mount-due-to-unknown-file-system-vfat-centos-7-5?answertab=active#tab-top) and this (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808380) does not help.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs on 2021/07/20, 17:16:00
Hello again,

unfortunately my problems persist with the updated kernel:

Code: [Select]
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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/20, 18:13:28
Quote from: towo
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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs on 2021/07/20, 18:27:16
Quote
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 (https://lkml.org/lkml/2021/7/16/794)

I don't trust myself building kernels ...
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/20, 18:33:07
That lkml report has nothing to do with your problem.
No clue why micha7 points to it.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: devil on 2021/07/20, 19:46:33
Quote
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.

Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/20, 21:08:08
Quote from: 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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/20, 21:09:56
Automatic module loading is not a kernel job, it's the job for the system, here especialy systemd.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/20, 21:31:17
yes, but why are these modules not loaded only with kernel 5.13...up to 5.12 I have had no problems - hmm
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/20, 21:41:02
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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/20, 22:07:13
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...
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/20, 22:10:41
Any messages in
Code: [Select]
journalctl -b | grep -i nfs?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/20, 22:23:14
fresh reboot with 5.13.4-1
Quote
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
Quote
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.
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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/20, 22:44:55
Can you paste

Code: [Select]
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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure 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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/20, 23:03:37
Why you have

Code: [Select]
timeo=14,x-systemd.idle-timeout=1min
that looks wrong to me.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure 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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo 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?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 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).
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/20, 23:49:41
Any USB related error in dmesg or journal?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage 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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo 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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 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

Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs 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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure 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


Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: titan 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
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: unklarer 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!
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl 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.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: unklarer on 2021/07/21, 13:29:08
^^@dibl,

i can confirm that!
Exactly that I had yesterday also on the screen.   ;D
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage on 2021/07/21, 13:39:00
Well, there might be something with the very old installation (or it's something HW config related) as I just rebooted my other laptop and 5.13 works fine so far, lsmod shows iwlmvm, vfat or nft_ modules loaded, which does not happen on the older installation

Code: [Select]
System:    Host: tomato Kernel: 5.13.4-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 18.3.0 Patience - nox - (202002161822) base: Debian GNU/Linux 11 (bullseye)

some old udev rules leftovers, suddenly tiggered by some micro change in how kernel reports something?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/21, 13:54:38
while on my system, which is an uptodate old installation (riders on the storm), the nfs modules are not loaded on booting, I made an entry in /etc/modules (with nfs and nfsv4) and set a link to /etc/modules-loaded.d/nfs.conf
Now nfs modules are loaded while booting and the nfs shares are mounted like before with the 5.12er kernel on the same system.

Code: [Select]
cat modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
nfs
nfsv4

Code: [Select]
ls -l modules-load.d/
insgesamt 4
-rw-r--r-- 1 root root 119 24. Feb 2014  cups-filters.conf
lrwxrwxrwx 1 root root  10 13. Jul 19:29 modules.conf -> ../modules
lrwxrwxrwx 1 root root  12 21. Jul 13:38 nfs.conf -> /etc/modules
lrwxrwxrwx 1 root root  39 27. Mai 15:53 nvidia.conf -> /etc/alternatives/glx--nvidia-load.conf
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/21, 14:35:41
Quote
while on my system, which is an uptodate old installation (riders on the storm),
Ähm, that can't be!

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)

That's what you have postet before. Your system is a bullseye install, not a siduction base.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/21, 14:41:05
@all

please show your

/etc/initramfs-tools/modules
/etc/initramfs-tools/initramfs.conf

also an
Code: [Select]
ls -ld /boot/initrd.img*
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/21, 14:47:41
Quote from: jure
... I made an entry in /etc/modules

I made an entry for vfat, and confirmed that is is also in /etc/modules-load.d/modules.conf, and rebooted.  Now the fat and vfat modules are loaded, but the USB thumb drive still won't mount. In dmesg appears the same error "codepage cp437 not found".
Google led me to this (https://unix.stackexchange.com/questions/479310/failed-to-mount-fat-filesystem-codepage-cp437-not-found). 
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage on 2021/07/21, 14:50:47
@all

please show your

/etc/initramfs-tools/modules
/etc/initramfs-tools/initramfs.conf

also an
Code: [Select]
ls -ld /boot/initrd.img*

Code: [Select]
# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax:  module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod

Code: [Select]
#
# initramfs.conf
# Configuration file for mkinitramfs(8). See initramfs.conf(5).
#
# Note that configuration options from this file can be overridden
# by config files in the /etc/initramfs-tools/conf.d directory.

#
# MODULES: [ most | netboot | dep | list ]
#
# most - Add most filesystem and all harddrive drivers.
#
# dep - Try and guess which modules to load.
#
# netboot - Add the base modules, network modules, but skip block devices.
#
# list - Only include modules from the 'additional modules' list
#

MODULES=most

#
# BUSYBOX: [ y | n | auto ]
#
# Use busybox shell and utilities.  If set to n, klibc utilities will be used.
# If set to auto (or unset), busybox will be used if installed and klibc will
# be used otherwise.
#

BUSYBOX=auto

#
# KEYMAP: [ y | n ]
#
# Load a keymap during the initramfs stage.
#

KEYMAP=n

#
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ]
#

COMPRESS=gzip

#
# DEVICE: ...
#
# Specify a specific network interface, like eth0
# Overridden by optional ip= or BOOTIF= bootarg
#

DEVICE=

#
# NFSROOT: [ auto | HOST:MOUNT ]
#

NFSROOT=auto

#
# RUNSIZE: ...
#
# The size of the /run tmpfs mount point, like 256M or 10%
# Overridden by optional initramfs.runsize= bootarg
#

RUNSIZE=10%

#
# FSTYPE: ...
#
# The filesystem type(s) to support, or "auto" to use the current root
# filesystem type
#

FSTYPE=auto

Code: [Select]
-rw-r--r-- 1 root root 28567250 Jul 21 14:42 /boot/initrd.img-5.12.17-1-siduction-amd64
-rw-r--r-- 1 root root 28916752 Jul 21 14:42 /boot/initrd.img-5.13.3-3-siduction-amd64
-rw-r--r-- 1 root root 28921960 Jul 21 14:41 /boot/initrd.img-5.13.4-1-siduction-amd64
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/21, 14:52:17
Hm, not the case of the problem, sadly.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/21, 14:54:50
Quote from: dibl
I made an entry for vfat, and confirmed that is is also in /etc/modules-load.d/modules.conf, and rebooted.  Now the fat and vfat modules are loaded, but the USB thumb drive still won't mount. In dmesg appears the same error "codepage cp437 not found".
Google led me to this.

nls_cp437 is also a kernel module.

Code: [Select]
towo:Defiant> sudo modinfo nls_cp437
filename:       /lib/modules/5.14.0-rc2-siduction-amd64/kernel/fs/nls/nls_cp437.ko
license:        Dual BSD/GPL
depends:
retpoline:      Y
intree:         Y
name:           nls_cp437
vermagic:       5.14.0-rc2-siduction-amd64 SMP preempt mod_unload modversions
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/21, 14:56:23
Same here:

Code: [Select]
don@Hibiscus:~$ cat /etc/initramfs-tools/modules
# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax:  module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
don@Hibiscus:~$ cat /etc/initramfs-tools/initramfs.conf
#
# initramfs.conf
# Configuration file for mkinitramfs(8). See initramfs.conf(5).
#
# Note that configuration options from this file can be overridden
# by config files in the /etc/initramfs-tools/conf.d directory.

#
# MODULES: [ most | netboot | dep | list ]
#
# most - Add most filesystem and all harddrive drivers.
#
# dep - Try and guess which modules to load.
#
# netboot - Add the base modules, network modules, but skip block devices.
#
# list - Only include modules from the 'additional modules' list
#

MODULES=most

#
# BUSYBOX: [ y | n | auto ]
#
# Use busybox shell and utilities.  If set to n, klibc utilities will be used.
# If set to auto (or unset), busybox will be used if installed and klibc will
# be used otherwise.
#

BUSYBOX=auto

#
# KEYMAP: [ y | n ]
#
# Load a keymap during the initramfs stage.
#

KEYMAP=n

#
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ]
#

COMPRESS=gzip

#
# DEVICE: ...
#
# Specify a specific network interface, like eth0
# Overridden by optional ip= or BOOTIF= bootarg
#

DEVICE=

#
# NFSROOT: [ auto | HOST:MOUNT ]
#

NFSROOT=auto

#
# RUNSIZE: ...
#
# The size of the /run tmpfs mount point, like 256M or 10%
# Overridden by optional initramfs.runsize= bootarg
#

RUNSIZE=10%

#
# FSTYPE: ...
#
# The filesystem type(s) to support, or "auto" to use the current root
# filesystem type
#

FSTYPE=auto

don@Hibiscus:~$ ls -ld /boot/initrd.img*
-rw-r--r-- 1 root root 30676978 Jul 13 04:47 /boot/initrd.img-5.12.16-1-siduction-amd64
-rw-r--r-- 1 root root 30678716 Jul 15 05:28 /boot/initrd.img-5.12.17-1-siduction-amd64
-rw-r--r-- 1 root root 31018372 Jul 21 07:00 /boot/initrd.img-5.13.4-1-siduction-amd64
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/21, 14:58:29
Same as vfat:

Code: [Select]
don@Hibiscus:~$ sudo modinfo nls_cp437
[sudo] password for don:
filename:       /lib/modules/5.12.17-1-siduction-amd64/kernel/fs/nls/nls_cp437.ko
license:        Dual BSD/GPL
depends:       
retpoline:      Y
intree:         Y
name:           nls_cp437
vermagic:       5.12.17-1-siduction-amd64 SMP preempt mod_unload modversions
don@Hibiscus:~$ lsmod | grep nls_cp437
don@Hibiscus:~$

(I'm booted in a kernel that has networking ...)
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 on 2021/07/21, 15:02:32
Quote
$ more /etc/initramfs-tools/modules
# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax:  module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod

Quote
$ more /etc/initramfs-tools/initramfs.conf
#
# initramfs.conf
# Configuration file for mkinitramfs(8). See initramfs.conf(5).
#
# Note that configuration options from this file can be overridden
# by config files in the /etc/initramfs-tools/conf.d directory.

#
# MODULES: [ most | netboot | dep | list ]
#
# most - Add most filesystem and all harddrive drivers.
#
# dep - Try and guess which modules to load.
#
# netboot - Add the base modules, network modules, but skip block devices.
#
# list - Only include modules from the 'additional modules' list
#

MODULES=most

#
# BUSYBOX: [ y | n | auto ]
#
# Use busybox shell and utilities.  If set to n, klibc utilities will be used.
# If set to auto (or unset), busybox will be used if installed and klibc will
# be used otherwise.
#

...skipping 1 line
BUSYBOX=auto

#
# KEYMAP: [ y | n ]
#
# Load a keymap during the initramfs stage.
#

KEYMAP=n

#
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ]
#

COMPRESS=gzip

#
# DEVICE: ...
#
# Specify a specific network interface, like eth0
# Overridden by optional ip= or BOOTIF= bootarg
#

DEVICE=

#
# NFSROOT: [ auto | HOST:MOUNT ]
#

...skipping 1 line
NFSROOT=auto

#
# RUNSIZE: ...
#
# The size of the /run tmpfs mount point, like 256M or 10%
# Overridden by optional initramfs.runsize= bootarg
#

RUNSIZE=10%

#
# FSTYPE: ...
#
# The filesystem type(s) to support, or "auto" to use the current root
# filesystem type
#

FSTYPE=auto

Quote
$ ls -ld /boot/initrd.img*
-rw-r--r-- 1 root root 77124201 21. Jul 12:02 /boot/initrd.img-5.10.0-8-amd64
-rw-r--r-- 1 root root 68578383 20. Jul 14:06 /boot/initrd.img-5.13.3-3-siduction-amd64
-rw-r--r-- 1 root root 68580019 21. Jul 00:57 /boot/initrd.img-5.13.4-1-siduction-amd64
-rw-r--r-- 1 root root 63600472 13. Feb 16:18 /boot/initrd.img-5.7.8-towo.1-siduction-amd64
-rw-r--r-- 1 root root 64538128 23. Dez 2020  /boot/initrd.img-5.9.15-towo.1-siduction-amd64

Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/21, 15:02:48
@towo

Code: [Select]
cat siduction-version
siduction 12.2.0 Riders on the Storm - kde - (201212092131) upgrade to plasma 5 kde-full

Code: [Select]
cat debian_version
11.0

may be the version 11 (bullseye) comes from my system cleanup (https://forum.siduction.org/index.php?topic=8246.msg66493#msg66493) in march 2021, but this is an old installation ... I would remember if had made a new installation ;-)

edit2
changelog
Quote
base-files (11.1) unstable; urgency=medium
...
  - Use 11.0 as version in /etc/debian_version.
    (expected to change at every point release)
...


edit:
Code: [Select]
ls -ld /boot/initrd.img*
-rw-r--r-- 1 root root 61124578 16. Jul 18:51 /boot/initrd.img-5.12.17-1-siduction-amd64
-rw-r--r-- 1 root root 61663455 21. Jul 10:59 /boot/initrd.img-5.13.4-1-siduction-amd64

Code: [Select]
cat  /etc/initramfs-tools/modules
# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax:  module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod

Code: [Select]
/etc/initramfs-tools/initramfs.conf
#
# initramfs.conf
# Configuration file for mkinitramfs(8). See initramfs.conf(5).
#
# Note that configuration options from this file can be overridden
# by config files in the /etc/initramfs-tools/conf.d directory.

#
# MODULES: [ most | netboot | dep | list ]
#
# most - Add most filesystem and all harddrive drivers.
#
# dep - Try and guess which modules to load.
#
# netboot - Add the base modules, network modules, but skip block devices.
#
# list - Only include modules from the 'additional modules' list
#

MODULES=most

#
# BUSYBOX: [ y | n | auto ]
#
# Use busybox shell and utilities.  If set to n, klibc utilities will be used.
# If set to auto (or unset), busybox will be used if installed and klibc will
# be used otherwise.
#

BUSYBOX=auto

#
# KEYMAP: [ y | n ]
#
# Load a keymap during the initramfs stage.
#

KEYMAP=n

#
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ]
#

COMPRESS=gzip

#
# DEVICE: ...
#
# Specify a specific network interface, like eth0
# Overridden by optional ip= or BOOTIF= bootarg
#

DEVICE=

#
# NFSROOT: [ auto | HOST:MOUNT ]
#

NFSROOT=auto

#
# RUNSIZE: ...
#
# The size of the /run tmpfs mount point, like 256M or 10%
# Overridden by optional initramfs.runsize= bootarg
#

RUNSIZE=10%

#
# FSTYPE: ...
#
# The filesystem type(s) to support, or "auto" to use the current root
# filesystem type
#

FSTYPE=auto

Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs on 2021/07/21, 15:29:45
@towo

Here we go again:

Code: [Select]
ls -ld /boot/initrd.img*
-rw-r--r-- 1 root root 68749648 17. Jul 19:22 /boot/initrd.img-5.12.17-1-siduction-amd64
-rw-r--r-- 1 root root 69364492 21. Jul 08:47 /boot/initrd.img-5.13.4-1-siduction-amd64

Code: [Select]
cat /etc/initramfs-tools/modules

# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax:  module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod

Code: [Select]
cat /etc/initramfs-tools/initramfs.conf
#
# initramfs.conf
# Configuration file for mkinitramfs(8). See initramfs.conf(5).
#
# Note that configuration options from this file can be overridden
# by config files in the /etc/initramfs-tools/conf.d directory.

#
# MODULES: [ most | netboot | dep | list ]
#
# most - Add most filesystem and all harddrive drivers.
#
# dep - Try and guess which modules to load.
#
# netboot - Add the base modules, network modules, but skip block devices.
#
# list - Only include modules from the 'additional modules' list
#

MODULES=most

#
# BUSYBOX: [ y | n | auto ]
#
# Use busybox shell and utilities.  If set to n, klibc utilities will be used.
# If set to auto (or unset), busybox will be used if installed and klibc will
# be used otherwise.
#

BUSYBOX=auto

#
# KEYMAP: [ y | n ]
#
# Load a keymap during the initramfs stage.
#

KEYMAP=n

#
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ]
#

COMPRESS=gzip

#
# DEVICE: ...
#
# Specify a specific network interface, like eth0
# Overridden by optional ip= or BOOTIF= bootarg
#

DEVICE=

#
# NFSROOT: [ auto | HOST:MOUNT ]
#

NFSROOT=auto

#
# RUNSIZE: ...
#
# The size of the /run tmpfs mount point, like 256M or 10%
# Overridden by optional initramfs.runsize= bootarg
#

RUNSIZE=10%

#
# FSTYPE: ...
#
# The filesystem type(s) to support, or "auto" to use the current root
# filesystem type
#

FSTYPE=auto

Thanks for your efforts!
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/21, 15:39:39
For an experiment, while booted in 5.13.4-1, I added nls_cp437 to /etc/modules, then ran

Code: [Select]
update-initramfs -u
and rebooted. Still no networking, and the USB thumb drive mounting fails silently.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: unklarer on 2021/07/21, 15:44:58
@towo

Code: [Select]
ls -ld /boot/initrd.img*
-rw-r--r-- 1 root root 31424936  8. Jul 09:12 /boot/initrd.img-5.12.15-1-siduction-amd64
-rw-r--r-- 1 root root 31429269 16. Jul 10:10 /boot/initrd.img-5.12.17-1-siduction-amd64
-rw-r--r-- 1 root root 31721377 20. Jul 08:57 /boot/initrd.img-5.13.3-2-siduction-amd64
-rw-r--r-- 1 root root 31721223 20. Jul 14:20 /boot/initrd.img-5.13.3-3-siduction-amd64
-rw-r--r-- 1 root root 31721640 21. Jul 12:08 /boot/initrd.img-5.13.4-1-siduction-amd64

Code: [Select]
cat /etc/initramfs-tools/modules
# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax:  module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod

Code: [Select]
cat /etc/initramfs-tools/initramfs.conf
#
# initramfs.conf
# Configuration file for mkinitramfs(8). See initramfs.conf(5).
#
# Note that configuration options from this file can be overridden
# by config files in the /etc/initramfs-tools/conf.d directory.

#
# MODULES: [ most | netboot | dep | list ]
#
# most - Add most filesystem and all harddrive drivers.
#
# dep - Try and guess which modules to load.
#
# netboot - Add the base modules, network modules, but skip block devices.
#
# list - Only include modules from the 'additional modules' list
#

MODULES=most

#
# BUSYBOX: [ y | n | auto ]
#
# Use busybox shell and utilities.  If set to n, klibc utilities will be used.
# If set to auto (or unset), busybox will be used if installed and klibc will
# be used otherwise.
#

BUSYBOX=auto

#
# KEYMAP: [ y | n ]
#
# Load a keymap during the initramfs stage.
#

KEYMAP=n

#
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ]
#

COMPRESS=gzip

#
# DEVICE: ...
#
# Specify a specific network interface, like eth0
# Overridden by optional ip= or BOOTIF= bootarg
#

DEVICE=

#
# NFSROOT: [ auto | HOST:MOUNT ]
#

NFSROOT=auto

#
# RUNSIZE: ...
#
# The size of the /run tmpfs mount point, like 256M or 10%
# Overridden by optional initramfs.runsize= bootarg
#

RUNSIZE=10%

#
# FSTYPE: ...
#
# The filesystem type(s) to support, or "auto" to use the current root
# filesystem type
#

FSTYPE=auto
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/21, 15:55:56
As i written earlyer, it's even not a problem with generating initrd.
At the moment i'm out of ideas, why old systems have those problems with kernel 5.13.

I have no system anymore, which was installed with an old iso und upgraded permanently.
All my systems are working fine after switch from 5.12 to 5.13.

Also i do not own hardware with an Renesas USB3 chipset, so i can't see, what's going wrong here.
But it seems, the Renesas problem is an upstream regression, since kernel 5.12.17 hast the same problems.

Maybe it could help, if anyone can test with the recent aptosid kernel

http://aptosid.com/debian/pool/main/l/linux-aptosid/linux-image-5.13.0-3.slh.1-aptosid-amd64_5.13-7_amd64.deb
http://aptosid.com/debian/pool/main/l/linux-aptosid/linux-headers-5.13.0-3.slh.1-aptosid-amd64_5.13-7_amd64.deb

Maybe i can find the diff, which is the cause of the problem.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage on 2021/07/21, 16:16:30
Code: [Select]
Linux hal9001 5.13.0-3.slh.1-aptosid-amd64 #1 SMP PREEMPT aptosid 5.13-7 (2021-07-20) x86_64 GNU/LinuxSeems to work just fine  ???
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: unklarer on 2021/07/21, 16:32:59
^Here too.

Code: [Select]
inxi -Sxxx
System:    Host: sidukde Kernel: 5.13.0-3.slh.1-aptosid-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)
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 on 2021/07/21, 16:34:48
aptosidkernel fully working. All three soundcards available, USB-TV-Card working.

Quote
~$ dmesg | egrep -i "failed"
~$

Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs on 2021/07/21, 16:42:09
No luck and no sound with external sound card for me with the aptosid kernel:

Quote
uname -a
Linux x13-cord 5.13.0-3.slh.1-aptosid-amd64 #1 SMP PREEMPT aptosid 5.13-7 (2021-07-20) x86_64 GNU/Linux

Quote
dmesg | egrep -i "failed"
[    1.335881] xhci_hcd 0000:05:00.0: Direct firmware load for renesas_usb_fw.mem failed with error -2
[   62.505248] xhci_hcd 0000:05:00.0: request_firmware failed: -11
[   62.505530] xhci_hcd: probe of 0000:05:00.0 failed with error -11
[   83.638308] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-63.ucode failed with error -2
[   83.924289] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
[   84.040599] thermal thermal_zone0: failed to read out thermal zone (-61)

Quote
dmesg | egrep -i "error"
[    1.222539] RAS: Correctable Errors collector initialized.
[    1.335881] xhci_hcd 0000:05:00.0: Direct firmware load for renesas_usb_fw.mem failed with error -2
[   62.505530] xhci_hcd: probe of 0000:05:00.0 failed with error -11
[   83.448051] EXT4-fs (nvme0n1p2): re-mounted. Opts: errors=remount-ro. Quota mode: none.
[   83.638308] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-63.ucode failed with error -2
[   86.770000] pipewire-media-[2451]: segfault at 1cc ip 00007f975758fcba sp 00007ffd03feca20 error 4 in libasound.so.2.0.0[7f975756a000+8d000]
[   86.948482] #PF: error_code(0x0010) - not-present page
[   86.997810] pulseaudio[2383]: segfault at 50 ip 0000000000000050 sp 00007ffde36ffe68 error 14 in pulseaudio[5643f8639000+5000]
[   87.012113] #PF: error_code(0x0010) - not-present page
[   87.405392] pulseaudio[5254]: segfault at 50 ip 0000000000000050 sp 00007fff565e96b8 error 14 in pulseaudio[56251f5a3000+5000]
[   87.634304] pulseaudio[6253]: segfault at 50 ip 0000000000000050 sp 00007ffedd685c88 error 14 in pulseaudio[558193f04000+5000]
[   87.879583] pulseaudio[7307]: segfault at 50 ip 0000000000000050 sp 00007ffc604c8268 error 14 in pulseaudio[55a472529000+5000]
[   88.136293] pulseaudio[7504]: segfault at 1cc ip 00007ff8c41b9cba sp 00007ffe5760b160 error 4 in libasound.so.2.0.0[7ff8c4194000+8d000]
[   96.718460] pipewire-media-[8089]: segfault at 50 ip 0000000000000050 sp 00007ffc9acedee8 error 14 in pipewire-media-session[5561757b6000+1a000]

Regards

cs
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 on 2021/07/21, 16:52:32

@ cs


Maybe this is a different problem. This error is currently discussed on lkml:

https://lkml.org/lkml/2021/7/19/83
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs on 2021/07/21, 17:03:23
@michaa7 and towo

Quote
Maybe this is a different problem. This error is currently discussed on lkml:

https://lkml.org/lkml/2021/7/19/83

Yes, that sounds familiar to me, thanks for the hint!
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/21, 19:13:39
Yes.

Code: [Select]
don@Hibiscus:~$ inxi -Sn
System:    Host: Hibiscus Kernel: 5.13.0-3.slh.1-aptosid-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.20.5
           Distro: siduction 13.2.1 December - kde - (201401272125)
Network:   Device-1: Intel I210 Gigabit Network driver: igb
           IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: xxxxxxx
           Device-2: Intel I210 Gigabit Network driver: igb
           IF: enp9s0 state: down mac: e0:3f:49:e6:85:c4
           IF-ID-1: br0 state: up speed: 1000 Mbps duplex: unknown mac: xxxxxxx

Networking works as expected, USB thumb drive mounts as expected.

THANKS @towo!
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/21, 22:09:50
@all with problems

You all ave old siduction basis, have you done the usrmerge?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage on 2021/07/21, 22:19:24
That would be a no from my side. I somehow missed the existence of https://wiki.debian.org/UsrMerge
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: jure on 2021/07/21, 22:23:08
no

Code: [Select]
apt policy usrmerge
usrmerge:
  Installiert:           (keine)
  Installationskandidat: 25
  Versionstabelle:
     25 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        500 http://httpredir.debian.org/debian unstable/main i386 Packages
        500 http://ftp.de.debian.org/debian unstable/main amd64 Packages
        500 http://ftp.de.debian.org/debian unstable/main i386 Packages

Some info about usrmerge written by devil https://www.linux-community.de/ausgaben/linuxuser/2019/08/zusammengefasst/
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/21, 22:34:34
No, all mine are original siduction installations.  Here's another one that works correctly with the slh kernel.

Code: [Select]
System:    Kernel: 5.13.0-3.slh.1-aptosid-amd64 x86_64 bits: 64 Desktop: LXQt 0.16.1
           Distro: siduction 17.1.0 Patience - lxqt - (201703051830)
Machine:   Type: Portable System: Dell product: Inspiron N5110 v: N/A serial: <filter>
           Mobo: Dell model: 034W60 v: A11 serial: <filter> BIOS: Dell v: A11 date: 08/03/2012
Battery:   ID-1: BAT0 charge: 66.6 Wh condition: 82.2/73.3 Wh (112%)
CPU:       Info: Dual Core model: Intel Core i3-2330M bits: 64 type: MT MCP L2 cache: 3 MiB
           Speed: 1022 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 1022 2: 1089 3: 1538 4: 1265
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel
           Device-2: Microdia Laptop_Integrated_Webcam_HD type: USB driver: uvcvideo
           Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa
           resolution: 1366x768~60Hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 21.1.5
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel
           Sound Server: ALSA v: k5.13.0-3.slh.1-aptosid-amd64
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
           IF: enp5s0 state: down mac: <filter>
           Device-2: Intel Centrino Wireless-N 1030 [Rainbow Peak] driver: iwlwifi
           IF: wlp9s0 state: up mac: <filter>
Bluetooth: Device-1: Intel Centrino Advanced-N 6230 Bluetooth adapter type: USB driver: btusb
           Report: ID: hci0 state: down address: <filter>
Drives:    Local Storage: total: 74.53 GiB used: 20.86 GiB (28.0%)
           ID-1: /dev/sda vendor: Intel model: SSDSA2CW080G3 size: 74.53 GiB
Partition: ID-1: / size: 16.61 GiB used: 15.62 GiB (94.1%) fs: ext4 dev: /dev/sda1
Swap:      ID-1: swap-1 type: partition size: 1024 MiB used: 0 KiB (0.0%) dev: /dev/sda2
Sensors:   System Temperatures: cpu: 57.0 C mobo: N/A
           Fan Speeds (RPM): cpu: 0
Info:      Processes: 246 Uptime: 49m Memory: 3.76 GiB used: 2.47 GiB (65.7%) Shell: Bash inxi: 3.3.01
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 on 2021/07/21, 22:40:55
@all with problems

You all ave old siduction basis, have you done the usrmerge?

If (A) this was mandatory and if (B) this was to be done manually then the answer is NO.

But if A and B are true I would have expected some strong hint in the update section.

If this is the root cause for all the problems with siduction + kernel 5.13, why don't we have problems with the aptosid kernel?


Anyway, should we now insztall usrmerge?

Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/21, 23:13:06
In the kernel config the path to modprobe is only valid on systems with usrmerge installed.
In the slh kernel modprobe path is set ti /sbin/modprobe, which is valid on all systems.
And yes. usrmerge is recommend, because it's default in debian bullseye, on buster i'm not sure.

The new kernel, which is building at the moment, should work on all systems, usrmerged or not.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Carnophage on 2021/07/21, 23:31:31
After usrmerge
Code: [Select]
# uname -a
Linux hal9001 5.13.4-1-siduction-amd64 #1 SMP PREEMPT siduction 5.13-4 (2021-07-20) x86_64 GNU/Linux
runs just fine.

Thanks towo!
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: michaa7 on 2021/07/22, 00:22:20
New kernel 5.13.4-2-siduction-amd64 works fine, no problems!
Quote
~$ dmesg | egrep -i "failed"
~$

Problem solved. All soundcards available, usb-dvb working again.

Explanation makes  lot of sense. Thanks, good job .... as always

Will now install usrmerge ...
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/22, 00:32:05
After usrmerge, all seems good:

Code: [Select]
System:    Host: n5110 Kernel: 5.13.4-2-siduction-amd64 x86_64 bits: 64 Desktop: LXQt 0.16.1
           Distro: siduction 17.1.0 Patience - lxqt - (201703051830)
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
           IF: enp5s0 state: down mac: 18:03:73:8c:6c:c5
           Device-2: Intel Centrino Wireless-N 1030 [Rainbow Peak] driver: iwlwifi
           IF: wlp9s0 state: up mac: ac:72:89:b0:31:14
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs on 2021/07/22, 06:39:45
No luck for me: I installed usrmerge and the newest kernel, but still the external usb sound card is not doing well:

Quote
uname -a
Linux x13-cord 5.13.4-2-siduction-amd64 #1 SMP PREEMPT siduction 5.13-4.2 (2021-07-21) x86_64 GNU/Linux

Quote
dmesg | egrep -i "error"
[    0.988069] RAS: Correctable Errors collector initialized.
[   12.530484] EXT4-fs (nvme0n1p2): re-mounted. Opts: errors=remount-ro. Quota mode: none.
[   12.909141] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-63.ucode failed with error -2
[   16.089467] #PF: error_code(0x0010) - not-present page
[   16.150299] #PF: error_code(0x0010) - not-present page
[   16.678778] pipewire-media-[4482]: segfault at 1cc ip 00007f534860bcba sp 00007ffe547fba00 error 4 in libasound.so.2.0.0[7f53485e6000+8d000]
[   17.096864] pulseaudio[4413]: segfault at 50 ip 0000000000000050 sp 00007ffe031a7fb8 error 14 in pulseaudio[55ba0d042000+5000]
[   17.921743] pulseaudio[8156]: segfault at 1cc ip 00007fb38f62fcba sp 00007ffcad62d840 error 4 in libasound.so.2.0.0[7fb38f60a000+8d000]
[   18.754631] pulseaudio[8270]: segfault at 1cc ip 00007fcce2167cba sp 00007ffc4be8ec90 error 4 in libasound.so.2.0.0[7fcce2142000+8d000]
[   19.554126] pulseaudio[8274]: segfault at 50 ip 0000000000000050 sp 00007ffe6bc92738 error 14 in pulseaudio[55787a30d000+5000]
[   20.353320] pulseaudio[8278]: segfault at 50 ip 0000000000000050 sp 00007ffd686f7ca8 error 14 in pulseaudio[556163548000+5000]
[   32.038688] pipewire-media-[8385]: segfault at 50 ip 0000000000000050 sp 00007ffc4e5d9738 error 14 in pipewire-media-session[55ef584e6000+1a000]

Quote
dmesg | egrep -i "failed"
[   12.909119] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-63.ucode (-2)
[   12.909139] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-63.ucode (-2)
[   12.909141] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-63.ucode failed with error -2
[   13.051416] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[   13.051434] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[   13.055566] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
[   13.187885] thermal thermal_zone0: failed to read out thermal zone (-61)

Quote
[   16.089449] BUG: kernel NULL pointer dereference, address: 0000000000000000
[   16.089463] #PF: supervisor instruction fetch in kernel mode
[   16.089467] #PF: error_code(0x0010) - not-present page
[   16.089470] PGD 0 P4D 0
[   16.089474] Oops: 0010 [#1] PREEMPT SMP NOPTI
[   16.089479] CPU: 5 PID: 3944 Comm: tpacpi-bat Tainted: G           O      5.13.4-2-siduction-amd64 #1 siduction 5.13-4.2
[   16.089485] Hardware name: LENOVO 20UGS00800/20UGS00800, BIOS R1CET63W(1.32 ) 04/09/2021
[   16.089488] RIP: 0010:0x0
[   16.089497] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   16.089500] RSP: 0018:ffffc9000214bef0 EFLAGS: 00010246
[   16.089504] RAX: 0000000000000000 RBX: ffff888103650540 RCX: 0000000000000001
[   16.089507] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff888114f2bc00
[   16.089510] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   16.089512] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   16.089514] R13: ffffffffffffffea R14: ffff888114f2bc00 R15: 0000000000000000
[   16.089517] FS:  00007feff45da280(0000) GS:ffff8883ff740000(0000) knlGS:0000000000000000
[   16.089521] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   16.089524] CR2: ffffffffffffffd6 CR3: 0000000127c5a000 CR4: 0000000000350ee0
[   16.089527] Call Trace:
[   16.089531]  proc_reg_llseek+0x45/0x80
[   16.089541]  ksys_lseek+0x7d/0xb0
[   16.089548]  do_syscall_64+0x40/0x80
[   16.089554]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   16.089560] RIP: 0033:0x7feff47ee647
[   16.089564] 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
[   16.089568] RSP: 002b:00007ffc9f0c9368 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
[   16.089573] RAX: ffffffffffffffda RBX: 00005595b382ce80 RCX: 00007feff47ee647
[   16.089575] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000003
[   16.089578] RBP: 00005595b5112fd0 R08: 00007ffc9f0c9310 R09: 00000000ffffffff
[   16.089580] R10: 00007feff47d4b80 R11: 0000000000000246 R12: 00005595b50f22a0
[   16.089583] R13: 00007ffc9f0c9560 R14: 00005595b50f23f0 R15: 00005595b519dfb0
[   16.089588] Modules linked in: acpi_call(O) cmac algif_hash algif_skcipher af_alg vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cpufreq_conservative bnep cpufreq_powersave snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device binfmt_misc btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc iwlmvm mac80211 libarc4 intel_rapl_msr intel_rapl_common snd_acp3x_pdm_dma snd_acp3x_rn snd_soc_dmic snd_soc_core snd_compress edac_mce_amd snd_pcm_dmaengine ac97_bus snd_ctl_led vmwgfx snd_hda_codec_realtek kvm_amd snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel nls_utf8 iwlwifi snd_intel_dspcfg snd_intel_sdw_acpi nls_cp437 kvm snd_hda_codec vfat irqbypass snd_hda_core fat rapl snd_hwdep joydev thinkpad_acpi snd_pcm pcspkr ucsi_acpi nvram typec_ucsi serio_raw platform_profile cfg80211 ledtrig_audio typec snd_timer snd_rn_pci_acp3x k10temp sp5100_tco snd snd_pci_acp3x ccp wmi_bmof ipmi_devintf soundcore rng_core ipmi_msghandler
[   16.089674]  rfkill roles ac evdev acpi_cpufreq loop msr parport_pc ppdev lp parport fuse configfs sunrpc bpf_preload ip_tables x_tables hid_microsoft dm_crypt dm_mod 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 drm_ttm_helper rtsx_pci_sdmmc ttm mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops xhci_pci crypto_simd xhci_pci_renesas cryptd psmouse drm i2c_piix4 agpgart rtsx_pci xhci_hcd ehci_pci mfd_core r8169 ehci_hcd realtek wmi battery i2c_designware_platform i2c_scmi i2c_designware_core video i2c_core button
[   16.089750] CR2: 0000000000000000
[   16.089753] ---[ end trace 33285a73eb3044bd ]---
[   16.089756] RIP: 0010:0x0
[   16.089760] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   16.089762] RSP: 0018:ffffc9000214bef0 EFLAGS: 00010246
[   16.089765] RAX: 0000000000000000 RBX: ffff888103650540 RCX: 0000000000000001
[   16.089768] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff888114f2bc00
[   16.089770] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   16.089772] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   16.089775] R13: ffffffffffffffea R14: ffff888114f2bc00 R15: 0000000000000000
[   16.089777] FS:  00007feff45da280(0000) GS:ffff8883ff740000(0000) knlGS:0000000000000000
[   16.089780] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   16.089783] CR2: ffffffffffffffd6 CR3: 0000000127c5a000 CR4: 0000000000350ee0
[   16.150289] BUG: kernel NULL pointer dereference, address: 0000000000000000
[   16.150298] #PF: supervisor instruction fetch in kernel mode
[   16.150299] #PF: error_code(0x0010) - not-present page
[   16.150301] PGD 0 P4D 0
[   16.150304] Oops: 0010 [#2] PREEMPT SMP NOPTI
[   16.150308] CPU: 0 PID: 4246 Comm: tpacpi-bat Tainted: G      D    O      5.13.4-2-siduction-amd64 #1 siduction 5.13-4.2
[   16.150311] Hardware name: LENOVO 20UGS00800/20UGS00800, BIOS R1CET63W(1.32 ) 04/09/2021
[   16.150312] RIP: 0010:0x0
[   16.150319] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   16.150320] RSP: 0018:ffffc9000216bef0 EFLAGS: 00010246
[   16.150323] RAX: 0000000000000000 RBX: ffff888103650540 RCX: 0000000000000002
[   16.150324] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff888110552a00
[   16.150326] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   16.150327] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   16.150328] R13: ffffffffffffffea R14: ffff888110552a00 R15: 0000000000000000
[   16.150330] FS:  00007f8d44ee0280(0000) GS:ffff8883ff600000(0000) knlGS:0000000000000000
[   16.150332] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   16.150333] CR2: ffffffffffffffd6 CR3: 000000010d850000 CR4: 0000000000350ef0
[   16.150335] Call Trace:
[   16.150337]  proc_reg_llseek+0x45/0x80
[   16.150344]  ksys_lseek+0x7d/0xb0
[   16.150348]  do_syscall_64+0x40/0x80
[   16.150352]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   16.150356] RIP: 0033:0x7f8d450f4647
[   16.150357] 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
[   16.150359] RSP: 002b:00007fff82f24988 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
[   16.150362] RAX: ffffffffffffffda RBX: 00005627bf917e80 RCX: 00007f8d450f4647
[   16.150363] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000003
[   16.150364] RBP: 00005627c0920fd0 R08: 00007fff82f24930 R09: 00000000ffffffff
[   16.150365] R10: 00007f8d450dab80 R11: 0000000000000246 R12: 00005627c09002a0
[   16.150366] R13: 00007fff82f24b80 R14: 00005627c09003f0 R15: 00005627c09f2f80
[   16.150369] Modules linked in: acpi_call(O) cmac algif_hash algif_skcipher af_alg vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cpufreq_conservative bnep cpufreq_powersave snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device binfmt_misc btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc iwlmvm mac80211 libarc4 intel_rapl_msr intel_rapl_common snd_acp3x_pdm_dma snd_acp3x_rn snd_soc_dmic snd_soc_core snd_compress edac_mce_amd snd_pcm_dmaengine ac97_bus snd_ctl_led vmwgfx snd_hda_codec_realtek kvm_amd snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel nls_utf8 iwlwifi snd_intel_dspcfg snd_intel_sdw_acpi nls_cp437 kvm snd_hda_codec vfat irqbypass snd_hda_core fat rapl snd_hwdep joydev thinkpad_acpi snd_pcm pcspkr ucsi_acpi nvram typec_ucsi serio_raw platform_profile cfg80211 ledtrig_audio typec snd_timer snd_rn_pci_acp3x k10temp sp5100_tco snd snd_pci_acp3x ccp wmi_bmof ipmi_devintf soundcore rng_core ipmi_msghandler
[   16.150429]  rfkill roles ac evdev acpi_cpufreq loop msr parport_pc ppdev lp parport fuse configfs sunrpc bpf_preload ip_tables x_tables hid_microsoft dm_crypt dm_mod 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 drm_ttm_helper rtsx_pci_sdmmc ttm mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops xhci_pci crypto_simd xhci_pci_renesas cryptd psmouse drm i2c_piix4 agpgart rtsx_pci xhci_hcd ehci_pci mfd_core r8169 ehci_hcd realtek wmi battery i2c_designware_platform i2c_scmi i2c_designware_core video i2c_core button
[   16.150474] CR2: 0000000000000000
[   16.150476] ---[ end trace 33285a73eb3044be ]---
[   16.150478] RIP: 0010:0x0
[   16.150480] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   16.150481] RSP: 0018:ffffc9000214bef0 EFLAGS: 00010246
[   16.150483] RAX: 0000000000000000 RBX: ffff888103650540 RCX: 0000000000000001
[   16.150484] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff888114f2bc00
[   16.150485] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   16.150486] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   16.150487] R13: ffffffffffffffea R14: ffff888114f2bc00 R15: 0000000000000000
[   16.150488] FS:  00007f8d44ee0280(0000) GS:ffff8883ff600000(0000) knlGS:0000000000000000
[   16.150490] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   16.150491] CR2: ffffffffffffffd6 CR3: 000000010d850000 CR4: 0000000000350ef0
[   16.678778] pipewire-media-[4482]: segfault at 1cc ip 00007f534860bcba sp 00007ffe547fba00 error 4 in libasound.so.2.0.0[7f53485e6000+8d000]
[   16.678799] Code: b4 da 06 00 e8 d7 a8 fd ff 0f 1f 80 00 00 00 00 41 54 53 48 83 ec 08 48 85 ff 0f 84 bb 00 00 00 48 89 fb 48 8b bf a8 01 00 00 <8b> b7 cc 01 00 00 85 f6 75 3c 48 8b 83 98 01 00 00 48 8b 40 38 48
[   17.096864] pulseaudio[4413]: segfault at 50 ip 0000000000000050 sp 00007ffe031a7fb8 error 14 in pulseaudio[55ba0d042000+5000]
[   17.096877] Code: Unable to access opcode bytes at RIP 0x26.
[   17.921743] pulseaudio[8156]: segfault at 1cc ip 00007fb38f62fcba sp 00007ffcad62d840 error 4 in libasound.so.2.0.0[7fb38f60a000+8d000]
[   17.921752] Code: b4 da 06 00 e8 d7 a8 fd ff 0f 1f 80 00 00 00 00 41 54 53 48 83 ec 08 48 85 ff 0f 84 bb 00 00 00 48 89 fb 48 8b bf a8 01 00 00 <8b> b7 cc 01 00 00 85 f6 75 3c 48 8b 83 98 01 00 00 48 8b 40 38 48
[   17.964359] r8169 0000:02:00.0 enp2s0f0: Link is Up - 1Gbps/Full - flow control rx/tx
[   17.964387] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0f0: link becomes ready
[   17.978012] NET: Registered protocol family 17
[   18.754631] pulseaudio[8270]: segfault at 1cc ip 00007fcce2167cba sp 00007ffc4be8ec90 error 4 in libasound.so.2.0.0[7fcce2142000+8d000]
[   18.754643] Code: b4 da 06 00 e8 d7 a8 fd ff 0f 1f 80 00 00 00 00 41 54 53 48 83 ec 08 48 85 ff 0f 84 bb 00 00 00 48 89 fb 48 8b bf a8 01 00 00 <8b> b7 cc 01 00 00 85 f6 75 3c 48 8b 83 98 01 00 00 48 8b 40 38 48
[   19.554126] pulseaudio[8274]: segfault at 50 ip 0000000000000050 sp 00007ffe6bc92738 error 14 in pulseaudio[55787a30d000+5000]
[   19.554139] Code: Unable to access opcode bytes at RIP 0x26.
[   20.353320] pulseaudio[8278]: segfault at 50 ip 0000000000000050 sp 00007ffd686f7ca8 error 14 in pulseaudio[556163548000+5000]
[   20.353336] Code: Unable to access opcode bytes at RIP 0x26.
[   27.977231] logitech-hidpp-device 0003:046D:1028.0007: HID++ 1.0 device connected.
[   32.038688] pipewire-media-[8385]: segfault at 50 ip 0000000000000050 sp 00007ffc4e5d9738 error 14 in pipewire-media-session[55ef584e6000+1a000]
[   32.038705] Code: Unable to access opcode bytes at RIP 0x26.
[   34.210037] Bluetooth: RFCOMM TTY layer initialized
[   34.210051] Bluetooth: RFCOMM socket layer initialized
[   34.210059] Bluetooth: RFCOMM ver 1.11
[   65.641115] EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[  695.246663] usb 6-1.4.2: USB disconnect, device number 10
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: unklarer on 2021/07/22, 09:31:59
Thanks @towo, for solving this puzzle and thanks for your work!

Again, usrmerge was not installed.
Now everything is OK again.   :)

Code: [Select]
inxi -Sxxx
System:    Host: sidukde Kernel: 5.13.4-2-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)

@jure, thanks also to you for the link.   ;)
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: titan on 2021/07/22, 09:49:39
Thanks Towo for resolving this issue, All is working again but it begs the question why did we have to break our systems before we find out about usrmerge this is the first I and a lot of others knew about it.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: devil on 2021/07/22, 10:09:51
In 2019 there was a long thread on the topic: https://forum.siduction.org/index.php?topic=7640.msg62293#msg62293
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/22, 12:00:13
@cs,

Quote from: cs
....

[   16.089474] Oops: 0010 [#1] PREEMPT SMP NOPTI
[   16.089479] CPU: 5 PID: 3944 Comm: tpacpi-bat Tainted: G           O      5.13.4-2-siduction-amd64 #1 siduction 5.13-4.2
[   16.089485] Hardware name: LENOVO 20UGS00800/20UGS00800, BIOS R1CET63W(1.32 ) 04/09/2021
[   16.089488] RIP: 0010:0x0
[   16.089497] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   16.089500] RSP: 0018:ffffc9000214bef0 EFLAGS: 00010246
[   16.089504] RAX: 0000000000000000 RBX: ffff888103650540 RCX: 0000000000000001
[   16.089507] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff888114f2bc00
[   16.089510] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   16.089512] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   16.089514] R13: ffffffffffffffea R14: ffff888114f2bc00 R15: 0000000000000000
[   16.089517] FS:  00007feff45da280(0000) GS:ffff8883ff740000(0000) knlGS:0000000000000000
[   16.089521] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   16.089524] CR2: ffffffffffffffd6 CR3: 0000000127c5a000 CR4: 0000000000350ee0
[   16.089527] Call Trace:
[   16.089531]  proc_reg_llseek+0x45/0x80
[   16.089541]  ksys_lseek+0x7d/0xb0
[   16.089548]  do_syscall_64+0x40/0x80
[   16.089554]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   16.089560] RIP: 0033:0x7feff47ee647
[   16.089564] 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
.....

Are you sure this is kernel related?  Without the sound card attached, is the boot error-free on that Lenovo? Is the sound card very new, or very old?
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs on 2021/07/22, 21:14:27
@dibl

Without the sond-card attached, my box produces the following error messages:

Quote
dmesg | egrep -i "failed"
[   12.327790] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-63.ucode (-2)
[   12.327943] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-63.ucode (-2)
[   12.327969] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-63.ucode failed with error -2
[   12.619742] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[   12.619761] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[   12.695686] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
[   12.757741] thermal thermal_zone0: failed to read out thermal zone (-61)

Quote
dmesg | egrep -i "error"
[    0.982816] RAS: Correctable Errors collector initialized.
[   11.933049] EXT4-fs (nvme0n1p2): re-mounted. Opts: errors=remount-ro. Quota mode: none.
[   12.327969] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-63.ucode failed with error -2
[   15.573968] #PF: error_code(0x0010) - not-present page
[   15.630270] #PF: error_code(0x0010) - not-present page

Code: [Select]
[   15.573958] BUG: kernel NULL pointer dereference, address: 0000000000000000
[   15.573967] #PF: supervisor instruction fetch in kernel mode
[   15.573968] #PF: error_code(0x0010) - not-present page
[   15.573970] PGD 0 P4D 0
[   15.573972] Oops: 0010 [#1] PREEMPT SMP NOPTI
[   15.573975] CPU: 10 PID: 3699 Comm: tpacpi-bat Tainted: G           O      5.13.4-2-siduction-amd64 #1 siduction 5.13-4.2
[   15.573977] Hardware name: LENOVO 20UGS00800/20UGS00800, BIOS R1CET63W(1.32 ) 04/09/2021
[   15.573979] RIP: 0010:0x0
[   15.573984] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   15.573985] RSP: 0018:ffffc90002c8bef0 EFLAGS: 00010246
[   15.573987] RAX: 0000000000000000 RBX: ffff88810c9f3740 RCX: 0000000000000001
[   15.573988] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff88810a003000
[   15.573990] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   15.573991] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   15.573992] R13: ffffffffffffffea R14: ffff88810a003000 R15: 0000000000000000
[   15.573993] FS:  00007f25f9097280(0000) GS:ffff8883ff880000(0000) knlGS:0000000000000000
[   15.573995] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   15.573996] CR2: ffffffffffffffd6 CR3: 000000010b4be000 CR4: 0000000000350ee0
[   15.573998] Call Trace:
[   15.574000]  proc_reg_llseek+0x45/0x80
[   15.574006]  ksys_lseek+0x7d/0xb0
[   15.574010]  do_syscall_64+0x40/0x80
[   15.574013]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   15.574016] RIP: 0033:0x7f25f92ab647
[   15.574018] 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.574020] RSP: 002b:00007ffcc5661898 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
[   15.574022] RAX: ffffffffffffffda RBX: 0000564f99f09e80 RCX: 00007f25f92ab647
[   15.574023] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000003
[   15.574024] RBP: 0000564f9ababfd0 R08: 00007ffcc5661840 R09: 00000000ffffffff
[   15.574025] R10: 00007f25f9291b80 R11: 0000000000000246 R12: 0000564f9ab8b2a0
[   15.574026] R13: 00007ffcc5661a90 R14: 0000564f9ab8b3f0 R15: 0000564f9ac5fb10
[   15.574029] Modules linked in: acpi_call(O) af_packet cmac algif_hash algif_skcipher af_alg vboxnetadp(O) vboxnetflt(O) vboxdrv(O) bnep cpufreq_conservative cpufreq_powersave snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common btusb btrtl btbcm videodev btintel mc bluetooth iwlmvm snd_acp3x_pdm_dma snd_acp3x_rn snd_soc_dmic mac80211 libarc4 snd_soc_core intel_rapl_msr snd_compress snd_pcm_dmaengine ac97_bus snd_ctl_led snd_hda_codec_realtek intel_rapl_common snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi edac_mce_amd snd_hda_codec kvm_amd snd_hda_core nls_utf8 nls_cp437 snd_hwdep vmwgfx thinkpad_acpi iwlwifi vfat nvram kvm snd_pcm ucsi_acpi platform_profile fat joydev irqbypass snd_timer typec_ucsi ledtrig_audio ccp serio_raw pcspkr snd_rn_pci_acp3x rapl typec ipmi_devintf snd_pci_acp3x wmi_bmof snd k10temp sp5100_tco cfg80211 rng_core soundcore
[   15.574076]  ipmi_msghandler roles rfkill ac acpi_cpufreq evdev loop msr parport_pc ppdev lp parport fuse configfs sunrpc bpf_preload ip_tables x_tables hid_microsoft dm_crypt dm_mod 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 rtsx_pci_sdmmc i2c_algo_bit drm_ttm_helper mmc_core ttm crct10dif_pclmul crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel syscopyarea sysfillrect sysimgblt aesni_intel crypto_simd fb_sys_fops xhci_pci xhci_pci_renesas cryptd psmouse drm i2c_piix4 rtsx_pci agpgart xhci_hcd ehci_pci mfd_core r8169 ehci_hcd realtek wmi battery i2c_designware_platform i2c_scmi i2c_designware_core video i2c_core button
[   15.574117] CR2: 0000000000000000
[   15.574119] ---[ end trace 4a1b0933ed40f17f ]---
[   15.574120] RIP: 0010:0x0
[   15.574122] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   15.574123] RSP: 0018:ffffc90002c8bef0 EFLAGS: 00010246
[   15.574124] RAX: 0000000000000000 RBX: ffff88810c9f3740 RCX: 0000000000000001
[   15.574125] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff88810a003000
[   15.574126] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   15.574127] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   15.574128] R13: ffffffffffffffea R14: ffff88810a003000 R15: 0000000000000000
[   15.574129] FS:  00007f25f9097280(0000) GS:ffff8883ff880000(0000) knlGS:0000000000000000
[   15.574131] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   15.574132] CR2: ffffffffffffffd6 CR3: 000000010b4be000 CR4: 0000000000350ee0
[   15.630262] BUG: kernel NULL pointer dereference, address: 0000000000000000
[   15.630268] #PF: supervisor instruction fetch in kernel mode
[   15.630270] #PF: error_code(0x0010) - not-present page
[   15.630271] PGD 0 P4D 0
[   15.630274] Oops: 0010 [#2] PREEMPT SMP NOPTI
[   15.630276] CPU: 4 PID: 3980 Comm: tpacpi-bat Tainted: G      D    O      5.13.4-2-siduction-amd64 #1 siduction 5.13-4.2
[   15.630279] Hardware name: LENOVO 20UGS00800/20UGS00800, BIOS R1CET63W(1.32 ) 04/09/2021
[   15.630280] RIP: 0010:0x0
[   15.630286] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   15.630287] RSP: 0018:ffffc90002cd3ef0 EFLAGS: 00010246
[   15.630289] RAX: 0000000000000000 RBX: ffff88810c9f3740 RCX: 0000000000000002
[   15.630291] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff888114d7c600
[   15.630292] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   15.630293] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   15.630293] R13: ffffffffffffffea R14: ffff888114d7c600 R15: 0000000000000000
[   15.630295] FS:  00007fdf93c26280(0000) GS:ffff8883ff700000(0000) knlGS:0000000000000000
[   15.630296] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   15.630298] CR2: ffffffffffffffd6 CR3: 000000012a1d2000 CR4: 0000000000350ee0
[   15.630299] Call Trace:
[   15.630302]  proc_reg_llseek+0x45/0x80
[   15.630307]  ksys_lseek+0x7d/0xb0
[   15.630311]  do_syscall_64+0x40/0x80
[   15.630315]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   15.630318] RIP: 0033:0x7fdf93e3a647
[   15.630320] 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.630321] RSP: 002b:00007fff6216a7f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
[   15.630323] RAX: ffffffffffffffda RBX: 000055aeae4b2e80 RCX: 00007fdf93e3a647
[   15.630324] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000003
[   15.630325] RBP: 000055aeae644fd0 R08: 00007fff6216a7a0 R09: 00000000ffffffff
[   15.630326] R10: 00007fdf93e20b80 R11: 0000000000000246 R12: 000055aeae6242a0
[   15.630327] R13: 00007fff6216a9f0 R14: 000055aeae6243f0 R15: 000055aeae6f4e70
[   15.630330] Modules linked in: acpi_call(O) af_packet cmac algif_hash algif_skcipher af_alg vboxnetadp(O) vboxnetflt(O) vboxdrv(O) bnep cpufreq_conservative cpufreq_powersave snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common btusb btrtl btbcm videodev btintel mc bluetooth iwlmvm snd_acp3x_pdm_dma snd_acp3x_rn snd_soc_dmic mac80211 libarc4 snd_soc_core intel_rapl_msr snd_compress snd_pcm_dmaengine ac97_bus snd_ctl_led snd_hda_codec_realtek intel_rapl_common snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi edac_mce_amd snd_hda_codec kvm_amd snd_hda_core nls_utf8 nls_cp437 snd_hwdep vmwgfx thinkpad_acpi iwlwifi vfat nvram kvm snd_pcm ucsi_acpi platform_profile fat joydev irqbypass snd_timer typec_ucsi ledtrig_audio ccp serio_raw pcspkr snd_rn_pci_acp3x rapl typec ipmi_devintf snd_pci_acp3x wmi_bmof snd k10temp sp5100_tco cfg80211 rng_core soundcore
[   15.630377]  ipmi_msghandler roles rfkill ac acpi_cpufreq evdev loop msr parport_pc ppdev lp parport fuse configfs sunrpc bpf_preload ip_tables x_tables hid_microsoft dm_crypt dm_mod 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 rtsx_pci_sdmmc i2c_algo_bit drm_ttm_helper mmc_core ttm crct10dif_pclmul crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel syscopyarea sysfillrect sysimgblt aesni_intel crypto_simd fb_sys_fops xhci_pci xhci_pci_renesas cryptd psmouse drm i2c_piix4 rtsx_pci agpgart xhci_hcd ehci_pci mfd_core r8169 ehci_hcd realtek wmi battery i2c_designware_platform i2c_scmi i2c_designware_core video i2c_core button
[   15.630420] CR2: 0000000000000000
[   15.630422] ---[ end trace 4a1b0933ed40f180 ]---
[   15.630423] RIP: 0010:0x0
[   15.630425] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   15.630426] RSP: 0018:ffffc90002c8bef0 EFLAGS: 00010246
[   15.630427] RAX: 0000000000000000 RBX: ffff88810c9f3740 RCX: 0000000000000001
[   15.630429] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff88810a003000
[   15.630430] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   15.630430] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   15.630431] R13: ffffffffffffffea R14: ffff88810a003000 R15: 0000000000000000
[   15.630432] FS:  00007fdf93c26280(0000) GS:ffff8883ff700000(0000) knlGS:0000000000000000
[   15.630434] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   15.630435] CR2: ffffffffffffffd6 CR3: 000000012a1d2000 CR4: 0000000000350ee0

The sound-card is not particulary old, it's a Steinberg UR 22 C.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/23, 01:22:21
Quote
.....
[   15.573958] BUG: kernel NULL pointer dereference, address: 0000000000000000
[   15.573967] #PF: supervisor instruction fetch in kernel mode
[   15.573968] #PF: error_code(0x0010) - not-present page
[   15.573970] PGD 0 P4D 0
[   15.573972] Oops: 0010 [#1] PREEMPT SMP NOPTI
[   15.573975] CPU: 10 PID: 3699 Comm: tpacpi-bat Tainted: G           O      5.13.4-2-siduction-amd64 #1 siduction 5.13-4.2
[   15.573977] Hardware name: LENOVO 20UGS00800/20UGS00800, BIOS R1CET63W(1.32 ) 04/09/2021
[   15.573979] RIP: 0010:0x0
[   15.573984] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
[   15.573985] RSP: 0018:ffffc90002c8bef0 EFLAGS: 00010246
[   15.573987] RAX: 0000000000000000 RBX: ffff88810c9f3740 RCX: 0000000000000001
[   15.573988] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff88810a003000
[   15.573990] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[   15.573991] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[   15.573992] R13: ffffffffffffffea R14: ffff88810a003000 R15: 0000000000000000
[   15.573993] FS:  00007f25f9097280(0000) GS:ffff8883ff880000(0000) knlGS:0000000000000000
[   15.573995] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   15.573996] CR2: ffffffffffffffd6 CR3: 000000010b4be000 CR4: 0000000000350ee0
[   15.573998] Call Trace:
[   15.574000]  proc_reg_llseek+0x45/0x80
[   15.574006]  ksys_lseek+0x7d/0xb0
[   15.574010]  do_syscall_64+0x40/0x80
[   15.574013]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   15.574016] RIP: 0033:0x7f25f92ab647
[   15.574018] 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.574020] RSP: 002b:00007ffcc5661898 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
[   15.574022] RAX: ffffffffffffffda RBX: 0000564f99f09e80 RCX: 00007f25f92ab647
[   15.574023] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000003
[   15.574024] RBP: 0000564f9ababfd0 R08: 00007ffcc5661840 R09: 00000000ffffffff
[   15.574025] R10: 00007f25f9291b80 R11: 0000000000000246 R12: 0000564f9ab8b2a0.....

OK, I am no kernel diagnostics guru, so I don't offer a solution. But in 10 years of working with Linux systems, I have learned that a kernel "Oops" is a very bad thing -- it means something is incompatible on your hardware, and that is before you plug in the sound card. So I am saying you have a hardware compatibility problem unrelated to the sound card, that must be resolved first, before troubleshooting a USB sound card issue.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: Geier0815 on 2021/07/23, 09:05:37
@cs,

do you have installed the firmware? Is there something into /lib/firmware for your wifi-device? The error-message seems to me pointing to a missing firmware or a wrong version of it.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: bevo on 2021/07/23, 09:15:47
Related to the topic, the problem is not yet solved.
The WiFi's are visible but the connetion fails in c-blues and far-well installation, only patience is ok.
Message: no password found
so most likely I have to go back to patience  :-\
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: dibl on 2021/07/23, 21:25:13
Quote from: bevo
... The WiFi's are visible but the connection fails ... 

The problems encountered with 5.13.3-1 were never strictly wifi issues, AFAIK. What is your wifi chip and driver?  Here, wifi is working correctly on two older laptops with 5.13.4-3 (KDE, plasma-nm):

Code: [Select]
System:    Host: dibl-HP350 Kernel: 5.13.4-3-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.20.5
           Distro: siduction 18.3.0 Patience - kde - (201805132121)
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           IF: eno1 state: down mac: 34:64:a9:d0:2d:f0
           Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
           IF: wlo1 state: up mac: 38:b1:db:0e:01:01
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: hendrikL on 2021/07/23, 21:29:05
...
The WiFi's are visible .......
Message: no password found

I don't think that is related to the kernel, because the wifi is visible. The kernel done his job!

That must be another reason. Maybe a software failure.
So my first question, which flavor you are using? Xfce, KDE, Xorg, nox. mate or what ever.
Are you using wpa_supplicant or IWD, with network manager or not, questions over questions.
What does dmesg and or journalctl telling you,

Without any information about your system, no one can help you.

Sorry, but there is no crystal ball around here!
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: bevo on 2021/07/24, 10:22:00
You are right, to less information, sorry  :-[
Code: [Select]
System:    Host: X230 Kernel: 5.13.4-3-siduction-amd64 x86_64 bits: 64
           Desktop: KDE Plasma 5.20.5
           Distro: siduction 21.1.0 C-Blues - kde - (202102141913)
Network:   Device-1: Intel 82579LM Gigabit Network driver: e1000e
           IF: enp0s25 state: down mac: 3c:97:0e:77:b2:6c
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
           IF: wlp3s0 state: up mac: 84:3a:4b:74:43:08
but...mean while i made a new far-well installation on another machine.
All is fine  ;)

Sorry for confusion.

bevo

 

Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: towo on 2021/07/24, 10:37:18
Code: [Select]
towo@TP:~$ inxi -SNxxx
System:    Host: TP Kernel: 5.13.4-3-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Console: tty 0 DM: SDDM
           Distro: siduction 21.1.0 C-Blues - xorg - (202102111821) base: Debian GNU/Linux 11 (bullseye)
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo ThinkPad T520 driver: e1000e v: kernel port: 5080
           bus ID: 00:19.0 chip ID: 8086:1502 class ID: 0200
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0
           chip ID: 8086:0085 class ID: 0280

As you can see, the kernel has no problem with wifi.
It's the same chipset as yours and is working fine here.
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: hendrikL on 2021/07/24, 12:33:58
@bevo , so you are testing a xorg-iso, then it uses IWD for to connect the network.
On the ISO is an information/ help about how to use in short.
You should find it under the point Info/help or similar.
Right-click on the desktop, choose the siduction menu point (c-blues), on farewell it should be in the task panel, one of the click buttons iirc "!".
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: cs on 2021/07/24, 16:57:09
@dibl and @towo

I've installed the testing iso of the upcoming siduction release on my box.

As a result I had a working external soundcard again.

There where some error messages:

Quote
dmesg | grep -i "error\|warn\|fail"
[    2.155012] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    2.306543] thermal thermal_zone0: failed to read out thermal zone (-61)
[    2.616027] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
[    2.640728] WARNING: CPU: 10 PID: 666 at net/wireless/nl80211.c:7762 nl80211_get_reg_do+0x22c/0x2a0 [cfg80211]

But after a reboot, the soundcard failed again:

Quote
    [   43.901569] pulseaudio[2885]: segfault at fffffffffffffff8 ip 00007f66e5a310d7 sp 00007ffe48bcf1e0 error 5 in libasound.so.2.0.0[7f66e5a23000+8d000]
    [   44.516116] pulseaudio[4859]: segfault at 50 ip 0000000000000050 sp 00007ffe847e5928 error 14 in pulseaudio[55aaaf7bf000+5000]
    [   45.252028] pulseaudio[4863]: segfault at 1cc ip 00007f88daecbcba sp 00007fff33024050 error 4 in libasound.so.2.0.0[7f88daea6000+8d000]
    [   45.987212] pulseaudio[4867]: segfault at 1cc ip 00007f1be9a7ccba sp 00007fff32a7aff0 error 4 in libasound.so.2.0.0[7f1be9a57000+8d000]
    [   46.756049] pulseaudio[4871]: segfault at 1cc ip 00007fb31de09cba sp 00007fff62914d50 error 4 in libasound.so.2.0.0[7fb31dde4000+8d000]
    [   47.491113] pulseaudio[4875]: segfault at 50 ip 0000000000000050 sp 00007ffd5e81c8c8 error 14 in pulseaudio[55ccb7ec3000+5000]
Title: Re: Upgrade Warning -- kernel 5.13.3-1 may break networking
Post by: bevo on 2021/07/25, 09:10:13
@hendrikL
I use the KDE-Plasma ISO. As I have written in my last post the Problem is solved by a new installation.
never.
Nevertheles thank you for your help.

bevo