When I don't disable AIGLX on my FreeBSD machines (one r100, one r200), I get a
hang on startup that appears to be due to incorrect locking. The dmesg says:
error: [drm:pid17529:radeon_cp_buffers] *ERROR* radeon_cp_buffers called without
error: [drm:pid17529:radeon_cp_reset] *ERROR* radeon_cp_reset called without
error: [drm:pid17529:radeon_cp_start] *ERROR* radeon_cp_start called without
over and over, as the server sits hung at a black screen. Log to follow.
Created attachment 5161 [details]
can you get a call trace of where you are when you get the GetBuffer message?
ajax: I'll try to dig up a backtrace at some point (my DRI is broken for other
reasons on the new laptop)
For others that I point at this bug, the section for xorg.conf to disable AIGLX is:
Option "AIGLX" "FALSE"
Created attachment 5659 [details]
Not surprising backtrace: first acceleration hangs grabbing the buffer, since
the lock is not held so the grab-a-buffer never succeeds.
This does appear to be Radeon-specific, as my i915 doesn't show this issue
(Still have a couple of crashes, but no hang at startup).
Created attachment 7615 [details]
Created attachment 7616 [details]
My X Log
Does this bug resolved already ?
My FreeBSD box that effected by this bug can ran normally now. I can start X,
run X apps, run OpenGL with DRI, quit X, and start X again without proble. My
source was fetched as of Oct 27, 2006.
Re: comment #7: you've found the wrong bug report. This is about radeon.
Tested with Mesa 6.5.2, mesa/drm HEAD and xorg-server 188.8.131.523, same thing.
Next up I'll try xorg-server HEAD. The ThinkPad doens't have a serial port so I
can't get to the kernel debugger.
doesn't look like it's getting fixed, so punting
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
*** This bug has been marked as a duplicate of bug 11870 ***