[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1086229: marked as done (linux-image-6.1.0-26-amd64: System don't boot the GUI)

Your message dated Sun, 3 Nov 2024 09:10:45 +0100
with message-id <ZycwBR1cC1Mtq1Mt@eldamar.lan>
and subject line Re: Bug#1086229: linux-image-6.1.0-26-amd64: System don't boot the GUI
has caused the Debian Bug report #1086229,
regarding linux-image-6.1.0-26-amd64: System don't boot the GUI
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.)


-- 
1086229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086229
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-6.1.0-26-amd64
Version: 6.1.0-26
Severity: critical
Tags: d-i
Justification: breaks the whole system
X-Debbugs-Cc: yossef.enkaoua@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

I made a upgrade with "sudo apt upgrade" and the kernel upgrade to the last and when bootup the gdm dont want to start, i have also tried lightdm to see but it won't work and i have no GUI.
This problem also occur for the linux-image-6.1.0-25-amd64 image
To resolve this problem i downgrade the linux kernel with the CLI to the previous when my system was working. I start my system now with the linux-image-6.1.0-23-amd64

*** End of the template - remove these template lines ***


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

Kernel: Linux 6.1.0-23-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-6.1.0-26-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142+deb12u1
ii  kmod                                    30+20221128-1
ii  linux-base                              4.9

Versions of packages linux-image-6.1.0-26-amd64 recommends:
ii  apparmor             3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.1.0-26-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-efi-amd64          2.06-13+deb12u1
pn  linux-doc-6.1           <none>

I s

--- End Message ---
--- Begin Message --- 
Hi Yossef,

On Sat, Nov 02, 2024 at 06:35:18PM +0100, Yossef Enkaoua wrote:
> Hello,
> 
> I have take the log that you request from my working version which is
> 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64
> GNU/Linux
> 
> 1) "dmesg" command in dmesg.txt
> 
> 2) "cat /proc/modules" in modules.txt
> 
> 3) "lspci -vvv -nn" in lspci.txt

So indeed this was very useful. And it's not a src:linux issue.

The output of /proc/modules shows:

nvidia_drm 73728 7 - Live 0x0000000000000000 (POE)
nvidia_modeset 1204224 11 nvidia_drm, Live 0x0000000000000000 (POE)
nvidia 35598336 453 nvidia_modeset, Live 0x0000000000000000 (POE)

So there are proprietary nvidia modules loaded, and in the lspci
output you see:

24:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00
[VGA controller])
        Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] [1462:8c93]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 76
        IOMMU group: 16
        Region 0: Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
        Region 1: Memory at 7ff0000000 (64-bit, prefetchable) [size=128M]
        Region 3: Memory at 7ff8000000 (64-bit, prefetchable) [size=32M]
        Region 5: I/O ports at f000 [size=128]
        Expansion ROM at fc000000 [virtual] [disabled] [size=512K]
        Capabilities: <access denied>
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia

What is suprising is that you have dkms modules (anymore?) installed, but the
boot log shows that:

[    4.820705] nvidia: loading out-of-tree module taints kernel.
[    4.820713] nvidia: module license 'NVIDIA' taints kernel.
[    4.820714] Disabling lock debugging due to kernel taint
[    4.831489] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    4.887292] nvidia-nvlink: Nvlink Core is being initialized, major device number 241

[    4.887905] nvidia 0000:24:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
[    5.003643] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  470.256.02  Thu May  2 14:37:44 UTC 2024
[    5.055373] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  470.256.02  Thu May  2 14:50:40 UTC 2024

which defintively not averison available in bookworm.

So I'm closing this report, it is likely that you are affected by one
of the nvidia-kernel-dkms bugs not letting the nvidia module compile
for newer 6.1.y kernels. Install those more recent from stable and
retry. 

If it still fails I think we can reopen this bug and then reassign it
to src:nvidia-graphics-drivers.

Hope the above helps you to further proceed.

Regards,
Salvatore

--- End Message ---
Reply to: