From owner-freebsd-threads@FreeBSD.ORG Mon Jul 25 04:39:35 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 EE26A16A41F for ; Mon, 25 Jul 2005 04:39:35 +0000 (GMT) (envelope-from Ady_Li@trendmicro.com.cn) Received: from udciscan05.udc.trendmicro.com (udciscan05.udc.trendmicro.com [66.35.255.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A11A43D45 for ; Mon, 25 Jul 2005 04:39:34 +0000 (GMT) (envelope-from Ady_Li@trendmicro.com.cn) Received: from localhost-imss.udc.trendmicro.com (localhost [127.0.0.1]) by udciscan05.udc.trendmicro.com (Postfix) with ESMTP id C78BD1826CA; Sun, 24 Jul 2005 21:39:28 -0700 (PDT) Received: from udcexbh03-vs2.us.trendnet.org (udcexbh03.udc.trendmicro.com [66.35.252.73]) by udciscan05.udc.trendmicro.com (Postfix) with ESMTP id 8BB931826C8; Sun, 24 Jul 2005 21:39:28 -0700 (PDT) Received: from adcexbh02.tw.trendnet.org ([202.133.236.202]) by udcexbh03-vs2.us.trendnet.org with Microsoft SMTPSVC(6.0.3790.211); Sun, 24 Jul 2005 21:39:29 -0700 Received: from cnexmail03.tw.trendnet.org ([10.28.128.9]) by adcexbh02.tw.trendnet.org with Microsoft SMTPSVC(6.0.3790.211); Mon, 25 Jul 2005 12:39:26 +0800 Received: from CDCEXMAIL01.tw.trendnet.org ([10.28.144.51]) by cnexmail03.tw.trendnet.org with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Jul 2005 12:39:25 +0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Jul 2005 12:39:23 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: system scope threads entering STOP state Thread-Index: AcWQ0tTFTg5FsgJgRGWwV7U9wShQvw== From: To: X-OriginalArrivalTime: 25 Jul 2005 04:39:25.0755 (UTC) FILETIME=[D5FC70B0:01C590D2] Cc: Subject: system scope threads entering STOP state 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, 25 Jul 2005 04:39:36 -0000 Dear all, I have found this program too, I wrote a backgound server program which= create out 14=0D SYSTEM_SCOPE threads, and fork a child process out in main-thread every= inteval-times=0D and waitpid it with NOHUP, but run for sometimes, this program would be in= STOP state,=0D and unkillabled=2E By the way, This occasion was found often in machines with single CPU, Our= QA didnot tell me=0D this question when they run it with few clients=2E But when they launch= about 500 client-processes to connect to my program in the same machine, my program will be stoped=2E= But In a 2-cpu-machine,=0D this occasion occurs fewly=2E I found Mr guy helmer has confronted this problem, could u tell me how did= u solve it? Thank in advance for any helps=2E Best Regards, Ady Li [TEL](86)25- 83190788x656 =0D TREND MICRO EMAIL NOTICE The information contained in this email and any attachments is confidential= and may be subject to copyright or other intellectual property protection= =2E If you are not the intended recipient, you are not authorized to use or= disclose this information, and we request that you notify us by reply mail= or telephone and delete the original message from your mail system=2E From owner-freebsd-threads@FreeBSD.ORG Mon Jul 25 06:16:30 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 E86C916A41F for ; Mon, 25 Jul 2005 06:16:30 +0000 (GMT) (envelope-from warlock@voip.kg) Received: from mail.elcat.kg (imap.elcat.kg [212.42.96.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id E234C43D5C for ; Mon, 25 Jul 2005 06:16:28 +0000 (GMT) (envelope-from warlock@voip.kg) Received: from localhost (localhost [127.0.0.1]) by mail.elcat.kg (Postfix) with ESMTP id 4D008419706; Mon, 25 Jul 2005 12:16:23 +0600 (KGST) Received: from mail.elcat.kg ([127.0.0.1]) by localhost (imap.elcat.kg [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54406-17; Mon, 25 Jul 2005 12:16:22 +0600 (KGST) Received: from warcomp.elcat.kg (warcomp.elcat.kg [212.42.96.26]) by mail.elcat.kg (Postfix) with ESMTP id 9680F4196B2; Mon, 25 Jul 2005 12:16:22 +0600 (KGST) From: Roman Streltsov Organization: Elcat To: freebsd-threads@freebsd.org Date: Mon, 25 Jul 2005 12:16:22 +0600 User-Agent: KMail/1.8.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507251216.22500.warlock@voip.kg> X-Virus-Scanned: by amavisd-new at elcat.kg X-Spam-Status: No, hits=-56.743 tagged_above=-999 required=999 tests=[ALL_TRUSTED=-10, AWL=3.257, LOCAL_RCVD=-50] X-Spam-Level: Cc: Ady_Li@trendmicro.com.cn Subject: Re: system scope threads entering STOP state 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, 25 Jul 2005 06:16:31 -0000 It looks like a failure in signal handling. The faster box has much more chances to avoid extreme conditions. On Monday 25 July 2005 10:39, Ady_Li@trendmicro.com.cn wrote: > > Dear all, > > I have found this program too, I wrote a backgound server program which create out 14 > SYSTEM_SCOPE threads, and fork a child process out in main-thread every inteval-times > and waitpid it with NOHUP, but run for sometimes, this program would be in STOP state, > and unkillabled. > > By the way, This occasion was found often in machines with single CPU, Our QA didnot tell me > this question when they run it with few clients. But when they launch about 500 client-processes to > connect to my program in the same machine, my program will be stoped. But In a 2-cpu-machine, > this occasion occurs fewly. > > I found Mr guy helmer has confronted this problem, could u tell me how did u solve it? > > Thank in advance for any helps. > > > Best Regards, > Ady Li > [TEL](86)25- 83190788x656 > > > > TREND MICRO EMAIL NOTICE > The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" > From owner-freebsd-threads@FreeBSD.ORG Mon Jul 25 06:29:25 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 8168B16A41F for ; Mon, 25 Jul 2005 06:29:25 +0000 (GMT) (envelope-from julian@elischer.org) Received: from postoffice.vicor-nb.com (postoffice.vicor.com [69.26.56.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 330CA43D46 for ; Mon, 25 Jul 2005 06:29:25 +0000 (GMT) (envelope-from julian@elischer.org) Received: from localhost (localhost [127.0.0.1]) by postoffice.vicor-nb.com (Postfix) with ESMTP id BAD504CE90B; Sun, 24 Jul 2005 23:29:24 -0700 (PDT) Received: from postoffice.vicor-nb.com ([127.0.0.1]) by localhost (postoffice.vicor-nb.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 65837-03; Sun, 24 Jul 2005 23:29:24 -0700 (PDT) Received: from [208.206.78.97] (julian.vicor-nb.com [208.206.78.97]) by postoffice.vicor-nb.com (Postfix) with ESMTP id 25E104CE8F1; Sun, 24 Jul 2005 23:29:24 -0700 (PDT) Message-ID: <42E486C3.9060702@elischer.org> Date: Sun, 24 Jul 2005 23:29:23 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050629 X-Accept-Language: en, hu MIME-Version: 1.0 To: Roman Streltsov References: <200507251216.22500.warlock@voip.kg> In-Reply-To: <200507251216.22500.warlock@voip.kg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postoffice.vicor.com Cc: Ady_Li@trendmicro.com.cn, freebsd-threads@freebsd.org Subject: Re: system scope threads entering STOP state 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, 25 Jul 2005 06:29:25 -0000 it may be worth looking at libthr too as it (the alternate threading library) is sufficiently different in this regard. Roman Streltsov wrote: >It looks like a failure in signal handling. The faster box has much more chances to avoid extreme conditions. > > >On Monday 25 July 2005 10:39, Ady_Li@trendmicro.com.cn wrote: > > >>Dear all, >> >>I have found this program too, I wrote a backgound server program which create out 14 >>SYSTEM_SCOPE threads, and fork a child process out in main-thread every inteval-times >>and waitpid it with NOHUP, but run for sometimes, this program would be in STOP state, >>and unkillabled. >> >>By the way, This occasion was found often in machines with single CPU, Our QA didnot tell me >>this question when they run it with few clients. But when they launch about 500 client-processes to >> connect to my program in the same machine, my program will be stoped. But In a 2-cpu-machine, >>this occasion occurs fewly. >> >>I found Mr guy helmer has confronted this problem, could u tell me how did u solve it? >> >>Thank in advance for any helps. >> >> >>Best Regards, >>Ady Li >>[TEL](86)25- 83190788x656 >> >> >> >>TREND MICRO EMAIL NOTICE >>The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. >>_______________________________________________ >>freebsd-threads@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-threads >>To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >> >> >> >_______________________________________________ >freebsd-threads@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-threads >To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" > > From owner-freebsd-threads@FreeBSD.ORG Mon Jul 25 07:07:39 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 7D6A716A41F for ; Mon, 25 Jul 2005 07:07:39 +0000 (GMT) (envelope-from Ady_Li@trendmicro.com.cn) Received: from udciscan05.udc.trendmicro.com (udciscan05.udc.trendmicro.com [66.35.255.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D8CE43D4C for ; Mon, 25 Jul 2005 07:07:38 +0000 (GMT) (envelope-from Ady_Li@trendmicro.com.cn) Received: from localhost-imss.udc.trendmicro.com (localhost [127.0.0.1]) by udciscan05.udc.trendmicro.com (Postfix) with ESMTP id AA943182658; Mon, 25 Jul 2005 00:07:36 -0700 (PDT) Received: from udcexbh03-vs2.us.trendnet.org (udcexbh03.udc.trendmicro.com [66.35.252.73]) by udciscan05.udc.trendmicro.com (Postfix) with ESMTP id 7382C18264C; Mon, 25 Jul 2005 00:07:36 -0700 (PDT) Received: from adcexbh01.tw.trendnet.org ([202.133.236.201]) by udcexbh03-vs2.us.trendnet.org with Microsoft SMTPSVC(6.0.3790.211); Mon, 25 Jul 2005 00:07:37 -0700 Received: from cnexmail03.tw.trendnet.org ([10.28.128.9]) by adcexbh01.tw.trendnet.org with Microsoft SMTPSVC(6.0.3790.211); Mon, 25 Jul 2005 15:06:55 +0800 Received: from CDCEXMAIL01.tw.trendnet.org ([10.28.144.51]) by cnexmail03.tw.trendnet.org with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Jul 2005 15:06:25 +0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Jul 2005 15:06:04 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: system scope threads entering STOP state Thread-Index: AcWQ4jd30JJ7vxLNQXiFBtZJLFSuZAABM9vQ From: To: , X-OriginalArrivalTime: 25 Jul 2005 07:06:25.0771 (UTC) FILETIME=[5F2013B0:01C590E7] Cc: freebsd-threads@freebsd.org Subject: RE: system scope threads entering STOP state 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, 25 Jul 2005 07:07:39 -0000 if i use vfork instead fork with compiling with libthr, my program will= block in vfork at beginning, if i use fork with compiling with libthr, my program cannot be killed by= input kill -9 -----Original Message----- From: Julian Elischer [mailto:julian@elischer=2Eorg] Sent: 2005=C4=EA7=D4=C225=C8=D5 14:29 To: Roman Streltsov Cc: freebsd-threads@freebsd=2Eorg; Ady Li (RD-CN) Subject: Re: system scope threads entering STOP state it may be worth looking at libthr too as it (the alternate threading library) is sufficiently different in this regard=2E Roman Streltsov wrote: >It looks like a failure in signal handling=2E The faster box has much more= chances to avoid extreme conditions=2E > > >On Monday 25 July 2005 10:39, Ady_Li@trendmicro=2Ecom=2Ecn wrote: > =0D > >>Dear all, >> >>I have found this program too, I wrote a backgound server program which= create out 14 >>SYSTEM_SCOPE threads, and fork a child process out in main-thread every= inteval-times >>and waitpid it with NOHUP, but run for sometimes, this program would be= in STOP state, >>and unkillabled=2E >> >>By the way, This occasion was found often in machines with single CPU, = Our QA didnot tell me >>this question when they run it with few clients=2E But when they launch= about 500 client-processes to >> connect to my program in the same machine, my program will be stoped=2E= But In a 2-cpu-machine, >>this occasion occurs fewly=2E >> >>I found Mr guy helmer has confronted this problem, could u tell me how= did u solve it? >> >>Thank in advance for any helps=2E >> >> >>Best Regards, >>Ady Li >>[TEL](86)25- 83190788x656 >> >> >> >>TREND MICRO EMAIL NOTICE >>The information contained in this email and any attachments is= confidential and may be subject to copyright or other intellectual= property protection=2E If you are not the intended recipient, you are not= authorized to use or disclose this information, and we request that you= notify us by reply mail or telephone and delete the original message from= your mail system=2E >>_______________________________________________ >>freebsd-threads@freebsd=2Eorg mailing list >>http://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-threads >>To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd= =2Eorg" >> >> =0D >> >_______________________________________________ >freebsd-threads@freebsd=2Eorg mailing list >http://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-threads >To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd= =2Eorg" > =0D > TREND MICRO EMAIL NOTICE The information contained in this email and any attachments is confidential= and may be subject to copyright or other intellectual property protection= =2E If you are not the intended recipient, you are not authorized to use or= disclose this information, and we request that you notify us by reply mail= or telephone and delete the original message from your mail system=2E From owner-freebsd-threads@FreeBSD.ORG Mon Jul 25 11:02:24 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 6C29816A41F for ; Mon, 25 Jul 2005 11:02:24 +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 9E95543D5E for ; Mon, 25 Jul 2005 11:02:23 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6PB2NUK018570 for ; Mon, 25 Jul 2005 11:02:23 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6PB2MP2018564 for freebsd-threads@freebsd.org; Mon, 25 Jul 2005 11:02:22 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 25 Jul 2005 11:02:22 GMT Message-Id: <200507251102.j6PB2MP2018564@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, 25 Jul 2005 11:02:24 -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 Jul 25 11:09:41 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id CF42F16A41F; Mon, 25 Jul 2005 11:09:39 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <42E4C873.5060305@freebsd.org> Date: Mon, 25 Jul 2005 19:09:39 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.8) Gecko/20050605 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ady_Li@trendmicro.com.cn References: In-Reply-To: Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 8bit Cc: julian@elischer.org, warlock@voip.kg, freebsd-threads@freebsd.org Subject: Re: system scope threads entering STOP state 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, 25 Jul 2005 11:09:41 -0000 You should tell us which version of FreeBSD you are using. David Xu Ady_Li@trendmicro.com.cn wrote: >if i use vfork instead fork with compiling with libthr, my program will block in vfork at beginning, >if i use fork with compiling with libthr, my program cannot be killed by input kill -9 > > >-----Original Message----- >From: Julian Elischer [mailto:julian@elischer.org] >Sent: 2005Äê7ÔÂ25ÈÕ 14:29 >To: Roman Streltsov >Cc: freebsd-threads@freebsd.org; Ady Li (RD-CN) >Subject: Re: system scope threads entering STOP state > > >it may be worth looking at libthr too >as it (the alternate threading library) >is sufficiently different in this regard. > > >>Roman Streltsov wrote: >> >> >> >>>It looks like a failure in signal handling. The faster box has much more chances to avoid extreme conditions. >>> >>> >>>On Monday 25 July 2005 10:39, Ady_Li@trendmicro.com.cn wrote: >>> >>> >>> >>> >>>>Dear all, >>>> >>>>I have found this program too, I wrote a backgound server program which create out 14 >>>>SYSTEM_SCOPE threads, and fork a child process out in main-thread every inteval-times >>>>and waitpid it with NOHUP, but run for sometimes, this program would be in STOP state, >>>>and unkillabled. >>>> >>>>By the way, This occasion was found often in machines with single CPU, Our QA didnot tell me >>>>this question when they run it with few clients. But when they launch about 500 client-processes to >>>>connect to my program in the same machine, my program will be stoped. But In a 2-cpu-machine, >>>>this occasion occurs fewly. >>>> >>>>I found Mr guy helmer has confronted this problem, could u tell me how did u solve it? >>>> >>>>Thank in advance for any helps. >>>> >>>> >>>>Best Regards, >>>>Ady Li >>>>[TEL](86)25- 83190788x656 >>>> >>>> >>>> >>>>TREND MICRO EMAIL NOTICE >>>>The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. >>>>_______________________________________________ >>>>freebsd-threads@freebsd.org mailing list >>>>http://lists.freebsd.org/mailman/listinfo/freebsd-threads >>>>To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >>>> >>>> >>>> >>>> >>>> >>>_______________________________________________ >>>freebsd-threads@freebsd.org mailing list >>>http://lists.freebsd.org/mailman/listinfo/freebsd-threads >>>To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >>> >>> >>> >>> >> >>TREND MICRO EMAIL NOTICE >>The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. >>_______________________________________________ >>freebsd-threads@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-threads >>To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >> >> >> >> From owner-freebsd-threads@FreeBSD.ORG Mon Jul 25 12:23:14 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 02B4C16A41F for ; Mon, 25 Jul 2005 12:23:14 +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 6E08943D46 for ; Mon, 25 Jul 2005 12:23:13 +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 j6PCN9d7006048; Mon, 25 Jul 2005 08:23:09 -0400 (EDT) Date: Mon, 25 Jul 2005 08:23:09 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Julian Elischer In-Reply-To: <42E486C3.9060702@elischer.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: Ady_Li@trendmicro.com.cn, Roman Streltsov , freebsd-threads@freebsd.org Subject: Re: system scope threads entering STOP state 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, 25 Jul 2005 12:23:14 -0000 On Sun, 24 Jul 2005, Julian Elischer wrote: > it may be worth looking at libthr too > as it (the alternate threading library) > is sufficiently different in this regard. If there's a problem with libpthread, I suspect it's in the kernel, so it should be present for libthr as well. The user library does nothing special for SIGSTOP nor waitXXX(). -- DE From owner-freebsd-threads@FreeBSD.ORG Mon Jul 25 19:34:12 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 9106316A41F; Mon, 25 Jul 2005 19:34:12 +0000 (GMT) (envelope-from julian@elischer.org) Received: from postoffice.vicor-nb.com (postoffice.vicor.com [69.26.56.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A20843D46; Mon, 25 Jul 2005 19:34:06 +0000 (GMT) (envelope-from julian@elischer.org) Received: from localhost (localhost [127.0.0.1]) by postoffice.vicor-nb.com (Postfix) with ESMTP id 897BD4CE7B7; Mon, 25 Jul 2005 12:34:06 -0700 (PDT) Received: from postoffice.vicor-nb.com ([127.0.0.1]) by localhost (postoffice.vicor-nb.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95779-05; Mon, 25 Jul 2005 12:34:06 -0700 (PDT) Received: from [208.206.78.97] (julian.vicor-nb.com [208.206.78.97]) by postoffice.vicor-nb.com (Postfix) with ESMTP id 1D6A24CE910; Mon, 25 Jul 2005 12:34:06 -0700 (PDT) Message-ID: <42E53EAD.4030205@elischer.org> Date: Mon, 25 Jul 2005 12:34:05 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050629 X-Accept-Language: en, hu MIME-Version: 1.0 To: Daniel Eischen References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postoffice.vicor.com Cc: Ady_Li@trendmicro.com.cn, Roman Streltsov , freebsd-threads@freebsd.org Subject: Re: system scope threads entering STOP state 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, 25 Jul 2005 19:34:12 -0000 Daniel Eischen wrote: >On Sun, 24 Jul 2005, Julian Elischer wrote: > > > >>it may be worth looking at libthr too >>as it (the alternate threading library) >>is sufficiently different in this regard. >> >> > >If there's a problem with libpthread, I suspect it's in the >kernel, so it should be present for libthr as well. The user >library does nothing special for SIGSTOP nor waitXXX(). > > but the kernel handles signals differently between the two threading models so different code paths are followed which measn that it may be an instructive experiment. From owner-freebsd-threads@FreeBSD.ORG Tue Jul 26 01:26:02 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 931B216A41F for ; Tue, 26 Jul 2005 01:26:02 +0000 (GMT) (envelope-from Ady_Li@trendmicro.com.cn) Received: from udciscan05.udc.trendmicro.com (udciscan05.udc.trendmicro.com [66.35.255.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40C8443D48 for ; Tue, 26 Jul 2005 01:26:00 +0000 (GMT) (envelope-from Ady_Li@trendmicro.com.cn) Received: from localhost-imss.udc.trendmicro.com (localhost [127.0.0.1]) by udciscan05.udc.trendmicro.com (Postfix) with ESMTP id 37B8F18266F for ; Mon, 25 Jul 2005 18:25:59 -0700 (PDT) Received: from udcexbh03-vs2.us.trendnet.org (udcexbh03.udc.trendmicro.com [66.35.252.73]) by udciscan05.udc.trendmicro.com (Postfix) with ESMTP id 04A9B1826F2 for ; Mon, 25 Jul 2005 18:25:59 -0700 (PDT) Received: from adcexbh02.tw.trendnet.org ([202.133.236.202]) by udcexbh03-vs2.us.trendnet.org with Microsoft SMTPSVC(6.0.3790.211); Mon, 25 Jul 2005 18:25:59 -0700 Received: from cnexmail03.tw.trendnet.org ([10.28.128.9]) by adcexbh02.tw.trendnet.org with Microsoft SMTPSVC(6.0.3790.211); Tue, 26 Jul 2005 09:25:56 +0800 Received: from CDCEXMAIL01.tw.trendnet.org ([10.28.144.51]) by cnexmail03.tw.trendnet.org with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Jul 2005 09:25:56 +0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Date: Tue, 26 Jul 2005 09:25:53 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: system scope threads entering STOP state Thread-Index: AcWRgPc61X7Epta4S6eNWu5rcg3m5Q== From: To: X-OriginalArrivalTime: 26 Jul 2005 01:25:56.0290 (UTC) FILETIME=[F89E6A20:01C59180] Subject: system scope threads entering STOP state 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: Tue, 26 Jul 2005 01:26:02 -0000 Oh, The version is 5=2E3 Best Regards, Ady Li [TEL](86)25- 83190788x656 =0D TREND MICRO EMAIL NOTICE The information contained in this email and any attachments is confidential= and may be subject to copyright or other intellectual property protection= =2E If you are not the intended recipient, you are not authorized to use or= disclose this information, and we request that you notify us by reply mail= or telephone and delete the original message from your mail system=2E