kernel: ldt allocation failed
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines
We suddenly started seeing freezing problems on a number of machines in the past couple of days. There is no pattern as far as I can tell. It has happened while running OpenGL apps, netscape, or even when not doing anything.
Software:
- NVIDIA drivers 1.0-1541
Sorry, we do not have the source to NVIDIA's driver, so we cannot help you debug this problem. Please contact NVIDIA support.
Regards,
Dan
Quoted 10 lines · Dan Maas
Quoted 7 lines
We suddenly started seeing freezing problems on a number of machines in the past couple of days. There is no pattern as far as I can tell. It has happened while running OpenGL apps, netscape, or even when not doing anything.
Software:
- NVIDIA drivers 1.0-1541Sorry, we do not have the source to NVIDIA's driver, so we cannot help you debug this problem. Please contact NVIDIA support.
I don't see how one can magically tell that this is an NVIDIA problem. I am contacting NVIDIA at the same time and it's possible that the problem is with their drivers. However, there is something going on 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.
KV
--
___________________________________________________________________
Studio Tools [email protected]
Pixar Animation Studios http://www.pixar.com/
Quoted 1 line
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.
Quoted 3 lines
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.
Quoted 9 lines · Alan Cox
Quoted 1 line
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.
Quoted 3 lines
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.
Quoted 7 lines
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 driversthen please report it. If not, its between you and nvidia.
Without turning this into a religous debate, is there any way to find out what those messages really mean? When does one run into an ldt allocation failure? What is ldt? I am not just trying to solve this problem; I also want to understand what is going on in the kernel.
Thanks for any explanations.
KV
--
___________________________________________________________________
Studio Tools [email protected]
Pixar Animation Studios http://www.pixar.com/
Quoted 5 lines
Without turning this into a religous debate, is there any way to find out what those messages really mean? When does one run into an ldt allocation failure? What is ldt? I am not just trying to solve this problem; I also want to understand what is going on in the kernel.
Have a look in arch/i386/kernel/*.c. LDT is a descriptor table of segment registers. Its generally used by emulators to run things like win16 binaries and sometimes by threaded apps to do thread specific address spaces by giving each thread a different %fs or %gs segment register
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.
Quoted 15 lines · Alan Cox
Quoted 1 line
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.
Quoted 3 lines
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
Quoted 6 lines
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 [email protected]
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
Quoted 2 lines
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 Nvidia drivers are not open source. Please stop pedalling this myth. All you are doing is risking confusing other unfortunates into buying nvidia hardware and finding there is no open 3D support.
Quoted 3 lines
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.
So tell me why I keep getting people who remove the Nvidia drivers and have their machine work. I'm sure some of them are hardware related issues, but all of them ?
Alan
Quoted 6 lines · Alan Cox
Quoted 2 lines
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 Nvidia drivers are not open source. Please stop pedalling this myth. All you are doing is risking confusing other unfortunates into buying nvidia hardware and finding there is no open 3D support.
I wan't trying to state that it is GPL or similar, but the kernel driver source code IS available for free under a restrictive license. the GLX drivers are closed.
Quoted 7 lines
Quoted 3 lines
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.
So tell me why I keep getting people who remove the Nvidia drivers and have their machine work. I'm sure some of them are hardware related issues, but all of them ?
I can't comment on the stability in all configurations, but I've found them to work quite well with my box since 1.0 came out. the 0.9 serious were notorious for crashing though.
Quoted 1 line
Alan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Quoted 2 lines · James Davies
source code IS available for free under a restrictive license. the GLX drivers are closed.
Bzzzt...
Quoted 1 line
From the tarball you posted a link to..
-rwxr-xr-x 1 davej users 889615 Nov 27 20:39 Module-nvkernel*
(davej@noodles:NVIDIA_kernel-1.0-2313)$ file Module-nvkernel Module-nvkernel: ELF 32-bit LSB relocatable, Intel 80386, version 1, not stripped
No-one but nvidia knows whats in this.
regards,
Dave.
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Ok I see my mistake now. While the kernel driver contains source code, it is only enough to link with the current kernel correctly, and the rest binary. Sorry.
Quoted 11 lines · Dave Jones
Quoted 2 lines · James Davies
source code IS available for free under a restrictive license. the GLX drivers are closed.
Bzzzt...
Quoted 1 line
From the tarball you posted a link to..
-rwxr-xr-x 1 davej users 889615 Nov 27 20:39 Module-nvkernel*
Quoted 12 lines
(davej@noodles:NVIDIA_kernel-1.0-2313)$ file Module-nvkernel Module-nvkernel: ELF 32-bit LSB relocatable, Intel 80386, version 1, not strippedNo-one but nvidia knows whats in this.
regards,
Dave.Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Quoted 7 lines
Quoted 3 lines
The Nvidia drivers are not open source. Please stop pedalling this myth. All you are doing is risking confusing other unfortunates into buying nvidia hardware and finding there is no open 3D support.
I wan't trying to state that it is GPL or similar, but the kernel driver source code IS available for free under a restrictive license. the GLX drivers are closed.
No. The kernel driver source code is not available. Stop trying to mislead people.
Alan
Quoted 4 lines · Alan Cox
Quoted 1 line
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.
Not doing any debugging is fine.
However, looking at 2.4.16/arch/i386/kernel/process.c::copy_segments() which generates this message it seems odd: It returns void, yet it can fail because it is doing a vmalloc().
When the vmalloc() fails, the new_mm->context.segments is set to NULL and the function returns.
That seems wrong, no? Shouldn't there be a panic() when the allocation fails at least? Or even better the function should perhaps return an error code?
Considering there is only one caller (kernel/fork.c::copy_mm()) it would be easy to modify copy_mm() to handle a returned error code gracefully and goto fail_nomem, which would in turn result in kernel/fork.c::do_fork(), the only caller of copy_mm(), cleaning up properly and returning an error code.
Or have I missed something and the situation where the ldt is missing can be recovered from? - I would think (without looking into this in the kernel code) that loosing the local descriptor table would be rather detrimental on the first context switch to the new process created by fork... And considering all kinds of errors are being handled in this code path, except for the vmalloc() failure, it seems like a good idea to add the appropriate fail mechanism.
If nvidia is causing this to get triggered they will likely run into problems elsewhere anyway and we don't care but we should get the kernel working. As it is AFAICS we have a potential DOS, just get the box close to OOM and start calling man 2 fork and/or man 3 clone and you could trigger this with a finite probability.
Best regards,
Anton
Signature · 5 lines
"I've not lost my mind. It's backed up on tape somewhere." - Unknown -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/ ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
Quoted 12 lines · Anton Altaparmakov
Quoted 4 lines · Alan Cox
Quoted 1 line
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.
Not doing any debugging is fine.
However, looking at 2.4.16/arch/i386/kernel/process.c::copy_segments() which generates this message it seems odd: It returns void, yet it can fail because it is doing a
vmalloc().When the
vmalloc()fails, thenew_mm->context.segmentsis set to NULL and the function returns.
Quoted 7 lines
That seems wrong, no? Shouldn't there be a
panic()when the allocation fails at least? Or even better the function should perhaps return an error code?Considering there is only one caller (kernel/fork.c::copy_mm()) it would be easy to modify
copy_mm()to handle a returned error code gracefully and gotofail_nomem, which would in turn result in kernel/fork.c::do_fork(), the only caller ofcopy_mm(), cleaning up properly and returning an error code.Or have I missed something and the situation where the ldt is missing can be recovered from? - I would think (without looking into this in the kernel code) that loosing the local descriptor table would be rather detrimental on the first context switch to the new process created by fork... And considering all kinds of errors are being handled in this code path, except for the
vmalloc()failure, it seems like a good idea to add the appropriate fail mechanism.If nvidia is causing this to get triggered they will likely run into problems elsewhere anyway and we don't care but we should get the kernel working. As it is AFAICS we have a potential DOS, just get the box close to OOM and start calling man 2 fork and/or man 3 clone and you could trigger
s/man 3 clone/man 2 clone/
Quoted 19 lines
this with a finite probability.
Best regards,
Anton
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 5 lines
"I've not lost my mind. It's backed up on tape somewhere." - Unknown -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/ ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
Quoted 9 lines
When the
vmalloc()fails, thenew_mm->context.segmentsis set to NULL and the function returns.That seems wrong, no? Shouldn't there be a
panic()when the allocation fails at least? Or even better the function should perhaps return an error code?Considering there is only one caller (kernel/fork.c::copy_mm()) it would be easy to modify
copy_mm()to handle a returned error code gracefully and
That sounds like an appropriate change.
Quoted 11 lines · Anton Altaparmakov
However, looking at 2.4.16/arch/i386/kernel/process.c::copy_segments() which generates this message it seems odd: It returns void, yet it can fail because it is doing a
vmalloc().When the
vmalloc()fails, thenew_mm->context.segmentsis set to NULL and the function returns.That seems wrong, no? Shouldn't there be a
panic()when the allocation fails at least? Or even better the function should perhaps return an error code?
Quoted 5 lines
Considering there is only one caller (kernel/fork.c::copy_mm()) it would be easy to modify
copy_mm()to handle a returned error code gracefully and gotofail_nomem, which would in turn result in kernel/fork.c::do_fork(), the only caller ofcopy_mm(), cleaning up properly and returning an error code.
I am ignorant on the subject, but why LDT is used in Linux at all? LDT register can be set to 0, this can speed up task switch time and save some memory used for LDT.
I see a i386 specific syscall (kernel/ldt.c:sys_modify_ldt()) and
/*
* default LDT is a single-entry callgate to lcall7 for iBCS
* and a callgate to lcall27 for Solaris/x86 binaries
*/
set_call_gate(&default_ldt[0],lcall7);
set_call_gate(&default_ldt[4],lcall27);in kernel/traps.c:trap_init().
Is it used elsewhere?
--
vda
Quoted 3 lines
I am ignorant on the subject, but why LDT is used in Linux at all? LDT register can be set to 0, this can speed up task switch time and save some memory used for LDT.
Wine and certain threaded applications
Quoted 5 lines · In article <[email protected]> you wrote:
Quoted 3 lines
I am ignorant on the subject, but why LDT is used in Linux at all? LDT register can be set to 0, this can speed up task switch time and save some memory used for LDT.
Wine and certain threaded applications
Xenix/286 binary emulation.