[drm] Fence fallback timer expired on ring gfx_0.0.0 (on FreeBSD)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- c
- Domain
- operating-systems
Research direction
Start by reproducing the failure with drm-612-kmod on FreeBSD 15.1-STABLE, the AMD Ryzen 9 9950X system, and Xorg, while checking the amdgpu driver paths related to gfx_0.0.0 and sdma0 fence timers. The report names no source file or test, so progress requires locating the relevant driver code and determining why the fallback timer expires. Done means identifying a reproducible cause and validating a fix without the repeated errors or near-freeze.
Written by the indexing model from the issue text.
Description
I use the drm-612-kmod driver on FreeBSD 15.1-STABLE in order to use the embedded AMD GPU on the Tomahawk 870 motherboard to run Xorg.
CPU is AMD Ryzen 9 9950X 16-Core.
drm-612-kmod begins to print the following errors and becomes almost frozen.
The source code is taken from this project: amdgpu.
[drm] Fence fallback timer expired on ring gfx_0.0.0
[drm] Fence fallback timer expired on ring sdma0
[drm] Fence fallback timer expired on ring gfx_0.0.0
[drm] Fence fallback timer expired on ring gfx_0.0.0
[drm] Fence fallback timer expired on ring gfx_0.0.0
[drm] Fence fallback timer expired on ring gfx_0.0.0
[drm] Fence fallback timer expired on ring gfx_0.0.0
[drm] Fence fallback timer expired on ring gfx_0.0.0
[drm] Fence fallback timer expired on ring gfx_0.0.0
- Dominant language
- C
- Stars
- 463
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ROCm/amdgpu
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ARM-software/sysarch-acs#600 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
EchoTools/nevr-runtime#117 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
darktable-org/darktable#22523 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
DarkFlippers/qUnleashed#240 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day