#StackBounty: #usb #serial #kernel Device drivers only working on boot

Bounty: 50

I am trying to connect some peripheral devices (test equipment) to a Raspberry Pi 4B+ running Raspbian and I am running into issues with device drivers for serial (using a pl2303 driver) and usb devices (using kernel module driver for usbtmc).

If I boot the Pi with both devices plugged in, there are no issues with the device nodes, and they both mount properly under /dev/usbtmc0 and /dev/ttyUSB0 respectively. However, if I unplug them and plug them back in, they no longer appear under these nodes. It seems like the device drivers are not loading and they are just recognized as USB devices.

Upon booting:

pi@raspberrypi:~ $ lsusb -t # shows driver information
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M
        |__ Port 3: Dev 5, If 0, Class=Application Specific Interface, Driver=usbtmc, 480M

You can see that the drivers are being used to interface with the devices.

After unplug/plug:

pi@raspberrypi:~ $ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

The drivers now disappear. Confirmation that they still exist as USB devices:

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 009: ID 1ab1:0e11 Rigol Technologies
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

My lshw output shows that they are now unclaimed devices:

*-usb:0 UNCLAIMED
                      description: Generic USB device
                      product: DP800 Serials
                      vendor: Rigol Technologies.
                      physical id: 1
                      bus info: usb@1:1.1
                      version: 0.02
                      serial: DP8B185050162
                      capabilities: usb-2.00
                      configuration: speed=480Mbit/s
                 *-usb:1 UNCLAIMED
                      description: Generic USB device
                      product: USB-Serial Controller D
                      vendor: Prolific Technology Inc.
                      physical id: 4
                      bus info: usb@1:1.4
                      version: 4.00
                      capabilities: usb-1.10
                      configuration: speed=12Mbit/s

This is my current kernel version:

$ cat /proc/version
Linux version 5.4.51-v7l+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1333 SMP Mon Aug 10 16:51:40 BST 2020

I’ve tried looking into manually adding the devices by VID and PID to the pl2303 driver, but that did not work. udev seems to not be able to do anything as well, as without the drivers it only sees them as usb devices and not the higher level usbtmc and usb-serial respectively. From my understanding, having these modules installed should allow it to load automatically upon plug-in, but that has not been the case for me. Any help would be greatly appreciated!


Get this bounty!!!

#StackBounty: #drivers #kernel #suspend #20.10 Suspend to RAM not working

Bounty: 150

Ubuntu 20.10 here, first installation upon a newly built system. Everything works perfectly except one thing that’s very important to me: suspend2ram.

If I try to suspend (sleep) via systemctl suspend, the screen blanks out, but nothing else happens, power stays on, fans spinning. At this point, if I press the power button, the monitor turns on, and all is how I left it.

Look at this now. On my system:

$ cat /sys/power/mem_sleep
[s2idle]

Whereas upon a laptop where suspend works, it is:

$ cat /sys/power/mem_sleep
s2idle [deep]

How can I debug the issue? Surely, there is some device which prevents suspend, but how to find it?

What follows are:

  1. inxi dump to show you the system config.
  2. relevant syslog dump.
System:    Host: bliz Kernel: 5.8.0-26-lowlatency x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: KDE Plasma 5.19.5 
           tk: Qt 5.14.2 wm: kwin_x11 dm: SDDM Distro: Ubuntu 20.10 (Groovy Gorilla) 
Machine:   Mobo: Supermicro model: X11SPA-TF v: 1.01 serial: <superuser/root required> UEFI: American Megatrends v: 3.3 
           date: 02/21/2020 
Memory:    RAM: total: 125.44 GiB used: 1.94 GiB (1.5%) 
           RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:       Info: 24-Core model: Intel Xeon Platinum 8260M bits: 64 type: MT MCP arch: Cascade Lake rev: 5 
           L2 cache: 33.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 220800 
           Speed: 1000 MHz min/max: 1000/3900 MHz Core speeds (MHz): 1: 1204 2: 1001 3: 1000 4: 1167 5: 1001 6: 1000 
           7: 1088 8: 1200 9: 1504 10: 1000 11: 1200 12: 1049 13: 1146 14: 1000 15: 1100 16: 1000 17: 1098 18: 1036 
           19: 1000 20: 1141 21: 1113 22: 1341 23: 1041 24: 1143 25: 1000 26: 1089 27: 1000 28: 1043 29: 1001 30: 1141 
           31: 1087 32: 1001 33: 1086 34: 1200 35: 1101 36: 1307 37: 1001 38: 1177 39: 1070 40: 1000 41: 1017 42: 1001 
           43: 1089 44: 1056 45: 1000 46: 1086 47: 1001 48: 1099 
Graphics:  Device-1: ASPEED Graphics Family vendor: Super Micro driver: ast v: kernel bus ID: 04:00.0 chip ID: 1a03:2000 
           Device-2: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 455.28 bus ID: 19:00.0 chip ID: 10de:1f06 
           Device-3: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 455.28 bus ID: 1a:00.0 chip ID: 10de:1f06 
           Device-4: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 455.28 bus ID: 65:00.0 chip ID: 10de:1f06 
           Device-5: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 455.28 bus ID: b4:00.0 chip ID: 10de:1f06 
           Display: x11 server: X.Org 1.20.9 compositor: kwin_x11 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           resolution: 1920x1080~60Hz s-dpi: 101 
           OpenGL: renderer: GeForce RTX 2060 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 455.28 direct render: Yes 
Network:   Device-1: Intel I210 Gigabit Network vendor: Super Micro driver: igb v: 5.6.0-k port: 2000 bus ID: 05:00.0 
           chip ID: 8086:1533 
           IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 00:25:90:be:43:2d 
           Device-2: Aquantia AQC107 NBase-T/IEEE 802.3bz Ethernet [AQtion] vendor: Super Micro driver: atlantic v: kernel 
           port: 2000 bus ID: 06:00.0 chip ID: 1d6a:07b1 
           IF: eth0 state: down mac: 00:25:90:be:43:f5 
Drives:    Local Storage: total: 476.94 GiB used: 11.38 GiB (2.4%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 PRO 512GB size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 
Partition: ID-1: / size: 287.37 GiB used: 11.37 GiB (4.0%) fs: ext4 dev: /dev/nvme0n1p2 
Swap:      ID-1: swap-1 type: partition size: 180.06 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A gpu: nvidia temp: 62 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 29% 
Info:      Processes: 752 Uptime: 2m Init: systemd v: 246 runlevel: 5 Compilers: gcc: 10.2.0 alt: 10 Packages: apt: 2979 
           Shell: Bash v: 5.0.17 running in: konsole inxi: 3.1.07 
Nov  7 17:50:25 bliz systemd[1]: anacron.service: Succeeded.
Nov  7 17:51:48 bliz ModemManager[1471]: <info>  [sleep-monitor] system is about to suspend
Nov  7 17:51:48 bliz NetworkManager[1289]: <info>  [1604767908.1255] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov  7 17:51:48 bliz NetworkManager[1289]: <info>  [1604767908.1256] manager: NetworkManager state is now ASLEEP
Nov  7 17:51:48 bliz whoopsie[2263]: [17:51:48] offline
Nov  7 17:51:48 bliz systemd[1]: Reached target Sleep.
Nov  7 17:51:48 bliz systemd[1]: Starting Suspend...
Nov  7 17:51:48 bliz kernel: [  995.921939] PM: suspend entry (s2idle)
Nov  7 17:51:48 bliz systemd-sleep[3346]: Suspending system...
Nov  7 17:51:48 bliz kernel: [  995.928295] Filesystems sync: 0.006 seconds
Nov  7 17:51:48 bliz acpid: client 1788[0:0] has disconnected
Nov  7 17:52:10 bliz kernel: [  996.340713] Freezing user space processes ... (elapsed 0.002 seconds) done.
Nov  7 17:52:10 bliz kernel: [  996.343045] OOM killer disabled.
Nov  7 17:52:10 bliz kernel: [  996.343046] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov  7 17:52:10 bliz kernel: [  996.344199] printk: Suspending console(s) (use no_console_suspend to debug)
Nov  7 17:52:10 bliz kernel: [  996.346322] serial 00:04: disabled
Nov  7 17:52:10 bliz kernel: [  996.346577] serial 00:03: disabled
Nov  7 17:52:10 bliz kernel: [ 1016.883067] pci 0000:16:05.0: disabled boot interrupts on device [8086:2034]
Nov  7 17:52:10 bliz kernel: [ 1016.883157] pci 0000:64:05.0: disabled boot interrupts on device [8086:2034]
Nov  7 17:52:10 bliz kernel: [ 1016.883192] pci 0000:b2:05.0: disabled boot interrupts on device [8086:2034]
Nov  7 17:52:10 bliz kernel: [ 1016.883581] usb usb3: root hub lost power or was reset
Nov  7 17:52:10 bliz kernel: [ 1016.883584] usb usb4: root hub lost power or was reset
Nov  7 17:52:10 bliz kernel: [ 1016.883594] usb usb5: root hub lost power or was reset
Nov  7 17:52:10 bliz kernel: [ 1016.883597] usb usb6: root hub lost power or was reset
Nov  7 17:52:10 bliz kernel: [ 1016.883940] power_meter ACPI000D:00: Found ACPI power meter.
Nov  7 17:52:10 bliz kernel: [ 1016.885528] serial 00:03: activated
Nov  7 17:52:10 bliz kernel: [ 1016.886870] serial 00:04: activated
Nov  7 17:52:10 bliz kernel: [ 1016.943776] nvme nvme0: Shutdown timeout set to 8 seconds
Nov  7 17:52:10 bliz kernel: [ 1016.972019] nvme nvme0: 32/0/0 default/read/poll queues
Nov  7 17:52:10 bliz kernel: [ 1017.212955] ata3: SATA link down (SStatus 0 SControl 300)
Nov  7 17:52:10 bliz kernel: [ 1017.214100] ata2: SATA link down (SStatus 0 SControl 300)
Nov  7 17:52:10 bliz kernel: [ 1017.214135] ata8: SATA link down (SStatus 0 SControl 300)
Nov  7 17:52:10 bliz kernel: [ 1017.214177] ata6: SATA link down (SStatus 0 SControl 300)
Nov  7 17:52:10 bliz kernel: [ 1017.214222] ata5: SATA link down (SStatus 0 SControl 300)
Nov  7 17:52:10 bliz kernel: [ 1017.214266] ata7: SATA link down (SStatus 0 SControl 300)
Nov  7 17:52:10 bliz kernel: [ 1017.214312] ata1: SATA link down (SStatus 0 SControl 300)
Nov  7 17:52:10 bliz kernel: [ 1017.214368] ata4: SATA link down (SStatus 0 SControl 300)
Nov  7 17:52:10 bliz kernel: [ 1017.392324] usb 1-1.2: reset low-speed USB device number 6 using xhci_hcd
Nov  7 17:52:10 bliz kernel: [ 1017.751867] usb 1-1.2: device descriptor read/64, error -32
Nov  7 17:52:10 bliz kernel: [ 1018.749136] fbcon: Taking over console
Nov  7 17:52:10 bliz kernel: [ 1018.749140] OOM killer enabled.
Nov  7 17:52:10 bliz kernel: [ 1018.749141] Restarting tasks ... 
Nov  7 17:52:10 bliz kernel: [ 1018.751194] Console: switching to colour frame buffer device 128x48
Nov  7 17:52:10 bliz kernel: [ 1018.751614] done.
Nov  7 17:52:10 bliz kernel: [ 1018.754898] PM: suspend exit
Nov  7 17:52:10 bliz acpid: client 1788[0:0] has disconnected
Nov  7 17:52:10 bliz pipewire[2335]: #033[1;33m[W][000000998.421004][main-loop.c:157 pw_main_loop_run()] main-loop 0x55fa059cc0a0: iterate error -4 (Interrupted system call)#033[0m
Nov  7 17:52:10 bliz systemd-sleep[3346]: System resumed.
Nov  7 17:52:10 bliz acpid: client 1788[0:0] has disconnected
Nov  7 17:52:10 bliz pipewire[2341]: #033[1;33m[W][000000998.421027][main-loop.c:157 pw_main_loop_run()] main-loop 0x55eacc699e10: iterate error -4 (Interrupted system call)#033[0m
Nov  7 17:52:10 bliz acpid: client 1788[0:0] has disconnected
Nov  7 17:52:10 bliz systemd[1]: systemd-suspend.service: Succeeded.
Nov  7 17:52:10 bliz systemd[1]: Finished Suspend.
Nov  7 17:52:10 bliz systemd[1]: Stopped target Sleep.
Nov  7 17:52:10 bliz systemd[1]: Reached target Suspend.
Nov  7 17:52:10 bliz systemd[1]: Stopped target Suspend.
Nov  7 17:52:10 bliz ModemManager[1471]: <info>  [sleep-monitor] system is resuming
Nov  7 17:52:10 bliz NetworkManager[1289]: <info>  [1604767930.9755] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Nov  7 17:52:10 bliz NetworkManager[1289]: <info>  [1604767930.9757] device (eno1): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov  7 17:52:10 bliz NetworkManager[1289]: <info>  [1604767930.9928] dhcp4 (eno1): canceled DHCP transaction
Nov  7 17:52:10 bliz NetworkManager[1289]: <info>  [1604767930.9929] dhcp4 (eno1): state changed bound -> done
Nov  7 17:52:10 bliz avahi-daemon[1283]: Withdrawing address record for 192.168.1.7 on eno1.
Nov  7 17:52:10 bliz avahi-daemon[1283]: Leaving mDNS multicast group on interface eno1.IPv4 with address 192.168.1.7.
Nov  7 17:52:10 bliz avahi-daemon[1283]: Interface eno1.IPv4 no longer relevant for mDNS.
Nov  7 17:52:10 bliz avahi-daemon[1283]: Withdrawing address record for fe80::b8ff:d7cb:f7bb:ca99 on eno1.
Nov  7 17:52:10 bliz avahi-daemon[1283]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80::b8ff:d7cb:f7bb:ca99.
Nov  7 17:52:10 bliz avahi-daemon[1283]: Interface eno1.IPv6 no longer relevant for mDNS.
Nov  7 17:52:11 bliz NetworkManager[1289]: <info>  [1604767931.0036] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov  7 17:52:11 bliz NetworkManager[1289]: <info>  [1604767931.0329] manager: NetworkManager state is now DISCONNECTED
Nov  7 17:52:11 bliz NetworkManager[1289]: <info>  [1604767931.0341] device (eth0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov  7 17:52:11 bliz NetworkManager[1289]: <info>  [1604767931.0369] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Nov  7 17:52:11 bliz dbus-daemon[1287]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1289 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Nov  7 17:52:11 bliz systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov  7 17:52:11 bliz dbus-daemon[1287]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov  7 17:52:11 bliz systemd[1]: Started Network Manager Script Dispatcher Service.
Nov  7 17:52:11 bliz nm-dispatcher[3625]: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
Nov  7 17:52:11 bliz NetworkManager[1289]: <info>  [1604767931.0651] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Nov  7 17:52:11 bliz acpid: client connected from 1788[0:0]
Nov  7 17:52:11 bliz acpid: 1 client rule loaded
Nov  7 17:52:11 bliz acpid: client connected from 1788[0:0]
Nov  7 17:52:11 bliz acpid: 1 client rule loaded
Nov  7 17:52:11 bliz acpid: client connected from 1788[0:0]
Nov  7 17:52:11 bliz acpid: 1 client rule loaded
Nov  7 17:52:11 bliz acpid: client connected from 1788[0:0]
Nov  7 17:52:11 bliz acpid: 1 client rule loaded
Nov  7 17:52:13 bliz ModemManager[1471]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.6/0000:05:00.0': not supported by any plugin
Nov  7 17:52:14 bliz kernel: [ 1021.957276] igb 0000:05:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Nov  7 17:52:14 bliz kernel: [ 1022.063973] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2455] device (eno1): carrier: link connected
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2459] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2475] policy: auto-activating connection 'Wired connection 1' (da1d0e20-bea3-38af-9caf-d380db64c81e)
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2485] device (eno1): Activation: starting connection 'Wired connection 1' (da1d0e20-bea3-38af-9caf-d380db64c81e)
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2487] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2494] manager: NetworkManager state is now CONNECTING
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2499] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2509] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2513] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Nov  7 17:52:14 bliz avahi-daemon[1283]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::b8ff:d7cb:f7bb:ca99.
Nov  7 17:52:14 bliz avahi-daemon[1283]: New relevant interface eno1.IPv6 for mDNS.
Nov  7 17:52:14 bliz avahi-daemon[1283]: Registering new address record for fe80::b8ff:d7cb:f7bb:ca99 on eno1.*.
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2811] dhcp4 (eno1): option dhcp_lease_time      => '21600'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2811] dhcp4 (eno1): option domain_name          => 'homenet.telecomitalia.it'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2811] dhcp4 (eno1): option domain_name_servers  => '192.168.1.1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2811] dhcp4 (eno1): option expiry               => '1604789534'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2812] dhcp4 (eno1): option ip_address           => '192.168.1.7'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2812] dhcp4 (eno1): option requested_broadcast_address => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2812] dhcp4 (eno1): option requested_domain_name => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2812] dhcp4 (eno1): option requested_domain_name_servers => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2812] dhcp4 (eno1): option requested_domain_search => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2812] dhcp4 (eno1): option requested_host_name  => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2812] dhcp4 (eno1): option requested_interface_mtu => '1'
Nov  7 17:52:14 bliz avahi-daemon[1283]: Joining mDNS multicast group on interface eno1.IPv4 with address 192.168.1.7.
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2812] dhcp4 (eno1): option requested_ms_classless_static_routes => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2813] dhcp4 (eno1): option requested_nis_domain => '1'
Nov  7 17:52:14 bliz avahi-daemon[1283]: New relevant interface eno1.IPv4 for mDNS.
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2813] dhcp4 (eno1): option requested_nis_servers => '1'
Nov  7 17:52:14 bliz avahi-daemon[1283]: Registering new address record for 192.168.1.7 on eno1.IPv4.
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2813] dhcp4 (eno1): option requested_ntp_servers => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2813] dhcp4 (eno1): option requested_rfc3442_classless_static_routes => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2813] dhcp4 (eno1): option requested_root_path  => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2813] dhcp4 (eno1): option requested_routers    => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2813] dhcp4 (eno1): option requested_static_routes => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2813] dhcp4 (eno1): option requested_subnet_mask => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2814] dhcp4 (eno1): option requested_time_offset => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2814] dhcp4 (eno1): option requested_wpad       => '1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2814] dhcp4 (eno1): option routers              => '192.168.1.1'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2814] dhcp4 (eno1): option subnet_mask          => '255.255.255.0'
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2814] dhcp4 (eno1): state changed unknown -> bound
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2836] device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2858] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2860] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2865] manager: NetworkManager state is now CONNECTED_LOCAL
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2875] manager: NetworkManager state is now CONNECTED_SITE
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2876] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2953] device (eno1): Activation: successful, device activated.
Nov  7 17:52:14 bliz NetworkManager[1289]: <info>  [1604767934.2965] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov  7 17:52:16 bliz systemd-resolved[1264]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Nov  7 17:52:16 bliz whoopsie[2263]: [17:52:16] Cannot reach: https://daisy.ubuntu.com
Nov  7 17:52:16 bliz whoopsie[2263]: [17:52:16] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov  7 17:52:16 bliz whoopsie[2263]: [17:52:16] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov  7 17:52:16 bliz whoopsie[2263]: [17:52:16] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov  7 17:52:16 bliz whoopsie[2263]: [17:52:16] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov  7 17:52:16 bliz whoopsie[2263]: [17:52:16] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov  7 17:52:16 bliz whoopsie[2263]: [17:52:16] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov  7 17:52:16 bliz whoopsie[2263]: [17:52:16] online
Nov  7 17:52:16 bliz dbus-daemon[2340]: [session uid=1000 pid=2340] Activating service name='org.kde.KSplash' requested by ':1.98' (uid=1000 pid=3707 comm="/usr/bin/kwin_x11 --crashes 1 " label="unconfined")
Nov  7 17:52:24 bliz systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Nov  7 17:52:29 bliz systemd-resolved[1264]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.


Get this bounty!!!

#StackBounty: #kernel #boot #raid #sata change order of SATA and RAID controller when booting linux kernel

Bounty: 300

I have onboard SATA controller, and also an additional RAID controller card:

00:17.0 SATA controller: Intel Corporation Device a282
...
04:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 3108 [Invader] (rev 02)

When linux kernel boots, disks connected on the LSI raid controller are recognized/enumerated first (sda,sdb,…), and disk hanging on the SATA controller after that (sde).

My kernel is monolithic, without loadable modules. Is it possible to tell the kernel, the disk on the SATA controller should be first (sda) ?

What affects the order? Is this just an accident, that LSI raid is recognized first, or can this be changed?


Get this bounty!!!

#StackBounty: #networking #drivers #network-adapter #kernel #ubuntu-18.04 How To Find Root Cause of Network Card Down

Bounty: 100

Recently I encounter a very puzzuling problem. We are doing AI traingings based on some type of NPU device. The training usually read/write data from/to some NFS directory, and during the training we found the network device became down status.

We tried executing ip link set dev xxxx up, only to find that it doesn’t take any effect in the real status of this device. It keeps down status until we reboots the machine.

Via the system log (ubuntu 18.04) and the NIC driver log, we know something is wrong either with the card or the driver upon the card. The driver keeps complaining something like "update mac stats fail, get mac pkt stats fail" etc.

The most interesting and difficult thing is to figure out what application behavior triggers this issue and how that makes it happens.

How can a user-space application cause the NIC to go down? Is it possible to figure out what happens there without having the source code of the NIC driver?

Please help me to explain this, or give me some suggestions about how to figure it out, or list some documentations on it.


Get this bounty!!!

#StackBounty: #boot #grub2 #upgrade #kernel #20.04 ZFS doesn't allow me to follow kernels with updates

Bounty: 150

I installed ubuntu 20.04 sometime in june.

by now I’m updated to ubuntu 20.04.1 LTS

there’s been a few kernel updates. end everytime I run updates Zsys tries to put new kernel version as the first option.

And I’d like nothing more but to use the new kernels.

but they simply won’t boot.

when I say won’t boot, I mean some kinda freeze happens during the boot process I can’t drop to TTY/boot command line and I don’t get any error messages (maybe I’m not hitting the right key)

I just have my motherboard logo and that’s it.

the ubuntu logo and spinner don’t show up and it could stay like this indefinitely if I did nothing.

luckily i still have my old grub entry and with grub customizer I’ve been keeping it at the top of the list.

but I want to solve this issue now before ubuntu decides I’ve been hoarding an old kernel for too long.

is there something in particular I’m supposed to do to boot a new kernel with ZFS?

I’m guessing it has nothing to do with the specific kernel version and more to do with zfs being a block that’s not yet intricately tied into the rest of the OS. and where ubuntu is able to automatically update the kernel references everywhere else it doesn’t yet automatically update a variable inside ZFS that points to the kernel version, or something like that?

I don’t know.

Anyways :

t@tsu:~$ dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'
ii  linux-image-5.4.0-40-generic                                5.4.0-40.44                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-45-generic                                5.4.0-45.49                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-47-generic                                5.4.0-47.51                                                 amd64        Signed kernel image generic

5.4.0-40 boots and is the one my ubuntu 20.04 installed with

5.4.0-45 does not boot and was installed by updates not by me

5.4.0-47 does not boot and was installed by updates not by me

Ideally I’d like to boot 5.4.0-47

EDIT :

On kernel installs I do get an error :

Setting up linux-modules-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
Setting up linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-47-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-47-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.48-050448-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.4.48-050448-generic
Processing triggers for linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.48-050448-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.48-050448-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=53c19176-f03e-4c40-a6ed-3a2627160647)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...

and a ton of these :

Warning: Couldn't find any valid initrd for dataset rpool/ROOT/ubuntu_38tazy@autozsys_7lfyl1.

and here’s update-grub :

(doesn’t look optimal)

https://pastebin.com/8y6x36u4


Get this bounty!!!

#StackBounty: #boot #grub2 #upgrade #kernel #20.04 ZFS doesn't allow me to follow kernels with updates

Bounty: 150

I installed ubuntu 20.04 sometime in june.

by now I’m updated to ubuntu 20.04.1 LTS

there’s been a few kernel updates. end everytime I run updates Zsys tries to put new kernel version as the first option.

And I’d like nothing more but to use the new kernels.

but they simply won’t boot.

when I say won’t boot, I mean some kinda freeze happens during the boot process I can’t drop to TTY/boot command line and I don’t get any error messages (maybe I’m not hitting the right key)

I just have my motherboard logo and that’s it.

the ubuntu logo and spinner don’t show up and it could stay like this indefinitely if I did nothing.

luckily i still have my old grub entry and with grub customizer I’ve been keeping it at the top of the list.

but I want to solve this issue now before ubuntu decides I’ve been hoarding an old kernel for too long.

is there something in particular I’m supposed to do to boot a new kernel with ZFS?

I’m guessing it has nothing to do with the specific kernel version and more to do with zfs being a block that’s not yet intricately tied into the rest of the OS. and where ubuntu is able to automatically update the kernel references everywhere else it doesn’t yet automatically update a variable inside ZFS that points to the kernel version, or something like that?

I don’t know.

Anyways :

t@tsu:~$ dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'
ii  linux-image-5.4.0-40-generic                                5.4.0-40.44                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-45-generic                                5.4.0-45.49                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-47-generic                                5.4.0-47.51                                                 amd64        Signed kernel image generic

5.4.0-40 boots and is the one my ubuntu 20.04 installed with

5.4.0-45 does not boot and was installed by updates not by me

5.4.0-47 does not boot and was installed by updates not by me

Ideally I’d like to boot 5.4.0-47

EDIT :

On kernel installs I do get an error :

Setting up linux-modules-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
Setting up linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-47-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-47-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.48-050448-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.4.48-050448-generic
Processing triggers for linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.48-050448-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.48-050448-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=53c19176-f03e-4c40-a6ed-3a2627160647)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...

and a ton of these :

Warning: Couldn't find any valid initrd for dataset rpool/ROOT/ubuntu_38tazy@autozsys_7lfyl1.

and here’s update-grub :

(doesn’t look optimal)

https://pastebin.com/8y6x36u4


Get this bounty!!!

#StackBounty: #boot #grub2 #upgrade #kernel #20.04 ZFS doesn't allow me to follow kernels with updates

Bounty: 150

I installed ubuntu 20.04 sometime in june.

by now I’m updated to ubuntu 20.04.1 LTS

there’s been a few kernel updates. end everytime I run updates Zsys tries to put new kernel version as the first option.

And I’d like nothing more but to use the new kernels.

but they simply won’t boot.

when I say won’t boot, I mean some kinda freeze happens during the boot process I can’t drop to TTY/boot command line and I don’t get any error messages (maybe I’m not hitting the right key)

I just have my motherboard logo and that’s it.

the ubuntu logo and spinner don’t show up and it could stay like this indefinitely if I did nothing.

luckily i still have my old grub entry and with grub customizer I’ve been keeping it at the top of the list.

but I want to solve this issue now before ubuntu decides I’ve been hoarding an old kernel for too long.

is there something in particular I’m supposed to do to boot a new kernel with ZFS?

I’m guessing it has nothing to do with the specific kernel version and more to do with zfs being a block that’s not yet intricately tied into the rest of the OS. and where ubuntu is able to automatically update the kernel references everywhere else it doesn’t yet automatically update a variable inside ZFS that points to the kernel version, or something like that?

I don’t know.

Anyways :

t@tsu:~$ dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'
ii  linux-image-5.4.0-40-generic                                5.4.0-40.44                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-45-generic                                5.4.0-45.49                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-47-generic                                5.4.0-47.51                                                 amd64        Signed kernel image generic

5.4.0-40 boots and is the one my ubuntu 20.04 installed with

5.4.0-45 does not boot and was installed by updates not by me

5.4.0-47 does not boot and was installed by updates not by me

Ideally I’d like to boot 5.4.0-47

EDIT :

On kernel installs I do get an error :

Setting up linux-modules-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
Setting up linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-47-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-47-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.48-050448-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.4.48-050448-generic
Processing triggers for linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.48-050448-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.48-050448-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=53c19176-f03e-4c40-a6ed-3a2627160647)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...

and a ton of these :

Warning: Couldn't find any valid initrd for dataset rpool/ROOT/ubuntu_38tazy@autozsys_7lfyl1.

and here’s update-grub :

(doesn’t look optimal)

https://pastebin.com/8y6x36u4


Get this bounty!!!

#StackBounty: #boot #grub2 #upgrade #kernel #20.04 ZFS doesn't allow me to follow kernels with updates

Bounty: 150

I installed ubuntu 20.04 sometime in june.

by now I’m updated to ubuntu 20.04.1 LTS

there’s been a few kernel updates. end everytime I run updates Zsys tries to put new kernel version as the first option.

And I’d like nothing more but to use the new kernels.

but they simply won’t boot.

when I say won’t boot, I mean some kinda freeze happens during the boot process I can’t drop to TTY/boot command line and I don’t get any error messages (maybe I’m not hitting the right key)

I just have my motherboard logo and that’s it.

the ubuntu logo and spinner don’t show up and it could stay like this indefinitely if I did nothing.

luckily i still have my old grub entry and with grub customizer I’ve been keeping it at the top of the list.

but I want to solve this issue now before ubuntu decides I’ve been hoarding an old kernel for too long.

is there something in particular I’m supposed to do to boot a new kernel with ZFS?

I’m guessing it has nothing to do with the specific kernel version and more to do with zfs being a block that’s not yet intricately tied into the rest of the OS. and where ubuntu is able to automatically update the kernel references everywhere else it doesn’t yet automatically update a variable inside ZFS that points to the kernel version, or something like that?

I don’t know.

Anyways :

t@tsu:~$ dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'
ii  linux-image-5.4.0-40-generic                                5.4.0-40.44                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-45-generic                                5.4.0-45.49                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-47-generic                                5.4.0-47.51                                                 amd64        Signed kernel image generic

5.4.0-40 boots and is the one my ubuntu 20.04 installed with

5.4.0-45 does not boot and was installed by updates not by me

5.4.0-47 does not boot and was installed by updates not by me

Ideally I’d like to boot 5.4.0-47

EDIT :

On kernel installs I do get an error :

Setting up linux-modules-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
Setting up linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-47-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-47-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.48-050448-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.4.48-050448-generic
Processing triggers for linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.48-050448-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.48-050448-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=53c19176-f03e-4c40-a6ed-3a2627160647)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...

and a ton of these :

Warning: Couldn't find any valid initrd for dataset rpool/ROOT/ubuntu_38tazy@autozsys_7lfyl1.

and here’s update-grub :

(doesn’t look optimal)

https://pastebin.com/8y6x36u4


Get this bounty!!!

#StackBounty: #boot #grub2 #upgrade #kernel #20.04 ZFS doesn't allow me to follow kernels with updates

Bounty: 150

I installed ubuntu 20.04 sometime in june.

by now I’m updated to ubuntu 20.04.1 LTS

there’s been a few kernel updates. end everytime I run updates Zsys tries to put new kernel version as the first option.

And I’d like nothing more but to use the new kernels.

but they simply won’t boot.

when I say won’t boot, I mean some kinda freeze happens during the boot process I can’t drop to TTY/boot command line and I don’t get any error messages (maybe I’m not hitting the right key)

I just have my motherboard logo and that’s it.

the ubuntu logo and spinner don’t show up and it could stay like this indefinitely if I did nothing.

luckily i still have my old grub entry and with grub customizer I’ve been keeping it at the top of the list.

but I want to solve this issue now before ubuntu decides I’ve been hoarding an old kernel for too long.

is there something in particular I’m supposed to do to boot a new kernel with ZFS?

I’m guessing it has nothing to do with the specific kernel version and more to do with zfs being a block that’s not yet intricately tied into the rest of the OS. and where ubuntu is able to automatically update the kernel references everywhere else it doesn’t yet automatically update a variable inside ZFS that points to the kernel version, or something like that?

I don’t know.

Anyways :

t@tsu:~$ dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'
ii  linux-image-5.4.0-40-generic                                5.4.0-40.44                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-45-generic                                5.4.0-45.49                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-47-generic                                5.4.0-47.51                                                 amd64        Signed kernel image generic

5.4.0-40 boots and is the one my ubuntu 20.04 installed with

5.4.0-45 does not boot and was installed by updates not by me

5.4.0-47 does not boot and was installed by updates not by me

Ideally I’d like to boot 5.4.0-47

EDIT :

On kernel installs I do get an error :

Setting up linux-modules-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
Setting up linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-47-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-47-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.48-050448-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.4.48-050448-generic
Processing triggers for linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.48-050448-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.48-050448-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=53c19176-f03e-4c40-a6ed-3a2627160647)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...

and a ton of these :

Warning: Couldn't find any valid initrd for dataset rpool/ROOT/ubuntu_38tazy@autozsys_7lfyl1.

and here’s update-grub :

(doesn’t look optimal)

https://pastebin.com/8y6x36u4


Get this bounty!!!

#StackBounty: #boot #grub2 #upgrade #kernel #20.04 ZFS doesn't allow me to follow kernels with updates

Bounty: 150

I installed ubuntu 20.04 sometime in june.

by now I’m updated to ubuntu 20.04.1 LTS

there’s been a few kernel updates. end everytime I run updates Zsys tries to put new kernel version as the first option.

And I’d like nothing more but to use the new kernels.

but they simply won’t boot.

when I say won’t boot, I mean some kinda freeze happens during the boot process I can’t drop to TTY/boot command line and I don’t get any error messages (maybe I’m not hitting the right key)

I just have my motherboard logo and that’s it.

the ubuntu logo and spinner don’t show up and it could stay like this indefinitely if I did nothing.

luckily i still have my old grub entry and with grub customizer I’ve been keeping it at the top of the list.

but I want to solve this issue now before ubuntu decides I’ve been hoarding an old kernel for too long.

is there something in particular I’m supposed to do to boot a new kernel with ZFS?

I’m guessing it has nothing to do with the specific kernel version and more to do with zfs being a block that’s not yet intricately tied into the rest of the OS. and where ubuntu is able to automatically update the kernel references everywhere else it doesn’t yet automatically update a variable inside ZFS that points to the kernel version, or something like that?

I don’t know.

Anyways :

t@tsu:~$ dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'
ii  linux-image-5.4.0-40-generic                                5.4.0-40.44                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-45-generic                                5.4.0-45.49                                                 amd64        Signed kernel image generic
ii  linux-image-5.4.0-47-generic                                5.4.0-47.51                                                 amd64        Signed kernel image generic

5.4.0-40 boots and is the one my ubuntu 20.04 installed with

5.4.0-45 does not boot and was installed by updates not by me

5.4.0-47 does not boot and was installed by updates not by me

Ideally I’d like to boot 5.4.0-47

EDIT :

On kernel installs I do get an error :

Setting up linux-modules-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
Setting up linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-47-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-47-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.48-050448-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.4.48-050448-generic
Processing triggers for linux-image-unsigned-5.4.48-050448-generic (5.4.48-050448.202006220832) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.48-050448-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.48-050448-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=53c19176-f03e-4c40-a6ed-3a2627160647)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...

and a ton of these :

Warning: Couldn't find any valid initrd for dataset rpool/ROOT/ubuntu_38tazy@autozsys_7lfyl1.

and here’s update-grub :

(doesn’t look optimal)

https://pastebin.com/8y6x36u4


Get this bounty!!!