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

Newegg Daily Deals

Reply
 
Thread Tools
Old 10-16-06, 02:27 AM   #1
PrakashP
gentoo ~x86_64 user
 
PrakashP's Avatar
 
Join Date: Jul 2004
Location: Germania
Posts: 213
Default 1.0-9625/6 don't like 2.6.19-rc* multi-threaded probe

Something about the nvidia driver seems racy, because a lot of time, this happens, if the new PCI multi-threaded probe is activated:

PHP Code:
Oct 16 08:58:48 graviton InitNG: Service system/mountroot is up.
Oct 16 08:58:48 graviton InitNG: Service system/modules/usbcore is up.
Oct 16 08:58:48 graviton InitNG: Service system/modules/nvram is up.
Oct 16 08:58:48 graviton system/modules: Loading module "powernow_k8" ...
Oct 16 08:58:48 graviton system/modules: Loading module "nvidia" ...
Oct 16 08:58:48 graviton system/checkfs: /dev/sda6: clean, 139246/3662848 files, 5308215/7325632 blocks
Oct 16 08
:58:48 graviton system/checkfs:
Oct 16 08:58:48 graviton system/checkfs: /dev/sda1: clean, 45/4016 files, 10870/16032 blocks
Oct 16 08
:58:48 graviton system/checkfs:
Oct 16 08:58:48 graviton InitNG: Service system/checkfs is up.
Oct 16 08:58:48 graviton system/modules: FATAL: Error inserting nvidia (/lib/modules/2.6.19-rc2/video/nvidia.ko): No such device
Oct 16 08
:58:48 graviton system/modules: Loading module "loop" ...
and later (I don't know if related):
PHP Code:
Oct 16 08:58:52 graviton Unable to handle kernel paging request at ffffffff885638f0 RIP:
Oct 16 08:58:52 graviton [<ffffffff803ed8a5>] show_device+0xe5/0x120
Oct 16 08
:58:52 graviton PGD 203027 PUD 205027 PMD 7880e067 PTE 0
Oct 16 08
:58:52 graviton Oops: 0000 [1] PREEMPT SMP
Oct 16 08
:58:52 graviton CPU 1
Oct 16 08
:58:52 graviton Modules linked in: loop powernow_k8
Oct 16 08
:58:52 graviton Pid: 1084, comm: X Tainted: P      2.6.19-rc2 #64
Oct 16 08:58:52 graviton RIP: 0010:[<ffffffff803ed8a5>]  [<ffffffff803ed8a5>] show_device+0xe5/0x120
Oct 16 08
:58:52 graviton RSP: 0018:ffff810079549e68  EFLAGS: 00010282
Oct 16 08
:58:52 graviton RAX: 0000000000000000 RBX: 0000000000000188 RCX: ffff81007879f31e
Oct 16 08
:58:52 graviton RDX: 000000000000031e RSI: 0000000000000009 RDI: ffff81007a26d340
Oct 16 08
:58:52 graviton RBP: ffff81007b616000 R08: ffff810079549c98 R09: 0000000000000005
Oct 16 08
:58:52 graviton R10: fffffffffffffffb R11: 00000000fffffffe R12: ffff81007b6162f8
Oct 16 08
:58:52 graviton R13: ffff81007a26d340 R14: ffffffff885638e0 R15: ffff810077ce6dc0
Oct 16 08
:58:52 graviton FS:  00002b035c5f3b00(0000) GS:ffff810002e7b540(0000) knlGS:0000000000000000
Oct 16 08
:58:52 graviton CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Oct 16 08
:58:52 graviton CR2: ffffffff885638f0 CR3: 00000000796c5000 CR4: 00000000000006e0
Oct 16 08
:58:52 graviton Process X (pid: 1084, threadinfo ffff810079548000, task ffff81007bc58280)
Oct 16 08:58:52 graviton Stack:  0000000000000010 ffffffff803ebab6 ffff81007a26d340 ffff81007b616000
Oct 16 08
:58:52 graviton 0000000000000220 ffff810079549ed0 00000000000002f8 ffffffff80242627
Oct 16 08
:58:52 graviton 0000000000000000 ffff810079549f50 00002b035ca8d108 ffff81007a26d370
Oct 16 08
:58:52 graviton Call Trace:
Oct 16 08:58:52 graviton [<ffffffff803ebab6>] pci_get_subsys+0xe6/0x100
Oct 16 08
:58:52 graviton [<ffffffff80242627>] seq_read+0x1e7/0x2c0
Oct 16 08
:58:52 graviton [<ffffffff8020b22a>] vfs_read+0xba/0x180
Oct 16 08
:58:52 graviton [<ffffffff80211683>] sys_read+0x53/0x90
Oct 16 08
:58:52 graviton [<ffffffff8026611e>] system_call+0x7e/0x83
Oct 16 08
:58:52 graviton
Oct 16 08
:58:52 graviton
Oct 16 08
:58:52 graviton Code: 49 8b 56 10 48 c7 c6 ec 9c 60 80 4c 89 ef 31 c0 e8 e6 e1 e6
Oct 16 08
:58:52 graviton RIP  [<ffffffff803ed8a5>] show_device+0xe5/0x120
Oct 16 08
:58:52 graviton RSP <ffff810079549e68>
Oct 16 08:58:52 graviton CR2: ffffffff885638f0
Oct 16 08
:58:52 graviton kdm: :0[1311]: IO Error in XOpenDisplay
Oct 16 08
:58:52 graviton kdm[946]: Display :0 cannot be opened
Oct 16 08
:58:52 graviton kdm[946]: Unable to fire up local display :0; disabling.
I have to reboot and hope that next time it works. So I disabled the pci mt probing and this seems to help.
Attached Files
File Type: bz2 nvidia-bug-report.log.bz2 (28.3 KB, 95 views)
PrakashP is offline   Reply With Quote
Old 10-16-06, 11:45 AM   #2
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: 1.0-9625/6 don't like 2.6.19-rc* multi-threaded probe

Everything that you've posted points to a kernel or BIOS bug, as the PCI bus isn't being probed or enumerated properly at boot time. I'm afraid that this isn't an nvidia driver bug.

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 10-30-06, 12:29 PM   #3
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-9625/6 don't like 2.6.19-rc* multi-threaded probe

@PrakashP: thanks for your report; at this point, PCI_MULTITHREAD_PROBE is still considered highly experimental and is known to have bugs and/or break other subsystems, but we'll keep an eye on it and make sure that as the feature matures, the NVIDIA Linux graphics driver interacts with it correctly.
zander is offline   Reply With Quote
Old 10-30-06, 12:43 PM   #4
PrakashP
gentoo ~x86_64 user
 
PrakashP's Avatar
 
Join Date: Jul 2004
Location: Germania
Posts: 213
Default Re: 1.0-9625/6 don't like 2.6.19-rc* multi-threaded probe

Yes, I noticed it following lkml, that there is high fall-out and some devs want to make it depend on "broken"... So sorry for the noise.
PrakashP 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 02:54 AM.


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