Created attachment 464764 [details] Logfile of Xserver-crash Description of problem: Since upgrading from FC13 to FC14 the Xserver crashes with a Segmentation fault every startup of the Xserver using the radeon driver on my ATI Mobility Radeon X700. Booting with kernel-flag "nomodeset", disabling selinux or deleting xorg.conf lead to the same segfault. At the moment I'm using vesa-driver without any errors of the Xserver. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.9.1-3.fc14 xorg-x11-drv-ati-6.13.1-0.3.20100705git37b348059.fc14 How reproducible: Starting X-Server with radeon driver. Steps to Reproduce: 1. startx 2. 3. Actual results: Segmentation fault (see logfile for further details) Expected results: normal startup Additional info: - Hardware: ATI Mobility Radeon X700 on Samsung X20 Laptop (Comment: Since this is my very-fist bug-report simply ask for further information if I've forgotten something.)
Created attachment 464765 [details] Used Xorg configuration
Created attachment 464766 [details] Smolt-profile
Created attachment 464767 [details] Output of "lspci"
Backtrace: [ 213.326] 0: /usr/bin/Xorg (xorg_backtrace+0x39) [0x80c6ea1] [ 213.326] 1: /usr/bin/Xorg (0x8047000+0x4ebb7) [0x8095bb7] [ 213.326] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xe5840c] [ 213.326] Segmentation fault at address (nil) [ 213.326] Fatal server error: [ 213.326] Caught signal 11 (Segmentation fault). Server aborting [ 213.326] [ 213.326] Please consult the Fedora Project support at http://wiki.x.org for help. [ 213.326] Please also check the log file at "/var/log/Xorg.1.log" for additional information. [ 213.326] [ 213.330] disable LVDS [ 213.330] (II) RADEON(0): RADEONRestoreMemMapRegisters() : [ 213.330] (II) RADEON(0): MC_FB_LOCATION : 0xd7ffd000 0xd7ffd000 [ 213.330] (II) RADEON(0): MC_AGP_LOCATION : 0x003f0000
For additional information the same segmentation fault is still occurring with Xorg-1.9.3-3.fc14: Backtrace: [ 26060.242] 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e7f2c] [ 26060.242] 1: /usr/bin/Xorg (0x8048000+0x5dd56) [0x80a5d56] [ 26060.242] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x18e40c] [ 26060.242] Segmentation fault at address (nil) [ 26060.242] Fatal server error: [ 26060.242] Caught signal 11 (Segmentation fault). Server aborting [ 26060.242] [ 26060.243] Please consult the Fedora Project support at http://wiki.x.org for help. [ 26060.243] Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 26060.243] [ 26060.246] disable LVDS [ 26060.246] (II) RADEON(0): RADEONRestoreMemMapRegisters() : [ 26060.246] (II) RADEON(0): MC_FB_LOCATION : 0xd7ffd000 0xd7ffd000 [ 26060.246] (II) RADEON(0): MC_AGP_LOCATION : 0x003f0000
Same on Dell Dimension 5150 Fedora 14. Fedora 13 works fine. Xorg-1.9.3-3.fc14 xorg-x11-drv-ati-6.13.1-0.3.20100705git37b348059.fc14 kernel-2.6.35.10-74.fc14 # lspci | grep ATI 01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE] -- (Nearly) the end of Xorg.0.log -- [ 2122.780] drmOpenDevice: node name is /dev/dri/card0 [ 2122.780] drmOpenDevice: open result is 13, (OK) [ 2122.780] drmOpenByBusid: Searching for BusID pci:0000:01:00.0 [ 2122.780] drmOpenDevice: node name is /dev/dri/card0 [ 2122.780] drmOpenDevice: open result is 13, (OK) [ 2122.780] drmOpenByBusid: drmOpenMinor returns 13 [ 2122.780] drmOpenByBusid: Interface 1.4 failed, trying 1.1 [ 2122.780] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 [ 2122.903] Backtrace: [ 2122.917] 0: /usr/bin/X (xorg_backtrace+0x3c) [0x80e7f2c] [ 2122.917] 1: /usr/bin/X (0x8048000+0x5dd56) [0x80a5d56] [ 2122.917] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x97540c] [ 2122.917] Segmentation fault at address (nil) [ 2122.917] Fatal server error: [ 2122.917] Caught signal 11 (Segmentation fault). Server aborting [ 2122.917]
Upgraded from F13 to F14 and X server seg faults with xorg.conf from F13. Removing xorg.conf fixes issue or commenting out "Virtual" in 'Section "Screen"' 'Subsection "Display"' also fixes issue. See attached xorg.conf.
Created attachment 471102 [details] working xorg configuration file
Same problem after upgrade FC12 to FC14 with ATI Mobility X1400. Start without xorg.conf or with cleaned xorg.conf didn´t fix it. System is now running with FBDev till fix is available. Regards
I am using gentoo. But anyway I got the same bug when I disabled the Kernel build option CONFIG_DRM_RADEON_KMS. After reenabling it all run fine again.
And still the same with xorg-x11-server-Xorg-1.9.3-4.fc14: Backtrace: [ 4910.199] 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e7f0c] [ 4910.199] 1: /usr/bin/Xorg (0x8047000+0x5ed56) [0x80a5d56] [ 4910.199] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x7fc40c] [ 4910.199] Segmentation fault at address (nil) [ 4910.199] Fatal server error: [ 4910.199] Caught signal 11 (Segmentation fault). Server aborting [ 4910.199] [ 4910.199] Please consult the Fedora Project support at http://wiki.x.org for help. [ 4910.199] Please also check the log file at "/var/log/Xorg.1.log" for additional information. [ 4910.199] [ 4910.203] disable LVDS [ 4910.203] (II) RADEON(0): RADEONRestoreMemMapRegisters() : [ 4910.203] (II) RADEON(0): MC_FB_LOCATION : 0xd7ffd000 0xd7ffd000 [ 4910.203] (II) RADEON(0): MC_AGP_LOCATION : 0x003f0000 I really would be happy to see someone trying to work on a fix for this cause its getting annoying to me :( Best regards!
Has there been any progress on fixing this bug? I installed Fedora 14 on my Thinkpad today and face the same issue.
I just realized that I was booting with "nomodest" kernel-flag all the time. I simply overlooked it (shame on me). After removing the kernel-flag I am able to start Xorg with radeon-driver again - so the problem is "solved" from my side, even if Xorg shouldn't segfault. Greetings!
Nanority, you're my hero! That was the problem! The nomodeset came with the FC14-Installation and I didn't look on something like that. While I am writing this comment, I read what this parameter is doing. Why is such a parameter the default after install FC14? Once again: Thank you for this hint! Best regards.
(In reply to comment #13) > I just realized that I was booting with "nomodest" kernel-flag all the time. I > simply overlooked it (shame on me). After removing the kernel-flag I am able to > start Xorg with radeon-driver again - so the problem is "solved" from my side, > even if Xorg shouldn't segfault. Even I am using the "nomodeset" kernel cmdline arg, but because this is a supported arg, the X driver mustn't segfault still. Using "nomodeset" was necessary to get 3D working in previous Fedora releases.
(In reply to comment #15) > Even I am using the "nomodeset" kernel cmdline arg, but because this is a > supported arg, the X driver mustn't segfault still. Using "nomodeset" was > necessary to get 3D working in previous Fedora releases. Yes, certainly, XServer shouldn't crash, but supporting nomodeset is definitively less priority for us.
3D is working fine with KMS for most user, we have few bugs on few apps with few specific configurations
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping