#1121227 linux-image-6.12.48+deb13-amd64: Black screen with Nouveau TRAP_PROP [RT-FAULT] on NVIDIA GT 230M (GT216M)

Package:
linux
Source:
linux
Submitter:
Giorgos Kourafas
Date:
2025-12-09 23:43:04 UTC
Severity:
normal
Tags:
#1121227#5
Date:
2025-11-23 09:59:10 UTC
From:
To:
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.
--- end of report ---
#1121227#16
Date:
2025-11-23 15:21:18 UTC
From:
To:
Hi Giorgos,

Thanks for your report.

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
#1121227#23
Date:
2025-11-24 23:07:04 UTC
From:
To:
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 <carnil@debian.org> wrote:
#1121227#28
Date:
2025-11-24 23:07:58 UTC
From:
To:
the new number og the bug is  Bug#1121348
#1121227#41
Date:
2025-12-01 22:03:22 UTC
From:
To:
Hello Giorgos,

the new bug report doesn't contain the requested kernel log however.

Please proceed as follows:

 - Boot the broken kernel and login (if that doesn't work using keyboard
   and monitor, please use ssh).
 - Run `reportbug linux-image-$(uname -r)`
 - On the prompt "Is the bug you found listed above
   [y|N|b|m|r|q|s|f|e|?]?" enter "1121348" (without the quotes).
 - On the next prompt "What do you want to do now [N|x|o|r|b|e|q|?]?"
   reply "x" and then answer the question "Use sudo to read the kernel
   log?" with "y".

After some more interaction with reportbug that should result in an
addition to the original bug that we can work with.

Thanks
Uwe
#1121227#48
Date:
2025-12-09 23:41:17 UTC
From:
To:
dear Uwe,
i found time to proceed as you proposed, managed to send an updated bug
report with reportbug.
Please see the
Bug#1121348best regards

On Tue, Dec 2, 2025 at 12:03 AM Uwe Kleine-König < u.kleine-koenig@baylibre.com> wrote: