Re: licq & KSE - resolved

2003-12-03 Thread Daniel Eischen
On Wed, 3 Dec 2003, Alexander Motin wrote: > Daniel Eischen wrote: > > > >>From which system is this? The nvidia or the ATI? We know nvidia > > I try to use same HDD on two systems. On system with ATI video I only > disable nvidia kernel module loading and change X driver. Right, it's not onl

Re: licq & KSE - resolved

2003-12-03 Thread Alexander Motin
Daniel Eischen wrote: If I use libkse I get: kernel: Warning: pid 25341 used static ldt allocation. kernel: See the i386_set_ldt man page for more info in my messages. When I use libc_r I do not get this messages. I'm sorry. Messages seems to be independent from library. I get messages with both l

Re: licq & KSE

2003-12-02 Thread David Xu
Daniel Eischen wrote: Do you know what port this belongs to and if it is built from source? mplayer also used static ldt allocations, but I fixed that port. Hmm, I found multimedia/libxine that might be the culprit. I'll look into submitting a patch for that. Search word "win32" in page http:/

Re: licq & KSE

2003-12-02 Thread Daniel Eischen
On Wed, 3 Dec 2003, David Xu wrote: > Daniel Eischen wrote: > > >It is not libkse that is causing the messages. It is some library > >or driver that licq is using. The kernel spews these messages > >whenever something uses static LDT allocation. We know that nvidia > >drivers and/or their Open

Re: licq & KSE

2003-12-02 Thread David Xu
Daniel Eischen wrote: It is not libkse that is causing the messages. It is some library or driver that licq is using. The kernel spews these messages whenever something uses static LDT allocation. We know that nvidia drivers and/or their OpenGL library do this, and they have been notified of it

Re: licq & KSE

2003-12-02 Thread Jeremy Messenger
On Tue, 2 Dec 2003 15:58:07 -0500 (EST), Daniel Eischen <[EMAIL PROTECTED]> wrote: On Tue, 2 Dec 2003, Alexander Motin wrote: Daniel Eischen wrote: > On Tue, 2 Dec 2003, Alexander Motin wrote: > >>Alexander Motin wrote: >> >>>If I use libkse I get: >>> kernel: Warning: pid 25341 used static ldt

Re: licq & KSE

2003-12-02 Thread Daniel Eischen
On Tue, 2 Dec 2003, Alexander Motin wrote: > Daniel Eischen wrote: > > On Tue, 2 Dec 2003, Alexander Motin wrote: > > > >>Alexander Motin wrote: > >> > >>>If I use libkse I get: > >>> kernel: Warning: pid 25341 used static ldt allocation. > >>> kernel: See the i386_set_ldt man page for more info

Re: licq & KSE

2003-12-02 Thread Alexander Motin
Daniel Eischen wrote: On Tue, 2 Dec 2003, Alexander Motin wrote: Alexander Motin wrote: If I use libkse I get: kernel: Warning: pid 25341 used static ldt allocation. kernel: See the i386_set_ldt man page for more info in my messages. When I use libc_r I do not get this messages. I'm sorry. Messag

Re: licq & KSE

2003-12-02 Thread Daniel Eischen
On Tue, 2 Dec 2003, Mark Dixon wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday 02 Dec 2003 14:05, Daniel Eischen wrote: > > > > libthr, libkse, and nvidia drivers/OpenGL use LDTs and %gs. > > nvidia drivers (and/or their version of OpenGL) stomp on > > the LDTs/%gs that bo

Re: licq & KSE

2003-12-02 Thread Daniel Eischen
On Tue, 2 Dec 2003, Alexander Motin wrote: > Alexander Motin wrote: > > If I use libkse I get: > > kernel: Warning: pid 25341 used static ldt allocation. > > kernel: See the i386_set_ldt man page for more info > > in my messages. > > When I use libc_r I do not get this messages. > > I'm sorry.

Re: licq & KSE

2003-12-02 Thread Mark Dixon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 02 Dec 2003 14:05, Daniel Eischen wrote: > > libthr, libkse, and nvidia drivers/OpenGL use LDTs and %gs. > nvidia drivers (and/or their version of OpenGL) stomp on > the LDTs/%gs that both libthr and libkse use. Have nvidia indicated if / w

Re: licq & KSE

2003-12-02 Thread Daniel Eischen
On Tue, 2 Dec 2003, Alexander Motin wrote: > Daniel Eischen wrote: > > You haven't told me if you are getting static LDT warnings > > out of the kernel (check /var/log/messages). > If I use libkse I get: > kernel: Warning: pid 25341 used static ldt allocation. > kernel: See the i386_set_ldt ma

Re: licq & KSE

2003-12-02 Thread Alexander Motin
Alexander Motin wrote: licq 1.2.7 installed from ports does not works on 5.2-BETA with mapping libc_r to libkse: %licq -d0 -p qt-gui -- -noxim Fatal error 'No current thread. ' at line 318 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2) I just built and installed this under -curre

Re: licq & KSE

2003-12-02 Thread Daniel Eischen
On Tue, 2 Dec 2003, Alexander Motin wrote: > Daniel Eischen wrote: > >>licq 1.2.7 installed from ports does not works on 5.2-BETA with mapping > >>libc_r to libkse: > >> > >>%licq -d0 -p qt-gui -- -noxim > >>Fatal error 'No current thread. > >>' at line 318 in file /usr/src/lib/libpthread/thread/

Re: licq & KSE

2003-12-02 Thread Alexander Motin
Daniel Eischen wrote: licq 1.2.7 installed from ports does not works on 5.2-BETA with mapping libc_r to libkse: %licq -d0 -p qt-gui -- -noxim Fatal error 'No current thread. ' at line 318 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2) I just built and installed this under -current a

Re: licq & KSE

2003-12-01 Thread Daniel Eischen
On Mon, 1 Dec 2003, Alexander Motin wrote: > Hi! > > licq 1.2.7 installed from ports does not works on 5.2-BETA with mapping > libc_r to libkse: > > %licq -d0 -p qt-gui -- -noxim > Fatal error 'No current thread. > ' at line 318 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2) I ju

Re: licq & KSE

2003-12-01 Thread Daniel Eischen
On Mon, 1 Dec 2003, Alexander Motin wrote: > Hi! > > licq 1.2.7 installed from ports does not works on 5.2-BETA with mapping > libc_r to libkse: > > %licq -d0 -p qt-gui -- -noxim > Fatal error 'No current thread. > ' at line 318 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2) > >

licq & KSE

2003-12-01 Thread Alexander Motin
Hi! licq 1.2.7 installed from ports does not works on 5.2-BETA with mapping libc_r to libkse: %licq -d0 -p qt-gui -- -noxim Fatal error 'No current thread. ' at line 318 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2) And after saying this it begins eat all free CPU. If I remove thi