Bug 49182 - Starting X server crashes when DRI is enabled
Summary: Starting X server crashes when DRI is enabled
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.6 (2010.12)
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
: 49900 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-04-26 10:34 UTC by Andreas Theofilu
Modified: 2012-05-14 06:06 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
The Xorg.0.log with the backtrace at the end (84.98 KB, patch)
2012-04-26 10:34 UTC, Andreas Theofilu
no flags Details | Splinter Review

Description Andreas Theofilu 2012-04-26 10:34:48 UTC
Created attachment 60624 [details] [review]
The Xorg.0.log with the backtrace at the end

I'm using Debian testing. It's coming with Xorg version 7.6. The version of the radeon driver is 6.14.4.

The graphic card is a HD 4350. With previous version of radeon/ati driver (v6.14.3) everything worked fine. Attached to this you will find the log from X during start up, the xorg.conf.

Is there something I can try to set? I need DRI on because without it I can't use the integrated TV-card and playing videos with "mplayer" does not work on full screen.

======= xorg.conf ==========
Section "ServerFlags"
        Option      "NoPM" "true"
        Option      "BlankTime" "0"
        Option      "StandbyTime" "0" 
        Option      "SuspendTime" "0"
        Option      "OffTime" "0"
EndSection

Section "ServerLayout"
        Identifier     "TheoSys"
        Screen         0 "Monitor"
        InputDevice    "Generic Keyboard" "CoreKeyboard"
        InputDevice    "Configured Mouse" "CorePointer"
EndSection

Section "InputDevice"
        Identifier  "Generic Keyboard"
        Driver      "kbd"
#       Option      "XkbRules" "xorg"
#       Option      "XkbModel" "pc105"
#       Option      "XkbLayout" "de"
#       Option      "XkbVariant" "nodeadkeys"
EndSection

Section "InputDevice"
        Identifier  "Configured Mouse"
        Driver      "mouse"
EndSection

Section "Monitor"
        Identifier   "Fujitsu"
        Option      "VendorName" "Fujitsu Siemens"
        Option      "ModelName" "L24W-2"
        Option      "DPMS" "false"
EndSection

Section "Monitor"
        Identifier   "Denon"
        Option      "VendorName" "Denon"
#       HorizSync   30.0 - 110.0
#       VertRefresh 50.0 - 150.0
        Option      "DPMS" "false"
EndSection

Section "Device"
        Identifier  "AMD"
        Driver      "radeon"
#       Option      "ZaphodHeads" "DVI-0,HDMI-0"
#       Option      "ColorTiling" "on"
        Option      "DRI" "off"
#       BusID       "PCI:1:0:0"
EndSection

Section "Device"
        Identifier  "VESA"
        Driver      "vesa"
EndSection

Section "Screen"
        Identifier "Monitor"
        Device     "AMD"
        Monitor    "Fujitsu"
        Monitor    "Denon"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes     "1920x1200" "1920x1080" "1680x1050" "1440x900" "1280x1024" "1024x768"
        EndSubSection
EndSection

============ EOF ===========
Comment 1 Alex Deucher 2012-04-26 10:47:40 UTC
Any reason you are not using KMS?  UMS is not really supported any more.  Please make sure the radeon kernel module is loaded in KMS mode before starting X.
Comment 2 Andreas Theofilu 2012-04-27 01:22:02 UTC
I just wasn't aware of that. Switched now to KMS and everything works as expected. The reported error is gone and DRI is working again.
Many thanks for that hint. And I'll mark this bug as solved.
Comment 3 Michel Dänzer 2012-05-01 01:20:18 UTC
It is a bug, but it won't be fixed unless someone provides at least a proper gdb backtrace of the crash.
Comment 4 Michel Dänzer 2012-05-03 06:43:32 UTC
Hopefully fixed in current xf86-video-ati Git, reopen if not.
Comment 5 Michel Dänzer 2012-05-14 06:06:48 UTC
*** Bug 49900 has been marked as a duplicate of this bug. ***


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.