i386_set_ldt messages with today's world

[Eric Anholt]

On Sun, 2003-09-07 at 14:13, Daniel Eischen wrote:
> On Sun, 7 Sep 2003, Harald Schmalzbauer wrote:
> 
> > Hi all,
> > 
> > I have no idea what it means, but since today's world I get the following 
> > messages after starting x:
> > 
> > Warning: pid 541 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 547 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 548 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 567 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 568 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 569 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 570 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 573 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 572 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> > Warning: pid 577 used static ldt allocation.
> > See the i386_set_ldt man page for more info
> 
> Something is using i386_set_ldt() static ldt allocations.  We
> added the warning message to detect usage of these allocations
> so they could be changed to dynamic allocations.
> 
> Our threads libraries make use of LDTs on i386, so having
> other code also use (possibly) the same LDT would break
> things.
> 
> > Only ode still exists which is:
> > 541  ??  S      0:15,50 /usr/X11R6/bin/XFree86 -auth /var/run/xauth/A:0-2CitM
> 
> What is ode?  Typo?  pid?
> 
> I don't see how XFree86 can use i386_set_ldt().  It doesn't
> reference it on my box:
> 
>   $ nm /usr/X11R6/bin/XFree86 | grep ldt
>   $

XFree86 loads various modules from /usr/X11R6/lib/modules.  That said, I
could find nothing about ldts being used anywhere in the source
(grepping for LDT, sldt, and set_ldt).

Perhaps the nvidia driver is being used?  That's the only thing I could
think of.

-- 
Eric Anholt                                eta at lclark.edu          
http://people.freebsd.org/~anholt/         anholt at FreeBSD.org