driver x86 8174 dual display crash

[cmos_designer]

Hey guys,

The new driver is awesome and totally faster than the 7676. I have 2.6.11-1.1369_FC4smp running.

I was dragging the real player window in my second display (which is in the PCI slot) and the Xserver crashed and rebooted. Here is the error:

SetClientVersion: 0 8
SetClientVersion: 0 8

SetClientVersion: 0 8
SetGrabKeysState - disabled
SetGrabKeysState - enabled

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

Fatal server error:
Caught signal 11. Server aborting

What does this mean? Besides this everything is fine, however, this has happend twice. I can recreate the error when dragging around the glxgears window too. Any ideas on how to debug and and determind what the error may be?

- cmos_design guy

[netllama]

What you've posted means that the X server crashed with a segfault.

First, I'd suggest updating to the latest FC4 kernel (yum update). If that has no impact, please generate a bug report immediately after this next reproduces.

Also, what kind of motherboard are you using?

Thanks,
Lonni

[cmos_designer]

Originally Posted by netllama

What you've posted means that the X server crashed with a segfault.

First, I'd suggest updating to the latest FC4 kernel (yum update). If that has no impact, please generate a bug report immediately after this next reproduces.

Also, what kind of motherboard are you using?

Thanks,
Lonni

netllama,

I am using a SUPER Micro X5DAL-G, dual processor board. Do you think this is board related? Any additional information you may need? I am going to upgrade kernel right away.

[netllama]

I've seen many bugs that were caused by motherboard problems rather than the nvidia driver. Can you verify that you're using the latest BIOS:
http://www.supermicro.com/support/bios/

If updating the BIOS & OS doesn't help, then please post the bug report that I requested.

Thanks,
Lonni

[cmos_designer]

I have updated my kernel to 2.6.14-1.1644_FC4smp. It seems that this has fixed the probelm, and I can not recreate the Signal 11 error. Thank you very much for your help!