Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
I'll be honest, I'm not entirely sure. I am now trying again on a different Alienware laptop to see if the issue resurfaces. On Mon, 27 Jan 2025 at 09:52, Salvatore Bonaccorso wrote: > HI, > > On Sun, Jan 26, 2025 at 11:19:45AM -0800, Mark Mandel wrote: > > Installed the manual proprietary Nvidia drivers and the crash is > > back 🤷🏻♂️ > > > > I think this is the end of me debugging this. > > So I interpret the results as having identified the problem might just > be in src:nvidia-graphics-drivers. > > If this is correct we would reassign the bug, but will wait for your > reply. > > Regards, > Salvatore >
Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
HI, On Sun, Jan 26, 2025 at 11:19:45AM -0800, Mark Mandel wrote: > Installed the manual proprietary Nvidia drivers and the crash is > back 🤷🏻♂️ > > I think this is the end of me debugging this. So I interpret the results as having identified the problem might just be in src:nvidia-graphics-drivers. If this is correct we would reassign the bug, but will wait for your reply. Regards, Salvatore
Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
Installed the manual proprietary Nvidia drivers and the crash is back 🤷🏻♂️ I think this is the end of me debugging this. >
Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
Woah! I think I can reproduce this! I was trying to manually install Nvidia drivers to see how that would go! But didn't get that far. Only got as far as creating a file in /etc/modprobe.d to disable nouveau, with contents: ``` blacklist nouveau options nouveau modeset=0 ``` Once that is in place, I get the regular freezes on startup (as above). I've not even installed any nvidia packages. I'm going to try just removing the nouveau packages entirely, see if that does anything. mark >
Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
So good news! I removed Nvidia packages, and it seems like I can't reproduce this on 6.12.10 anymore. I've rebooted several times. So it's quite possible this is more to do with Nvidia issues than the kernel. Appreciate you taking the time to walk me through this! Mark >
Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
> > > > 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). > Totally fair - thanks for explaining. Would a boot from a liveUSB suffice? I did have similar issues off a liveUSB when installing - but it was relatively random, and less frequent. I tried to SSH In on a hang, but unfortunately, SSH was unresponsive. > > 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? > Right now I don't use a graphical login like sddm/gdm/etc -- been starting from scratch, so my system boots directly into a terminal. But yes, I also have the 1089513 issue, i.e. Nvidia doesn't work with 6.12.x (but that's a separate issue! 😆) > > 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? > Ooh I can try this! Recently I've noticed it will boot into 6.12.9 -- it doesn't seem to fail as often (I have been trying it after every apt full-upgrade I run). I've been keeping everything very up to date, in hopes of a fix ☺️🤞🏻 so, maybe something else got updated recenty? I'll keep you updated as I dig in further! Mark
Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
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
Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
This is a system I use regularly, so I am unable to test without Nvidia. That being said, all nvidia packages came from Debian repositories. ❯ apt list --installed | grep nvidia firmware-nvidia-graphics/testing,now 20241210-1 all [installed] firmware-nvidia-gsp/testing,now 535.216.03-1 amd64 [installed,automatic] glx-alternative-nvidia/testing,now 1.2.2 amd64 [installed,automatic] libegl-nvidia0/testing,now 535.216.03-1 amd64 [installed,automatic] libgl1-nvidia-glvnd-glx/testing,now 535.216.03-1 amd64 [installed,automatic] libgles-nvidia1/testing,now 535.216.03-1 amd64 [installed,automatic] libgles-nvidia2/testing,now 535.216.03-1 amd64 [installed,automatic] libglx-nvidia0/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-allocator1/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-api1/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-cfg1/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-egl-gbm1/testing,now 1.1.2-1 amd64 [installed] libnvidia-egl-wayland1/testing,now 1:1.1.16-1 amd64 [installed] libnvidia-eglcore/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-encode1/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-fbc1/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-glcore/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-glvkspirv/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-ml1/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-ngx1/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-nvvm4/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-opticalflow1/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-pkcs11-openssl3/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-ptxjitcompiler1/testing,now 535.216.03-1 amd64 [installed,automatic] libnvidia-rtcore/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-alternative/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-cuda-mps/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-detect/testing,now 535.216.03-1 amd64 [installed] nvidia-driver-bin/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-driver-full/testing,now 535.216.03-1 amd64 [installed] nvidia-driver-libs/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-driver/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-egl-common/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-egl-icd/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-installer-cleanup/testing,now 20240109+1 amd64 [installed,automatic] nvidia-kernel-common/testing,now 20240109+1 amd64 [installed,automatic] nvidia-kernel-dkms/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-kernel-support/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-legacy-check/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-modprobe/testing,now 550.78-1 amd64 [installed,automatic] nvidia-opencl-common/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-opencl-icd/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-persistenced/testing,now 535.216.01-2 amd64 [installed,automatic] nvidia-powerd/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-settings/testing,now 535.216.01-1 amd64 [installed,automatic] nvidia-smi/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-support/testing,now 20240109+1 amd64 [installed,automatic] nvidia-suspend-common/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-vaapi-driver/testing,now 0.0.13-1 amd64 [installed] nvidia-vdpau-driver/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-vulkan-common/testing,now 535.216.03-1 amd64 [installed,automatic] nvidia-vulkan-icd/testing,now 535.216.03-1 amd64 [installed,automatic] xserver-xorg-video-nvidia/testing,now 535.216.03-1 amd64 [installed,automatic] On Sat, 18 Jan 2025 at 23:26, Salvatore Bonaccorso wrote: > Control: tags -1 + moreinfo > Control: severity -1 important > > On Sat, Jan 18, 2025 at 09:16:35AM -0800, Mark Mandel wrote: > > Package: src:linux > > Version: 6.12.9-1 > > Severity: critical > > Justification: breaks the whole system > > > > Dear Maintainer, > > > >* What led up to the situation? > > Attempting to boot on the 6.12 Kernel. > > > >* What exactly did you do (or not do) that was effective (or > > ineffective)? > >Booting into 6.12.9 fails every time with a hang (see boot log below > that I was able to capture). > >Nothing I could see immeadiately jumps out as an issue in the log > however. > > > >Booting into 6.12.6 fails approximately half the time with a hang. > > > >Booting into 6.11.10 only fails rarely. > > > >* What was the outcome of this action? > >Unable to use the system if I can't boot in. > > > >* What outcome did you expect instead? > >Be able to boot into Debian. > > > > > > > > -- Package-specific info: > > ** Kernel log: > > > > 1.3221221 xhci hcd :0
Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
Control: tags -1 + moreinfo Control: severity -1 important On Sat, Jan 18, 2025 at 09:16:35AM -0800, Mark Mandel wrote: > Package: src:linux > Version: 6.12.9-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > >* What led up to the situation? > Attempting to boot on the 6.12 Kernel. > >* What exactly did you do (or not do) that was effective (or > ineffective)? >Booting into 6.12.9 fails every time with a hang (see boot log below that > I was able to capture). >Nothing I could see immeadiately jumps out as an issue in the log however. > >Booting into 6.12.6 fails approximately half the time with a hang. > >Booting into 6.11.10 only fails rarely. > >* What was the outcome of this action? >Unable to use the system if I can't boot in. > >* What outcome did you expect instead? >Be able to boot into Debian. > > > > -- Package-specific info: > ** Kernel log: > > 1.3221221 xhci hcd :01:00.2: XHCI Host Controller > 1.3234491 xhci hcd :01:00.2: new USB bus registered, assigned bus number > 3 1.3253941 xhci hcd :01:00.2: hcc params 0x0180ff05 hci version 0x110 > quirks 0x0010 > 1.3268241 xhci Jhcd :01:00.2: XHCI Host Controller > 1.3281451 xhci_hcd :01:06.2: new USB bus registered, assigned bus number 4 > 1.3294601 xhci Jhcd :01:00.2: Host supports USB 3.1 Enhanced SuperSpeed > 1.3307851 usb usb3: New USB device found, idVendor 1d6b, idProduct=0002, > bcdDevice= 6.12 1.3320811 usb usb3: New USB device strings: Mfr-3, Product 2, > SerialNumber=1 > 1.76] usb usb3: Product: XHCI Host Controller > 1.3346431 usb usb3: Manufacturer: Linux 6.12.9-amd64 xhci-hcd 1.3358961 usb > usb3: SerialNumber: :01:00.2 > 1.3373171 hub 3-0:1.0: USB hub found > 1.3385571 hub 3-0:1.0: 2 ports detected > 1.3399371 usb usb4: We don't know the algorithms for LPM for this host, > disabling LPM. > 1.341206] usb usb4: New USB device found, idVendor-1d6b, idProduct=0003, > bcdDevice= 6.12 1.3424681 usb usb4: New USB device strings: Mfr-3, Product-2, > SerialNumber=1 > 1.343729] usb usb4: Product: XHCI Host Controller > 1.3449831 usb usb4: Manufacturer: Linux 6.12.9-and64 xhci-hcd > 1.346241] usb usb4: SerialNumber: :01:00.2 1.347586] hub 4-0:1.0: USB hub > found > 1.348833] hub 4-0:1.0: 4 ports detected > 1.3503981 xhci hcd :43:00.0: XHCI Host Controller 1.3516421 xhcỉ hcd > :43:00.0: new USB bus registered, assigned bus number 5 > 1.3540771 xhcỉ hcd :43:00.0: hcc params 0x200077c1 hci version 0x110 > quirks 0x00029810 > 1.355682] xhci_hcd :43:00.0: XHCI Host Controller > 1.3569361 xhcỉ hcd :43:00.0: new USB bus registered, assigned bus number > 6 1.3582841 xhcỉ hcd :43:00.0: Host supports USB 3.1 Enhanced SuperSpeed > 1.359623] usb usb5: New USB device found, idVendor-1d6b, idProduct=0002, > bcdDevice= 6.12 1.360924] usb usb5: New USB device strings: Mfr 3, Product-2, > SerialNumber=1 > 1.362199] usb usb5: Product: XHCI Host Controller 1.363454] usb usb5: > Manufacturer: Linux 6.12.9-amd64 xhci-hed > 1.3647263 usb usb5: SerialNumber: :43:00.0 > 1.3660751 hub 5-0:1.0: USB hub found > 1.3673591 hub 5-0:1.0: 2 ports detected > 1.3691061 usb usb6: Neu USB device found, idVendor 1d6b, idProduct=0003, > bcdDevice 6.12 1.3704031 usb usb6: New USB device strings: Mfr 3, Product-2, > SerialNumber=1 > 1.3717111 usb usb6: Product: XHCI Host Controller > 1.3730183 usb usb6: Manufacturer: Linux 6.12.9-and64 xhci-hod > 1.374336] usb usb6: SerialNumber: :43:00.0 1.375719] hub 6-0:1.0: USB hub > found > 1.3771061 hub 6-0:1.0: 2 ports detected 1.441039] tsc: Refined TSC > clocksource calibration: 3600.000 MHz > 1.4423371 clocksource: tsc: mask: 0x max_cycles: > 0x33e452fbb2f, max_idle_ns: 440795236593 ns > 1.4437331 clocksource: Suitched to clocksource tsc 1.569138] usb 1-2: new > high-speed USB device number 2 using xhci_hcd > 1.6056501 ata1: SATA link down (SStatus 4 SControl 300) > 1.6133571 8169 :45:00.0 enp69s09: renaned fron ethe > 1.615278] input: DELL08C4:00 06CB:8495 House > as/devices/pc1:00/:00:15.6/12c_designware.0/120-1/12c-DELL08C4:00/0018:06CB:8495.0001/input/input6 > 1.6167241 hid-generic 0018:06CB:8495.0001: input, hidrauß: 12C HID 01.00 > Mouse [DELL08C4:00 06CB:84951 on 120-BELL08C4:00 > 1.7095061 usb 1-2: New USB device found, idVendor 1a40, idProduct=0101, > bcdDevice 1.11 1.710872] usb 1-2: New USB device strings: fr-9, Product 1, > SerialNumber=0 > 1.7122263 usb 1-2: Product: USB 2.0 Hub > 1.714519] hub 1-2:1.0: USB hub found > 1.715979) hub 1-2:1.0: 4 ports detected > 160442853 rni4 f34 rni4-00.fn34: rni f34u7 probe: Unrecognized bootloader > version: 13 ( 1.7456411 rmi4 f34 rai4-00.fn34: probe with driver rm14 134 > failed with error -22 > 1.778860] rm14 f01 rm14-00.fn01: found BMI device, manufacturer: Synaptics, > product: TM3394-001, fu 14: 2706778 1.8290911 usb 2-5: neu SuperSpeed USB > devic
Processed: Re: Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
Processing control commands: > tags -1 + moreinfo Bug #1093435 [src:linux] linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64 Added tag(s) moreinfo. > severity -1 important Bug #1093435 [src:linux] linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64 Severity set to 'important' from 'critical' -- 1093435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1093435: linux-image-6.12.9-amd64: Unable to boot on linux-image-6.12.9-amd64
Package: src:linux Version: 6.12.9-1 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? Attempting to boot on the 6.12 Kernel. * What exactly did you do (or not do) that was effective (or ineffective)? Booting into 6.12.9 fails every time with a hang (see boot log below that I was able to capture). Nothing I could see immeadiately jumps out as an issue in the log however. Booting into 6.12.6 fails approximately half the time with a hang. Booting into 6.11.10 only fails rarely. * What was the outcome of this action? Unable to use the system if I can't boot in. * What outcome did you expect instead? Be able to boot into Debian. -- Package-specific info: ** Kernel log: 1.3221221 xhci hcd :01:00.2: XHCI Host Controller 1.3234491 xhci hcd :01:00.2: new USB bus registered, assigned bus number 3 1.3253941 xhci hcd :01:00.2: hcc params 0x0180ff05 hci version 0x110 quirks 0x0010 1.3268241 xhci Jhcd :01:00.2: XHCI Host Controller 1.3281451 xhci_hcd :01:06.2: new USB bus registered, assigned bus number 4 1.3294601 xhci Jhcd :01:00.2: Host supports USB 3.1 Enhanced SuperSpeed 1.3307851 usb usb3: New USB device found, idVendor 1d6b, idProduct=0002, bcdDevice= 6.12 1.3320811 usb usb3: New USB device strings: Mfr-3, Product 2, SerialNumber=1 1.76] usb usb3: Product: XHCI Host Controller 1.3346431 usb usb3: Manufacturer: Linux 6.12.9-amd64 xhci-hcd 1.3358961 usb usb3: SerialNumber: :01:00.2 1.3373171 hub 3-0:1.0: USB hub found 1.3385571 hub 3-0:1.0: 2 ports detected 1.3399371 usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. 1.341206] usb usb4: New USB device found, idVendor-1d6b, idProduct=0003, bcdDevice= 6.12 1.3424681 usb usb4: New USB device strings: Mfr-3, Product-2, SerialNumber=1 1.343729] usb usb4: Product: XHCI Host Controller 1.3449831 usb usb4: Manufacturer: Linux 6.12.9-and64 xhci-hcd 1.346241] usb usb4: SerialNumber: :01:00.2 1.347586] hub 4-0:1.0: USB hub found 1.348833] hub 4-0:1.0: 4 ports detected 1.3503981 xhci hcd :43:00.0: XHCI Host Controller 1.3516421 xhcỉ hcd :43:00.0: new USB bus registered, assigned bus number 5 1.3540771 xhcỉ hcd :43:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x00029810 1.355682] xhci_hcd :43:00.0: XHCI Host Controller 1.3569361 xhcỉ hcd :43:00.0: new USB bus registered, assigned bus number 6 1.3582841 xhcỉ hcd :43:00.0: Host supports USB 3.1 Enhanced SuperSpeed 1.359623] usb usb5: New USB device found, idVendor-1d6b, idProduct=0002, bcdDevice= 6.12 1.360924] usb usb5: New USB device strings: Mfr 3, Product-2, SerialNumber=1 1.362199] usb usb5: Product: XHCI Host Controller 1.363454] usb usb5: Manufacturer: Linux 6.12.9-amd64 xhci-hed 1.3647263 usb usb5: SerialNumber: :43:00.0 1.3660751 hub 5-0:1.0: USB hub found 1.3673591 hub 5-0:1.0: 2 ports detected 1.3691061 usb usb6: Neu USB device found, idVendor 1d6b, idProduct=0003, bcdDevice 6.12 1.3704031 usb usb6: New USB device strings: Mfr 3, Product-2, SerialNumber=1 1.3717111 usb usb6: Product: XHCI Host Controller 1.3730183 usb usb6: Manufacturer: Linux 6.12.9-and64 xhci-hod 1.374336] usb usb6: SerialNumber: :43:00.0 1.375719] hub 6-0:1.0: USB hub found 1.3771061 hub 6-0:1.0: 2 ports detected 1.441039] tsc: Refined TSC clocksource calibration: 3600.000 MHz 1.4423371 clocksource: tsc: mask: 0x max_cycles: 0x33e452fbb2f, max_idle_ns: 440795236593 ns 1.4437331 clocksource: Suitched to clocksource tsc 1.569138] usb 1-2: new high-speed USB device number 2 using xhci_hcd 1.6056501 ata1: SATA link down (SStatus 4 SControl 300) 1.6133571 8169 :45:00.0 enp69s09: renaned fron ethe 1.615278] input: DELL08C4:00 06CB:8495 House as/devices/pc1:00/:00:15.6/12c_designware.0/120-1/12c-DELL08C4:00/0018:06CB:8495.0001/input/input6 1.6167241 hid-generic 0018:06CB:8495.0001: input, hidrauß: 12C HID 01.00 Mouse [DELL08C4:00 06CB:84951 on 120-BELL08C4:00 1.7095061 usb 1-2: New USB device found, idVendor 1a40, idProduct=0101, bcdDevice 1.11 1.710872] usb 1-2: New USB device strings: fr-9, Product 1, SerialNumber=0 1.7122263 usb 1-2: Product: USB 2.0 Hub 1.714519] hub 1-2:1.0: USB hub found 1.715979) hub 1-2:1.0: 4 ports detected 160442853 rni4 f34 rni4-00.fn34: rni f34u7 probe: Unrecognized bootloader version: 13 ( 1.7456411 rmi4 f34 rai4-00.fn34: probe with driver rm14 134 failed with error -22 1.778860] rm14 f01 rm14-00.fn01: found BMI device, manufacturer: Synaptics, product: TM3394-001, fu 14: 2706778 1.8290911 usb 2-5: neu SuperSpeed USB device number 2 using xhaị hoả 1.8307701 ish-hid ( 33AECD58-8679-4E54-9809-004034F0C226): (hid-ishli enun devices done OK, nun hid devices-1 1.835597] hid-generic 001F:8087:00C2.0002: hidraud: SENSOR HUB HID 02.00 Device Chid-ishtp 0007:08C2) on 1.8389781 hid-sensor-hub 001F:8087:0AC2,0002: hidraud: SENSOR HUB HID 02.00 Devic
