nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   AMD64/2.6 Kernel Questions (http://www.nvnews.net/vbulletin/showthread.php?t=24743)

tamran 02-10-04 08:14 PM

AMD64/2.6 Kernel Questions
 
1 Attachment(s)
To whom it may concern,

First, a little about my hardware and config.

Dual Opteron, MSI Master2-far motherboard. Latest bios (1.1) - 1 GIG of RAM (I ram memtest for 12 hours so there is no problem with the ram)
NVIDIA Geforce4 TI 4800SE video card (64mb of ram)
APIC is enabled (tried disabled, that is yucky)
ACPI is disabled completely
Kernel: 2.6.2

I'm not going to waste a bunch of space with error outputs, however you can see similar posts all over these forums if you search for the keyword "lockups". Although, for the heck of it, I've attached my XF86Config-4 file and lspci output (pasted at the bottom).

I have read through many posts and I have the following questions.

1. If IOMMU support is disabled, and agpgart is NOT loaded there is still no support for using the NvAGP "1" setting. I found this to be much more stable on my x86 system. Now on my dual opteron system, using agpgart, I get random lockups like many others I've seen in these forums. Will this option ever be available for the amd64 driver? This is important for amd64, as the 2.4 kernels are essentially depreciated for that architecture.

2. It seems the official stance is that 2.6 kernels are not supported yet. When will this driver be "officially supported"? I realize it's hard to give an exact date, but an answer in the form of "we expect to officially support the 2.6 kernels within XX-YY weeks time" would suffice.

3. 32bit GL apps are not currently supported, and don't work with the amd64 driver, but I could not get an official answer if this is in the works. When is this scheduled to be completed?

4. I really do not want to turn off APIC support, as that just made life exhaustingly slow. Are these drivers not known to play nice with APIC? Is it in the plans to have this type of support in the near future? I realize it's working well for most, but I just thought I'd officially ask the question.

I'd like to end by saying Kudos to the nvidia team for their support so far. NVIDIA is the only card that even remotely works well on AMD64 Linux platforms from what I can tell. Other than the occasional lockup (usually once a night if I'm unlucky) I'm very happy with the product and support.

Regards,

Tamran

lspci output:
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3188 (rev 01)
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device b188
00:08.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 07)
00:0b.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit Ethe
rnet (rev 03)
00:0f.0 RAID bus controller: VIA Technologies, Inc.: Unknown device 3149 (rev 80
)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/
C/VT8235 PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3227
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
01:00.0 VGA compatible controller: nVidia Corporation NV28 [GeForce4 Ti 4800 SE]
(rev a1)

tamran 02-10-04 08:17 PM

Oh, before someone asks or suggests, I've tried the NvAGP "0" option and it seems to stop the lockups ... however this is crappy and slow. So, I don't particularly see this as a "acceptable" option.

Regards,

Tamran

whig 02-10-04 10:30 PM

There was a bit of trouble with some nvidia drivers on Via motherboards, at least on this 32 bit Debian setup. I haven't had the same worries with the 64 bit drivers (Suse, Mandrake.) This Via thing was meant to be fixed, and I have only minor complaints with 5336. I should get around to moving from 2.6.1 to 2.6.2 on Mandrake 64 sometime. As you can see my setup is somewhat like yours, but mine is stable across these distros.

00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3188 (rev 01)
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device b188
00:0c.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
00:0c.1 Input device controller: Creative Labs SB Live! (rev 0a)
00:0f.0 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. UHCI USB (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. UHCI USB (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc.: Unknown device 3104 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3227
00:11.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio Controller (rev 60)
00:12.0 Ethernet controller: VIA Technologies, Inc. Ethernet Controller (rev 78)
00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd.: Unknown device 8169 (rev 10)
00:14.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8025 (rev 01)
00:18.0 Host bridge: Advanced Micro Devices [AMD]: Unknown device 1100
00:18.1 Host bridge: Advanced Micro Devices [AMD]: Unknown device 1101
00:18.2 Host bridge: Advanced Micro Devices [AMD]: Unknown device 1102
00:18.3 Host bridge: Advanced Micro Devices [AMD]: Unknown device 1103
01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0331 (rev a1)

tamran 02-11-04 06:00 PM

Another Crash, but have good output
 
Here is my latest crash. I have output from my /var/log/messages file:

Feb 11 11:50:18 gen2 Badness in pci_find_subsys at drivers/pci/search.c:132
Feb 11 11:50:18 gen2
Feb 11 11:50:18 gen2 Call Trace:<IRQ> <ffffffff80211a73>{pci_find_subsys+83} <ffffffff80211a00>{pci_find_slot+48}
Feb 11 11:50:18 gen2 <ffffffffa0144528>{:nvidia:os_pci_init_handle+40 } <ffffffffa016002e>{:nvidia:_nv000904rm+24}
Feb 11 11:50:18 gen2 <ffffffffa02b5dfb>{:nvidia:_nv000711rm+897} <ffffffff802ed2e3>{eth_header+227}
Feb 11 11:50:18 gen2 <ffffffffa018c3ac>{:nvidia:_nv004131rm+92} <ffffffffa0235f67>{:nvidia:_nv001272rm+51}
Feb 11 11:50:18 gen2 <ffffffffa02350dc>{:nvidia:_nv001217rm+28} <ffffffffa02b584a>{:nvidia:_nv000704rm+46}
Feb 11 11:50:18 gen2 <ffffffffa02471fa>{:nvidia:_nv002797rm+428} <ffffffff8032978e>{fn_hash_lookup+190}
Feb 11 11:50:18 gen2 <ffffffffa017e112>{:nvidia:_nv004381rm+114} <ffffffffa0236053>{:nvidia:_nv001271rm+123}
Feb 11 11:50:18 gen2 <ffffffffa0154d29>{:nvidia:_nv000996rm+39} <ffffffffa01662a6>{:nvidia:_nv005021rm+100}
Feb 11 11:50:18 gen2 <ffffffffa0246d24>{:nvidia:_nv002756rm+2352} <ffffffffa0234cd4>{:nvidia:_nv001214rm+112}
Feb 11 11:50:18 gen2 <ffffffffa017adf8>{:nvidia:_nv004375rm+268} <ffffffffa01617a6>{:nvidia:_nv000884rm+16}
Feb 11 11:50:18 gen2 <ffffffffa0283ce0>{:nvidia:_nv001134rm+536} <ffffffffa016311e>{:nvidia:_nv005317rm+112}
Feb 11 11:50:18 gen2 <ffffffffa0164abd>{:nvidia:rm_isr_bh+9} <ffffffff8013c81f>{tasklet_action+111}
Feb 11 11:50:18 gen2 <ffffffff8013c4fb>{do_softirq+123} <ffffffff8011384f>{do_IRQ+463}
Feb 11 11:50:18 gen2 <ffffffff80110f8d>{ret_from_intr+0} <EOI> <ffffffff80110a14>{system_call+124}
Feb 11 11:50:18 gen2
Feb 11 11:50:18 gen2 Badness in pci_find_subsys at drivers/pci/search.c:132
Feb 11 11:50:18 gen2
Feb 11 11:50:18 gen2 Call Trace:<IRQ> <ffffffff80211a73>{pci_find_subsys+83} <ffffffff80211a00>{pci_find_slot+48}
Feb 11 11:50:18 gen2 <ffffffffa0144528>{:nvidia:os_pci_init_handle+40 } <ffffffffa016002e>{:nvidia:_nv000904rm+24}
Feb 11 11:50:18 gen2 <ffffffffa0219844>{:nvidia:_nv002969rm+178} <ffffffff80211b45>{pci_find_subsys+293}
Feb 11 11:50:18 gen2 <ffffffffa0287b8f>{:nvidia:_nv001148rm+121} <ffffffffa02b5e40>{:nvidia:_nv000711rm+966}
Feb 11 11:50:18 gen2 <ffffffff802ed2e3>{eth_header+227} <ffffffffa0235f67>{:nvidia:_nv001272rm+51}
Feb 11 11:50:18 gen2 <ffffffffa02350dc>{:nvidia:_nv001217rm+28} <ffffffffa02b584a>{:nvidia:_nv000704rm+46}
Feb 11 11:50:18 gen2 <ffffffffa02471fa>{:nvidia:_nv002797rm+428} <ffffffff8032978e>{fn_hash_lookup+190}
Feb 11 11:50:18 gen2 <ffffffffa017e112>{:nvidia:_nv004381rm+114} <ffffffffa0236053>{:nvidia:_nv001271rm+123}
Feb 11 11:50:18 gen2 <ffffffffa0154d29>{:nvidia:_nv000996rm+39} <ffffffffa01662a6>{:nvidia:_nv005021rm+100}
Feb 11 11:50:18 gen2 <ffffffffa0246d24>{:nvidia:_nv002756rm+2352} <ffffffffa0234cd4>{:nvidia:_nv001214rm+112}
Feb 11 11:50:18 gen2 <ffffffffa017adf8>{:nvidia:_nv004375rm+268} <ffffffffa01617a6>{:nvidia:_nv000884rm+16}
Feb 11 11:50:18 gen2 <ffffffffa0283ce0>{:nvidia:_nv001134rm+536} <ffffffffa016311e>{:nvidia:_nv005317rm+112}
Feb 11 11:50:18 gen2 <ffffffffa0164abd>{:nvidia:rm_isr_bh+9} <ffffffff8013c81f>{tasklet_action+111}
Feb 11 11:50:18 gen2 <ffffffff8013c4fb>{do_softirq+123} <ffffffff8011384f>{do_IRQ+463}
Feb 11 11:50:18 gen2 <ffffffff80110f8d>{ret_from_intr+0} <EOI> <ffffffff80110a14>{system_call+124}
Feb 11 11:50:18 gen2

Here's another one from a few days back:

Feb 6 21:46:09 gen2 Badness in pci_find_subsys at drivers/pci/search.c:132
Feb 6 21:46:09 gen2
Feb 6 21:46:09 gen2 Call Trace:<IRQ> <ffffffff80211a73>{pci_find_subsys+83} <ffffffff80211a00>{pci_find_slot+48}
Feb 6 21:46:09 gen2 <ffffffffa0137528>{:nvidia:os_pci_init_handle+40 } <ffffffffa015302e>{:nvidia:_nv000904rm+24}
Feb 6 21:46:09 gen2 <ffffffffa02a8dfb>{:nvidia:_nv000711rm+897} <ffffffff801310fa>{scheduler_tick+90}
Feb 6 21:46:09 gen2 <ffffffffa0228f67>{:nvidia:_nv001272rm+51} <ffffffffa02280dc>{:nvidia:_nv001217rm+28}
Feb 6 21:46:09 gen2 <ffffffffa02a884a>{:nvidia:_nv000704rm+46} <ffffffffa020b222>{:nvidia:_nv002988rm+438}
Feb 6 21:46:09 gen2 <ffffffffa02283b6>{:nvidia:_nv002812rm+16} <ffffffffa021ad3f>{:nvidia:_nv001834rm+2317}
Feb 6 21:46:09 gen2 <ffffffffa015437e>{:nvidia:_nv000719rm+62} <ffffffffa0154603>{:nvidia:_nv000858rm+103}
Feb 6 21:46:09 gen2 <ffffffffa02097b5>{:nvidia:_nv002967rm+1907} <ffffffffa0227cd4>{:nvidia:_nv001214rm+112}
Feb 6 21:46:09 gen2 <ffffffffa01547a6>{:nvidia:_nv000884rm+16} <ffffffffa0276d9b>{:nvidia:_nv001134rm+723}
Feb 6 21:46:09 gen2 <ffffffffa015611e>{:nvidia:_nv005317rm+112} <ffffffffa0157abd>{:nvidia:rm_isr_bh+9}
Feb 6 21:46:09 gen2 <ffffffff8013c81f>{tasklet_action+111} <ffffffff8013c4fb>{do_softirq+123}
Feb 6 21:46:09 gen2 <ffffffff8011384f>{do_IRQ+463} <ffffffff80110f8d>{ret_from_intr+0}
Feb 6 21:46:09 gen2 <EOI>
Feb 6 21:46:09 gen2 Badness in pci_find_subsys at drivers/pci/search.c:132
Feb 6 21:46:09 gen2
Feb 6 21:46:09 gen2 Call Trace:<IRQ> <ffffffff80211a73>{pci_find_subsys+83} <ffffffff80211a00>{pci_find_slot+48}
Feb 6 21:46:09 gen2 <ffffffffa0137528>{:nvidia:os_pci_init_handle+40 } <ffffffffa015302e>{:nvidia:_nv000904rm+24}
Feb 6 21:46:09 gen2 <ffffffffa020c844>{:nvidia:_nv002969rm+178} <ffffffff80211b45>{pci_find_subsys+293}
Feb 6 21:46:09 gen2 <ffffffffa027ab8f>{:nvidia:_nv001148rm+121} <ffffffffa02a8e40>{:nvidia:_nv000711rm+966}
Feb 6 21:46:09 gen2 <ffffffffa0228f67>{:nvidia:_nv001272rm+51} <ffffffffa02280dc>{:nvidia:_nv001217rm+28}
Feb 6 21:46:09 gen2 <ffffffffa02a884a>{:nvidia:_nv000704rm+46} <ffffffffa020b222>{:nvidia:_nv002988rm+438}
Feb 6 21:46:09 gen2 <ffffffffa02283b6>{:nvidia:_nv002812rm+16} <ffffffffa021ad3f>{:nvidia:_nv001834rm+2317}
Feb 6 21:46:09 gen2 <ffffffffa015437e>{:nvidia:_nv000719rm+62} <ffffffffa0154603>{:nvidia:_nv000858rm+103}
Feb 6 21:46:09 gen2 <ffffffffa02097b5>{:nvidia:_nv002967rm+1907} <ffffffffa0227cd4>{:nvidia:_nv001214rm+112}
Feb 6 21:46:09 gen2 <ffffffffa01547a6>{:nvidia:_nv000884rm+16} <ffffffffa0276d9b>{:nvidia:_nv001134rm+723}
Feb 6 21:46:09 gen2 <ffffffffa015611e>{:nvidia:_nv005317rm+112} <ffffffffa0157abd>{:nvidia:rm_isr_bh+9}
Feb 6 21:46:09 gen2 <ffffffff8013c81f>{tasklet_action+111} <ffffffff8013c4fb>{do_softirq+123}
Feb 6 21:46:09 gen2 <ffffffff8011384f>{do_IRQ+463} <ffffffff80110f8d>{ret_from_intr+0}
Feb 6 21:46:09 gen2 <EOI>

Can someone please help me with this problem?

tamran 02-11-04 06:37 PM

And more ....
 
Just for the heck of it, I've also posted the entire /var/log/messages file as an attachment. Perhaps it will shed some light? You'll see multiple instances of the crash in there.


All times are GMT -5. The time now is 02:48 PM.

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