Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Jul 2007 02:31:02 -0700
From:      vehemens <vehemens@verizon.net>
To:        freebsd-x11@freebsd.org
Subject:   RADEON/AIGLX/DRM Problem
Message-ID:  <200707150231.03162.vehemens@verizon.net>
In-Reply-To: <200707092112.06905.vehemens@verizon.net>
References:  <200707030247.52207.vehemens@verizon.net> <1183974697.15243.58.camel@thor.sulgenrain.local> <200707092112.06905.vehemens@verizon.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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'm looking for ideas here as I don't know what direction to go in a this 
point.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707150231.03162.vehemens>