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


Groups > linux.debian.kernel > #85219

Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64

Path csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From Salvatore Bonaccorso <carnil@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
Date Sun, 19 Jan 2025 21:00:01 +0100
Message-ID <K6JCF-afry-1@gated-at.bofh.it> (permalink)
References <K6kNX-9ZLr-1@gated-at.bofh.it> <K6y4x-a8o4-7@gated-at.bofh.it> <K6J9D-afhD-1@gated-at.bofh.it> <K6kNX-9ZLr-1@gated-at.bofh.it> <K6J9D-afhD-1@gated-at.bofh.it>
X-Original-To Mark Mandel <mark.mandel@gmail.com>
X-Mailbox-Line From debian-bugs-dist-request@lists.debian.org Sun Jan 19 19:57:07 2025
Old-Return-Path <debbugs@buxtehude.debian.org>
X-Spam-Flag NO
X-Spam-Score -4
Reply-To Salvatore Bonaccorso <carnil@debian.org>, 1093435@bugs.debian.org
Original-Sender Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>
Resent-To debian-bugs-dist@lists.debian.org
Resent-Cc Debian Kernel Team <debian-kernel@lists.debian.org>
X-Debian-Pr-Message followup 1093435
X-Debian-Pr-Package src:linux
X-Debian-Pr-Keywords moreinfo
X-Debian-Pr-Source linux
X-Gm-Message-State AOJu0YxjHdSWNynhzY2/xdi2mwtDkM7u85eKXxC1Q9yNQ+a00jbcGnU1 nfSt3onXU+uPR1lIikhd3LIQAKtkQZ24MRdpZipomruTN05DaN45XF19N0q+
X-Gm-Gg ASbGncubx+Nr251Ir/uQvTAZoMunqZd8f5tp31ktljDxJC8QC5BlHZ7xYaPUuAMViYe TrxZODDbYZ3Lh0ghqo+xo2+B4CHeEpCMdFFJ/AcJfEB1OeuG6dhXs5jwUkClnI4oQbRnyNQPd9f S0vYffKXHVzS7aGRmsFyyyiH6nI5H2gnlZQiq6ex27zb5VF+AvNwSn6Uy5EE1BxlmFnBs0cFaNi 70y+lInBUkjzNiPZIOj9GgWdHTHytBh4SqdsJUumAW/M11917XwI0+gKmVO/bX8/Ip6eg1v3e6m nsaCs5D7Vl3sGr0w7GRzmjB8XRQ=
X-Google-SMTP-Source AGHT+IHyO3tPKao4l27Nz+vUvxQmGqU+uK0vBcZbivUtpRd129nLPpbAyQRGtMU8e66rn99dxmaSXQ==
X-Received by 2002:a17:907:3ea3:b0:aa6:9198:75a6 with SMTP id a640c23a62f3a-ab38b24d3bemr930339466b.21.1737316448816; Sun, 19 Jan 2025 11:54:08 -0800 (PST)
Sender robomod@news.nic.it
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
X-Debian-Message from BTS
X-Mailing-List <debian-bugs-dist@lists.debian.org> archive/latest/1881371
List-ID <debian-bugs-dist.lists.debian.org>
List-URL <https://lists.debian.org/debian-bugs-dist/>
Approved robomod@news.nic.it
Lines 32
Organization linux.* mail to news gateway
X-Original-Cc 1093435@bugs.debian.org
X-Original-Date Sun, 19 Jan 2025 20:54:06 +0100
X-Original-Message-ID <Z41YXmkzTsZ2Spmm@eldamar.lan>
X-Original-References <173722059596.17668.16385904438899187258.reportbug@oss-dev.compoundtheory.com> <Z4ypDiGUEzS5bMo2@eldamar.lan> <CAFiDPQcLL1V2zT_5qbGXfAKKihPcN1qjbAu6D+04eCV0hOba3w@mail.gmail.com> <173722059596.17668.16385904438899187258.reportbug@oss-dev.compoundtheory.com> <CAFiDPQcLL1V2zT_5qbGXfAKKihPcN1qjbAu6D+04eCV0hOba3w@mail.gmail.com>
X-Original-Sender Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>
Xref csiph.com linux.debian.bugs.dist:1229230 linux.debian.kernel:85219

Cross-posted to 2 groups.

Show key headers only | View raw


Hi Mark,

Thanks for the reply.

On Sun, Jan 19, 2025 at 11:24:15AM -0800, Mark Mandel wrote:
> This is a system I use regularly, so I am unable to test without Nvidia.

Yes I understand, we need though a way to determine if the proprietary
modules tainting the kernel are responsible (for an upstream report
thee is need for the kernel not to be tainted, otherwise there is
unlikely it is going to be looked at).
> 
> That being said, all nvidia packages came from Debian repositories.

FWIW, it does less "matter" here if they are from Debian or externally
installed, the problem I would like to exclude is if tainting modules
have an influence. Let's try to tackle it from another angle: You can
have a look at #1089513.

Assuming you can access the machine remotely as well, when the system
seems to hang, can you still login remotely to the machine? Is just
the graphical stack not coming up? If you can login, can you provide
the full boot log and check if things matches to the bug #1089513?

Secondly, we have in meanwhile 6.12.10 in unstable, can you upgrade to
this kernel. Is the problem still reproducible with 6.12.10?

Is the system booting with quiet in the kernel command line? If Yes,
can you drop it so you get more verbose boot log, where does it stops?

Regards,
Salvatore

Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64 Salvatore Bonaccorso <carnil@debian.org> - 2025-01-19 21:00 +0100
  Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64 Mark Mandel <mark.mandel@gmail.com> - 2025-01-22 00:30 +0100
    Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64 Mark Mandel <mark.mandel@gmail.com> - 2025-01-26 18:50 +0100
      Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64 Mark Mandel <mark.mandel@gmail.com> - 2025-01-26 19:40 +0100
        Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64 Mark Mandel <mark.mandel@gmail.com> - 2025-01-26 20:30 +0100
          Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64 Salvatore Bonaccorso <carnil@debian.org> - 2025-01-27 19:00 +0100
            Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64 Mark Mandel <mark.mandel@gmail.com> - 2025-01-27 19:10 +0100

csiph-web