kern/114688: RADEON/AIGLX/DRM Problem
vehemens
vehemens at verizon.net
Wed Jul 18 06:50:02 UTC 2007
>Number: 114688
>Category: kern
>Synopsis: RADEON/AIGLX/DRM Problem
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jul 18 06:50:01 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator: vehemens
>Release: Current
>Organization:
>Environment:
FreeBSD hep.dsl-verizon.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sun Jul 15 22:20:10 PDT 2007 vehemens at hep.dsl-verizon.net:/usr/obj/usr/src/sys/HEP i386
>Description:
The problem with the RADEON driver failing when run with the AIGLX extension
appears to be a problem with the DRM piece (library and/or driver).
What is happening is that the RADEON driver initializes DRM and sets a lock
using one file descriptor. When the AIGLX extension loads, it probes via
DRM using open/close calls on another file descriptor.
As both the RADEON driver and the AIGLX extension are part of the same
process, the AIGLX probe close calls drm_close which removes the DRI lock
causing the RADEON driver to fail during xserver initialization (i.e. system
hang).
Just to complicate the issue, I've been told that this doesn't occur with
linux with the suggestion that the BSD driver is broken or that the close
semantics are different between the two operating systems.
I don't know what direction to go in a this point, as I don't have the system knowledge to determine if the problem should be fixed in 1) the DRM driver, 2) libdrm, 3) the xserver, 4) the video driver, or 5) the AIGLX extension.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list