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

Newegg Daily Deals

Reply
 
Thread Tools
Old 08-10-06, 09:16 PM   #25
sphincter
Registered User
 
sphincter's Avatar
 
Join Date: Mar 2003
Posts: 154
Default Re: Enabling SLI == hardlock at startx

<sound of crickets>
__________________
It never gets easier, you just go faster. - Greg Lemond
sphincter is offline   Reply With Quote
Old 08-11-06, 06:50 PM   #26
sphincter
Registered User
 
sphincter's Avatar
 
Join Date: Mar 2003
Posts: 154
Default Re: Enabling SLI == hardlock at startx

Lonni,

Do you have any AMD SMP or multi-core systems you can try to reproduce this on?
__________________
It never gets easier, you just go faster. - Greg Lemond
sphincter is offline   Reply With Quote
Old 08-11-06, 06:53 PM   #27
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Enabling SLI == hardlock at startx

sphincter,
The majority of the systems that I have here are AMD SMP systems, and I'm not able to reproduce this problem on any of them. This problem seems to be limited to the motherboard that you're using (or at least isn't present on any that I have here), which I, unfortunately, do not have here.

-Lonni
netllama is offline   Reply With Quote
Old 08-11-06, 10:22 PM   #28
sphincter
Registered User
 
sphincter's Avatar
 
Join Date: Mar 2003
Posts: 154
Default Re: Enabling SLI == hardlock at startx

According to westep, it's also happening on a Gigabyte GA-K8N-SLI. So it's not just my board.
__________________
It never gets easier, you just go faster. - Greg Lemond
sphincter is offline   Reply With Quote
Old 08-11-06, 10:52 PM   #29
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Enabling SLI == hardlock at startx

westep hasn't posted a bug report, so its not at all clear that he's hitting the same issue as you. If he posts a bug report, I'll be happy to look into his issue.
netllama is offline   Reply With Quote
Old 08-19-06, 07:41 PM   #30
sphincter
Registered User
 
sphincter's Avatar
 
Join Date: Mar 2003
Posts: 154
Default Re: Enabling SLI == hardlock at startx

Posting this is probably pointless, but I got the system to boot into X using pci=conf1. That seems to mess with the system a bit, as sometimes my hard disk isn't found at boot. That caused me to think that the option wasn't compatible with my system, but when it fails, I found that a power cycle will get the drive to be recognized. At any rate, the system hard locks exiting ut2004, and I found this in dmesg at boot:

[17185282.236000] irq 58: nobody cared (try booting with the "irqpoll" option)
[17185282.236000] [<c014e31a>] __report_bad_irq+0x2a/0x90
[17185282.236000] [<c014daed>] handle_IRQ_event+0x3d/0x70
[17185282.236000] [<c014e427>] note_interrupt+0x87/0xe0
[17185282.236000] [<c014dc1c>] __do_IRQ+0xfc/0x110
[17185282.236000] [<c0105c69>] do_IRQ+0x19/0x30
[17185282.236000] [<c0103ef6>] common_interrupt+0x1a/0x20
[17185282.236000] [<c012a503>] __do_softirq+0x63/0xe0
[17185282.236000] [<c012a5b5>] do_softirq+0x35/0x40
[17185282.236000] [<c012a695>] irq_exit+0x45/0x50
[17185282.236000] [<c0105c6e>] do_IRQ+0x1e/0x30
[17185282.236000] [<c0103ef6>] common_interrupt+0x1a/0x20
[17185282.236000] [<c0101030>] default_idle+0x0/0x60
[17185282.236000] [<c010105c>] default_idle+0x2c/0x60
[17185282.236000] [<c010111b>] cpu_idle+0x6b/0xb0
[17185282.236000] [<c03aa9ff>] start_kernel+0x19f/0x200
[17185282.236000] [<c03aa370>] unknown_bootoption+0x0/0x1e0
[17185282.236000] handlers:
[17185282.236000] [<f8c2ec90>] (ohci_irq_handler+0x0/0x8c0 [ohci1394])
[17185282.236000] [<f957c467>] (nv_kern_isr+0x0/0x64 [nvidia])
[17185282.236000] Disabling IRQ #58

lspci -v|grep 58 -a1
0000:02:00.0 VGA compatible controller: nVidia Corporation GeForce 7800 GTX (rev a1) (prog-if 00 [VGA])
Flags: bus master, fast devsel, latency 0, IRQ 58
Memory at fa000000 (32-bit, non-prefetchable) [size=16M]


Yes, I'm going to try to replicate with all the extra options stripped from my xorg.conf and see if that makes any difference.
Attached Files
File Type: zip nvidia-bug-report.log.zip (29.4 KB, 121 views)
__________________
It never gets easier, you just go faster. - Greg Lemond
sphincter is offline   Reply With Quote
Old 08-19-06, 08:10 PM   #31
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Enabling SLI == hardlock at startx

If you're seeing "irq 58: nobody cared", then you're likely hitting a BIOS bug. Does booting with irqpoll have any impact?
netllama is offline   Reply With Quote
Old 08-20-06, 12:02 PM   #32
sphincter
Registered User
 
sphincter's Avatar
 
Join Date: Mar 2003
Posts: 154
Default Re: Enabling SLI == hardlock at startx

Quote:
Originally Posted by netllama
If you're seeing "irq 58: nobody cared", then you're likely hitting a BIOS bug. Does booting with irqpoll have any impact?
Yes, there's an effect. The system hard locks when X tries to start. So far, only conf1 will let me get into X reliably, though exiting a 3D app leaves the system hard locked.
__________________
It never gets easier, you just go faster. - Greg Lemond
sphincter is offline   Reply With Quote

Old 08-21-06, 03:43 PM   #33
sphincter
Registered User
 
sphincter's Avatar
 
Join Date: Mar 2003
Posts: 154
Default Re: Enabling SLI == hardlock at startx

It looks like that error is happening when my OpenGL screensaver kicks in, if that means anything.

Also, can anyone tell me why this system would work for the most part under XP, yet have so many problems under linux? Are there that many work arounds in the windows driver? If so, why doesn't nvidia get after it's partners about not shipping such broken BIOSes?
__________________
It never gets easier, you just go faster. - Greg Lemond
sphincter is offline   Reply With Quote
Old 08-22-06, 10:01 AM   #34
sphincter
Registered User
 
sphincter's Avatar
 
Join Date: Mar 2003
Posts: 154
Default Re: Enabling SLI == hardlock at startx

One other thing possibly of interest or not.. from the xorg.0.log.old:


*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x86) [0x80b4a86]
1: [0xffffe420]
2: /usr/bin/X(CreateConnectionBlock+0x4a) [0x806d7a2]
3: /usr/bin/X(main+0x5cf) [0x806e1fb]
4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7d6aea2]
5: /usr/bin/X(FontFileCompleteXLFD+0x81) [0x806d611]

Fatal server error:
Caught signal 11. Server aborting

That's from a boot with both pci=nommconf and noapic on the kernel line.
__________________
It never gets easier, you just go faster. - Greg Lemond
sphincter is offline   Reply With Quote
Old 08-23-06, 10:29 PM   #35
diablo266
Registered User
 
Join Date: Aug 2005
Posts: 3
Default Re: Enabling SLI == hardlock at startx

I am also having the same problem in ubuntu dapper with the 2.6.15-26-k7 kernel and the 87.62 nvidia drivers on an AMD X2 4400+, abit fatal1ty AN8-SLI, 2x 7800gtx when i startx the whole thing just locks up and i have to hard reset.
diablo266 is offline   Reply With Quote
Old 08-24-06, 08:20 AM   #36
sphincter
Registered User
 
sphincter's Avatar
 
Join Date: Mar 2003
Posts: 154
Default Re: Enabling SLI == hardlock at startx

Quote:
Originally Posted by diablo266
I am also having the same problem in ubuntu dapper with the 2.6.15-26-k7 kernel and the 87.62 nvidia drivers on an AMD X2 4400+, abit fatal1ty AN8-SLI, 2x 7800gtx when i startx the whole thing just locks up and i have to hard reset.
Please file a bug report. NVIDIA can't verify that it's the same issue unless you do.
__________________
It never gets easier, you just go faster. - Greg Lemond
sphincter 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
680 GTX SLI + 560 Physx bench for those interested gerardfraser NVIDIA GeForce 600 Series 2 06-20-12 04:34 AM
Nvidia GeForce 301.42 WHQL drivers DSC NVIDIA Windows Graphics Drivers 5 05-29-12 10:12 PM

All times are GMT -5. The time now is 07:59 AM.


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