Radeon 7500 w/ DRI locking on restart of X
welchsm at earthlink.net
Tue Oct 28 06:53:22 PST 2003
Okay. I won't worry about the messages then.
I mentioned the suspend/resume problem only because it
actually worked correctly when using option ForcePCIMode;
I was shocked when it did and was hoping that your fix for
AGP accelerated DRI would pull off the same trick.
I should note here that I didn't see any of the panics other
people did before your last iteration of the fix. I'm guessing
it is because I didn't actually compile the code into my kernel
but instead let it build new modules. Any idea why that would
make the difference?
From: Eric Anholt <eta at lclark.edu>
Sent: Oct 27, 2003 11:48 PM
To: Sean Welch <Sean_Welch at alum.wofford.org>
Cc: freebsd-stable at freebsd.org, freebsd-current at freebsd.org
Subject: Re: Radeon 7500 w/ DRI locking on restart of X
On Fri, 2003-10-24 at 11:06, Sean Welch wrote:
> Eric, I updated my 5.1-RELEASE system to CURRENT dated today at
> approx. 9:10 CDT to give your changes a try. I had a bit of a fright at
> first with kernel panics right at the end of the boot sequence but it turned
> out I had forgotten to disable the ltmdm code -- the kernel module
> compiled under -RELEASE wasn't friendly to -CURRENT.
> I've got just a basic install with my custom kernel. I'm using the packages
> for X from the 5.1-RELEASE cd running twm. Hangs on restart are gone!
> I restarted about 10 times in a row and ran glxinfo and glxgears each time
> to verify DRI was still activated and working -- no issues. VT switches are
> fine (even while running glxgears). The one thing that does not work is
> resume from acpiconf -s 4 (disk) -- there is a failure to refresh in X and no
> ability *apparently* to switch to a VT; the keystrokes just generate beeps.
> Interestingly, the cursor still changed between the different modes when
> mousing over the xterm and onto the background. Also, Alt-Cntl-Del did
> work just fine.
Suspend/resume is doesn't work well. You might get lucky with the
-current DRM with XFree86-4-Server-snap.
> The only other thing I noticed is that there seems to be a syslog entry for
> every instance of running glxgears that reads:
> [MP SAFE] drm0
> Is this expected behavior? I noticed that same message (in brackets) in
> front of each of my disks as they were probed during boot.
That printout happens whenever an mpsafe interrupt handler is
installed. It gets installed upon initializing the DRI in the server.
I don't think any drivers do it more often. It may happen frequently if
glxgears is your only app running, in which case you'll get a server
regenerate on exit of glxgears.
Eric Anholt eta at lclark.edu
http://people.freebsd.org/~anholt/ anholt at FreeBSD.org
More information about the freebsd-stable