All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeffrey H. Ingber" <jhingber@ix.netcom.com>
To: Kiril Vidimce <vkire@pixar.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel: ldt allocation failed
Date: 07 Dec 2001 00:58:33 -0500	[thread overview]
Message-ID: <1007704718.10108.0.camel@eleusis> (raw)
In-Reply-To: <Pine.LNX.4.21.0112062124440.18796-100000@tombigbee.pixar.com>
In-Reply-To: <Pine.LNX.4.21.0112062124440.18796-100000@tombigbee.pixar.com>

This problem is very familiar.  It was fixed in an -ac patch against
2.4.9 (although I don't recall the exact one), and is included in
subsequent Linus kernels.  Without this fix, I experienced similar
problems with X on multiprocessor workstations.

Jeffrey H. Ingber (jhingber _at_ ix.netcom.com)

On Fri, 2001-12-07 at 00:40, Kiril Vidimce wrote:
> 
> 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. The machine will usually just hang and while it's 
> still pingable, it's totally unresponsive and you can't remotely log in.
> The 2.4.3 kernel usually hangs forever; the machines with 2.4.9
> kernels usually come back within 10-15 secs.
> 
> Every time this happens we see the following message in the system log:
> 
> Dec  6 21:29:00 stranger kernel: ldt allocation failed
> 
> The machines are:
> 
> Hardware:
>     - IBM Intellistation M Pro 
>     - dual 2 GHz P4's
>     - 2 GB RAM
>     - NVIDIA Quadro DCC card
> 
> Software:
>     - Red Hat 7.1
>     - kernel 2.4.3smp or 2.4.9smp
>     - XFree 4.1
>     - Ximian Gnome 1.4
>     - NVIDIA drivers 1.0-1541
> 
> Once this problem occurs, even if the hang is temporary, the machine
> is extremely flakey. Almost any app will start causing ldt allocation
> failure messages in the system log. Only a reboot really helps.
> 
> Questions:
> - Does this ring a bell to anybody? What is ldt anyway and what would 
>   cause an allocation to fail?
> 
> - I still keep one of these messages in this state. Is there anything
>   I can probe to get useful debugging info?
> 
> Any help would greatly be appreciated.
> 
> Thanks,
> KV
> --
>   ___________________________________________________________________
>   Studio Tools                                        vkire@pixar.com
>   Pixar Animation Studios                        http://www.pixar.com/
> 
> -
> 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/



  reply	other threads:[~2001-12-07 15:36 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07  5:40 kernel: ldt allocation failed Kiril Vidimce
2001-12-07  5:58 ` Jeffrey H. Ingber [this message]
     [not found] <fa.kit1f7v.j024op@ifi.uio.no>
2001-12-07  7:24 ` 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
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

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=1007704718.10108.0.camel@eleusis \
    --to=jhingber@ix.netcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.