From: Brian Gerst <bgerst@didntduck.org>
To: Dominik Karall <dominik.karall@gmx.net>
Cc: Steve Youngs <sryoungs@bigpond.net.au>, linux-kernel@vger.kernel.org
Subject: Re: NVIDIA and 2.6.4?
Date: Tue, 16 Mar 2004 15:50:05 -0500 [thread overview]
Message-ID: <4057687D.5050902@didntduck.org> (raw)
In-Reply-To: <200403162149.41018.dominik.karall@gmx.net>
Dominik Karall wrote:
> On Monday 15 March 2004 04:36, Steve Youngs wrote:
>
>>* Valdis Kletnieks <Valdis.Kletnieks@vt.edu> writes:
>> > On Fri, 12 Mar 2004 18:24:01 GMT, Adam Jones <adam@yggdrasl.demon.co.uk>
>
> said:
>
>> >> 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. :-)
>>
>> > 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!
Complain to NVidia. It's the binary-only part of the driver that's the
real stack hog.
--
Brian Gerst
next prev parent reply other threads:[~2004-03-16 20:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 15:15 NVIDIA and 2.6.4? Sid Boyce
2004-03-11 19:26 ` Max Valdez
2004-03-12 1:31 ` Sid Boyce
2004-03-12 18:24 ` Adam Jones
2004-03-13 5:15 ` Valdis.Kletnieks
2004-03-15 3:36 ` Steve Youngs
2004-03-16 20:49 ` Dominik Karall
2004-03-16 20:50 ` Brian Gerst [this message]
2004-03-16 21:19 ` Valdis.Kletnieks
2004-03-16 21:55 ` Dominik Karall
-- strict thread matches above, loose matches on Subject: below --
2004-03-15 1:24 Sid Boyce
2004-03-14 2:23 Sid Boyce
2004-03-14 2:28 ` Sid Boyce
[not found] <1yxEK-7cw-5@gated-at.bofh.it>
2004-03-11 13:20 ` Dennis Bliefernicht
2004-03-11 15:05 ` Robert L. Harris
2004-03-11 12:31 Robert L. Harris
2004-03-11 13:07 ` Nerijus Baliunas
2004-03-11 13:23 ` Martin Zwickel
2004-03-13 14:34 ` venom
2004-03-11 14:52 ` Alistair John Strachan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4057687D.5050902@didntduck.org \
--to=bgerst@didntduck.org \
--cc=dominik.karall@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sryoungs@bigpond.net.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox