On Tue, Sep 20, 2005 at 05:05:11PM -0400, B. Bogart wrote:
> Hey again,
>
> If this is any help I did manage to get pdp and Gem loaded with the
> LD_ASSUME_KERNEL=2.4.19 by renaming the tls libnvidia so LD could not
> find it.
>
> So the trace I now get is:
If the bug occurs with both LinuxThrea
Hey again,
If this is any help I did manage to get pdp and Gem loaded with the
LD_ASSUME_KERNEL=2.4.19 by renaming the tls libnvidia so LD could not
find it.
So the trace I now get is:
Program received signal SIGTERM, Terminated.
---Type to continue, or q to quit---
[Switching to Thread 16384
Hi Joerg,
I tried seeting this variable but PD then fails to load the Gem object
due to:
Gem.pd_linux: libnvidia-tls.so.1 cannot handle TLS data
I also tried LD_ASSUME_KERNEL as 2.4.0 and 2.4.20 with the same results.
I also thought I could recompile the nvidia module with
LD_ASSUME_KERNEL=2.4
Well, you can try http://people.redhat.com/drepper/assumekernel.html
LD_ASSUME_KERNEL=2.4.19
That will avoid NPTL and should use the libc in /lib instead of /lib/tls
See how that works. It could be that pd/gem tries to do multiple
thread_joins which will fail except in old pthreads.
On T
Hello,
Ok well what happens is I try and set the v4l channel, then the
application freezes (pd/gem). I manually kill the application and look
at the trace and its sitting in pthread_join() just before the syscall.
pthread_join is all I have to go on, how do I check what threads are
running? How d
On Tue, Sep 20, 2005 at 01:23:12PM -0400, B. Bogart wrote:
> Hello all,
>
> I tried on debian-user without any luck, perhaps someone on here will
> have an idea how I can further debug this issue. Sorry for anyone who
> got tired of seeing this on debian-user.
>
> I'm running a stock sarge machin
On Tue, Sep 20, 2005 at 11:32:14AM -0700, Joerg wrote:
> See below output. I have a dumb question, if I remember correctly,
> running /lib/libc.so.6 used to include NPTL. Is that no longe the
> case? The threading problems with 2.6.x + libc 2.3.2 were related to
> the NPTL version, no? Now I se
hi Joerg,
Thanks for very much for responding.
Here is my output, looks to be identical to yours.
GNU C Library stable release version 2.3.5, by Roland McGrath et al.
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warr
See below output. I have a dumb question, if I remember correctly,
running /lib/libc.so.6 used to include NPTL. Is that no longe the
case? The threading problems with 2.6.x + libc 2.3.2 were related to
the NPTL version, no? Now I seeno more NPTL in 2.3.5 or even the
current 2.3.2. Maybe I'm
Hello all,
I tried on debian-user without any luck, perhaps someone on here will
have an idea how I can further debug this issue. Sorry for anyone who
got tired of seeing this on debian-user.
I'm running a stock sarge machine with the 32bit 2.6.8 kernel on a AMD64
3200+ machine. I'm using some u
10 matches
Mail list logo
