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

Newegg Daily Deals

Reply
 
Thread Tools
Old 11-07-03, 06:45 AM   #1
spity
Registered User
 
Join Date: Nov 2003
Posts: 1
Default FX5200 + kernel badness in Q3A

Hi,

Recently i bought Inno3d geforce fx5200 w/ passive heatsink,
because my old card(gf2 gts) died. now when i try to run Q3A my computer
hardfreezes after something in between 5 to 10 minutes. Only reset works.
I've tried touching the card, and it's been _very_ hot (i couldn't hold my
hand on it). I hope that it's just some random problem w/ software, as I
guess that they won't sell hw that overheats in normal conditions.My
configuration isn't especially stable but I don't know what It might be
causing. Linux kernel is 2.6.0-test9, glibc (from debian unstable) with NPTL,
and XFree86-4.3.0 from debian experiemtal. I'm attaching a badness report.

Videocard: Inno3D GeForce FX5200
Drivers: 1.0-4496
Distro: Debian unstable
VBios: 04.34.20.27.06
CPU: AMD Athlon XP 1600+
Mobo: ASUS A7V333


Here is badness reported by kernel:
Nov 2 22:14:08 noodles kernel: Losing too many ticks!
Nov 2 22:14:08 noodles kernel: TSC cannot be used as a timesource. (Are you running with SpeedStep?)
Nov 2 22:14:08 noodles kernel: Falling back to a sane timesource.
Nov 2 22:14:08 noodles kernel: Badness in pci_find_subsys at drivers/pci/search.c:132
Nov 2 22:14:08 noodles kernel: Call Trace:
Nov 2 22:14:08 noodles kernel: [<c01be4f8>] pci_find_subsys+0xe8/0xf0
Nov 2 22:14:08 noodles kernel: [<c01be52f>] pci_find_device+0x2f/0x40
Nov 2 22:14:08 noodles kernel: [<c01be3e8>] pci_find_slot+0x28/0x50
Nov 2 22:14:08 noodles kernel: [<e0de0f89>] os_pci_init_handle+0x39/0x70 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cb62af>] __nvsym00057+0x1f/0x24 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0dc6808>] __nvsym04875+0xf8/0x170 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d492ed>] __nvsym03749+0x41/0xbc [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0dc65da>] __nvsym00780+0x21a/0x224 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d49c94>] __nvsym03741+0x74/0x88 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d48c5a>] __nvsym03751+0x5a2/0x8a4 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cd0df5>] __nvsym00805+0x11/0x228 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d8d233>] __nvsym00688+0x1e3/0x338 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cb89b9>] __nvsym00827+0xd/0x1c [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cba054>] rm_isr_bh+0xc/0x10 [nvidia]
Nov 2 22:14:08 noodles kernel: [<c0122636>] tasklet_action+0x46/0x70
Nov 2 22:14:08 noodles kernel: [<c0122450>] do_softirq+0x90/0xa0
Nov 2 22:14:08 noodles kernel: [<c010b7ed>] do_IRQ+0xfd/0x130
Nov 2 22:14:08 noodles kernel: [<c0109b48>] common_interrupt+0x18/0x20
Nov 2 22:14:08 noodles kernel: [<c01147bb>] get_offset_pit+0x6b/0x100
Nov 2 22:14:08 noodles kernel: [<c010f11a>] do_gettimeofday+0x1a/0xa0
Nov 2 22:14:08 noodles kernel: [<c0121b07>] sys_gettimeofday+0x27/0xb0
Nov 2 22:14:08 noodles kernel: [<c01091db>] syscall_call+0x7/0xb
Nov 2 22:14:08 noodles kernel:
Nov 2 22:14:08 noodles kernel: Badness in pci_find_subsys at drivers/pci/search.c:132
Nov 2 22:14:08 noodles kernel: Call Trace:
Nov 2 22:14:08 noodles kernel: [<c01be4f8>] pci_find_subsys+0xe8/0xf0
Nov 2 22:14:08 noodles kernel: [<c01be52f>] pci_find_device+0x2f/0x40
Nov 2 22:14:08 noodles kernel: [<c01be3e8>] pci_find_slot+0x28/0x50
Nov 2 22:14:08 noodles kernel: [<e0de0f89>] os_pci_init_handle+0x39/0x70 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cb62af>] __nvsym00057+0x1f/0x24 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d4a8e2>] __nvsym03763+0x72/0xe0 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d8f3f1>] __nvsym04466+0x15/0x78 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0dc6837>] __nvsym04875+0x127/0x170 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d492ed>] __nvsym03749+0x41/0xbc [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0dc65da>] __nvsym00780+0x21a/0x224 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d49c94>] __nvsym03741+0x74/0x88 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d48c5a>] __nvsym03751+0x5a2/0x8a4 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cd0df5>] __nvsym00805+0x11/0x228 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d8d233>] __nvsym00688+0x1e3/0x338 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cb89b9>] __nvsym00827+0xd/0x1c [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cba054>] rm_isr_bh+0xc/0x10 [nvidia]
Nov 2 22:14:08 noodles kernel: [<c0122636>] tasklet_action+0x46/0x70
Nov 2 22:14:08 noodles kernel: [<c0122450>] do_softirq+0x90/0xa0
Nov 2 22:14:08 noodles kernel: [<c010b7ed>] do_IRQ+0xfd/0x130
Nov 2 22:14:08 noodles kernel: [<c0109b48>] common_interrupt+0x18/0x20
Nov 2 22:14:08 noodles kernel: [<c01147bb>] get_offset_pit+0x6b/0x100
Nov 2 22:14:08 noodles kernel: [<c010f11a>] do_gettimeofday+0x1a/0xa0
Nov 2 22:14:08 noodles kernel: [<c0121b07>] sys_gettimeofday+0x27/0xb0
Nov 2 22:14:08 noodles kernel: [<c01091db>] syscall_call+0x7/0xb
Nov 2 22:14:08 noodles kernel:
Nov 2 22:14:08 noodles kernel: Badness in pci_find_subsys at drivers/pci/search.c:132
Nov 2 22:14:08 noodles kernel: Call Trace:
Nov 2 22:14:08 noodles kernel: [<c01be4f8>] pci_find_subsys+0xe8/0xf0
Nov 2 22:14:08 noodles kernel: [<c01be52f>] pci_find_device+0x2f/0x40
Nov 2 22:14:08 noodles kernel: [<c01be3e8>] pci_find_slot+0x28/0x50
Nov 2 22:14:08 noodles kernel: [<e0de0f89>] os_pci_init_handle+0x39/0x70 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cb62af>] __nvsym00057+0x1f/0x24 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0dc6808>] __nvsym04875+0xf8/0x170 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d492ed>] __nvsym03749+0x41/0xbc [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0dc65da>] __nvsym00780+0x21a/0x224 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d49c94>] __nvsym03741+0x74/0x88 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d48daf>] __nvsym03751+0x6f7/0x8a4 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d8d233>] __nvsym00688+0x1e3/0x338 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cb89b9>] __nvsym00827+0xd/0x1c [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cba054>] rm_isr_bh+0xc/0x10 [nvidia]
Nov 2 22:14:08 noodles kernel: [<c0122636>] tasklet_action+0x46/0x70
Nov 2 22:14:08 noodles kernel: [<c0122450>] do_softirq+0x90/0xa0
Nov 2 22:14:08 noodles kernel: [<c010b7ed>] do_IRQ+0xfd/0x130
Nov 2 22:14:08 noodles kernel: [<c0109b48>] common_interrupt+0x18/0x20
Nov 2 22:14:08 noodles kernel: [<c01147bb>] get_offset_pit+0x6b/0x100
Nov 2 22:14:08 noodles kernel: [<c010f11a>] do_gettimeofday+0x1a/0xa0
Nov 2 22:14:08 noodles kernel: [<c0121b07>] sys_gettimeofday+0x27/0xb0
Nov 2 22:14:08 noodles kernel: [<c01091db>] syscall_call+0x7/0xb
Nov 2 22:14:08 noodles kernel:
Nov 2 22:14:08 noodles kernel: Badness in pci_find_subsys at drivers/pci/search.c:132
Nov 2 22:14:08 noodles kernel: Call Trace:
Nov 2 22:14:08 noodles kernel: [<c01be4f8>] pci_find_subsys+0xe8/0xf0
Nov 2 22:14:08 noodles kernel: [<c01be52f>] pci_find_device+0x2f/0x40
Nov 2 22:14:08 noodles kernel: [<c01be3e8>] pci_find_slot+0x28/0x50
Nov 2 22:14:08 noodles kernel: [<e0de0f89>] os_pci_init_handle+0x39/0x70 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cb62af>] __nvsym00057+0x1f/0x24 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d4a8e2>] __nvsym03763+0x72/0xe0 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d8f3f1>] __nvsym04466+0x15/0x78 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0dc6837>] __nvsym04875+0x127/0x170 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d492ed>] __nvsym03749+0x41/0xbc [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0dc65da>] __nvsym00780+0x21a/0x224 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d49c94>] __nvsym03741+0x74/0x88 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d48daf>] __nvsym03751+0x6f7/0x8a4 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0d8d233>] __nvsym00688+0x1e3/0x338 [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cb89b9>] __nvsym00827+0xd/0x1c [nvidia]
Nov 2 22:14:08 noodles kernel: [<e0cba054>] rm_isr_bh+0xc/0x10 [nvidia]
Nov 2 22:14:08 noodles kernel: [<c0122636>] tasklet_action+0x46/0x70
Nov 2 22:14:08 noodles kernel: [<c0122450>] do_softirq+0x90/0xa0
Nov 2 22:14:08 noodles kernel: [<c010b7ed>] do_IRQ+0xfd/0x130
Nov 2 22:14:08 noodles kernel: [<c0109b48>] common_interrupt+0x18/0x20
Nov 2 22:14:08 noodles kernel: [<c01147bb>] get_offset_pit+0x6b/0x100
Nov 2 22:14:08 noodles kernel: [<c010f11a>] do_gettimeofday+0x1a/0xa0
Nov 2 22:14:08 noodles kernel: [<c0121b07>] sys_gettimeofday+0x27/0xb0
Nov 2 22:14:08 noodles kernel: [<c01091db>] syscall_call+0x7/0xb
Nov 2 22:14:08 noodles kernel:

Last edited by spity; 11-07-03 at 06:50 AM.
spity is offline   Reply With Quote
Old 11-07-03, 11:21 PM   #2
ReKleSS
Registered User
 
Join Date: Dec 2002
Location: Australia (somewhere)
Posts: 16
Send a message via ICQ to ReKleSS
Default

hrm... I've got a GF FX 5200 Magic by Asus, very similar problem... my conclusion is that the heatsink sucks. Get a thermaltake blue orb (www.thermaltake.com) or something, and install that... that seems to have fixed it. That stuff in dmesg seems normal (because the driver wasn't designed for 2.6... when nvidia makes real 2.6 drivers it should go away)
-ReK
ReKleSS is offline   Reply With Quote
Old 11-08-03, 01:46 PM   #3
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default

You shouldn't be seeing these messages unless the system has data integrity problems, they typically indicate that something bad has happened.
zander is offline   Reply With Quote
Old 12-21-03, 09:48 PM   #4
Blu3
Registered User
 
Join Date: Jan 2003
Location: Meriden, CT
Posts: 6
Send a message via AIM to Blu3
Default

Quote:
Originally posted by zander
You shouldn't be seeing these messages unless the system has data integrity problems, they typically indicate that something bad has happened.
quoting an email from an LKML developer(http://www.ussg.iu.edu/hypermail/lin...07.3/0258.html):

Quote:
The 'badness in pci_find_subsys' may not be related to your hang.

The NVidia msgs are basically caused by the fact that pci_find_slot() is
getting called in an interrupt, so we trigger the WARN_ON in pci_find_subsys().
The worry here is that we may be walking the PCI list on the interrupt side
while something else is hotplugging a new device into existence, causing it to
walk off the end of a inconsistent list. Unless you actually crapped out right
at 13:08:23, it's probably unrelated.

(I was getting the same NVidia traceback on a regular basis (3-4 at every start
of the X server, and 1 at X server shutdown) under 2.5.72-mm3, they stopped
when I went to 2.5.73-mm1. If you're still seeing them in 2.6.0-test1, I would
suspect something different in the -mm series is fixing them for me - first place
to look is what got added between 72-mm3 and 73-mm1.
For what it's worth, I still get this pci badness in 2.6.0. I'd think that NV would want to clean things up.
Blu3 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 09:23 PM.


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