Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 04-21-06, 01:19 AM   #1
Compholio
Registered User
 
Join Date: Jul 2004
Posts: 66
Default Fedora Rawhide + 8756 = Signal 11

I'm getting the most non-descript error I've ever seen from the nvidia driver when I try to load Xorg (now that I've recently updated my system). The following is the only error that I see in any of the logs:


*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x82) [0x4762a2]
1: /lib64/libc.so.6 [0x2aaaab42b7d0]
2: /usr/lib64/xorg/modules/drivers/nvidia_drv.so(_nv000158X+0xda) [0x2aaaac2442ba]

Fatal server error:
Caught signal 11. Server aborting
Compholio is offline   Reply With Quote
Old 04-21-06, 02:04 AM   #2
Compholio
Registered User
 
Join Date: Jul 2004
Posts: 66
Default Re: Fedora Rawhide + 8756 = Signal 11

k, now i should actually have the bug report log attached...
Attached Files
File Type: log nvidia-bug-report.1.log (50.5 KB, 145 views)
File Type: log nvidia-bug-report.0.log (95.6 KB, 137 views)
Compholio is offline   Reply With Quote
Old 04-21-06, 03:31 PM   #3
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Fedora Rawhide + 8756 = Signal 11

The bug report that you posted only shows that the 'nv' X driver was in use. I'd like to see a bug report that captures the failure you're experiencing.

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 04-21-06, 08:05 PM   #4
Compholio
Registered User
 
Join Date: Jul 2004
Posts: 66
Default Re: Fedora Rawhide + 8756 = Signal 11

sorry about that, for some reason it won't export the correct Xorg.0.log, so here it is attached separately. it really looks like everything worked fine and then it just mysteriously crashes at the end...
Attached Files
File Type: log Xorg.0.log (20.5 KB, 137 views)
Compholio is offline   Reply With Quote
Old 04-21-06, 09:25 PM   #5
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Fedora Rawhide + 8756 = Signal 11

If you comment out the glx module in xorg.conf does X startup?

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 04-21-06, 10:43 PM   #6
Compholio
Registered User
 
Join Date: Jul 2004
Posts: 66
Default Re: Fedora Rawhide + 8756 = Signal 11

no, the driver retuns an error (but continues) and does the exact same thing
Compholio is offline   Reply With Quote
Old 04-22-06, 12:32 AM   #7
Compholio
Registered User
 
Join Date: Jul 2004
Posts: 66
Default Re: Fedora Rawhide + 8756 = Signal 11

Here's the log for it, relevant lines below for convenience:
(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
(EE) NVIDIA(0): log file that the GLX module has been loaded in your X
(EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
(EE) NVIDIA(0): you continue to encounter problems, Please try
(EE) NVIDIA(0): reinstalling the NVIDIA driver.
...

*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x82) [0x4762a2]
1: /lib64/libc.so.6 [0x2aaaab42b7d0]
2: /usr/lib64/xorg/modules/drivers/nvidia_drv.so(_nv000158X+0xda) [0x2aaaac2442ba]

Fatal server error:
Caught signal 11. Server aborting
Attached Files
File Type: log Xorg.0.log (20.6 KB, 139 views)
Compholio is offline   Reply With Quote
Old 04-24-06, 08:09 PM   #8
randomuser
Registered User
 
Join Date: Aug 2005
Posts: 2
Default Re: Fedora Rawhide + 8756 = Signal 11

I am seeing the same failure on my x86_64 box running a recent fedora rawhide. startx gets past most of the initialization and I see the nvidia splash screen right before it drops back to the console. Removing the glx module doesn't help. I also tried going back to 8178, but that is failing with a similar error.

...
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX

*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Backtrace:
0: X(xf86SigHandler+0x82) [0x4762a2]
1: /lib64/libc.so.6 [0x321c42f7d0]
2: /usr/lib64/xorg/modules/drivers/nvidia_drv.so(_nv000158X+0xda) [0x2b9b9dd6e2ba]

Fatal server error:
Caught signal 11. Server aborting
randomuser is offline   Reply With Quote

Old 04-24-06, 08:50 PM   #9
Compholio
Registered User
 
Join Date: Jul 2004
Posts: 66
Default Re: Fedora Rawhide + 8756 = Signal 11

Yes! That is the exact same problem I'm having, I would say that it "half-loads" the splash screen for me though - I can see the white of it but it's so quick that I don't see the logo.
Compholio is offline   Reply With Quote
Old 05-09-06, 04:07 PM   #10
ellson
Registered User
 
Join Date: Mar 2004
Posts: 21
Default Re: Fedora Rawhide + 8756 = Signal 11

I'm seeing the same problem on x86_64 with all xorg-xll-server-*rpm
after 1.0.99.1-2. Reverting to that version works around the problem.
ellson is offline   Reply With Quote
Old 05-09-06, 06:08 PM   #11
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Fedora Rawhide + 8756 = Signal 11

xorg-1.1 is currently not expected to work properly with 1.0-8756 due to ABI changes. However, it shouldn't be segfaulting. People using other distributions have reported font rendering problems.

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 05-09-06, 07:05 PM   #12
ellson
Registered User
 
Join Date: Mar 2004
Posts: 21
Default Re: Fedora Rawhide + 8756 = Signal 11

It segfaults for me just as reported in comment #8. This is with xorg-x11-server-*-1.0.99.902-1.x86_64.rpm

$ tail -20 Xorg.0.log
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX

*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Backtrace:
0: X(xf86SigHandler+0x82) [0x4762b2]
1: /lib64/libc.so.6 [0x355522f700]
2: /usr/lib64/xorg/modules/drivers/nvidia_drv.so(_nv000158X+0xda) [0x2aaaac30c2ba]

Fatal server error:
Caught signal 11. Server aborting
ellson is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 04:19 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.