Bug 562713 - Starting from 1.7.4-7, X segfaults on start
Summary: Starting from 1.7.4-7, X segfaults on start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 563101 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-08 06:01 UTC by Dario Castellarin
Modified: 2018-04-11 18:03 UTC (History)
8 users (show)

Fixed In Version: 0.0.15-20.20091105gite1c2efd.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-11 16:41:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
X log file that shows the backtrace and consequent abort (17.10 KB, text/plain)
2010-02-08 06:01 UTC, Dario Castellarin
no flags Details

Description Dario Castellarin 2010-02-08 06:01:22 UTC
Created attachment 389462 [details]
X log file that shows the backtrace and consequent abort

Description of problem:
I usually manually update X with koji builds, starting from xorg-x11-server-1.7.4-7.x86_64 I experience a segfault at every start. Same goes for xorg-x11-server-1.7.4.902-1.x86_64.
My system is a Compal JFL92 laptop with a Nvidia GeForce 8600M video card, using nouveau driver.
Plymouth works fine, the problem occours when screen tries to switch to X.
The attached Xorg.0.log shows the backtrace.
Let me know how I can gather more useful debug informations.

Version-Release number of selected component (if applicable):
xorg-x11-server-1.7.4-7.x86_64
xorg-x11-server-1.7.4.902-1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. update xorg-x11-server to something >= 1.7.4-7
2. reboot
3. X fails to load (plymouth fine)

Comment 1 Matěj Cepl 2010-02-08 16:49:38 UTC
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x49ecc8]
1: /usr/bin/X (0x400000+0x61cf9) [0x461cf9]
2: /lib64/libpthread.so.0 (0x339da00000+0xf0f0) [0x339da0f0f0]
3: /usr/bin/X (xf86GetPrimaryOutput+0x35) [0x4819a5]
4: /usr/bin/X (xf86SetDesiredModes+0x8b) [0x483dbb]
5: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7f7344178000+0x1edf1) [0x7f7344196df1]
6: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7f7344178000+0x1f7db) [0x7f73441977db]
7: /usr/bin/X (AddScreen+0x1d4) [0x4278b4]
8: /usr/bin/X (InitOutput+0x7b4) [0x470164]
9: /usr/bin/X (0x400000+0x21c5a) [0x421c5a]
10: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x339d61eb1d]
11: /usr/bin/X (0x400000+0x219a9) [0x4219a9]
Segmentation fault at address 0xa0

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting

Comment 2 Dario Castellarin 2010-02-09 22:22:34 UTC
I can confirm this doesn't occur with machines using the radeon driver, tomorrow I'll be able to test it on a PC with a different nvidia card (7600GS AGP).

Comment 3 Ben Skeggs 2010-02-10 23:03:19 UTC
*** Bug 563101 has been marked as a duplicate of this bug. ***

Comment 4 Ben Skeggs 2010-02-10 23:04:12 UTC
xorg-x11-drv-nouveau-0.0.15-20.20091105gite1c2efd.fc12 is available in koji to fix this issue.

Comment 5 Fedora Update System 2010-02-10 23:07:10 UTC
xorg-x11-drv-nouveau-0.0.15-20.20091105gite1c2efd.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.15-20.20091105gite1c2efd.fc12

Comment 6 Dario Castellarin 2010-02-11 08:37:47 UTC
Thank you, xorg-x11-drv-nouveau-0.0.15-20.20091105gite1c2efd.fc12 solved the issue here!

Comment 7 Matěj Cepl 2010-02-11 16:41:14 UTC
Thank you for letting us know.

Comment 8 Fedora Update System 2010-02-12 04:47:40 UTC
xorg-x11-drv-nouveau-0.0.15-20.20091105gite1c2efd.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.