Skip to contentSkip to conversation

NVIDIA and 2.6.4?

DISCUSSION Sid Boyce 7 participants 10 messages Mar 11, 2004 – Mar 16, 2004

lore
Share & tools
lore

Sid Boyce

author
#0 lore raw

I tried 5336 with 2.6.4-rc2-mm1 and it locks the box up completely after switching to kdm. It worked with 2.6.3-mm4 previously, now even that kernel gets a lock up. I've done a reiserfsck --rebuild-tree which repaired some files and left 10 files in /lost+found and I can't determine what they are. I am currently using 2.6.4-rc2-mm1 with the standard SuSE 9.0 Driver "nv".
I also went back to the minion.de release and still got a lockup, I guess it's down to some of those files in lost+found that are missing.
Regards
Sid.

Signature · 2 lines
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
#1 lore raw

That's weird:
uname -a
Linux garaged 2.6.4-rc2-mm1 #1 SMP Wed Mar 10 20:27:04 CST 2004 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux

$ lsmod | grep nv
nvidia               2075144  12

Running KDE, using kdm, with nvidia module, no problem, I notice a slight difference on fonts, but I dont know if it's my imagination.

Been using nvidia modules for quite a few 2.6.x kernels, most of them mmX. without problems

Max

Signature · 8 lines
Linux garaged 2.6.3-mm3 #2 SMP Tue Feb 24 15:44:58 CST 2004 i686 Intel(R) 
Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS/S d- s: a-29 C++(+++) ULAHI+++ P+ L++>+++ E--- W++ N* o-- K- w++++ O- M-- 
V-- PS+ PE Y-- PGP++ t- 5- X+ R tv++ b+ DI+++ D- G++ e++ h+ r+ z**
------END GEEK CODE BLOCK------
gpg-key: http://garaged.homeip.net/gpg-key.txt
author
#2 lore raw
Quoted 8 lines · Max Valdez

That's weird:
uname -a
Linux garaged 2.6.4-rc2-mm1 #1 SMP Wed Mar 10 20:27:04 CST 2004 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux

$ lsmod | grep nv
nvidia               2075144  12
Quoted 7 lines

Running KDE, using kdm, with nvidia module, no problem, I notice a slight difference on fonts, but I dont know if it's my imagination.

Been using nvidia modules for quite a few 2.6.x kernels, most of them mmX. without problems

Max

Something strange happened, I shall try 2.6.4-mm1 shortly to see if it is still the same. I reckon though that I've suffered a filesystem corruption. Regards
Sid.

Signature · 2 lines
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
#3 lore raw
Quoted 4 lines · Sid Boyce
Quoted 2 lines · Max Valdez

Been using nvidia modules for quite a few 2.6.x kernels, most of them mmX. without problems

I'm using it here with 2.6.4, no problems as yet.

Quoted 3 lines

Something strange happened, I shall try 2.6.4-mm1 shortly to see if it is still the same. I reckon though that I've suffered a filesystem corruption.

A quick thought - have you got CONFIG_REGPARM enabled in the kernel config? If so, disable it and try again. (It's almost certain to cause crashes with binary modules.)

Signature · 3 lines
Adam Jones ([email protected])(http://www.yggdrasl.demon.co.uk/)
.oO("Hizbollah Central Press Office"                                   )
PGP public key: http://www.yggdrasl.demon.co.uk/pubkey.asc
#4 lore raw
Quoted 9 lines · Adam Jones
Quoted 5 lines · Sid Boyce
Quoted 3 lines · Max Valdez

Been using nvidia modules for quite a few 2.6.x kernels, most of them mmX.

without problems

I'm using it here with 2.6.4, no problems as yet.

Quoted 7 lines
Quoted 3 lines

Something strange happened, I shall try 2.6.4-mm1 shortly to see if it is still the same. I reckon though that I've suffered a filesystem corruption.

A quick thought - have you got CONFIG_REGPARM enabled in the kernel config? If so, disable it and try again. (It's almost certain to cause crashes with binary modules.)

Also, the NVidia driver uses a bit of kernel stack, so it's incompatible with the CONFIG_4KSTACKS option in recent -mm kernels...

#5 lore raw
Quoted 4 lines · Valdis Kletnieks
Quoted 3 lines · Adam Jones

A quick thought - have you got CONFIG_REGPARM enabled in the kernel config? If so, disable it and try again. (It's almost certain to cause crashes with binary modules.)

  $ zgrep REGPARM /proc/config.gz
CONFIG_REGPARM=y
  $ grep nvidia /proc/modules
nvidia 2066568 22 - Live 0xe0b2d000
  $ uname -r
2.6.4-sy1

No problems here. :-)

Quoted 3 lines

Also, the NVidia driver uses a bit of kernel stack, so it's incompatible with the CONFIG_4KSTACKS option in recent -mm kernels...

Will have to remember that for 2.6.5, I'll let you know how it goes. Thanks, Valdis.

Signature · 4 lines
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|              Ashes to ashes, dust to dust.               |
|      The proof of the pudding, is under the crust.       |
|------------------------------<[email protected]>---|
#6 lore raw
Quoted 2 lines · Steve Youngs
Quoted 1 line · Valdis Kletnieks

On Fri, 12 Mar 2004 18:24:01 GMT, Adam Jones <[email protected]>

Quoted 13 lines · said:
Quoted 3 lines
Quoted 3 lines

A quick thought - have you got CONFIG_REGPARM enabled in the kernel config? If so, disable it and try again. (It's almost certain to cause crashes with binary modules.)

  $ zgrep REGPARM /proc/config.gz
CONFIG_REGPARM=y
  $ grep nvidia /proc/modules
nvidia 2066568 22 - Live 0xe0b2d000
  $ uname -r
2.6.4-sy1
Quoted 8 lines

No problems here. :-)

Quoted 3 lines

Also, the NVidia driver uses a bit of kernel stack, so it's incompatible with the CONFIG_4KSTACKS option in recent -mm kernels...

Will have to remember that for 2.6.5, I'll let you know how it goes. Thanks, Valdis.

can you let me know how to compile the nvidia drivers for 4KSTACK? cause in the 2.6.5-rc1-mm1 is no more option to deactivate 4KSTACK.
thx!

greets

#7 lore raw
Quoted 26 lines · Dominik Karall
Quoted 2 lines · Steve Youngs
Quoted 1 line · Valdis Kletnieks

On Fri, 12 Mar 2004 18:24:01 GMT, Adam Jones <[email protected]>

Quoted 19 lines · said:
Quoted 3 lines
Quoted 3 lines

A quick thought - have you got CONFIG_REGPARM enabled in the kernel config? If so, disable it and try again. (It's almost certain to cause crashes with binary modules.)

 $ zgrep REGPARM /proc/config.gz
CONFIG_REGPARM=y
 $ grep nvidia /proc/modules
nvidia 2066568 22 - Live 0xe0b2d000
 $ uname -r
2.6.4-sy1

No problems here. :-)

Quoted 3 lines

Also, the NVidia driver uses a bit of kernel stack, so it's incompatible with the CONFIG_4KSTACKS option in recent -mm kernels...

Quoted 6 lines
Quoted 2 lines

Will have to remember that for 2.6.5, I'll let you know how it goes. Thanks, Valdis.

can you let me know how to compile the nvidia drivers for 4KSTACK? cause in the 2.6.5-rc1-mm1 is no more option to deactivate 4KSTACK. thx!

Complain to NVidia. It's the binary-only part of the driver that's the real stack hog.

--
Brian Gerst

#8 lore raw
In reply to Dominik Karall
Quoted 2 lines · Dominik Karall

can you let me know how to compile the nvidia drivers for 4KSTACK? cause in the 2.6.5-rc1-mm1 is no more option to deactivate 4KSTACK.

Get the 2.6.5-rc1-mm1-broken-out.tar.bz2, untar it, then

patch -p1 -R < broken-out/4k-stacks-always-on.patch

Yes, the *right* thing would be for NVidia to fix the binary. However, this is a lot more expedient than waiting. :)

#9 lore raw
Quoted 1 line · you

On Tue, 16 Mar 2004 21:49:40 +0100, Dominik Karall <[email protected]>

Quoted 9 lines · said:
Quoted 2 lines

can you let me know how to compile the nvidia drivers for 4KSTACK? cause in the 2.6.5-rc1-mm1 is no more option to deactivate 4KSTACK.

Get the 2.6.5-rc1-mm1-broken-out.tar.bz2, untar it, then

patch -p1 -R < broken-out/4k-stacks-always-on.patch

Yes, the *right* thing would be for NVidia to fix the binary. However, this is a lot more expedient than waiting. :)

thx, works now with 8k stack size :)

greets