search for: nptl

Hello, sorry for my later answer. so, after i started libvirtd (no vm´s running) and attach gdb i get the following threads (gdb) info thread Id Target Id Frame 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 10 Thread 0x7f18fe74d700 (LWP 20696) "libvirtd" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 9 Thread 0x7f18fdf4c700 (LWP 20697) "libvirtd" pthread_cond_wait@@GLIBC_2....

...>> so, after i started libvirtd (no vm´s running) and attach gdb i get the >> following threads >> >> (gdb) info thread >> Id Target Id Frame >> 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" >> pthread_cond_wait@@GLIBC_2.3.2 () at >> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 >> 10 Thread 0x7f18fe74d700 (LWP 20696) "libvirtd" >> pthread_cond_wait@@GLIBC_2.3.2 () at >> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 >> 9 Thread 0x7f18fdf4c700 (LWP 20697) "libvir...

Hi Michal, thank you for your answer. so if i understand that correctly, no matter if i shutdown or destroy the domain and no matter if it is a transient or an persistent vm, the thread should disappear, right? in my case they still exist, also an hour after i destroy the domain (and don´t start any new one). i use libvirt-1.1.35 on fedora core 20, for information. all the best max    

...lo, > > sorry for my later answer. > > so, after i started libvirtd (no vm´s running) and attach gdb i get the following threads > > (gdb) info thread > Id Target Id Frame > 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 > 10 Thread 0x7f18fe74d700 (LWP 20696) "libvirtd" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 > 9 Thread 0x7f18fdf4c700 (LWP 20697) "libvirtd" pthread_cond_wa...

...libvirtd (no vm´s running) and attach gdb i get the >>> following threads >>> >>> (gdb) info thread >>> Id Target Id Frame >>> 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" >>> pthread_cond_wait@@GLIBC_2.3.2 () at >>> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 >>> 10 Thread 0x7f18fe74d700 (LWP 20696) "libvirtd" >>> pthread_cond_wait@@GLIBC_2.3.2 () at >>> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 >>> 9 Thread 0x7f18fdf4c700 (LWP 206...

...have been using CentOS 4 on a UML (User-Mode Linux) box for some time (>1 year) and have kept up to date with updates. I think I started on CentOS 4.1 and have progressively "yum update"'d since. User-Mode Linux, or at least the version of it that my hosts use, doesn't support NPTL. This hasn't been a problem to date; I've just moved /lib/tls out of the way, as described in http://www.mythic-beasts.com/umlwiki/wiki.pl?2.6_And_TLS . No problems at all, until a recent libstdc++ update. The old version was: libstdc++-3.4.5-2 but with an update to CentOS 4.4 the new ve...

Hi, My main systems are Gentoo based. I am investigating switching to NPTL on one of them that uses a couple of different versions of Wine built from source. In doing the research I found that the Gentoo ebuilds for Wine use NPTL. Does this mean that if I switch to NPTL that I must recompile my source-caode based versions of Wine? If so, can someone tell my what options I...

root at memorex:~# winecfg wine: glibc >= 2.3 without NPTL or TLS is not a supported combination. It will most likely crash. Please upgrade to a glibc with NPTL support. wine: creating configuration directory '/root/.wine'... wine: glibc >= 2.3 without NPTL or TLS is not a supported combination. It will most likely crash. Please upgr...

...no error-messages, no crash, noting in "dmesg" or "xl dmesg". When i attached to the libvirtd via gdb and do a "info thread", i get the following: Id Target Id Frame 21 Thread 0x7f792a92c700 (LWP 1312) "libvirtd" __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 20 Thread 0x7f792a12b700 (LWP 1313) "libvirtd" __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 19 Thread 0x7f792992a700 (LWP 1314) "libvirtd" __lll_lock_wait () at ../nptl/sysdeps/unix/sysv...

Hi All I've bought a TDM400P and need some help with configuration. Can you tell me what to do ? I've tried to install and the message below has appeared: [root@voip asterisk]# modprobe zaptel [root@voip asterisk]# modprobe wcfxo /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o: insmod /lib/modules/2.4.22-1.2115....

When I do a yum update I get a couple of dependency issues: I see this one on every box I try to upgrade.. Package nptl-devel needs glibc-devel = 2.3.2-95.33, this is not available. I've only seen this one a couple of times.. Package up2date needs rpm >= 4.2.3-24_nonptl, this is not available. Tim

...ight get some help or a better explanation of this: /ADT/APInt.h:1217: uint64_t llvm::APInt::getZExtValue() const: Assertion `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6eb4d05 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. in ../nptl/sysdeps/unix/sysv/linux/raise.c (gdb) bt #0 0x00007ffff6eb4d05 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007ffff6eb8ab6 in abort () at abort.c:92...

Hello, I'm running Slackware 10.2 with kernel 2.4.31, and I'm trying to install Wine. I have glibc vers 2.3.5. Linux thread libraries are saved in the /lib directory, while NPTL libraries are saved in /lib/ tls. Other than the source I downloaded I have no other version of wine on my machine. I ran '.configure --with-nptl=/lib/tls' and everything seemed to compile properly, but Wine gives me an error that glibc without nptl or tls is unsupported and will probably...

>>> Hi all >>> >>> Thanks to Milan I am able to get further with xen and reiser4 >>> >>> - In swap line 6 and 7 status_flags.c >>> >>> #include <linux/bio.h> >>> #include <linux/page-flags.h> >>> >>> >>> - PACKED is redefined, but the definitions are the same, so the gcc >>>

Hello, I am a complete newbie to dovecot, but do have reasonable experience in compiling Unix/Linux software. I am currently trying to do a cross-compile of dovecot-2.29.1 to be used on my home office Thecus NAS (host: Thecus kernel 2.6.33 on 32-bit Intel Atom: "i686-nptl-linux-gnu"; my build machine has Ubuntu 16.04.2 LTS) "from ground up", i.e. I need to build and provide all dovecot dependencies from within my module. My compiler toolchain (using gcc-5.2.0) has been set up properly using ct-ng and works completely fine. I also have already suc...

I'm not sure what has happened but for some reason my CentOS 4 system is showing me using default threads?? # getconf GNU_LIBPTHREAD_VERSION linuxthreads-0.10 # uname -rimpv 2.6.9-42.0.10.EL #1 Tue Feb 27 09:24:42 EST 2007 i686 athlon i386 I could have sworn it used to show: NPTL 2.3.4 Like a couple other machines. Any ideas what might have changed this or how I get it back??? the devel package for NPTL is installed but from my understanding that has little to do with why getconf is showing this. I'm feeling new here :-) TIA -- Lonny -- "To mess up a Linux box,...

Hi *, i run several CentOS4 systems as xen3 domU, and all of them suffer from the well-known-to-this-list db4/nptl bug: <https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=91933> so that i needed to rebuild db4 to make cyrus-imapd work. But a member of the centos devel ML reported that he has no problem at all running cyrus-imapd. Our setups are almost identical (dom0=FC6, xen-3.0-x86_32p, domU=Cent...

...{fd=46, events=POLLIN|POLLERR|POLLHUP}, {fd=50, >> events=POLLIN|POLLERR|POLLHUP}, ...], 43, 5000 >> >> # gdb -p 5786 >> (gdb) thread apply all bt >> >> Thread 17 (Thread 0x7f411a9d7700 (LWP 5788)): >> #0 pthread_cond_wait@@GLIBC_2.3.2 () at >> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 >> #1 0x00007f4129c2a2e6 in virCondWait (c=c@entry=0x7f412b18ebb8, >> m=m@entry=0x7f412b18eb90) at util/virthread.c:154 >> #2 0x00007f4129c2ada3 in virThreadPoolWorker >> (opaque=opaque@entry=0x7f412b183ab0) at util/vi...

From: alex at milivojevic.org > At various points in time Red Hat made some somewhat conflicting > decisions. The first was that Red Hat distributions must have NPTL. > For NPTL support, there are two components of system where it is > implemented, kernel and glibc. Back then glibc supported NPTL only > for i686. NPTL support was later backported to i586 and i486. Also remember that sometimes someone has to adopt something before the issues are well...

(Me Too ++: I''m running into the same issues with a non-nptl DB4 and rpm on rhel4) And making it even more interesting: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release-notes/as-x86/ "Red Hat Enterprise Linux 5 will no longer include support for LinuxThreads. Therefore, applications that require LinuxThreads support must be updat...