Date: Mon, 05 May 2025 15:34:46 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 286512] linuxkpi: amdgpu regressed after base 325aa4dbd10d Message-ID: <bug-286512-227-2OBZ6ce0mP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-286512-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286512 --- Comment #28 from Mark Johnston <markj@FreeBSD.org> --- (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 the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-286512-227-2OBZ6ce0mP>