Red Hat Bugzilla – Bug 195782
GL on PCIE R300 fails
Last modified: 2007-11-30 17:11:35 EST
On my Thinkpad Z60m with an ATI Radeon Mobility X600 (RV380 PCIE), running
"glxgears" results in "drmRadeonCmdBuffer: -22 (exiting)". When I check the
kernel log, I see:
[drm:r300_emit_3d_load_vbpntr] *ERROR* Offset failed range check (k=0 i=2) while
processing 3D_LOAD_VBPNTR packet.
[drm:r300_emit_packet3] *ERROR* r300_emit_raw_packet3 failed
[drm:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet3 failed
Not really a Test1 blocker. not sure if t would be an FC6 blocker either,
making it FC6Target
Would seemingly be a bug in the kernel DRM, or in the 3D driver.
Assuming the latter, reassigning to mesa...
*** Bug 196470 has been marked as a duplicate of this bug. ***
*** Bug 188228 has been marked as a duplicate of this bug. ***
For reference, this is fixed in Mesa head, and the backport difficulty is too
high to justify. Planning to fix with either a build of Mesa HEAD or, ideally,
6.5.1 if it ever exists.
What does that mean for FC6 and rawhide?
"fix with" implies that.
Any chance we'll see an updated Mesa before FC6T2?
*** Bug 200677 has been marked as a duplicate of this bug. ***
Are we going to get an updated Mesa that fixes this? I saw discussion on the
mailing list about this, and I thought that someone was going to build a new
Mesa, but I haven't seen anything yet.
I originally reported this issue (though my bug got duped to this newer one)
My ATI based box has been my live box so for rawhide I've been mainly testing on
a nVidia based box, I thought I saw some Mesa updates so I'd revisit this now
FC6T2 has been released, did a fresh install on spare partition of my ATI box
Still get an error running glxgears, though now different to console
libGL warning: 3D driver claims to not support visual 0x4b
drmRadeonCmdBuffer: -22 (exiting)
same in /var/log/messages
Aug 14 23:08:35 htpc kernel: [drm:r300_emit_3d_load_vbpntr] *ERROR* Offset
failed range check (k=0 i=2) while processing 3D_LOAD_VBPNTR packet.
Aug 14 23:08:35 htpc kernel: [drm:r300_emit_packet3] *ERROR*
Aug 14 23:08:35 htpc kernel: [drm:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet3
unsurprisingly compiz also fails and causes Xorg to restart, should this be any
further forward, or do I still need to wait for a(nother) Mesa update?
Hey! The latest kernel/X/mesa updates on FC6t2 have opengl apps working
now, but the driver still seems a bit flakey. I start seeing little short
segments of horizontal white lines flashing on and off when running opengl
with the radeon driver on FC6t2 x86_64.
On the exact same machine, running fglrx on FC5 i686 no flashing lines appear,
the screen seems very clean with fglrx.
OK, just updated to rawhide, took the latest mesa/xorg-ati/kernel updates
and AIGLX functions for me, similar to comment #12 I have seen one or two stray
horizontal lines of corruption on screen.
I have desktops on a cube which whizz round merrily, and glxgears is smooth and
FWIW runs at 1400 fps (yes, I know it's not a benchmark)
My tooltips in gnome-panel wibble about a little bit, but though compiz *is*
running, it's as though I have no wndowmanager, windows have no decoration, no
borders, no menu, I'll chack and log a separate bugzilla for that though,
excellent work guys :-))
I notice that though most of the GL screensavers work fine in the small gnome
screensaver preview window, they don't work in the full-screen preview, or when
the screensaver kicks in for real.
Also some of the GL screensavers (GLMatrix, GLForestfire, GLHanoi) are obviously
a bit too close to the edge for current r300 DRI, they sometimes work, sometimes
fail after a few seconds.
Andy those problems you are experiencing are those with compiz (or an other
compostiing manager) or with just a plain windowmanager? With AIGLX / a
composite manager you can expect problems, thats still very new stuff. more
important is how 3D works in the plain setup.
the lack of window decorations is with compiz, mostly 3D isteld seems good, the
openGL screensavers seem happier to run in preview window than full screen,
glxgears if ok, google earth faster than without hardware 3D, but still slow,
though I gather that is due to anti-aliased line drawing dropping back to
Are you getting fallback messages on the terminal when starting googleearth frm
Ifso update your mesa to the latest from rawhide that contains a workaround for
the googleearth problem, please report if you stil, have problems with google
earth after updating.
Just thought I'd mention: With the latest updates on FC6t2 I no longer
see the flickering lines as described in Comment #12 above, everything
seems pretty smooth.
This should be fixed as of the first 6.5.1 rc. Please open new bugs for any
further issues on this hardware.