debcrafters-packages team mailing list archive

[Ubuntu Foundations Team Bug Bot <2121301@xxxxxxxxxxxxxxxxxx>]

The attachment "Script to diagnose and fix the reported bug" seems to be
a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2121301

Title:
  [Ubuntu 24.04.3 LTS] Chrome with Radeon HD 6770M (r600 driver) freezes
  system when GPU acceleration enabled — SwiftShader workaround stable

Status in mesa package in Ubuntu:
  New

Bug description:
  Description:

  On Ubuntu 24.04.3 LTS running on an iMac (Intel i5-2500S + AMD Radeon
  HD 6770M / Whistler, using the Mesa r600 driver), launching Google
  Chrome with GPU acceleration enabled causes a full system freeze.

  When Chrome is started normally, the browser window shows brief
  corruption, and then the system becomes unresponsive. The kernel
  itself is hung: SSH sessions stop responding, and htop freezes. This
  happens reliably with Chrome 138/139 and Mesa 25.0.7.

  Steps to reproduce:

  Boot Ubuntu 24.04.3 LTS (kernel 6.14.0-28-generic).

  Hardware: iMac 2011, Intel i5-2500S CPU, AMD Radeon HD 6770M
  (Whistler, PCI ID 1002:6740).

  Mesa version: 25.0.7-0ubuntu0.24.04.1 (r600 driver).

  Install Google Chrome 139.0.7258.138 (google-chrome-stable).

  Launch Chrome normally, no special flags.

  Observe: corruption appears in the Chrome window followed by a total
  system freeze.

  Expected behavior:
  Chrome should run with GPU acceleration enabled without freezing the system.

  Actual behavior:
  The entire system freezes immediately when Chrome attempts to use GPU acceleration.

  Workarounds tested:

  Running Chrome with --use-gl=swiftshader --disable-gpu-rasterization
  --disable-zero-copy is stable.

  Running Chrome with --disable-gpu is also stable but slower.

  Running with --use-gl=desktop or --use-gl=egl causes corruption and
  freezes.

  Setting R600_DEBUG=nohyperz reduces corruption but does not prevent
  freezes.

  Environment:

  Ubuntu 24.04.3 LTS (noble)

  Kernel: 6.14.0-28-generic

  Mesa: 25.0.7-0ubuntu0.24.04.1

  Chrome: 139.0.7258.138

  GPU: AMD Radeon HD 6770M / Whistler (r600 driver)

  Logs:

  dmesg and journalctl show no relevant GPU faults before the freeze.

  The hang only occurs when Chrome uses GPU acceleration.

  Additional information:
  A helper script (chrome_gpu_tools.sh) has been attached. This script normalizes the Chrome launcher, forces SwiftShader by default, provides software-only and experimental GPU modes, verifies the launcher and running process flags, and re-pins Chrome in the GNOME Dock so that the override is always used.

  This script is a workaround, not a fix. It demonstrates that the r600
  driver path used by Chrome is responsible for the instability, and it
  provides a stable fallback for users until an upstream fix is
  available.

  Cross-references:

  Chromium bug filed under Internals > GPU > Drivers > Linux.
  https://issues.chromium.org/issues/440750830

  Mesa upstream bug filed under Gallium/r600.
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/13761

  Attachment:
  chrome_gpu_tools.sh (workaround script)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2121301/+subscriptions