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

Newegg Daily Deals

Reply
 
Thread Tools
Old 08-15-05, 08:26 PM   #1
TheE
Registered User
 
Join Date: Aug 2005
Posts: 2
Default PCIE GF + nF4 Pro issues

Hi...

I did a quick search and I haven't been able to find any posts with issues similar to mine.

The post below has also been sent off to few other places such as board vendors and our nVIDIA contacts but any help from the community would be much appreciated.

Here's the issue...

The systems tested are all using nF4Pro chipset and a range of GeForce and Quadro boards. The problem is running an accelerated OpenGL app twice will hard crash the system; either the PCIE bus or NV chip is locked. The app can be anything from glxgear to simply glxinfo. Two queries will lock the system. Neither a soft reset or a hard reset (using the reset switch) will bring the system back up. The all power must be drained from the system before video can be restored.

Note: The lock up does not occur on the boards with "higher" chip numbers, i.e. GeForce 6800 GT and Quadro 4400. Although GL apps may terminate when initializing for the 2nd time with the previously given boards.

The systems were tested with SuSE 9.3 Pro, RHEL4WS, FC3 and FC4. All systems were updated to the latest kernel (2.6.11.4-21.8 for SuSE and 2.6.12-1.1398_FC4 for FC4) and vanilla kernel 2.6.12.3 were tried in both single and smp configuration. All result in the same lock up. The only thing I haven't tried yet is an x86 kernel. Unfortunately, I am testing this for an OEM and it must run 64bit.

A GL app will run fine as long as it is the first app to be launched. I can run glxgears or the doom3 demo for hours without issue as long as another GL app is never run again.

Also of note is the GeForce and Quadro cards do operate properly with 32bit and 64bit linux on an Intel based solution.

The system configuration is as follows:

All systems tested with OS:
SuSE 9.3 Professional (x86_64 2.6.11.4-21.8 smp and single)
Redhat Enterprise Linux 4 WS (x86_64 kernel-2.6.9-11.EL smp and single)
Fedora Core 3 (x86_64 2.6.12-1.1372_FC3 smp and single)
Fedora Core 4 (x86_64 2.6.12-1.1398_FC4 smp and single)
Kernel.org 2.6.12.3 (compiled as x86_64 smp and single)

Intel solution also tested with:
Fedora Core 4 (i686 single and smp) -- this was also tested since the x86_64 version worked.

nVIDIA boards tested:

GeForce 6800 GT (XFX and PNY)
GeForce 6600 GT (PNY)
Quadro FX4400 (PNY)
Quadro FX540 (PNY)
Quadro FX1300 (PNY)

nVIDIA drivers tested:
1.0-7667
1.0-7676
1.0-7664

Working PCIE testbox:

Supermicro X6DAE-G <-- not running a nVIDIA chipset
2 x 3.4GHz Xeon DP with EM64T
4 x 1024MB RAM
1 x 250GB SATA

Non-working PCIE testboxes:

Supermicro H8DCE
2 x Opteron 250
4 x 1024MB RAM
1 x 250GB IDE

IWILL DK8EW
2 x Opteron 250
4 x 1024MB RAM
1 x 250GB IDE

IWILL DK8ES
2 x Opteron 250
4 x 1024MB RAM
1 x 250GB IDE

Xorg configuration is default with the following changes: "dri" removed and device driver changed from "nv" or "vesa" to "nvidia". xorg.conf is also provided in the next post.

Since the system runs fine until the 2nd GL app launch which hard locks there are no debugging messages.

Incase anybody is wondering the default distro kernels don't fair any better.
TheE is offline   Reply With Quote
Old 08-15-05, 08:45 PM   #2
TheE
Registered User
 
Join Date: Aug 2005
Posts: 2
Default Re: PCIE GF + nF4 Pro issues

xorg.conf from FC4 x86_64

-----

# Xorg configuration created by system-config-display

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.

RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
EndSection

Section "InputDevice"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Unknown monitor"
HorizSync 31.5 - 37.9
VertRefresh 50.0 - 70.0
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "Videocard vendor"
BoardName "VESA driver (generic)"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Viewport 0 0
Depth 16
Modes "800x600" "640x480"
EndSubSection
EndSection
TheE is offline   Reply With Quote
Old 08-15-05, 10:29 PM   #3
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: PCIE GF + nF4 Pro issues

You may try to redirect the console to the serial line (add "console=ttyS0,115200n8"
to the kernel comand line), so that you can see any potential kernel debug messages
that the nvidia module may tell before the system freezes - maybe that gives
you some hints.

regards

Bernhard
JaXXoN 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


Similar Threads
Thread Thread Starter Forum Replies Last Post
Choosing The Right GPU To Take Adobe Workflows To The Max News Archived News Items 0 05-29-12 05:40 PM
Z77 SABERTOOTH or P8Z77-V PRO Glitch85 CPUs, Motherboards And Memory 3 05-11-12 11:35 AM
FalconNW and Voodoo under ATI 9700 spell!!! mizzer Other Desktop Graphics Cards 12 09-20-02 07:53 PM
Undecided - GeForce 3 Ti 200 or Radeon 9000 Pro? b5fan NVIDIA GeForce 7, 8, And 9 Series 8 08-19-02 01:23 PM
Driver removal under Windows XP Pro DivotMaker NVIDIA Windows Graphics Drivers 8 08-13-02 09:15 AM

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


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