Bug 24357 - Radeon KMS causes fatal errors with r600 DRI driver
Summary: Radeon KMS causes fatal errors with r600 DRI driver
Status: RESOLVED NOTABUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/R600 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: high critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-06 13:04 UTC by Bob Ham
Modified: 2009-10-06 14:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg output with KMS kernel (34.26 KB, text/plain)
2009-10-06 13:04 UTC, Bob Ham
Details
Xorg log with KMS kernel (36.99 KB, text/plain)
2009-10-06 13:05 UTC, Bob Ham
Details
Output of "LIBGL_DEBUG=verbose glxinfo" with KMS kernel (18.72 KB, text/plain)
2009-10-06 13:05 UTC, Bob Ham
Details
dmesg output with non-KMS kernel (33.02 KB, text/plain)
2009-10-06 13:06 UTC, Bob Ham
Details
Xorg log with non-KMS kernel (95.50 KB, text/plain)
2009-10-06 13:07 UTC, Bob Ham
Details
Output of "LIBGL_DEBUG=verbose glxinfo" with non-KMS kernel (5.92 KB, text/plain)
2009-10-06 13:07 UTC, Bob Ham
Details

Description Bob Ham 2009-10-06 13:04:17 UTC
Created attachment 30122 [details]
dmesg output with KMS kernel

With KMS from the drm-2.6 git tree, I get the following error running "LIBGL_DEBUG=verbose glxinfo":

libGL: OpenDriver: trying /opt/xorg-ati-free/lib64/dri//r600_dri.so
libGL error: failed to create dri screen
libGL: OpenDriver: trying /opt/xorg-ati-free/lib64/dri//swrast_dri.so

I also get the following in Xorg.0.log:

(EE) AIGLX error: Calling driver entry point failed
(EE) AIGLX: reverting to software rendering
(II) AIGLX: Screen 0 is not DRI capable

even though:

(II) RADEON(0): Direct rendering enabled

None of these errors are present without KMS.  Attached are dmesg output, Xorg.0.log and the output of glxinfo, for the same kernel both with and without KMS enabled.
Comment 1 Bob Ham 2009-10-06 13:05:05 UTC
Created attachment 30123 [details]
Xorg log with KMS kernel
Comment 2 Bob Ham 2009-10-06 13:05:52 UTC
Created attachment 30124 [details]
Output of "LIBGL_DEBUG=verbose glxinfo" with KMS kernel
Comment 3 Bob Ham 2009-10-06 13:06:33 UTC
Created attachment 30125 [details]
dmesg output with non-KMS kernel
Comment 4 Bob Ham 2009-10-06 13:07:06 UTC
Created attachment 30126 [details]
Xorg log with non-KMS kernel
Comment 5 Bob Ham 2009-10-06 13:07:36 UTC
Created attachment 30127 [details]
Output of "LIBGL_DEBUG=verbose glxinfo" with non-KMS kernel
Comment 6 Alex Deucher 2009-10-06 13:36:26 UTC
Did you build mesa against libdrm_radeon?
Comment 7 Bob Ham 2009-10-06 13:55:32 UTC
I'm not sure what it means to build mesa against libdrm_radeon.  There is a libdrm_radeon.so library but libGL.so doesn't depend on it.  What exactly does is mean to build mesa against libdrm_radeon?
Comment 8 Alex Deucher 2009-10-06 14:24:32 UTC
(In reply to comment #7)
> I'm not sure what it means to build mesa against libdrm_radeon.  There is a
> libdrm_radeon.so library but libGL.so doesn't depend on it.  What exactly does
> is mean to build mesa against libdrm_radeon?
> 

libdrm_radeon is in the libdrm tree and provides the memory manager interface needed for the ddx and mesa when used with KMS.  The radeon 3D drivers (radeon, r200, r300, r600) need to be built against libdrm_radeon if you want to use them with KMS.  The mesa build system should pick it up if it's present on your system.
Comment 9 Bob Ham 2009-10-06 14:39:21 UTC
I checked the config.log and found warnings about libdrm_radeon not being found.  I configured and installed the tree again. The glxinfo errors have gone away, it reports

  OpenGL renderer string: Mesa DRI R600 (RV770 9442) 20090101  TCL DRI2

and glxgears works.  Although I would point out that glxinfo still reports the following:

  do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
  Try adjusting the vblank_mode configuration parameter.

Regardless, the major issue is resolved, thanks.
Comment 10 Alex Deucher 2009-10-06 14:46:41 UTC
(In reply to comment #9)
> and glxgears works.  Although I would point out that glxinfo still reports the
> following:
> 
>   do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
>   Try adjusting the vblank_mode configuration parameter.

You can ignore this for now.  irqs aren't implemented yet on r6xx/r7xx hw.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.