Dear Salvatore, thank you for your response! As a novice user of "reportbugs" , I just filed the report of this bug using the "reportbug" application. Please contact me for any information that i may be able to provide and that i have omitted to provide.
Regards, Giorgos On Sun, Nov 23, 2025 at 5:21 PM Salvatore Bonaccorso <[email protected]> wrote: > Control: tags -1 + moreinfo > > Hi Giorgos, > > Thanks for your report. > > On Sun, Nov 23, 2025 at 11:59:10AM +0200, Giorgos Kourafas wrote: > > Package: linux > > Version: 6.12.48+deb13-1 > > Severity: serious > > Tags: upstream regression ftbfs Control: affects -1 + src:linux > > > > Dear Maintainer, > > > > The newer kernel image, **6.12.48+deb13-amd64**, causes a black screen > > during boot on a Sony Vaio VPCCW1S1E laptop. The issue is a > **regression**, > > as the previous stable kernel, **6.1.40-amd64, works perfectly** with the > > open-source Nouveau driver. ### Hardware Affected * **Laptop Model:** > Sony > > Vaio VPCCW1S1E * **Graphics Card:** **NVIDIA GT216M (GeForce GT 230M)** > ### > > Diagnostic Information When booting the 6.12.48+deb13 kernel, the system > > fails to initialize any display output, including virtual consoles > (TTYs), > > preventing a user from reaching the login prompt. By checking the system > > logs from a failed boot, the following critical error message was found, > > indicating a driver crash related to the GPU's core or power management: > > nouveau 0000:01.00.0: gr: TRAP_PROP TP1 - 00000040 [RT-FAULT] ### > > Troubleshooting Attempts > > All attempts to fix the issue via kernel parameters on the 6.12.48 kernel > > have failed: 1. Adding **'nouveau.modeset=0'** 2. Adding > > **'nouveau.runpm=0'** (disabling runtime power management) 3. > Blacklisting > > the Nouveau driver completely. > > The only way to boot the 6.12 kernel is by using the > > **'modprobe.blacklist=nouveau'** or **nomodeset=1** parameter, which > forces > > a generic VESA driver with poor resolution and no acceleration. > > 6.12.48-1 is not the newest kernel in Debian trixie, please thus test > as well with 6.12.57-1 and report back if the issue persists. > > We need full kernel logs and information about the hardware, ideally > you collect the information with reportbug following up on this bug. > > If the issue persist in 6.12.57-1, can you then please bisect the > changes between 6.12.43 and 6.12.48 (assuming you upgraded from > 6.12.43 to 6.12.48). Let us know if you need more psecific indication > on how to do the bisection. > > Regards, > Salvatore >
