From: James Davies <james_m_davies@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kiril Vidimce <vkire@pixar.com>, Dan Maas <dmaas@dcine.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel: ldt allocation failed
Date: 07 Dec 2001 19:26:28 +1000 [thread overview]
Message-ID: <1007717194.1342.1.camel@Lord> (raw)
In-Reply-To: <E16CH6i-00059b-00@the-village.bc.nu>
In-Reply-To: <E16CH6i-00059b-00@the-village.bc.nu>
The nVidia kernel drivers are open source. You can get them from
ftp://ftp.nvidia.com/pub/drivers/english/XFree86_40/1.0-2313/NVIDIA_kernel-1.0-2313.tar.gz
the 0.9 serious of drivers were buggy and crashed a lot, earning them a
bad rep. But the 1.0 series are faster and more stable than their
windows counterparts- I havn't had one crash, even with a faulty card
that kills windows constantly.
On Fri, 2001-12-07 at 19:15, Alan Cox wrote:
> > I don't see how one can magically tell that this is an NVIDIA problem.
>
> We don't know. But since we don't have their source and they have our
> source only they can tell you.
>
> > in the kernel and I imagine that even if the NVIDIA drivers are
> > triggering the problem, there are other modules/apps that can bring
> > about the same behavior.
>
> Possibly, but you'll have to ask Nvidia to debug it for you. If you can
> reproduce a bug by
> - removing the nvidia modules so they wont be loaded
> - hard booting the machine
> - triggering the bug without loading the nvidia drivers
>
> then please report it. If not, its between you and nvidia.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
next prev parent reply other threads:[~2001-12-07 9:31 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.kit1f7v.j024op@ifi.uio.no>
2001-12-07 7:24 ` kernel: ldt allocation failed Dan Maas
2001-12-07 9:00 ` Kiril Vidimce
2001-12-07 9:15 ` Alan Cox
2001-12-07 9:13 ` Kiril Vidimce
2001-12-07 9:28 ` Alan Cox
2001-12-07 9:26 ` James Davies [this message]
2001-12-07 9:43 ` Alan Cox
2001-12-07 13:10 ` James Davies
2001-12-07 13:41 ` Dave Jones
2001-12-07 13:59 ` James Davies
2001-12-07 13:53 ` Alan Cox
2001-12-07 9:45 ` Anton Altaparmakov
2001-12-07 10:38 ` Alan Cox
2002-02-06 16:58 ` Denis Vlasenko
2002-02-06 13:42 ` Alan Cox
2002-02-06 17:20 ` Christoph Hellwig
2001-12-07 10:12 ` Anton Altaparmakov
[not found] <Pine.LNX.4.21.0112070057480.20196-100000@tombigbee.pixar.com.suse.lists.linux.kernel>
[not found] ` <5.1.0.14.2.20011207092244.049f6720@pop.cus.cam.ac.uk.suse.lists.linux.kernel>
[not found] ` <200202061258.g16CwGt31197@Port.imtp.ilyichevsk.odessa.ua.suse.lists.linux.kernel>
2002-02-06 13:19 ` Andi Kleen
2002-02-06 14:06 ` Dave Jones
2002-02-06 14:13 ` Alan Cox
2002-02-06 14:09 ` Andi Kleen
2002-02-06 14:39 ` Alan Cox
2002-02-06 16:37 ` bert hubert
2002-02-06 15:51 ` Bill Davidsen
2002-02-06 16:08 ` Alan Cox
2002-02-06 16:29 ` John Levon
2002-02-06 18:01 ` Alan Cox
2002-02-06 18:02 ` Denis Vlasenko
2002-02-06 15:12 ` Jakub Jelinek
2002-02-06 18:11 ` Maciej W. Rozycki
2002-02-06 20:19 ` H. Peter Anvin
2002-02-06 21:15 ` Jakub Jelinek
2002-02-06 21:17 ` H. Peter Anvin
2002-02-06 20:21 ` yodaiken
2002-02-06 21:00 ` H. Peter Anvin
2002-02-06 21:31 ` Jakub Jelinek
2002-02-06 22:05 ` H. Peter Anvin
2002-02-06 22:20 ` Jakub Jelinek
2002-02-06 23:35 ` H. Peter Anvin
2002-02-07 0:21 ` Alan Cox
2002-02-07 0:12 ` Jakub Jelinek
2002-02-07 0:15 ` H. Peter Anvin
2002-02-07 0:13 ` H. Peter Anvin
2002-02-06 15:37 ` Alan Cox
2001-12-07 5:40 Kiril Vidimce
2001-12-07 5:58 ` Jeffrey H. Ingber
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=1007717194.1342.1.camel@Lord \
--to=james_m_davies@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmaas@dcine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkire@pixar.com \
/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