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

Newegg Daily Deals

Reply
 
Thread Tools
Old 05-10-07, 06:25 PM   #1
ppwaskie
Registered User
 
Join Date: May 2007
Posts: 7
Default Kernel oops on x86_64 FC6 with 1.0-9755

I'm currently running a Quadro FX 3500 on a 2.6.20-1.2948.fc6 #1 SMP x86_64 machine. It's throwing an Oops every time I try to start X.

The machine does not hard lock, but the console is toast after I run startx or allow runlevel 5 to run. This does *not* happen with the Xorg nv driver, only when I use the accelerated driver. I tried running nvidia-bug-report.sh, and it hangs on "cat /proc/driver/nvidia/cards/0," so I cannot get a full report. I'm trying to post as much information here as I can see from the bug report script; please let me know what else you want, or any other course of action to assist on this issue. I've looked at all the stability forums, checked the stuff on installing on FC6, etc. I also do not have issues installing or loading the driver, it's just when it gets opened by X that things blow up.

Any help or guidance is much appreciated.

This is my Xorg server info:

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.9-42.0.8.ELsmp x86_64 Red Hat, Inc.
Current Operating System: Linux phi 2.6.20-1.2948.fc6 #1 SMP Fri Apr 27 19:18:54 EDT 2007 x86_64
Build Date: 08 April 2007
Build ID: xorg-x11-server 1.1.1-47.8.fc6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

This is my listing from lspci:

00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub (rev 12)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev 12)
00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 12)
00:04.0 PCI bridge: Intel Corporation 5000X Chipset PCI Express x16 Port 4-7 (rev 12)
00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev 12)
00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 (rev 12)
00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev 12)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 12)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 12)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 12)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12)
00:1b.0 Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller (rev 09)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.3 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
00:1f.2 RAID bus controller: Intel Corporation 631xESB/632xESB SATA Storage Controller RAID (rev 09)
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
02:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01)
05:05.0 Ethernet controller: Intel Corporation 82543GC Gigabit Ethernet Controller (Copper) (rev 02)
07:00.0 VGA compatible controller: nVidia Corporation Quadro FX 3500 (rev a1)
0b:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
0c:02.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 61)


And this is the end of my Xorg.0.log:

(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 16, (--) framebuffer bpp 16
(==) NVIDIA(0): RGB weight 565
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(==) NVIDIA(0): Using HW cursor
(**) NVIDIA(0): Enabling RENDER acceleration
(==) NVIDIA(0): Video key set to default value of 0x83e
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.


Here is the Oops from dmesg:

Unable to handle kernel paging request at ffffc2004133054c RIP:
[<ffffffff88248a54>] :nvidia:_nv003297rm+0x60/0x74
PGD 33b4067 PUD 0
Oops: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:00.0/irq
CPU 1
Modules linked in: ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nfnetlink ip_tables x_tables autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6 dm_multipath video sbs i2c_ec dock button battery asus_acpi backlight ac lp snd_hda_intel snd_hda_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss floppy snd_pcm sg nvidia(P)(U) ata_piix snd_timer snd parport_pc i2c_i801 ohci1394 pcspkr soundcore tg3 snd_page_alloc e1000 shpchp parport ieee1394 i2c_core ide_cd serio_raw cdrom dm_snapshot dm_zero dm_mirror dm_mod ahci libata sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd
Pid: 3661, comm: X Tainted: P 2.6.20-1.2948.fc6 #1
RIP: 0010:[<ffffffff88248a54>] [<ffffffff88248a54>] :nvidia:_nv003297rm+0x60/0x74
RSP: 0018:ffff81006d0b1af8 EFLAGS: 00010206
RAX: 000000001002c153 RBX: ffff81006cf9e000 RCX: 0000000000000001
RDX: ffffc20001280000 RSI: 0000000000000031 RDI: ffff81006cf9e028
RBP: 00000000400b054c R08: ffff81007e051000 R09: 00000000fffffffe
R10: 0000000000000000 R11: 0000000000000001 R12: 00000000000b0440
R13: ffff81006cf9e000 R14: 000000000000b040 R15: 0000000000000014
FS: 00002aaaaaadba80(0000) GS:ffff810037e12ac0(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffc2004133054c CR3: 0000000037df8000 CR4: 00000000000006e0
Process X (pid: 3661, threadinfo ffff81006d0b0000, task ffff81007d45b0c0)
Stack: 00000000fffffffc ffff81007b019400 0000000040000148 ffffffff8849ee61
ffff810079f1e000 ffffffff883c0c42 0000025000020014 ffff81006d0b1ba0
0000000100020000 00000000fffffffc 0000000000020000 0000000000000000
Call Trace:
[<ffffffff8849ee61>] :nvidia:_nv005324rm+0x1d/0x24
[<ffffffff883c0c42>] :nvidia:_nv008512rm+0x142/0x164
[<ffffffff883c0c82>] :nvidia:_nv008513rm+0x1e/0x24
[<ffffffff8849e284>] :nvidia:_nv005338rm+0x34a/0x3f4
[<ffffffff88417be1>] :nvidia:_nv007922rm+0x5d/0x6c
[<ffffffff883f2b26>] :nvidia:_nv008528rm+0x568/0x608
[<ffffffff883c1c49>] :nvidia:_nv005462rm+0xbd/0x184
[<ffffffff883c2ff6>] :nvidia:_nv008335rm+0x72/0x156
[<ffffffff88503b06>] :nvidia:_nv001598rm+0x114/0x132
[<ffffffff8843065b>] :nvidia:_nv007265rm+0x7d/0x208
[<ffffffff88430339>] :nvidia:_nv006986rm+0x5b/0x74
[<ffffffff8821f886>] :nvidia:_nv007159rm+0xa/0x10
[<ffffffff88249fc7>] :nvidia:_nv002564rm+0xfb/0x198
[<ffffffff88253300>] :nvidia:_nv000014rm+0x0/0x1c
[<ffffffff8824aa65>] :nvidia:_nv002570rm+0x267/0x3a8
[<ffffffff8824f755>] :nvidia:rm_init_adapter+0x63/0x94
[<ffffffff8855402f>] :nvidia:nv_kern_open+0x256/0x329
[<ffffffff802465a9>] chrdev_open+0x149/0x198
[<ffffffff80246460>] chrdev_open+0x0/0x198
[<ffffffff8021e3be>] __dentry_open+0xd9/0x1aa
[<ffffffff802273ad>] do_filp_open+0x2a/0x38
[<ffffffff80250e6f>] sys_chown+0x45/0x56
[<ffffffff80215a2a>] get_unused_fd+0xf9/0x107
[<ffffffff802196db>] do_sys_open+0x44/0xc1
[<ffffffff8025a11e>] system_call+0x7e/0x83


Code: 8b 2c 82 89 e8 48 8b 5c 24 08 48 8b 6c 24 10 48 83 c4 18 c3
RIP [<ffffffff88248a54>] :nvidia:_nv003297rm+0x60/0x74
RSP <ffff81006d0b1af8>
CR2: ffffc2004133054c
<3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20
in_atomic():0, irqs_disabled():1

Call Trace:
[<ffffffff80299d93>] down_read+0x15/0x23
[<ffffffff802a6050>] acct_collect+0x42/0x18e
[<ffffffff802151ea>] do_exit+0x20b/0x832
[<ffffffff80262db8>] do_page_fault+0x74f/0x7ca
[<ffffffff802bde42>] zone_statistics+0x3f/0x60
[<ffffffff80260eed>] error_exit+0x0/0x84
[<ffffffff88248a54>] :nvidia:_nv003297rm+0x60/0x74
[<ffffffff88248a10>] :nvidia:_nv003297rm+0x1c/0x74
[<ffffffff8849ee61>] :nvidia:_nv005324rm+0x1d/0x24
[<ffffffff883c0c42>] :nvidia:_nv008512rm+0x142/0x164
[<ffffffff883c0c82>] :nvidia:_nv008513rm+0x1e/0x24
[<ffffffff8849e284>] :nvidia:_nv005338rm+0x34a/0x3f4
[<ffffffff88417be1>] :nvidia:_nv007922rm+0x5d/0x6c
[<ffffffff883f2b26>] :nvidia:_nv008528rm+0x568/0x608
[<ffffffff883c1c49>] :nvidia:_nv005462rm+0xbd/0x184
[<ffffffff883c2ff6>] :nvidia:_nv008335rm+0x72/0x156
[<ffffffff88503b06>] :nvidia:_nv001598rm+0x114/0x132
[<ffffffff8843065b>] :nvidia:_nv007265rm+0x7d/0x208
[<ffffffff88430339>] :nvidia:_nv006986rm+0x5b/0x74
[<ffffffff8821f886>] :nvidia:_nv007159rm+0xa/0x10
[<ffffffff88249fc7>] :nvidia:_nv002564rm+0xfb/0x198
[<ffffffff88253300>] :nvidia:_nv000014rm+0x0/0x1c
[<ffffffff8824aa65>] :nvidia:_nv002570rm+0x267/0x3a8
[<ffffffff8824f755>] :nvidia:rm_init_adapter+0x63/0x94
[<ffffffff8855402f>] :nvidia:nv_kern_open+0x256/0x329
[<ffffffff802465a9>] chrdev_open+0x149/0x198
[<ffffffff80246460>] chrdev_open+0x0/0x198
[<ffffffff8021e3be>] __dentry_open+0xd9/0x1aa
[<ffffffff802273ad>] do_filp_open+0x2a/0x38
[<ffffffff80250e6f>] sys_chown+0x45/0x56
[<ffffffff80215a2a>] get_unused_fd+0xf9/0x107
[<ffffffff802196db>] do_sys_open+0x44/0xc1
[<ffffffff8025a11e>] system_call+0x7e/0x83
ppwaskie is offline   Reply With Quote
Old 05-10-07, 06:30 PM   #2
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

Have you verified that you're using the latest motherboard BIOS?
Does this problem reproduce with the 100.14.03 beta driver?
netllama is offline   Reply With Quote
Old 05-10-07, 06:39 PM   #3
ppwaskie
Registered User
 
Join Date: May 2007
Posts: 7
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

I do have the latest mb BIOS, however I haven't tried the beta driver.

One thing to note is I did have OpenSUSE 10.2 (32-bit, not x86_64) running with the accelerated driver with no issues before.

I will try the beta driver and let you know.

Thanks,

-PJ
ppwaskie is offline   Reply With Quote
Old 05-10-07, 06:47 PM   #4
ppwaskie
Registered User
 
Join Date: May 2007
Posts: 7
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

Same result:

NVRM: loading NVIDIA UNIX x86_64 Kernel Module 100.14.03 Wed Apr 4 23:18:53 PDT 2007
PCI: Setting latency timer of device 0000:07:00.0 to 64
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 100.14.03 Wed Apr 4 23:18:53 PDT 2007
Unable to handle kernel paging request at ffffc2004133054c RIP:
[<ffffffff88bc1db9>] :nvidia:_nv003465rm+0x5d/0x6c
PGD 33b4067 PUD 0
Oops: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:05.0/irq
CPU 1
Modules linked in: nvidia(P)(U) ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nfnetlink ip_tables x_tables autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6 dm_multipath video sbs i2c_ec dock button battery asus_acpi backlight ac lp snd_hda_intel snd_hda_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device floppy snd_pcm_oss snd_mixer_oss snd_pcm sg ata_piix pcspkr snd_timer ohci1394 i2c_i801 snd ieee1394 e1000 soundcore snd_page_alloc tg3 i2c_core shpchp parport_pc parport ide_cd serio_raw cdrom dm_snapshot dm_zero dm_mirror dm_mod ahci libata sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd

...

Code: 44 8b 24 82 44 89 e0 48 83 c5 08 5b 41 5c c3 48 83 ed 08 be
RIP [<ffffffff88bc1db9>] :nvidia:_nv003465rm+0x5d/0x6c
RSP <ffff810067eafbd8>
CR2: ffffc2004133054c
<3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20
in_atomic():0, irqs_disabled():1


Any help or suggestions on what you need would be appreciated.
ppwaskie is offline   Reply With Quote
Old 05-10-07, 06:49 PM   #5
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

Please generate and attach an nvidia-bug-report.log
netllama is offline   Reply With Quote
Old 05-10-07, 06:58 PM   #6
ppwaskie
Registered User
 
Join Date: May 2007
Posts: 7
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

I tried to generate a bug report, but once the driver panics (after I try loading X), the nvidia-bug-report.sh script hangs on "cat /proc/driver/nvidia/cards/0". Should I comment those probes out and try running it again?
ppwaskie is offline   Reply With Quote
Old 05-10-07, 07:09 PM   #7
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

Or run it after rebooting
netllama is offline   Reply With Quote
Old 05-11-07, 06:16 PM   #8
ppwaskie
Registered User
 
Join Date: May 2007
Posts: 7
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

The driver was loaded on boot, but not accessed via X. The bug report is attached to the post. Thank you for the help.

Cheers,
-PJ
Attached Files
File Type: log nvidia-bug-report.log (131.4 KB, 85 views)
ppwaskie is offline   Reply With Quote

Old 05-11-07, 07:10 PM   #9
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

I'll see if I can reproduce this, but it might be a few days.
netllama is offline   Reply With Quote
Old 05-14-07, 03:38 PM   #10
ppwaskie
Registered User
 
Join Date: May 2007
Posts: 7
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

Thanks netllama, I appreciate the assistance. Anything I can provide outside of the bug report to help this along can be provided; please just let me know what I can do.

Thanks,
-PJ
ppwaskie is offline   Reply With Quote
Old 05-15-07, 07:11 PM   #11
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

I was not able to reproduce this on our Dell Precision 490 workstation. I tested with both the 1.0-9755 and 100.14.03 drivers. This system has the latest A04 BIOS installed. X started without any problems.
netllama is offline   Reply With Quote
Old 05-16-07, 05:44 PM   #12
ppwaskie
Registered User
 
Join Date: May 2007
Posts: 7
Default Re: Kernel oops on x86_64 FC6 with 1.0-9755

Is there anything else I can try? Was the call trace from the oops helpful? Like I said, the card starts fine with the nv driver, and worked fine with a 32-bit version of OpenSUSE 10.2 on it. I'm kinda at a loss here; anything you can suggest would be very helpful.

Thanks,

-PJ
ppwaskie 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
Random crashes, NVRM Xid messages Iesos NVIDIA Linux 90 10-04-12 03:27 AM
Corrupted display - 302.17 - Dell Precision T3500 (G98 [Quadro NVS 295]) gbailey NVIDIA Linux 1 06-27-12 10:24 AM
UEFI+Nvidia - NVRM: Your system is not currently configured to drive a VGA console... interzoneuk NVIDIA Linux 0 06-26-12 04:51 AM
xorg locks-up with newest nvidia drivers w/ vdpau. theroot NVIDIA Linux 1 06-24-12 11:04 AM
Crash when logout from X TGL NVIDIA Linux 10 09-13-02 08:22 PM

All times are GMT -5. The time now is 01:23 PM.


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