svn commit: r328436 - head/sys/compat/linuxkpi/common/src

[Jan Beich]

Hans Petter Selasky <hps at selasky.org> writes:

> On 02/01/18 11:25, Jan Beich wrote:
>
>> Hans Petter Selasky <hselasky at FreeBSD.org> writes:
>>
>>> Author: hselasky
>>> Date: Fri Jan 26 10:49:02 2018
>>> New Revision: 328436
>>> URL: https://svnweb.freebsd.org/changeset/base/328436
>>>
>>> Log:
>>>    Decouple Linux files from the belonging character device right after open
>>>    in the LinuxKPI. This is done by calling finit() just before returning a magic
>>>    value of ENXIO in the "linux_dev_fdopen" function.
>>
>> This breaks DRI3 (uses DMABUF) on drm-next-kmod (Linux 4.9 atm) e.g.,
>>
>> $ LIBGL_DRI3_ENABLE=1 LIBGL_DEBUG=verbose MESA_DEBUG=context glxgears
>> libGL: screen 0 does not appear to be DRI3 capable
>> libGL error: Connection closed during DRI3 initialization failure
>> XIO:  fatal IO error 35 (Resource temporarily unavailable) on X server ":0"
>>        after 22 requests (22 known processed) with 0 events remaining.
>>
>
> Hi,
>
> I'll have a look. It might be an issue in libdrm, because it uses some
> out-of date methods to enumerate the device nodes, like the major and
> minor numbers.
>
> Did you recompile drm-next-kmod after recompiling the LinuxKPI?

Yes, recompiled. However, this commit in particular doesn't touch any
kernel headers for recompilation to be necessary. I also confirm
reverting the commit works around the issue.