Dev1 Galaxy Forum / New bpo Kernel Upgrade 6.10.11+bpo-amd64 fails to boot

Re: New bpo Kernel Upgrade 6.10.11+bpo-amd64 fails to boot

dummy@example.com (alexkemp) — Sun, 17 Nov 2024 03:17:48 +0000

This turned out to be a bad dkms for a SDR device (software driven radio, which I do not use anymore) & was fixed like this (install following the purge):

$ sudo apt purge xtrx-dkms

14 updates made after including new firmware. Seems ok so far.

Re: New bpo Kernel Upgrade 6.10.11+bpo-amd64 fails to boot

dummy@example.com (stargate-sg1-cheyenne-mtn) — Sun, 10 Nov 2024 22:27:18 +0000

devuan daedalus normal/standard install

someone@somewhere:~$ reportbug --version
reportbug 12.0.0+devuan2

Re: New bpo Kernel Upgrade 6.10.11+bpo-amd64 fails to boot

dummy@example.com (Altoid) — Sun, 10 Nov 2024 17:23:03 +0000

Hello:

alexkemp wrote:

... could not find an easy way to do that ...

You can also do it via email.

See here: https://www.debian.org/Bugs/Reporting

Sending the bug report via e-mail
--- snip ---
You can report bugs in Debian by sending an e-mail to submit@bugs.debian.org with a special format described below. reportbug (see above) will properly format the e-mails for you; please use it!
--- snip ---

I guess that as long as it is properly formatted, it will not bounce / be ignored.
Maybe just avoid mentioning Devuan ... 8^°

Best,

Re: New bpo Kernel Upgrade 6.10.11+bpo-amd64 fails to boot

dummy@example.com (alexkemp) — Sun, 10 Nov 2024 12:28:35 +0000

I assume that a bug-report here needs to be to Debian. I could not find an easy way to do that (they use an auto-report which expects you to be using Debian). Any advice?

Re: New bpo Kernel Upgrade 6.10.11+bpo-amd64 fails to boot

dummy@example.com (steve_v) — Sun, 10 Nov 2024 11:36:11 +0000

A non-booting kernel or broken driver really isn't a big deal, and frankly I have no idea why people seem to get so flustered by it (see recent Debian drama WRT out-of-tree nvidia driver "completely breaking" systems).
Pretty much every distro keeps old kernels around (and generates bootloader entries for them) for exactly this scenario.

Even without that, you can just boot a livecd/usb and set root= appropriately or chroot in. Unless one is silly enough to encrypt / and not keep a record of the key OFC... Or use secure retarded-boot, but that's really a bootloader issue and only makes using live media more annoying.

Re: New bpo Kernel Upgrade 6.10.11+bpo-amd64 fails to boot

dummy@example.com (alexkemp) — Sun, 10 Nov 2024 11:04:08 +0000

steve_v wrote:

Why? You're running an uncommon driver for uncommon hardware, on a backported kernel.
Expect this class of problem with new kernels and out-of-tree drivers.

I'm not certain about the 'uncommon hardware' bit, but I accept your sentiments.

First time this has happened to me. Frightened the shit out of me when I got to the boot screen!

Re: New bpo Kernel Upgrade 6.10.11+bpo-amd64 fails to boot

dummy@example.com (steve_v) — Sun, 10 Nov 2024 03:59:00 +0000

xtrx-dkms is fixed in sid/ceres/unstable, either wait for somebody to punt it to backports or just do it yourself.

I cannot find anything on the web about this.

It literally took me longer to write this post than it did to find the information above.

Difficult to believe that I am the only one.

Why? You're running an uncommon driver for uncommon hardware, on a backported kernel.
Expect this class of problem with new kernels and out-of-tree drivers.

New bpo Kernel Upgrade 6.10.11+bpo-amd64 fails to boot

dummy@example.com (alexkemp) — Sun, 10 Nov 2024 02:09:36 +0000

Installed yesterday Saturday 9 November 2024, although the config file is dated different:

$ $ la /boot/config-6.10.11+bpo-amd64
-rw-r--r-- 1 root root 276562 Oct  3 21:43 /boot/config-6.10.11+bpo-amd64

Error immediately after install whilst (from memory) DKMS module build. Reboot into the new kernel failed & I have to boot from the old kernel. I cannot find anything on the web about this. Difficult to believe that I am the only one.

Here is the top of the install script output that failed:

Setting up linux-image-6.10.11+bpo-amd64 (6.10.11-1~bpo12+1) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.10.11+bpo-amd64.
Sign command: /lib/modules/6.10.11+bpo-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.10.11+bpo-amd64 -C /lib/modules/6.10.11+bpo-amd64/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build.....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.10.11+bpo-amd64 (x86_64)
Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.10.11+bpo-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.10.11+bpo-amd64 (--configure):
 installed linux-image-6.10.11+bpo-amd64 package post-installation script subprocess returned error exit status 1

...and here is the top of the error-log for the xtrx build:

$ head /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log
DKMS make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.2 for kernel 6.10.11+bpo-amd64 (x86_64)
Sat  9 Nov 14:45:35 GMT 2024
make: Entering directory '/usr/src/linux-headers-6.10.11+bpo-amd64'
  CC [M]  /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.o
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c: In function ‘xtrx_uart_do_tx’:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:472:28: error: ‘struct uart_state’ has no member named ‘xmit’
  472 |         xmit = &port->state->xmit;
      |                            ^~
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:473:13: error: implicit declaration of function ‘uart_circ_empty’; did you mean ‘uart_lsr_tx_empty’? [-Werror=implicit-function-declaration]
  473 |         if (uart_circ_empty(xmit))