All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221543] New: [nouveau] RTX 5080 (GB203): Xid:13 WIDTH CT Violation on kernels 6.16.7+ causing system hang
Date: Mon, 18 May 2026 09:29:26 +0000	[thread overview]
Message-ID: <bug-221543-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=221543

            Bug ID: 221543
           Summary: [nouveau] RTX 5080 (GB203): Xid:13 WIDTH CT Violation
                    on kernels 6.16.7+ causing system hang
           Product: Drivers
           Version: 2.5
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: wojciech.bielawski@gmail.com
        Regression: No

Hardware: Lenovo ThinkStation P8 (30HJS53F00)
  CPU: AMD Threadripper PRO 7975WX (32C/64T)
  GPU: NVIDIA GeForce RTX 5080 (GB203, rev a1) [PCI 81:00.0]
  RAM: 128GB
  OS: Fedora 43 (Workstation)
  Affected kernels: 6.16.7 through 7.0.8 (latest tested)
  Working kernel: 6.13.6-200.fc41

  Problem:
  On kernels 6.16.7 and later, the nouveau driver triggers repeated Xid:13
  (WIDTH CT Violation) errors on all 7 GPCs of the RTX 5080. The errors are
  triggered by Chrome GPU acceleration but occur even with hardware
  acceleration disabled in Chrome.

  The error cascade is:
  1. Chrome triggers Xid:13 on nouveau
  2. Chrome GPU channel is killed
  3. Xid:13 repeats every ~20 minutes
  4. Xwayland encounters an MMU fault
  5. System hangs completely (B0E1/S202 diagnostic codes on chassis)

  Reproducer:
  - Boot any kernel >= 6.16.7 with nouveau on RTX 5080
  - Open Chrome (or Chromium)
  - Xid:13 errors appear within seconds in dmesg
  - System hangs within hours (sometimes minutes)

  What does NOT help:
  - Switching to X11 (hangs before reaching graphical mode)
  - Disabling Chrome hardware acceleration
  - Disabling C-States in BIOS
  - glxgears/GPU stress tests do NOT reproduce (only Chrome triggers it)

  Workaround:
  Downgrade to kernel 6.13.6-200.fc41. On that kernel, nouveau reports
  "unknown chipset" for RTX 5080 (expected, as GB203 support was added
  later), so the proprietary NVIDIA driver is required.

  This suggests a regression was introduced between 6.13.6 and 6.16.7 in
  nouveau's GB203/RTX 5080 support path.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2026-05-18  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  9:29 bugzilla-daemon [this message]
2026-05-18 14:34 ` [Bug 221543] [nouveau] RTX 5080 (GB203): Xid:13 WIDTH CT Violation on kernels 6.16.7+ causing system hang bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-221543-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.