NVIDIA FC6 System Lockup --> HELP.

coffee412 · #1 18th May 2007, 01:29 PM

Hello Everyone,

I have a really wierd problem. Im having a total system lockup that is intermittet. This lockup is on FC6. Here are the systems:

1. System totally locks up while working on it. I cannot ssh into it or get anything to work. HARDLOCK.

2. Keyboard continually flashes the "Caps lock" and "scroll lock" lights after a few seconds into the lockup.

3. Nothing in any of the logs pertaining to this problem.

Im thinking my problem is related to my Geforce 6200 turbocache card because if I unload the nvidia driver and use the regular nv driver I dont have this problem.

Anyone have a problem like this? I have searched bug reports/forums/ect but dont see anything on this. Below is my hardware/software info.

Currently using this build for nvidia card. Have tried others. Same results.
NVIDIA-Linux-x86-1.0-9755

Xorg.conf file:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Mon Feb 26 23:38:46 PST 2007

# Xorg configuration created by livna-config-display

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules"
FontPath "unix/:7100"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "glx"
Load "dbe"
Load "extmod"
EndSection

Section "ServerFlags"
Option "Xinerama" "0"
EndSection

Section "InputDevice"

# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
EndSection

Section "Monitor"

# HorizSync source: edid, VertRefresh source: edid
# ## Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Acer AL1714"
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 75.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6200 TurboCache(TM)"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 16
Option "metamodes" "1024x768 +0+0; 800x600 +0+0; 640x480 +0+0"
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Linux coffee.athome.net 2.6.20-1.2948.fc6 #1 SMP Fri Apr 27 19:48:40 EDT 2007 i686 athlon i386 GNU/Linux

[root@coffee X11]# /sbin/lspci
00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 TurboCache(TM)] (rev a1)

Motherboard: ASUS board--> Model number not available as I write this.
memory: 1 gig

Ive tried turning off APCI but didnt change anything.

Any ideas are helpful.

coffee412

Dies · #2 18th May 2007, 04:17 PM

Adding

pci=nommconf idle=poll

to the end of the kernel line in /etc/grub/grub.conf, helps in a lot of cases, my specs are similar to yours btw but ymmv.

You can try it out first by highlighting the Fedora entry in the grub menu and hitting 'a' to append those options to the kernel line temporarily and see if it helps, if so add them permanently.

coffee412 · #3 18th May 2007, 10:18 PM

Im going to give that a shot. Thanks very much. Lets see how it runs this weekend and I will post back with results. Have a great weekend!

coffee

coffee412 · #4 20th May 2007, 01:28 PM

Sunday ---> Still locking up. Happens when running a combination like Pan and firefox. Switching between the two the system will lockup while drawing the screen for one of them. I tried turning off APCI on the Asus board and also resetting nvidia drivers in
Applications/System tools/Nvidia X server settings.

Tried your settings but also locked up.

Checked temp on vid card and its fine. So, Its not like its overheating. Ive never had it lockup using the NV driver instead of the nvidia module in xorg.conf. Acceleration problem in 2D?

Im going to look into upgrading the bios in the asus motherboard next I guess.

coffee

leigh123linux · #5 20th May 2007, 01:45 PM

can you post

cat /var/log/Xorg.0.log | grep EE

and

cat /var/log/Xorg.0.log | grep WW

skeptic · #6 20th May 2007, 05:37 PM

I had a similar issue, but I could reproduce it by running certain GL things (in addition to semi-random lockups). In my case I did not have the ModulePath entries correct in /etc/X11/xorg.conf correct, so it was picking up non-nvidia libraries when running the nvidia driver. Switching to nv driver or disabling gl caused the problems to go away. Setting this in xorg.conf fixed it:

Section "Files"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules/extensions"
ModulePath "/usr/lib/xorg/modules"
EndSection

BTW, this happened on a system that I upgraded from FC5 to FC6. The same day I did a fresh FC6 install and did not have the issues (copied the Files section to the upgraded sytsem and all was well).

HTH

dr death · #7 20th May 2007, 05:51 PM

FWIW I have a similar problem:

$ /sbin/lspci
00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f2)
00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f2)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a2)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a2)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a2)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 TurboCache(TM)] (rev a1)
05:07.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
05:07.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)

This is an ASUS K8N4E-Deluxe m/board, and a PCI-e graphics board (gigabyte I think)

Every time the system crashes, I get errors in my log that look something like:

May 15 18:37:09 localhost kernel: NVRM: Xid (0001:00): 6, PE0000 0304 0000b35b 0000fdf4 ffffffff 00240024
May 15 18:37:49 localhost kernel: NVRM: Xid (0001:00): 8, Channel 00000000
May 15 18:38:01 localhost kernel: NVRM: Xid (0001:00): 8, Channel 0000001e
May 15 18:38:13 localhost kernel: NVRM: Xid (0001:00): 8, Channel 00000020
May 15 18:38:50 localhost last message repeated 3 times

Anyway, I have had problems with certain combinations of kernels / nvidia drivers. If it starts giving me problems, I usually go back to the previous kernel version, and often that works (I suspect the problem lies with the nVidia drivers).

On a side note, it's not so much of a problem with journalled filesystems, but if you are getting frequent crashes, you can add "sysrq_always_enabled" to you kernel parameters (or "echo 1 > /proc/sys/kernel/sysrq" to your rc.local), and then pressing <Alt>-<SysRq>-s, <Alt>-<SysRq>-u, <Alt>-<SysRq>-b will sync and reboot the system.

I'm not sure that any of this helps you, except maybe to let you know that it's probably not a hardware problem

Dies · #8 20th May 2007, 10:20 PM

Quote:

Originally Posted by dr death

On a side note, it's not so much of a problem with journalled filesystems, but if you are getting frequent crashes, you can add "sysrq_always_enabled" to you kernel parameters (or "echo 1 > /proc/sys/kernel/sysrq" to your rc.local), and then pressing <Alt>-<SysRq>-s, <Alt>-<SysRq>-u, <Alt>-<SysRq>-b will sync and reboot the system.

Ahh, thanks, always kind of bugged me that it didn't work on FC, not enough to find out why but still good to know.

coffee412 · #9 21st May 2007, 02:05 PM

No Errors in my xorg log.

[coffee@coffee ~]$ cat /var/log/Xorg.0.log | grep EE
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension MIT-SCREEN-SAVER
[coffee@coffee ~]$

dr death · #10 21st May 2007, 02:12 PM

Try:
$ sudo grep NVRM /var/log/messages*

coffee412 · #11 21st May 2007, 02:34 PM

Ok, I did a bios upgrade and now when the system locks I can still get in via ssh. GOOD. Now running top shows xorg taking up 99 percent of the cpu cycles. I have the following in my logs now also:

May 21 09:12:46 coffee kernel: NVRM: Xid (0001:00): 6, PE0000 0638
00000000 0000faa4 ffffffff ffffffff
May 21 09:12:58 coffee kernel: NVRM: Xid (0001:00): 8, Channel 00000020
May 21 09:13:34 coffee last message repeated 3 times
May 21 09:14:47 coffee last message repeated 6 times
May 21 09:15:48 coffee last message repeated 5 times

So, Im a bit further. Atleast now we have something to google around with.

What do you think?

coffee

dr death · #12 21st May 2007, 02:44 PM

Try these:

http://www.nvnews.net/vbulletin/forumdisplay.php?f=14
http://www.nvnews.net/vbulletin/showthread.php?t=46678
http://www.nvnews.net/vbulletin/showthread.php?t=58498

The forum is active, but unless you are running the drivers installed from nVidia directly (rather than the packaged livna ones) & you submit the bug report with all the info they require, you may find that you don't get much help.

coffee412 · #13 22nd May 2007, 02:31 AM

Dear Doctor;

Ok, Did some research and this is what I have found out.

According to what Iam finding, The new kernels break something in the nvidia closed source driver for legacy cards - Cant believe my Geforce 6200 turbo is legacy???-- anyways, I found this in my messages on boot up:

May 21 17:00:05 coffee kernel: **WARNING** I2C adapter driver [NVIDIA i2c adapter 0 at 1:00.0] forgot to specify physical device; fix it!
May 21 17:00:05 coffee kernel: **WARNING** I2C adapter driver [NVIDIA i2c adapter 1 at 1:00.0] forgot to specify physical device; fix it!
May 21 17:00:05 coffee kernel: **WARNING** I2C adapter driver [NVIDIA i2c adapter 2 at 1:00.0] forgot to specify physical device; fix it!

Googling for that gave me the opinion above.

Also, I do believe that a rewrite of the I2C handler broke it.

Buy a new card? Hummm... Hate to do that.

coffee

ryptyde · #14 22nd May 2007, 03:30 AM

I have a GeForce 6200 card and do not experience any lockups with the '2948' kernel but then I'm not using the legacy driver.

dr death · #15 22nd May 2007, 07:55 AM

My understanding was that NV30 and earlier were legacy (96xx driver). Your lspci indicates that you have an NV44 (not legacy).

http://www.nvidia.com/object/IO_32667.html

So you shouldn't be using the legacy driver
$ rpm -q kmod-nvidia
should list your driver
$ rpm -q kmod-nvidia-96xx
should list nothing

Now the i2c stuff in the kernel is for the nVidia nForce chipset (nForce2/3/4). You graphics board seems to be an add-on board (PCI slot 01), so it doesn't use the kernel driver for the chipset. The chipset controls the USB, sound, PCI bus, SATA, etc (basically everything in your lspci that starts with 00 and contains nVidia / CK804), but not you graphics board.