Bug#1100895: Maybe the issue is buried in any changes between kernel versions kernel versions 6.1.0-27 and -28?

From	zb-public@mnet-online.de
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#1100895: Maybe the issue is buried in any changes between kernel versions kernel versions 6.1.0-27 and -28?
Date	2025-03-22 12:30 +0100
Message-ID	<Kt5d8-7SKt-3@gated-at.bofh.it> (permalink)
References	<KsjBv-7ooZ-7@gated-at.bofh.it> <Ksxl7-7xbd-11@gated-at.bofh.it> <KsTvk-7L7W-5@gated-at.bofh.it> <KsjBv-7ooZ-7@gated-at.bofh.it> <KsTvk-7L7W-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Dear Salvatore,

I will try my best to gather the boot log from a (failing) boot into
kernel version 6.1.0-28. I will get back on this as soon as I can.

In the meantime, I am happy to report I was able to add -27 to the list
of the versions I tried so far, which resulted in an "OK", so the cause
might have to do with any changes that happened between -27 and -28. I
hope this helps to narrow down the number of possible issues.

linux-image-6.1.0-18-amd64 OK
linux-image-6.1.0-20-amd64 OK
linux-image-6.1.0-21-amd64 OK
linux-image-6.1.0-23-amd64 OK
linux-image-6.1.0-26-amd64 OK
linux-image-6.1.0-27-amd64 OK
linux-image-6.1.0-28-amd64 FAIL
linux-image-6.1.0-29-amd64 FAIL
linux-image-6.1.0-30-amd64 FAIL
linux-image-6.1.0-31-amd64 FAIL
linux-image-6.1.0-32-amd64 FAIL

Just in case this helps to catch possible errors (becaue I am really
more of an interested user than a developer), I add the details of what
I did:

Downloaded
https://snapshot.debian.org/archive/debian/20241102T151100Z/pool/main/l/linux-signed-amd64/linux-image-6.1.0-27-amd64_6.1.115-1_amd64.deb
(https://snapshot.debian.org/package/linux-signed-amd64/6.1.115%2B1/#linux-image-6.1.0-27-amd64_6.1.115-1)
to
/var/cache/apt/archives/linux-image-6.1.0-27-amd64_6.1.115-1_amd64.deb

Installed using
# apt install
/var/cache/apt/archives/linux-image-6.1.0-27-amd64_6.1.115-1_amd64.deb
without any error messages.

-27 was automatically added to the list grub shows during boot, and,
obviously, I chose -27 manually using grub's menu.

Kind regards 

... and, of course, thank you very kindly for walking me through this
process of gathering as much useful information as I can, 

zb

Thread

Bug#1100895: linux-image-6.1.0-32-amd64: Failed to start systemd-journald.service/start, timeout, repeatedly killed, no boot possible zebonaut <zb-public@mnet-online.de> - 2025-03-20 09:40 +0100
  Bug#1100895: linux-image-6.1.0-32-amd64: Failed to start systemd-journald.service/start, timeout, repeatedly killed, no boot possible Salvatore Bonaccorso <carnil@debian.org> - 2025-03-20 21:10 +0100
  Processed: Re: Bug#1100895: linux-image-6.1.0-32-amd64: Failed to  start systemd-journald.service/start, timeout, repeatedly killed, no boot  possible "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-03-20 21:30 +0100
  Bug#1100895: Maybe the issue is buried in any changes between kernel versions kernel versions 6.1.0-27 and -28? zb-public@mnet-online.de - 2025-03-22 12:30 +0100
  Bug#1100895: Boot logs from versions 6.1.0-27-amd64 (booting), 6.1.0-28-amd64 (failing) and 6.1.0-32-amd64 (failing) Salvatore Bonaccorso <carnil@debian.org> - 2025-06-15 15:40 +0200
  Bug#1100895: marked as done (nouveau probe of GeForce 840M  crashes since 6.1.119-1) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-09-13 23:00 +0200

csiph-web