Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #80991 > unrolled thread

Bug#1057142: linux-image-6.5.0-0.deb12.4-amd64-unsigned: The system does not boot OK, systemd is KO

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1057142: linux-image-6.5.0-0.deb12.4-amd64-unsigned: The system does not boot OK, systemd is KO "jp.pozzi@izzop.net" <jp.pozzi@izzop.net> - 2023-11-30 15:20 +0100
    Bug#1057142: marked as done (linux-image-6.5.0-0.deb12.4-amd64-unsigned:  The system does not boot OK, systemd is KO) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-02-20 16:00 +0100

#80991 — Bug#1057142: linux-image-6.5.0-0.deb12.4-amd64-unsigned: The system does not boot OK, systemd is KO

Package: linux-image-6.5.0-0.deb12.4-amd64-unsigned
Severity: normal

Dear Maintainer,

   * What led up to the situation?
I upgrade a machine from bullseye to bookworm.
I install the lmast kernel (6.5)
The system does not boot correctly as systemd is KO
Even in "recovery mode" the system stay locked on the end od setting network.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I try the rescue mode which was ineffective.

I try a 6.4 kernel with the same problems ... the kernel 6.1.0-0.deb11.13-amd64
boots OK.

Regards

JP P

PS :
I have at least another system which cannot boot with 6.5 kernel (unless in
rescue mode) with looping message :
mdadm: nodevices listed in conf file were found
....
dropping to a shell
Busybox
....

That system boots OK in rescue mode with the 6.5 kernel.




-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-0.deb11.13-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-6.5.0-0.deb12.4-amd64-unsigned depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod                                    30+20221128-1
ii  linux-base                              4.9

Versions of packages linux-image-6.5.0-0.deb12.4-amd64-unsigned recommends:
ii  apparmor             3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.5.0-0.deb12.4-amd64-unsigned suggests:
pn  debian-kernel-handbook  <none>
ii  grub-pc                 2.06-13+deb12u1
pn  linux-doc-6.5           <none>

[toc] | [next] | [standalone]

#85959 — Bug#1057142: marked as done (linux-image-6.5.0-0.deb12.4-amd64-unsigned: The system does not boot OK, systemd is KO)

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

Your message dated Thu, 20 Feb 2025 15:37:16 +0100 (CET)
with message-id <20250220143716.0238BBE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1057142,
regarding linux-image-6.5.0-0.deb12.4-amd64-unsigned: The system does not boot OK, systemd is KO
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1057142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057142
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web