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

Newegg Daily Deals

Reply
 
Thread Tools
Old 07-10-09, 09:48 AM   #1
apm
Registered User
 
Join Date: Jun 2009
Location: Northern VA
Posts: 1
Default glxinfo Crash-Dual Monitor Remote Display

hi,

We have a repeatable case (on RHEL) where glxinfo can cause a crash under the following situation:
Starting from an RHEL 5 workstation with dual monitors (non-xinerama/twinview, separate X screens), an nVidia GPU, and using "nvidia" drivers (180.29) bring up a terminal in each window and log into a remote RHEL workstation via "ssh -X" in both terminals then type "glxinfo" in each terminal: usually the first "glxinfo" runs normally, and the second "glxinfo" command causes the X server to crash; CTRL-ALT-BKSPC doesn't restart X, but it is possible to ssh into the affected workstation and reboot. The attached bug report documents one such instance. The /var/log/Xorg.0.log finishes with something like:
<snip>
...
(II) Mouse0: ps2EnableDataReporting: succeeded

Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80e4fc1]
1: [0x1a1420]
2: /lib/libc.so.6 [0xc6f277]
3: /lib/libc.so.6(__libc_calloc+0x8d) [0xc70abd]
4: /usr/lib/xorg/modules/extensions/libglx.so [0xa64a47]

Fatal server error:
Caught signal 11. Server aborting

(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
</snip>

A similar session ended with /var/log/Xorg.0.log like:
<snip>
...
(II) Mouse0: ps2EnableDataReporting: succeeded

Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80e4fc1]
1: [0xd7f420]
2: /usr/lib/xorg/modules/extensions/libglx.so [0x372198]

Fatal server error:
Caught signal 11. Server aborting

(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
</snip>

This generally seems to occur when sshing from an RHEL 5 Server computer to an RHEL 4 WS/ES computer, or when sshing from a 32-bit RHEL 5 Server computer to a 64-bit RHEL 5 Server computer (although I only tested the last scenario once). sshing from 32/64-bit RHEL 4 to 32/64-bit RHEL 4 seems fine. sshing from 32-bit RHEL 5 Server computer to another 32-bit RHEL 5 Server computer also seems ok (again only one test case for the latter). In most cases the crash freezes the X server, in one case from 32-bit RHEL 5 Server to 64-bit RHEL 5 Server instead of locking up the X server restarted itself.

These errors all occurred using the 180.29 drivers. The 185.18.14 drivers don't fix the problem, and actually create a different set of problems. I've tried various permutations of "pci=nommconf", "idle=poll", "maxcpus=1" etc. as per zander's suggestions and none solve the problem.

Has anyone else seen any errors like this?
Attached Files
File Type: log nvidia-bug-report.log (135.2 KB, 70 views)
apm 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 01:07 PM.


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