Bug 23270

Summary: KMS DDX driver crashes on non KMS kernel when modprobe radeon failed
Product: xorg Reporter: Thierry Vignaud <thierry.vignaud>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium    
Version: 7.4 (2008.09)   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 24158    
Bug Blocks:    
Attachments:
Description Flags
X log showing crash on a non KMS kernel
none
X log showing success on a KMS kernel
none
interesting difference bits between KMS an non KMS w/o the radeon kernel module none

Description Thierry Vignaud 2009-08-12 06:45:27 UTC
Created attachment 28545 [details]
X log showing crash on a non KMS kernel

Using ati driver 6.2.99 (aka git shapshot as of 92baeafde8f0c1eed2b6769e96f8093e3d6d7478 (today)) works fine on a KMS aware kernel.
However, if booting on a non KMS kernel where it failed to load the radeon kernel module, it crashes trying to set up the 3D engine despte advertising disabling DRI.

Here /etc/modprobe.options contains "options radeon modeset=1" and thus radeon kernel module failed to load because of the unknown option with a non KMS kernel.

logs shows a crash in RADEONInit3DEngine() despite DRI being disabled. See attache traces.

Card is radeon 9600 (RV350).
Xserver is 1.6.2. Mesa is 7.5. ATI driver is 6.2.99

Solution: do not try to init 3D engine at all if DRI is disabled for whatever reason it is.
Comment 1 Thierry Vignaud 2009-08-12 06:46:03 UTC
Created attachment 28546 [details]
X log showing success on a KMS kernel
Comment 2 Thierry Vignaud 2009-08-12 06:48:08 UTC
Created attachment 28547 [details] [review]
interesting difference bits between KMS an non KMS w/o the radeon kernel module
Comment 3 Alex Deucher 2009-08-12 07:03:42 UTC
R4xx and older cards can use the 3D engine for EXA via MMIO, so it should work fine.  Can you get a backtrace of the crash with gdb?
http://wiki.x.org/wiki/Development/Documentation/ServerDebugging
Comment 4 Thierry Vignaud 2009-10-05 07:26:33 UTC
Looks like it got fixed along bug #24158

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.