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

Newegg Daily Deals

Reply
 
Thread Tools
Old 02-17-04, 10:02 AM   #1
darkhelmet03
Registered User
 
Join Date: Jul 2003
Posts: 62
Default 2.6.2 Kernel Badness with 1.0-5336 NVIDIA driver

Hi to all,

The kernel is 2.6.2 from www.kernel.org and I use AGPGART for AGP (_not_
NvAGP). Fast Writes and SBA are enabled. FC1 is the distro.
The mobo is Abit KG7.

X stopped responding out of the blue, at a KDE 3.2 desktop, and it could not
be killed either. The following messages were uncovered in
my /var/log/messages:

Feb 17 07:35:15 thunderbird kernel: Badness in pci_find_subsys at
drivers/pci/search.c:167
Feb 17 07:35:15 thunderbird kernel: Call Trace:
Feb 17 07:35:15 thunderbird kernel: [<c01ec168>] pci_find_subsys+0xe8/0xf0
Feb 17 07:35:15 thunderbird kernel: [<c01ec19f>] pci_find_device+0x2f/0x40
Feb 17 07:35:15 thunderbird kernel: [<c01ebfa8>] pci_find_slot+0x28/0x50
Feb 17 07:35:15 thunderbird kernel: [<e0e1222a>] os_pci_init_handle+0x39/0x68
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0ca685f>] _nv001243rm+0x1f/0x24
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0ded115>] _nv000816rm+0x2f5/0x384
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0d5592c>] _nv003801rm+0xd8/0x100
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0decc4f>] _nv000809rm+0x2f/0x34
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0d84b48>] _nv003606rm+0xe4/0x114
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0d846b8>] _nv003564rm+0x688/0x908
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0cbf267>] _nv004046rm+0x3a3/0x3b0
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0dc0b03>] _nv001476rm+0x1d3/0x45c
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0ca939a>] _nv000896rm+0x4a/0x64
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0caabb4>] rm_isr_bh+0xc/0x10 [nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0e0fab1>] nv_kern_isr_bh+0xf/0x13
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<c01208b6>] tasklet_action+0x46/0x70
Feb 17 07:35:15 thunderbird kernel: [<c01206d0>] do_softirq+0x90/0xa0
Feb 17 07:35:15 thunderbird kernel: [<c010b56d>] do_IRQ+0xfd/0x130
Feb 17 07:35:15 thunderbird kernel: [<c01098b4>] common_interrupt+0x18/0x20
Feb 17 07:35:15 thunderbird kernel:
Feb 17 07:35:15 thunderbird kernel: Badness in pci_find_subsys at
drivers/pci/search.c:167
Feb 17 07:35:15 thunderbird kernel: Call Trace:
Feb 17 07:35:15 thunderbird kernel: [<c01ec168>] pci_find_subsys+0xe8/0xf0
Feb 17 07:35:15 thunderbird kernel: [<c01ec19f>] pci_find_device+0x2f/0x40
Feb 17 07:35:15 thunderbird kernel: [<c01ebfa8>] pci_find_slot+0x28/0x50
Feb 17 07:35:15 thunderbird kernel: [<e0e1222a>] os_pci_init_handle+0x39/0x68
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0ca685f>] _nv001243rm+0x1f/0x24
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0d57a5d>] _nv003797rm+0xa9/0x128
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0dc44a1>] _nv001490rm+0x55/0xe4
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0ded154>] _nv000816rm+0x334/0x384
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0d5592c>] _nv003801rm+0xd8/0x100
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0decc4f>] _nv000809rm+0x2f/0x34
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0d84b48>] _nv003606rm+0xe4/0x114
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0d846b8>] _nv003564rm+0x688/0x908
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0cbf267>] _nv004046rm+0x3a3/0x3b0
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0dc0b03>] _nv001476rm+0x1d3/0x45c
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0ca939a>] _nv000896rm+0x4a/0x64
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0caabb4>] rm_isr_bh+0xc/0x10 [nvidia]
Feb 17 07:35:15 thunderbird kernel: [<e0e0fab1>] nv_kern_isr_bh+0xf/0x13
[nvidia]
Feb 17 07:35:15 thunderbird kernel: [<c01208b6>] tasklet_action+0x46/0x70
Feb 17 07:35:15 thunderbird kernel: [<c01206d0>] do_softirq+0x90/0xa0
Feb 17 07:35:15 thunderbird kernel: [<c010b56d>] do_IRQ+0xfd/0x130
Feb 17 07:35:15 thunderbird kernel: [<c01098b4>] common_interrupt+0x18/0x20
Feb 17 07:35:15 thunderbird kernel:
darkhelmet03 is offline   Reply With Quote
Old 02-18-04, 02:13 PM   #2
darkhelmet03
Registered User
 
Join Date: Jul 2003
Posts: 62
Default FYI

I checked my logs and found out that these Badnesses occured also when I used 5328.

2 times w/ 5328 -> NO CRASH of X
2 times so far w/ 5336 -> _CRASH_ in both, X hanged, not even changing consoles was possible, I had to login remotely and do shutdown -r now

to NVIDIA: ti seems a 5336 related problem...

btw next time it crashes I am reverting back to 5328...
darkhelmet03 is offline   Reply With Quote
Old 02-18-04, 02:40 PM   #3
SuLinUX
 
SuLinUX's Avatar
 
Join Date: Sep 2003
Location: UK
Posts: 847
Default

I think it's more kde 3.2 related, pretty rare it happened but the desktop just froze, mouse worked and could'nt click on anything, did come back after a while though.

Switching init modes and restarting KDE sorts it.
__________________
AthlonXP 2600+ / nForce2 Asus A7N8X-X / PNY GeForce FX5900 Ultra / 1024Mb Samsung Ram /nForce Sound / Hansol 920D Plus 19" monitor / Lite-On 32x12x40 / 2x Maxtor HD 40Gb/80Gb / nVidia 7174 driver / Gnome 2.10.1 / Kernel 2.6.11.9 / Slackware 10.0
SuLinUX is offline   Reply With Quote
Old 02-18-04, 04:34 PM   #4
Thoreau
Registered User
 
Join Date: Dec 2002
Posts: 95
Default Perhaps this will help

From www.minion.de:

"Words of caution

If you find that 1.0-5328 hangs on X startup on a newer Via chipset, please download the current 2.6 patch for this release. This bug is not specific to Linux 2.6.

Linux 2.6 AGPGART seems to be broken on some chipsets. If you find that your system hangs upon starting X, potentially with ASCII garbage all over the screen, try the built-in NVIDIA AGP GART driver (Option "NvAgp" "1", AGPGART not loaded) instead.

Many ACPI and UP I/O APIC configurations seem to be unreliable; if you're experiencing startup or stability problems, it may help to disable them with acpi=off and noapic. In some cases, a combination of pci=noacpi and pci=biosirq has also been reported to help.

The (partial) mem=nopentium workaround for the AMD Athlon/AGP stability problem on Linux will not work as expected on Linux 2.6. It has been made obsolete with the introduction of Andi Kleen's page attribute interface in Linux 2.4.20 (also present in Linux 2.6).

The 4GB/4GB split VM layout is incompatible with driver releases older than 1.0-5328. If you're using an older release, you will need to make sure to rebuild the kernel without support for the new layout, i.e. disable CONFIG_X86_4G_VM_LAYOUT.

The CONFIG_4K_STACK option available with William Lee Irwin III's kernel is incompatible with the NVIDIA driver.

If you built Linux 2.6 with separate source/object trees, you will need to specify the same object tree when building the NVIDIA kernel module (i.e. if you built with make O=/usr/obj/linux-2.6.0-test9 [...], build the kernel module with the same flag)."

Perhaps the same issue is persistent with the new nvidia driver. I choose the NvAGP module myself and am not getting the errors you are reporting in that chipset.
Thoreau is offline   Reply With Quote
Old 02-18-04, 05:14 PM   #5
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default

@darkhelmet03: you mention that you have both AGP fast writes and side band addressing enabled in your initial post; both have frequently been responsible for severe stability problems in the past, which is why the driver disables them in the first place. Please leave them disabled and check if the stability problems persist.
zander is offline   Reply With Quote
Old 02-18-04, 08:09 PM   #6
ByteEnable
Registered User
 
Join Date: Jun 2003
Posts: 24
Default

Hi All,

VIA Apollo Pro266T North Bridge (AGP) and 2.6.X kernel AGPGART

I get random ascii characters on the screen and the system freezes when using the newest NVIDIA driver (5536) and kernel 2.6.1-1.65. The error happens when X tries to load. I checked kernel.org and did not see any bugs in bugzilla. However, I did find this:


http://minion.de/

"Linux 2.6 AGPGART seems to be broken on some chipsets. If you find that your system hangs upon starting X, potentially with ASCII garbage all over the screen, try the built-in NVIDIA AGP GART driver (Option "NvAgp"1", AGPGART not loaded) instead." Has anyone else see this problem?

Byte
ByteEnable is offline   Reply With Quote
Old 02-18-04, 08:28 PM   #7
darkhelmet03
Registered User
 
Join Date: Jul 2003
Posts: 62
Default

I disabled FW and SBA upon loading 2.6.3
I will now cross my fingers....
In case X hangs again I will try NvAGP (do I need to NOT compile AGPGART in the kernel??? but as a module?) and as a last resort go back to 5328.
darkhelmet03 is offline   Reply With Quote
Old 02-19-04, 02:56 AM   #8
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default

When using NVIDIA's builtin AGP GART driver, you need to make sure that Linux AGPGART is not present, i.e. neither statically linked into the kernel nor loaded as a module.
zander is offline   Reply With Quote

Old 02-19-04, 09:07 AM   #9
geowiz
Registered User
 
Join Date: Jul 2003
Location: Houston, Tx USA
Posts: 110
Default window manager

darkhelmet03,

You didn't mention which window manager you were using ..... I had similar hang problems with KDE 3.2, Nvidia driver and Windowmaker. I went back to the KDE window manager and it has been goodness since. Hmmm...... where be the problem?

Just a side thought that may help.
geowiz is offline   Reply With Quote
Old 02-19-04, 10:27 AM   #10
darkhelmet03
Registered User
 
Join Date: Jul 2003
Posts: 62
Default

FC1 + KDE 3.2 + 2.6.2
since I switched to 2.6.3 and disabled FW and SBA no problems....yet

Thanks
darkhelmet03 is offline   Reply With Quote
Old 02-19-04, 12:32 PM   #11
LeVA
Guest
 
Posts: n/a
Default

I'm having the same exact problem with my card. But I've tried so many variations, and it always hangs my computer. I've tried to use the NvAGP "1" option, and disable the agpgart, but then my machine is still unstable. Now I'm using 2.6.3 kernel with 1.0-5336 nvidia driver. I have an ABIT BE7-RAID mainboard with Intel 82845PE chipset. I'm using KDE-3.2 too, and XFree-4.3.99.903. As you can see, I'm using the latest software from everything, and I've even updated my bios to the latest version. But this is still unstable. For a few days I tried to use the static int NVreg_UpdateKernelAGP = 0 feature in the nvidia driver source (still bad). After that I tried to use AGP in 2x mode (still bad). Now I'm using the:
static int NVreg_UpdateKernelAGP = 0;
static int NVreg_EnableAGPFW = 1;
static int NVreg_EnableAGPSBA = 0;
AGP-4x
nvidia driver 1.0-5336
linux kernel 2.6.3
Option "NvAGP" "2"

Anybody has a solution to this problem?
It would *really* nice to have a stable system now...

Thanks!

Daniel
  Reply With Quote
Old 02-19-04, 02:19 PM   #12
LeVA
Guest
 
Posts: n/a
Default

In case of instability, do you recommend to use the

static int NVreg_UpdateKernelAGP = 0;

option?

Anybody experienced that this solve some problems?

Thanks!
  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
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
Nvidia driver stopped working after X restart and Kernel taint msgs during boot mikejuni NVIDIA Linux 10 05-21-12 08:30 PM
Lucid rt kernel can't load latest nvidia driver module, but generic does. marcod NVIDIA Linux 0 05-02-12 06:23 AM
Getting the proprietary nvidia driver to run with Debian 3.0 r0 (woody) Katchina404 NVIDIA Linux 9 01-12-03 08:49 AM

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


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