[Bug 286512] linuxkpi: amdgpu regressed after base 325aa4dbd10d
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 286512] linuxkpi: amdgpu regressed after base 325aa4dbd10d"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 03 May 2025 06:29:21 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286512 --- Comment #13 from crahman@gmail.com --- Using drm-66-kmod's amdgpu, I'm unable to run X after 325aa4dbd10d. The X server simply exits with [ 60.098] (EE) modeset(0): failed to set mode: No such file or directory [ 115.161] (EE) Fatal server error: [ 115.161] (EE) Caught signal 6 (Abort trap). Server aborting The kernel produces some noise: May 2 23:25:34 hemlock kernel: [drm ERROR :amdgpu_job_timedout] ring gfx_0.0.0 timeout, signaled seq=4, emitted seq=6 May 2 23:25:34 hemlock kernel: [drm ERROR :amdgpu_job_timedout] Process information: process pid 101244 thread pid 101244 May 2 23:25:34 hemlock kernel: drmn0: GPU reset begin! May 2 23:25:35 hemlock kernel: drmn0: BACO reset May 2 23:25:38 hemlock kernel: drmn0: GPU reset succeeded, trying to resume May 2 23:25:38 hemlock kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000). May 2 23:25:38 hemlock kernel: [drm] VRAM is lost due to GPU reset! And quite a bit more, which I can attach upon request. amdgpu has been built from post-325aa4dbd10d sources. This is on a GENERIC kernel. -- You are receiving this mail because: You are the assignee for the bug.