Hi Matthew,
On Mon, 18 Jun 2001, Sottek, Matthew J wrote:
> I think the known limitations was written a long time ago,
> multiple servers has been working at least for some people for
> quite some time. I am not sure of what configurations are
> working and which are not.
OK, I guess I have one of the configurations that "almost always works".
> The debug information you provided doesn't say if you are
> using DRI or not. Are you?
I presume this snippet from the log means that I am:
----------------------------8<----------------------------
(II) LoadModule: "dri"
(II) Loading /usr/X11R6/lib/modules/extensions/libdri.a
(II) Module dri: vendor="The XFree86 Project"
compiled for 4.0.3, module version = 1.0.0
ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension XFree86-DRI
----------------------------8<----------------------------
Pardon the ignorance: what is the significance of this?
> Basically the problem is that the graphics engine is
> crashing and the X server cannot get any space in the command
> ring to put new commands. This is obviously the case since
> the graphics engine is hung. A reboot resets everything.
Nitpick: it takes more than a reboot - rebooting linux gets to the "Fatal
server error: Active ring not flushed" error (albeit with text mode
consoles now working); poweroff-poweron-boot restores everything.
> The lockup may be caused by both X servers trying to access
> the device at the same time. Does the lockup only occur
> when the system is in use (vt switching is taking place), or
> does it happen while idle as well?
I can't recall it being associated with a VC chamge. IIRC, the trigger
events (as judged by when the screen gets vertical lines) may be:
* moving the mouse(!)
* coming out of the screen blanker (there is no screen-saver loaded).
Thanks,
Neale.
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
