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
