From owner-freebsd-threads@FreeBSD.ORG Sun Jun 5 06:46:22 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14ADF16A41C for ; Sun, 5 Jun 2005 06:46:22 +0000 (GMT) (envelope-from ant@emict.com) Received: from mail.emict.com (brig.emict.com [212.90.172.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB39343D48 for ; Sun, 5 Jun 2005 06:46:21 +0000 (GMT) (envelope-from ant@emict.com) Received: from [10.0.0.232] (unknown [10.0.0.232]) by mail.emict.com (Postfix) with ESMTP id BCE2227666 for ; Sun, 5 Jun 2005 09:46:19 +0300 (EEST) From: Andriy Tkachuk Organization: eMICT To: freebsd-threads@freebsd.org Date: Sun, 5 Jun 2005 09:46:17 +0300 User-Agent: KMail/1.8 References: <200506031315.04920.ant@emict.com> <200506041607.00513.ant@emict.com> In-Reply-To: <200506041607.00513.ant@emict.com> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506050946.17421.ant@emict.com> Subject: Re: pthreaded program killed by sigsegv from time to time under load X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 06:46:22 -0000 btw. it works fine with -lc_r From owner-freebsd-threads@FreeBSD.ORG Sun Jun 5 14:23:23 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B760016A41C for ; Sun, 5 Jun 2005 14:23:23 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51EEB43D48 for ; Sun, 5 Jun 2005 14:23:23 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j55ENELn021652; Sun, 5 Jun 2005 10:23:14 -0400 (EDT) Date: Sun, 5 Jun 2005 10:23:14 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Andriy Tkachuk In-Reply-To: <200506050946.17421.ant@emict.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-threads@freebsd.org Subject: Re: pthreaded program killed by sigsegv from time to time under load X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 14:23:23 -0000 On Sun, 5 Jun 2005, Andriy Tkachuk wrote: > btw. it works fine with -lc_r You need to tell us how to reproduce it. Otherwise there is nothing we can do. Remember that libthr and libpthread run differently than libc_r. Timing is much different. -- DE From owner-freebsd-threads@FreeBSD.ORG Sun Jun 5 21:09:23 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27DDE16A41C for ; Sun, 5 Jun 2005 21:09:23 +0000 (GMT) (envelope-from lewissaunders@myrealbox.com) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EFD543D5F for ; Sun, 5 Jun 2005 21:09:20 +0000 (GMT) (envelope-from lewissaunders@myrealbox.com) Received: from sweet lewissaunders [81.101.64.94] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 1.5 $ on Linux via secured & encrypted transport (TLS); Sun, 05 Jun 2005 15:09:18 -0600 Message-ID: <000301c56a12$d5bce850$5e406551@sweet> From: "Lewis Saunders" To: Date: Sun, 5 Jun 2005 22:06:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: 5.4-RELEASE fails libpthread tests X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 21:09:23 -0000 Hi, Is it normal for most of the tests in /usr/src/lib/libpthread/test/ to fail? I've just upgraded from 5.3-RELEASE to 5.4-RELEASE, and running make there gives: Test static library: -------------------------------------------------------------------------- Test c_user c_system c_total chng passed/FAILED h_user h_system h_total % chng -------------------------------------------------------------------------- hello_d 0.00 0.00 0.00 passed -------------------------------------------------------------------------- hello_s 0.00 0.01 0.01 passed -------------------------------------------------------------------------- join_leak_d 0.00 0.07 0.07 *** FAILED *** -------------------------------------------------------------------------- mutex_d 0.00 144.76 144.76 *** FAILED *** -------------------------------------------------------------------------- sem_d 0.00 0.00 0.00 *** FAILED *** -------------------------------------------------------------------------- sigsuspend_d 0.00 0.00 0.00 passed -------------------------------------------------------------------------- sigwait_d 0.00 0.00 0.00 *** FAILED *** -------------------------------------------------------------------------- guard_s.pl 0.00 0.29 0.29 *** FAILED *** (30/30 failed) -------------------------------------------------------------------------- propagate_s.pl 0.00 0.07 0.07 *** FAILED *** (1/1 failed) -------------------------------------------------------------------------- Totals 0.00 0.01 0.01 0.00 3 / 9 passed (33.33%) 0.00 0.00 0.00 0.00% -------------------------------------------------------------------------- *** Error code 1 Stop in /usr/src/lib/libpthread/test I'm afraid I never thought to run the tests on 5.3. The guard tests also dump core: Core was generated by `guard_b'. Program terminated with signal 11, Segmentation fault. #0 0x0805c17f in kse_thr_interrupt () (gdb) bt full #0 0x0805c17f in kse_thr_interrupt () No symbol table info available. (gdb) info threads * 4 LWP 100073 0x0805c17f in kse_thr_interrupt () 3 Thread 4 (sleeping) 0x0804a2eb in _thr_sched_switch_unlocked () 2 Thread 3 (LWP 100106) 0x0804a3f8 in kse_sched_single () 1 Thread 1 (runnable) 0x0805eb68 in __vfprintf () Do these fail for everyone because things aren't finished yet or is it just me? I'm also having immense difficulties with the new nVIDIA drivers, which are supposedly thread safe now. They seem to make things die in random places and make a mess of the stack (lots of ?? in backtraces, and ldexp() calling itself which really can't happen), and sometimes prevent gdb from switching threads. They even make a program linked with libc_r crash, which worked fine with the previous driver. Would it be worth updating to -CURRENT? Otherwise I might have to port to Linux which would be rather a pity :) Thanks for any advice, Lewis From owner-freebsd-threads@FreeBSD.ORG Mon Jun 6 11:01:58 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0399016A420 for ; Mon, 6 Jun 2005 11:01:58 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD1CB43D1F for ; Mon, 6 Jun 2005 11:01:57 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j56B1vvf065723 for ; Mon, 6 Jun 2005 11:01:57 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j56B1uCn065718 for freebsd-threads@freebsd.org; Mon, 6 Jun 2005 11:01:56 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 6 Jun 2005 11:01:56 GMT Message-Id: <200506061101.j56B1uCn065718@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 11:01:58 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/01/26] threads/76690threads fork hang in child for (-lc_r & -lthr) o [2005/05/11] threads/80887threads ULE with SMP broke libpthread/libthr on 5 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/07/18] kern/20016 threads pthreads: Cannot set scheduling timer/Can o [2000/08/26] kern/20861 threads libc_r does not honor socket timeouts o [2001/01/20] threads/24472threads libc_r does not honor SO_SNDTIMEO/SO_RCVT o [2001/01/25] threads/24632threads libc_r delicate deviation from libc in ha o [2001/01/25] kern/24641 threads pthread_rwlock_rdlock can deadlock o [2001/11/26] bin/32295 threads pthread dont dequeue signals o [2002/02/01] threads/34536threads accept() blocks other threads o [2002/05/25] kern/38549 threads the procces compiled whith pthread stoppe o [2002/06/27] threads/39922threads [PATCH?] Threaded applications executed w o [2002/08/04] kern/41331 threads Pthread library open sets O_NONBLOCK flag o [2003/03/02] threads/48856threads Setting SIGCHLD to SIG_IGN still leaves z o [2003/03/10] threads/49087threads Signals lost in programs linked with libc o [2003/05/08] threads/51949threads thread in accept cannot be cancelled s [2004/03/15] kern/64313 threads FreeBSD (OpenBSD) pthread implicit set/un o [2004/08/26] threads/70975threads unexpected and unreliable behaviour when o [2004/09/14] threads/71725threads Mysql Crashes frequently giving Sock Erro o [2004/10/05] threads/72353threads Assertion fails in /usr/src/lib/libpthrea o [2004/10/07] threads/72429threads threads blocked in stdio (fgets, etc) are o [2004/10/21] threads/72953threads fork() unblocks blocked signals w/o PTHRE o [2004/12/19] threads/75273threads FBSD 5.3 libpthread (KSE) bug o [2004/12/21] threads/75374threads pthread_kill() ignores SA_SIGINFO flag o [2005/01/26] threads/76694threads fork cause hang in dup()/close() function o [2005/03/10] threads/78660threads Java hangs unkillably in STOP state after o [2005/04/08] threads/79683threads svctcp_create() fails if multiple threads o [2005/04/28] threads/80435threads panic on high loads o [2005/05/19] threads/81258threads Thread specific data is sometimes assigne 26 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/05/26] kern/18824 threads gethostbyname is not thread safe o [2000/06/13] kern/19247 threads uthread_sigaction.c does not do anything o [2000/10/21] kern/22190 threads A threaded read(2) from a socketpair(2) f o [2001/09/09] threads/30464threads pthread mutex attributes -- pshared o [2002/05/02] threads/37676threads libc_r: msgsnd(), msgrcv(), pread(), pwri s [2002/07/16] threads/40671threads pthread_cancel doesn't remove thread from o [2004/07/13] threads/69020threads pthreads library leaks _gc_mutex o [2004/09/21] threads/71966threads Mlnet Core Dumped : Fatal error '_pq_inse o [2004/11/21] threads/74180threads KSE problem. Applications those riched ma o [2005/01/20] threads/76513threads libpthread is not working o [2005/04/13] threads/79887threads [patch] freopen() isn't thread-safe o [2005/05/13] threads/80992threads abort() sometimes not caught by gdb depen o [2005/05/26] threads/81534threads [PATCH] libc_r close() will fail on any f 13 problems total. From owner-freebsd-threads@FreeBSD.ORG Mon Jun 6 21:30:22 2005 Return-Path: X-Original-To: freebsd-threads@hub.freebsd.org Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5477816A41F; Mon, 6 Jun 2005 21:30:22 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1029343D48; Mon, 6 Jun 2005 21:30:22 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j56LULkB053198; Mon, 6 Jun 2005 21:30:21 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j56LULt7053194; Mon, 6 Jun 2005 21:30:21 GMT (envelope-from ceri) Date: Mon, 6 Jun 2005 21:30:21 GMT From: Ceri Davies Message-Id: <200506062130.j56LULt7053194@freefall.freebsd.org> To: ceri@FreeBSD.org, perky@FreeBSD.org, freebsd-threads@FreeBSD.org Cc: Subject: Re: threads/20490: Termios timeout parameters, VMIN, VTIME, dont work with lang/python X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 21:30:22 -0000 Synopsis: Termios timeout parameters, VMIN, VTIME, dont work with lang/python Responsible-Changed-From-To: perky->freebsd-threads Responsible-Changed-By: ceri Responsible-Changed-When: Mon Jun 6 21:29:37 GMT 2005 Responsible-Changed-Why: Seems to be a thread library problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=20490 From owner-freebsd-threads@FreeBSD.ORG Mon Jun 6 21:59:59 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEC0616A41C; Mon, 6 Jun 2005 21:59:59 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A76143D49; Mon, 6 Jun 2005 21:59:59 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j56LxtG4023548; Mon, 6 Jun 2005 17:59:55 -0400 (EDT) Date: Mon, 6 Jun 2005 17:59:44 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Ceri Davies In-Reply-To: <200506062130.j56LULt7053194@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: perky@freebsd.org, freebsd-threads@freebsd.org Subject: Re: threads/20490: Termios timeout parameters, VMIN, VTIME, dont work with lang/python X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 22:00:00 -0000 On Mon, 6 Jun 2005, Ceri Davies wrote: > Synopsis: Termios timeout parameters, VMIN, VTIME, dont work with lang/python > > Responsible-Changed-From-To: perky->freebsd-threads > Responsible-Changed-By: ceri > Responsible-Changed-When: Mon Jun 6 21:29:37 GMT 2005 > Responsible-Changed-Why: > Seems to be a thread library problem. You might as well close this; it isn't going to be fixed. It's only a problem with libc_r. Works fine with libpthread and libthr. -- DE From owner-freebsd-threads@FreeBSD.ORG Thu Jun 9 01:59:51 2005 Return-Path: X-Original-To: freebsd-threads@FreeBSD.org Delivered-To: freebsd-threads@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCAA616A41C for ; Thu, 9 Jun 2005 01:59:51 +0000 (GMT) (envelope-from dan@langille.org) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id A488B43D4C for ; Thu, 9 Jun 2005 01:59:51 +0000 (GMT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 7A78D3D48 for ; Fri, 10 Jun 2005 17:58:41 -0400 (EDT) From: "Dan Langille" To: freebsd-threads@FreeBSD.org Date: Wed, 08 Jun 2005 21:59:50 -0400 MIME-Version: 1.0 Message-ID: <42A76A56.6869.5459055A@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Cc: Subject: no kernel threads => no true multi tasking? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 01:59:52 -0000 Folks, I don't know enough to reply this this post: http://article.gmane.org/gmane.comp.sysutils.backup.bacula.devel/2879 The part I'm concerned about: "As far as I know, this only happens on FreeBSD 4.11 systems where there are no kernel threads and hence no true multi-tasking. More precisely, there is no task scheduling (time-sharing) between the threads." Can someone help educate me please? thanks -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ From owner-freebsd-threads@FreeBSD.ORG Thu Jun 9 02:11:08 2005 Return-Path: X-Original-To: freebsd-threads@FreeBSD.org Delivered-To: freebsd-threads@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4396F16A41C for ; Thu, 9 Jun 2005 02:11:08 +0000 (GMT) (envelope-from samy@kerneled.org) Received: from perseus.interservers.com (perseus.interservers.com [65.202.242.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0141143D1D for ; Thu, 9 Jun 2005 02:11:07 +0000 (GMT) (envelope-from samy@kerneled.org) Received: from [212.76.83.11] (helo=localhost.localdomain) by perseus.interservers.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.43) id 1DgCVk-0001bU-23; Wed, 08 Jun 2005 22:11:12 -0400 From: Samy Al Bahra To: Dan Langille In-Reply-To: <42A76A56.6869.5459055A@localhost> References: <42A76A56.6869.5459055A@localhost> Content-Type: text/plain Organization: Kerneled.org Date: Thu, 09 Jun 2005 05:11:00 +0300 Message-Id: <1118283060.1729.6.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - perseus.interservers.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - kerneled.org X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-threads@FreeBSD.org Subject: Re: no kernel threads => no true multi tasking? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 02:11:08 -0000 On Wed, 2005-06-08 at 21:59 -0400, Dan Langille wrote: > Folks, > > I don't know enough to reply this this post: > > http://article.gmane.org/gmane.comp.sysutils.backup.bacula.devel/2879 > > The part I'm concerned about: > > "As far as I know, this only happens on FreeBSD 4.11 systems where > there are no kernel threads and hence no true multi-tasking. More > precisely, there is no task scheduling (time-sharing) between the > threads." 4.X used a user-space scheduling system (longjmp-based). So, basically, threads operate with-in the time-slice of the process (every thread would gratuitiously pass control over to another thread). The Linux threads FAQ covers this, it is available here: http://www.tldp.org/FAQ/Threads-FAQ/Types.html -- Samy Al Bahra