I thought I´d do an update.
Iĺl recap. Given under normal operation lspci -k | grep -EA3
'VGA|3D|Display' elicits the following, which "confirms"the radeon
driver is running.
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Kabini [Radeon HD 8210]
Subsystem: Hewlett-Packard Company Device 21f7
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu
I ran dmesg and journal and found some interesting errors:
"daeon ring 0 stalled for more than X msec"
and
"[DRM] amdgpu modsetting enabled"
The latter is surprising considering radeon runs, which suggests a ghost driver
is perhaps causing instability or amdgpu started, failed, and handed off to
radeon, which could also de causing instability, among other possibilities I'm
surely missing.
Solution or work around
Since radeon might be buggy, as indicated by the ring 0 error message, forcing
the amdgpu driver seemed the logical recourse.
edit /etc/default/grub to insert radeon.cik_support=0
amdgpu.cik_support=1
Results
I've tested all the problematic scenarios, except hibernation, and haven't been
able to reproduce a system freeze going on at least 3 days non-stop, since
enabling the amdgpu driver in the bootloader.
Observations
There's various possible issues.
1. Assuming the radeon driver is stable and it isn't appropriate for the
hardware, Ubuntu's hardware discovery might need some improvement.
2. Perhaps the radeon driver is unstable, which case suggests it needs some
maintenance work.
3. Perhaps the most likely scenario is that there may be a bug in the
corresponding service that attempts to start the amdgpu driver early on,
perhaps partially successfully, until it fails, before falling back onto
the radeon driver which is inadequate, either due to driver bugginess,
hardware incompatibility, or simply due to an incapability of meeting
modern graphical rendering demands, despite the hardware shows no such
lack of capacity.
So I wouldn't label this as "fixed", as, despite finding a working solution,
this case points to possibly multiple failure points, none of which seem to be
related to Firefox, Plasma, or transitions between desktops. That said, I
haven´t tested with hibernation yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2113479
Title:
[amdgpu] Video playback in Firefox freezes Wayland & Xorg
Status in linux package in Ubuntu:
New
Bug description:
Issue: Softlockup with udev-worker during video playback via Firefox
browsers on wayland/Xorg with AMD GPU driver
Expected: stable system, and smooth video playback
What actually happens: system freezes requiring a sysreq sequence. CU
soft lockup udev-worker message in logs. DrKonqi rate-limiting for
crashes.
Steps to reproduce:
1. Open a Firefox browser such as Zen, LibreWolf, Floorp, or Firefox itself.
2. Navigate to an online video playback service
3. Start playing videos
4. Switch desktops with fancy visual transitions or let system idle till
screen lock or manually log out
5. System freezes, cannot interact, although can reboot via SysReq sequence
Key observations
* Happens with Snap Firefox and Flatpak Zen. but NOT with Chrome based
browsers.
* Does not happen with youtube playback but with other codecs and or sources
* occurs on both wayland and xorg
"watchdog: BUG: soft lockup - CPU#0 stuck for 32s! [(udev-worker):574]" found
in journalctl -b -1
* "drkonqi-coredump-launcher: ... not starting since we tried this too often
recently" also in logs
* sometimes happens when moving desktops in plasma, upon arriving at the
desktop that has Firefox/Zen
* sometimes happens after logging back in after timeout in plasma
* has occurred across multiple Ubuntu versions
* using open-source drivers
* EDIT: I'll add the only other oddity I've noticed is that scrolling pages,
usually blog posts, in Brave often results in momentary and intermittent
unresponsiveness or lagginess, often in full screen (F11), while out of
full-screen on the same page and instance will not elicit such behaviour.
Firefox and derivatives do not demonstrate such performance issues.
Important observation: When I scrape the video URL from the browser
and play it directly in VLC, it plays without issues, despite using
the same video source that might cause freeze issues with Firefox/Zen.
This suggests the problem lies in the browser's specific
implementation of hardware video decoding/acceleration and its
interaction with the radeon driver Mesa stack, rather than the
fundamental inability if the driver to decode the video itself.
Hardware affected: AMD processor with integrated graphics on an HP 15 laptop
Vendor ID: AuthenticAMD
Model name: AMD E1-2100 APU with Radeon(TM) HD Graphics
CPU family: 22
lspci -k | grep -EA3 'VGA|3D|Display'
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Kabini [Radeon HD 8210]
Subsystem: Hewlett-Packard Company Device 21f7
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu
Work arounds:
1. Disable both "use recommended performance settings" and "use acceleration
when possible" selections in Firefox and related browser's Preferences panel.
2. Use Chrome based browsers (with acceleration enabled)
3. Disable timed lockout or use a compositor or WM that doesn't support
logging out.
4. Use a compositor or WM without fancy visual effects
5. EDIT: Use Chrome based browsers solely to use online video services, and
Firefox derivatives exclusively for surfing text based sites.
6. EDIT: scrape video URL via a browser, and play it via VLC.
Thoughts: My hardware is a about a 9 yr old laptop, it might be
supported by the amdgpu driver, although I haven't tried it. I'm
running the radeon driver, and have always done so, ever since
installing Ubuntu on this laptop several versions ago.
EDIT: Since the E-2100 APU hardware is a Kabini part, which means it's
based on GCN 1.1, it's a Sea Islands / CIK technology, for anyone
wondering.
EDIT: Furthermore, Google Earth runs fine, and I don't ever recall a
system freeze coinciding with its use, which despite this program
being a highly GPU intensive 3D program, suggests the issue doesn't
pertain to the 3D rendering capabilities of the Radeon driver on this
APU, but rather specific to its hardware video decoding pathway (as
used by browsers) and/or its handling of GPU power state transitions
and display controller management during desktop switching or system
resume/login.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: xorg 1:7.7+23ubuntu4
ProcVersionSignature: Ubuntu 6.14.0-15.15-generic 6.14.0
Uname: Linux 6.14.0-15-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.1
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: Hyprland
Date: Sat Jun 7 23:35:23 2025
DistUpgraded: 2025-05-18 14:18:02,194 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: plucky
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since before I upgraded
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834]
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:21f7]
InstallationDate: Installed on 2024-02-08 (485 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-15-generic
root=UUID=fd3c1a7c-072b-4ccf-a7fb-9b7c15923d16 ro quiet splash
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to plucky on 2025-05-18 (20 days ago)
dmi.bios.date: 08/06/2014
dmi.bios.release: 15.34
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 21F7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 52.2B
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 52.43
dmi.modalias:
dmi:bvnInsyde:bvrF.22:bd08/06/2014:br15.34:efr52.43:svnHewlett-Packard:pnHP15NotebookPC:pvr0976100000405F00001610180:rvnHewlett-Packard:rn21F7:rvr52.2B:cvnHewlett-Packard:ct10:cvrChassisVersion:skuF4H14LA#AKH:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 Notebook PC
dmi.product.sku: F4H14LA#AKH
dmi.product.version: 0976100000405F00001610180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.124-2
version.libgl1-mesa-dri: libgl1-mesa-dri 25.0.3-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.16-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.18-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2113479/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp