Date: Tue, 04 Jul 2017 14:21:53 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 220444] x11-servers/xorg-server crashes on attempt to play a video using VDPAU Message-ID: <bug-220444-7141-zfGvwkUtIJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220444-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-220444-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220444 --- Comment #11 from Mikhail Teterin <mi@FreeBSD.org> --- (In reply to Jan Beich from comment #10) >> Can you try to downgrade to Mesa 17.0.*? > Mikhail, you haven't provided feedback for this question. I'm sorry, but you indicated (in comment #6), that the alternative to downgrading is to try DRI2, which I did do -- and reported the success... The answer to this question is "No, I can not". There are only so many times per weekend I am willing to restart my entire desktop. Also, the move from graphics/dri to graphics/mesa-dri (which, BTW, remains unmentioned in MOVED), makes the task more difficult then simply unrolling one revision at a time. But, I thought, we've identified the true nature of the problem: VDPAU tries to exercise unimplemented DRI3 code -- unimplemented on all stock versions of FreeBSD (except, maybe, for NVidia users). The fix would seem to be to simply check for the missing functionality at the driver-initialization time and limit the X11-server to DRI2 if xorg.conf does not provide any other value. The unimplemented method (createImageFromFds) is not set to junk -- it is the good old NULL, which means, something set it to that value. Inserting the additional check into that code seems like an easy enough task for anyone familiar with the code. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220444-7141-zfGvwkUtIJ>