[Bug 286512] linuxkpi: amdgpu regressed after base 325aa4dbd10d
| Newsgroups | gmane.os.freebsd.devel.x11 |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286512 --- Comment #28 from Mark Johnston <[email protected]> --- (In reply to Guido Falsi from comment #27) Which version of the drm modules are you using? > [drm ERROR :amdgpu_ctx_wait_prev_fence] Error (-1) waiting for fence! So dma_fence_wait_timeout() returned -1. For amdgpu, this means that dma_fence_default_wait(MAX_SCHEDULE_TIMEOUT == LONG_MAX) was used. A return value of -1 must have come from schedule_timeout(), but linux_schedule_timeout(MAX_SCHEDULE_TIMEOUT) should always return MAX_SCHEDULE_TIMEOUT. So this error should be impossible, unless I'm looking at the wrong version of the drm-kmod sources... The affected code lives in dmabuf.ko. Are you sure this is getting recompiled together with amdgpu.ko? -- You are receiving this mail because: You are on the CC list for the bug.