From owner-freebsd-threads@FreeBSD.ORG Mon Feb 23 11:01:49 2004 Return-Path: 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 C904616A516 for ; Mon, 23 Feb 2004 11:01:49 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC55F43D1F for ; Mon, 23 Feb 2004 11:01:49 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) i1NJ1nbv035329 for ; Mon, 23 Feb 2004 11:01:49 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1NJ1nX1035323 for freebsd-threads@freebsd.org; Mon, 23 Feb 2004 11:01:49 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 23 Feb 2004 11:01:49 -0800 (PST) Message-Id: <200402231901.i1NJ1nX1035323@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 Subject: Current problem reports assigned to you X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 19:01:49 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/06/13] kern/19247 threads uthread_sigaction.c does not do anything 1 problem 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] misc/20861 threads libc_r does not honor socket timeouts o [2001/01/19] bin/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVT o [2001/01/25] bin/24632 threads libc_r delicate deviation from libc in ha o [2001/01/25] misc/24641 threads pthread_rwlock_rdlock can deadlock o [2001/04/02] bin/26307 threads libc_r aborts when using the KDE media pl o [2001/11/26] bin/32295 threads pthread dont dequeue signals o [2002/02/01] i386/34536 threads accept() blocks other threads o [2002/05/25] kern/38549 threads the procces compiled whith pthread stoppe o [2002/06/27] bin/39922 threads [PATCH?] Threaded applications executed w o [2002/08/04] misc/41331 threads Pthread library open sets O_NONBLOCK flag o [2003/03/02] bin/48856 threads Setting SIGCHLD to SIG_IGN still leaves z o [2003/03/10] bin/49087 threads Signals lost in programs linked with libc a [2003/04/08] bin/50733 threads buildworld won't build, because of linkin o [2003/05/07] bin/51949 threads thread in accept cannot be cancelled 15 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/05/25] misc/18824 threads gethostbyname is not thread safe o [2000/10/21] misc/22190 threads A threaded read(2) from a socketpair(2) f o [2001/09/09] bin/30464 threads pthread mutex attributes -- pshared o [2002/05/02] bin/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwri s [2002/07/16] misc/40671 threads pthread_cancel doesn't remove thread from 5 problems total. From owner-freebsd-threads@FreeBSD.ORG Tue Feb 24 08:27:50 2004 Return-Path: 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 55CF116A4CE; Tue, 24 Feb 2004 08:27:50 -0800 (PST) Received: from lakemtao06.cox.net (lakemtao06.cox.net [68.1.17.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2F8F43D1D; Tue, 24 Feb 2004 08:27:49 -0800 (PST) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.11]) by lakemtao06.cox.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040224162749.PISN3458.lakemtao06.cox.net@mezz.mezzweb.com>; Tue, 24 Feb 2004 11:27:49 -0500 Date: Tue, 24 Feb 2004 10:26:42 -0600 To: Khairil Yusof References: <20040224091827.GA9742@i18n.org> <1077615520.1002.10.camel@wolverine.cerebro.net.my> From: Jeremy Messenger Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <1077615520.1002.10.camel@wolverine.cerebro.net.my> User-Agent: Opera7.23/Linux M2 build 518 cc: freebsd-threads@freebsd.org cc: python@FreeBSD.org cc: Hye-Shik Chang Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 16:27:50 -0000 Great, thank guys! I now can install net/straw with optimized on libpthread. I am adding -thread in the CC, so the thread developers can catch here too. :-) Cheers, Mezz On Tue, 24 Feb 2004 17:38:41 +0800, Khairil Yusof wrote: > On Tue, 2004-02-24 at 18:18 +0900, Hye-Shik Chang wrote: > >> I am not sure if it's Python problem or our libpthread problem. I >> failed to reproduce the situation with compact C code. (waitpid(2) >> returned -1 with errno=EINTR on a child's normal termination.) >> If you get a reasonable explanation that saying it's Python's >> problem, please tell me. > > Great, thanks for the info. I can duplicate this problem with mail/ > evolution also. > > It may be a more universal problem caused by libpthread. At least it > also effects evolution1.5's em-junk-filter.c and other shell calls that > use waitpid. evolution doesn't catch it either, resulting in a hanged > process loop that has to be killed (also under libpthread). > > -- > "You keep using that word. I do not think it means what you think it > means." > > FreeBSD 5.2-CURRENT i386 > 5:26pm up 1:05, 1 user, load averages: 0.58, 0.40, 0.42 -- bsdforums.org 's moderator, mezz. From owner-freebsd-threads@FreeBSD.ORG Tue Feb 24 10:57:36 2004 Return-Path: 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 E374616A4CE; Tue, 24 Feb 2004 10:57:36 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD69443D31; Tue, 24 Feb 2004 10:57:34 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc13) with ESMTP id <2004022418573301500l3g4le>; Tue, 24 Feb 2004 18:57:34 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA78365; Tue, 24 Feb 2004 10:57:33 -0800 (PST) Date: Tue, 24 Feb 2004 10:57:32 -0800 (PST) From: Julian Elischer To: Jeremy Messenger In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Hye-Shik Chang cc: python@FreeBSD.org cc: freebsd-threads@freebsd.org Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 18:57:37 -0000 On Tue, 24 Feb 2004, Jeremy Messenger wrote: > Great, thank guys! I now can install net/straw with optimized on > libpthread. I am adding -thread in the CC, so the thread developers can > catch here too. :-) so what was fixed between teh quoted mail below and now? > > Cheers, > Mezz > > On Tue, 24 Feb 2004 17:38:41 +0800, Khairil Yusof > wrote: > > > On Tue, 2004-02-24 at 18:18 +0900, Hye-Shik Chang wrote: > > > >> I am not sure if it's Python problem or our libpthread problem. I > >> failed to reproduce the situation with compact C code. (waitpid(2) > >> returned -1 with errno=EINTR on a child's normal termination.) > >> If you get a reasonable explanation that saying it's Python's > >> problem, please tell me. > > > > Great, thanks for the info. I can duplicate this problem with mail/ > > evolution also. > > > > It may be a more universal problem caused by libpthread. At least it > > also effects evolution1.5's em-junk-filter.c and other shell calls that > > use waitpid. evolution doesn't catch it either, resulting in a hanged > > process loop that has to be killed (also under libpthread). > > > > -- > > "You keep using that word. I do not think it means what you think it > > means." > > > > FreeBSD 5.2-CURRENT i386 > > 5:26pm up 1:05, 1 user, load averages: 0.58, 0.40, 0.42 > > > -- > bsdforums.org 's moderator, mezz. > _______________________________________________ > 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 Tue Feb 24 11:50:12 2004 Return-Path: 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 47A1416A4CE; Tue, 24 Feb 2004 11:50:12 -0800 (PST) Received: from lakemtao06.cox.net (lakemtao06.cox.net [68.1.17.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id A673F43D39; Tue, 24 Feb 2004 11:50:11 -0800 (PST) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.11]) by lakemtao06.cox.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040224195011.SUDZ3458.lakemtao06.cox.net@mezz.mezzweb.com>; Tue, 24 Feb 2004 14:50:11 -0500 Date: Tue, 24 Feb 2004 13:49:05 -0600 To: Julian Elischer References: From: Jeremy Messenger Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: User-Agent: Opera7.23/Linux M2 build 518 cc: Hye-Shik Chang cc: python@FreeBSD.org cc: freebsd-threads@freebsd.org Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 19:50:12 -0000 On Tue, 24 Feb 2004 10:57:32 -0800 (PST), Julian Elischer wrote: > > > On Tue, 24 Feb 2004, Jeremy Messenger wrote: > >> Great, thank guys! I now can install net/straw with optimized on >> libpthread. I am adding -thread in the CC, so the thread developers can >> catch here too. :-) > > so what was fixed between teh quoted mail below and now? A workaround (not real fix?) as perky has committed[1]. There's something wrong with waitpid if it runs as libpthread, since without the workaround can run fine with libc_r. [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/python/files/patch-Lib%3a%3adistutils%3a%3aspawn.py Cheers, Mezz >> Cheers, >> Mezz >> >> On Tue, 24 Feb 2004 17:38:41 +0800, Khairil Yusof >> wrote: >> >> > On Tue, 2004-02-24 at 18:18 +0900, Hye-Shik Chang wrote: >> > >> >> I am not sure if it's Python problem or our libpthread problem. I >> >> failed to reproduce the situation with compact C code. (waitpid(2) >> >> returned -1 with errno=EINTR on a child's normal termination.) >> >> If you get a reasonable explanation that saying it's Python's >> >> problem, please tell me. >> > >> > Great, thanks for the info. I can duplicate this problem with mail/ >> > evolution also. >> > >> > It may be a more universal problem caused by libpthread. At least it >> > also effects evolution1.5's em-junk-filter.c and other shell calls >> that >> > use waitpid. evolution doesn't catch it either, resulting in a hanged >> > process loop that has to be killed (also under libpthread). >> > >> > -- >> > "You keep using that word. I do not think it means what you think it >> > means." >> > >> > FreeBSD 5.2-CURRENT i386 >> > 5:26pm up 1:05, 1 user, load averages: 0.58, 0.40, 0.42 -- bsdforums.org 's moderator, mezz. From owner-freebsd-threads@FreeBSD.ORG Tue Feb 24 14:26:24 2004 Return-Path: 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 4927916A4CE; Tue, 24 Feb 2004 14:26:24 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF08743D2F; Tue, 24 Feb 2004 14:26:23 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i1OMQDDF005092; Tue, 24 Feb 2004 17:26:13 -0500 (EST) Date: Tue, 24 Feb 2004 17:26:13 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Jeremy Messenger In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-threads@freebsd.org cc: python@freebsd.org cc: Julian Elischer cc: Hye-Shik Chang Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 22:26:24 -0000 On Tue, 24 Feb 2004, Jeremy Messenger wrote: > On Tue, 24 Feb 2004 10:57:32 -0800 (PST), Julian Elischer > wrote: > > > > > > > On Tue, 24 Feb 2004, Jeremy Messenger wrote: > > > >> Great, thank guys! I now can install net/straw with optimized on > >> libpthread. I am adding -thread in the CC, so the thread developers can > >> catch here too. :-) > > > > so what was fixed between teh quoted mail below and now? > > A workaround (not real fix?) as perky has committed[1]. There's something > wrong with waitpid if it runs as libpthread, since without the workaround > can run fine with libc_r. It is not necessarily a problem with libpthread. waitpid() can return EINTR when interrupted by a signal. If SIGCHLD isn't masked by the thread, then it is certainly plausible that it can get interrupted by it. You may not have seen it with libc_r because it handles signals differently as well as wrap waitpid() so it doesn't block the process. Libpthread doesn't wrap waitpid() except to make it a cancellation point. If its returning EINTR, I would suspect that it has received a signal. -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Wed Feb 25 14:25:26 2004 Return-Path: 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 77B0116A4CE for ; Wed, 25 Feb 2004 14:25:26 -0800 (PST) Received: from mail.asn.net (mail.asn.net [66.235.231.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 3B83643D1F for ; Wed, 25 Feb 2004 14:25:26 -0800 (PST) (envelope-from kris-fbsd@asn.net) Received: (qmail 32393 invoked by uid 80); 25 Feb 2004 22:25:25 -0000 Received: from 68.228.211.254 (SquirrelMail authenticated user kgale) by mail.asn.net with HTTP; Wed, 25 Feb 2004 15:25:25 -0700 (MST) Message-ID: <53059.68.228.211.254.1077747925.squirrel@mail.asn.net> In-Reply-To: References: <50189.68.3.131.72.1077123041.squirrel@mail.asn.net> Date: Wed, 25 Feb 2004 15:25:25 -0700 (MST) From: "Kris Gale" To: freebsd-threads@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Re: More on MySQL (Crash dump) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2004 22:25:26 -0000 Thanks to a recent patch to savecore, I was able to obtain a crash dump for one of those panics that I've been seeing when MySQL tries to create lots of threads very quickly. Here it is. Let me know if there's any other information that would be handy. GNU gdb 5.2.1 (FreeBSD)Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... panic: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 07 fault virtual address = 0xe8993028 fault code = supervisor read, page not present instruction pointer = 0x8:0xc06b0087 stack pointer = 0x10:0xe7cb0d74 frame pointer = 0x10:0xb9d8487c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 808 (mysqld) trap number = 12 panic: page fault at line 819 in file /usr/src/sys/i386/i386/trap.c cpuid = 3; boot() called on cpu#3 syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue at line 647 in file /usr/src/sys/kern/vfs_bio.ccpuid = 3; boot() called on cpu#3 Uptime: 6m8s Dumping 3072 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 1024 1040 1056 1072 1088 1104 1120 1136 1152 1168 1184 1200 1216 1232 1248 1264 1280 1296 1312 1328 1344 1360 1376 1392 1408 1424 1440 1456 1472 1488 1504 1520 1536 1552 1568 1584 1600 1616 1632 1648 1664 1680 1696 1712 1728 1744 1760 1776 1792 1808 1824 1840 1856 1872 1888 1904 1920 1936 1952 1968 1984 2000 2016 2032 2048 2064 2080 2096 2112 2128 2144 2160 2176 2192 2208 2224 2240 2256 2272 2288 2304 2320 2336 2352 2368 2384 2400 2416 2432 2448 2464 2480 2496 2512 2528 2544 2560 2576 2592 2608 2624 2640 2656 2672 2688 2704 2720 2736 2752 2768 2784 2800 2816 2832 2848 2864 2880 2896 2912 2928 2944 2960 2976 2992 3008 3024 3040 3056 --- Reading symbols from /boot/kernel/acpi.ko...done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 240 dumping++; (kgdb) backtrace #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 #1 0xc056b0e5 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:374 #2 0xc056b39d in __panic () at /usr/src/sys/kern/kern_shutdown.c:552 #3 0xc05a23b1 in bremfreel (bp=0xd4e03a38) at /usr/src/sys/kern/vfs_bio.c:647 #4 0xc05a22f1 in bremfree (bp=0xd4e03a38) at /usr/src/sys/kern/vfs_bio.c:629 #5 0xc05a5384 in getblk (vp=0xc8d2bb2c, blkno=-399372, size=16384, slpflag=0, slptimeo=0, flags=0) at /usr/src/sys/kern/vfs_bio.c:2466 #6 0xc05a2439 in breadn (vp=0xc8d2bb2c, blkno=-399372, size=16384, rablkno=0x0, rabsize=0x0, cnt=0, cred=0x0, bpp=0x0) at /usr/src/sys/kern/vfs_bio.c:700 #7 0xc05a2404 in bread (vp=0xc8d2bb2c, blkno=-399372, size=16384, cred=0x0, bpp=0xe7cb09b8) at /usr/src/sys/kern/vfs_bio.c:682 #8 0xc0663fd3 in ffs_balloc_ufs2 (vp=0xc8d2bb2c, startoffset=0, size=16384, cred=0xc4675200, flags=131072, bpp=0xe7cb0ac4) at /usr/src/sys/ufs/ffs/ffs_balloc.c:706 #9 0xc066b5ff in ffs_copyonwrite (devvp=0xc8b2ab2c, bp=0xd4f8b680) at /usr/src/sys/ufs/ffs/ffs_snapshot.c:1998 #10 0xc053f589 in spec_xstrategy (vp=0xc8b2ab2c, bp=0xd4f8b680) at /usr/src/sys/fs/specfs/spec_vnops.c:493 #11 0xc053f671 in spec_specstrategy (ap=0x0) at /usr/src/sys/fs/specfs/spec_vnops.c:553 #12 0xc053eb63 in spec_vnoperate (ap=0x0) at /usr/src/sys/fs/specfs/spec_vnops.c:122 #13 0xc05a2a3e in bwrite (bp=0xd4f8b680) at vnode_if.h:1141 #14 0xc05a42eb in vfs_bio_awrite (bp=0xd4f8b680) at /usr/src/sys/kern/vfs_bio.c:1713 #15 0xc05aa89d in vop_stdfsync (ap=0xe7cb0bfc) at /usr/src/sys/kern/vfs_default.c:738 #16 0xc053f46f in spec_fsync (ap=0xe7cb0bfc) at /usr/src/sys/fs/specfs/spec_vnops.c:441 #17 0xc053eb63 in spec_vnoperate (ap=0x0) at /usr/src/sys/fs/specfs/spec_vnops.c:122 #18 0xc0675f7c in ffs_sync (mp=0xc8a50400, waitfor=2, cred=0xc4675200, td=0xc07b1240) at vnode_if.h:627 #19 0xc05b36e7 in sync (td=0xc07b1240, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:141 #20 0xc056ad47 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:281 #21 0xc056b39d in __panic () at /usr/src/sys/kern/kern_shutdown.c:552 #22 0xc06c1a52 in trap_fatal (frame=0xe7cb0d34, eva=3902353448) at /usr/src/sys/i386/i386/trap.c:819 #23 0xc06c1783 in trap_pfault (frame=0xe7cb0d34, usermode=0, eva=3902353448) at /usr/src/sys/i386/i386/trap.c:733 #24 0xc06c1461 in trap (frame= {tf_fs = 47, tf_es = 47, tf_ds = 175308816, tf_edi = 0, tf_esi = 216568576, tf_ebp = -1177008004, tf_isp = -406123168, tf_ebx = 216568640, tf_edx = 216568620, tf_ecx = 0, tf_eax = -549195776, tf_trapno = 12, tf_err = 0, tf_eip = -1066729337, tf_cs = 8, tf_eflags = 65538, tf_esp = 47, tf_ss = 2020}) at /usr/src/sys/i386/i386/trap.c:420 #25 0xc06b0087 in Xinvlpg () at {standard input}:88 (kgdb) quit From owner-freebsd-threads@FreeBSD.ORG Thu Feb 26 11:18:07 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9FA3D16A4CE for ; Thu, 26 Feb 2004 11:18:07 -0800 (PST) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.10/8.12.9) with ESMTP id i1QJI6ws084766 for ; Thu, 26 Feb 2004 14:18:07 -0500 (EST) (envelope-from green@green.homeunix.org) Received: from localhost (green@localhost)i1QJI6LX084762 for ; Thu, 26 Feb 2004 14:18:06 -0500 (EST) Message-Id: <200402261918.i1QJI6LX084762@green.homeunix.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: threads@FreeBSD.org From: Brian Fundakowski Feldman Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Feb 2004 14:18:06 -0500 Sender: green@green.homeunix.org Subject: OO.org 1.1 compilation issue on -lpthread/SMP/4BSD X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2004 19:18:08 -0000 I get these lockups pretty predictably, but randomly, when the Sun IDL compiler is running during the OpenOffice.org compilation. Has anyone else seen/not seen this? Seems like it's a race in fork.... (gdb) bt #0 0x28278e7b in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x28279f62 in __error () from /usr/lib/libpthread.so.1 #2 0x28267f7d in pthread_sigmask () from /usr/lib/libpthread.so.1 #3 0x28267e30 in sigprocmask () from /usr/lib/libpthread.so.1 #4 0x2827063c in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #5 0x28264eee in fork () from /usr/lib/libpthread.so.1 #6 0x280c1761 in ChildStatusProc () from /home/ports/editors/openoffice-1.1/work/oo_1.1_src/solver/645/unxfbsd.pro/lib/libsal.so.3 #7 0x280bffd0 in osl_thread_start_Impl () from /home/ports/editors/openoffice-1.1/work/oo_1.1_src/solver/645/unxfbsd.pro/lib/libsal.so.3 #8 0x28265bfd in pthread_create () from /usr/lib/libpthread.so.1 #9 0x28488fb3 in _ctx_start () from /lib/libc.so.5 (gdb) info threads * 1 process 84704 0x28278e7b in pthread_testcancel () from /usr/lib/libpthread.so.1 -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-threads@FreeBSD.ORG Fri Feb 27 11:54:16 2004 Return-Path: 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 7842A16A4CE for ; Fri, 27 Feb 2004 11:54:16 -0800 (PST) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20CB143D45 for ; Fri, 27 Feb 2004 11:54:16 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 23066 invoked from network); 27 Feb 2004 19:54:15 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 27 Feb 2004 19:54:15 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i1RJsC28058047 for ; Fri, 27 Feb 2004 14:54:12 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: threads@FreeBSD.org Date: Fri, 27 Feb 2004 14:55:38 -0500 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200402271455.38197.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Proper algorithm for return values from sleep X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2004 19:54:16 -0000 As part of my sleep queue work, I found that msleep() and the cv_wait() functions have differing semantics for return vales. It appears that at least some of the early changes KSE made to msleep() were ported to cv's but not later cleanups. Specifically, in msleep(), if we are awakened while checking for signals but we didn't find a signal, we prefer a timeout-related return value over a signal-related value. Secondly, cv's don't really handle td_intrval very well at all. It has one hard-coded override for the P_EXIT case but that's it. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-threads@FreeBSD.ORG Fri Feb 27 12:35:51 2004 Return-Path: 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 C82DB16A4CE; Fri, 27 Feb 2004 12:35:51 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6980743D2F; Fri, 27 Feb 2004 12:35:51 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i1RKZoDF009601; Fri, 27 Feb 2004 15:35:50 -0500 (EST) Date: Fri, 27 Feb 2004 15:35:50 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: John Baldwin In-Reply-To: <200402271455.38197.jhb@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: Proper algorithm for return values from sleep X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2004 20:35:51 -0000 On Fri, 27 Feb 2004, John Baldwin wrote: > As part of my sleep queue work, I found that msleep() and the cv_wait() > functions have differing semantics for return vales. It appears that at > least some of the early changes KSE made to msleep() were ported to cv's but > not later cleanups. Specifically, in msleep(), if we are awakened while > checking for signals but we didn't find a signal, we prefer a timeout-related > return value over a signal-related value. It doesn't look like kern_thread.c uses any return values from msleep. Where else would one look? I would think that cv's would want to behave in the same manner. > Secondly, cv's don't really handle > td_intrval very well at all. It has one hard-coded override for the P_EXIT > case but that's it. I'm not sure about this. Julian or David would know better. -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Fri Feb 27 12:42:21 2004 Return-Path: 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 852BE16A4CE for ; Fri, 27 Feb 2004 12:42:21 -0800 (PST) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B3D643D31 for ; Fri, 27 Feb 2004 12:42:21 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 27311 invoked from network); 27 Feb 2004 20:42:20 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 27 Feb 2004 20:42:20 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i1RKgH28058220; Fri, 27 Feb 2004 15:42:18 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Daniel Eischen Date: Fri, 27 Feb 2004 15:43:43 -0500 User-Agent: KMail/1.6 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402271543.43087.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: threads@freebsd.org Subject: Re: Proper algorithm for return values from sleep X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2004 20:42:21 -0000 On Friday 27 February 2004 03:35 pm, Daniel Eischen wrote: > On Fri, 27 Feb 2004, John Baldwin wrote: > > As part of my sleep queue work, I found that msleep() and the cv_wait() > > functions have differing semantics for return vales. It appears that at > > least some of the early changes KSE made to msleep() were ported to cv's > > but not later cleanups. Specifically, in msleep(), if we are awakened > > while checking for signals but we didn't find a signal, we prefer a > > timeout-related return value over a signal-related value. > > It doesn't look like kern_thread.c uses any return values from msleep. > Where else would one look? I would think that cv's would want to behave > in the same manner. Not specific to kern_thread.c, but the values msleep() itself returns to all callers. Compare the implementation of msleep() and cv_timedwait_sig() post-sleep queues to see some of the XXX comments and differing code. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-threads@FreeBSD.ORG Fri Feb 27 17:28:58 2004 Return-Path: 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 D267616A4CE; Fri, 27 Feb 2004 17:28:58 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDD6343D1D; Fri, 27 Feb 2004 17:28:58 -0800 (PST) (envelope-from davidxu@freebsd.org) Received: from freebsd.org (davidxu@localhost [127.0.0.1]) i1S1Svbv010051; Fri, 27 Feb 2004 17:28:58 -0800 (PST) (envelope-from davidxu@freebsd.org) Message-ID: <403FEE22.2040507@freebsd.org> Date: Sat, 28 Feb 2004 09:25:54 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031208 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200402271455.38197.jhb@FreeBSD.org> In-Reply-To: <200402271455.38197.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: threads@freebsd.org Subject: Re: Proper algorithm for return values from sleep X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2004 01:28:58 -0000 John Baldwin wrote: > As part of my sleep queue work, I found that msleep() and the cv_wait() > functions have differing semantics for return vales. It appears that at > least some of the early changes KSE made to msleep() were ported to cv's but > not later cleanups. Specifically, in msleep(), if we are awakened while > checking for signals but we didn't find a signal, we prefer a timeout-related > return value over a signal-related value. Yes, I think cv and msleep code should be synchronized. > Secondly, cv's don't really handle > td_intrval very well at all. It is a bug. :-( > It has one hard-coded override for the P_EXIT > case but that's it. > I think it should includes P_SINGLE_EXIT, P_WEXIT is set when there is only one thread in process (see exit1() ). both msleep and cv are incorrect in the case. Are you fixing these bugs ? David Xu From owner-freebsd-threads@FreeBSD.ORG Sat Feb 28 01:33:09 2004 Return-Path: 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 4909E16A4CE; Sat, 28 Feb 2004 01:33:09 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BAE243D31; Sat, 28 Feb 2004 01:33:09 -0800 (PST) (envelope-from lofi@FreeBSD.org) Received: from freefall.freebsd.org (lofi@localhost [127.0.0.1]) i1S9X9bv082573; Sat, 28 Feb 2004 01:33:09 -0800 (PST) (envelope-from lofi@freefall.freebsd.org) Received: (from lofi@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1S9X94E082569; Sat, 28 Feb 2004 01:33:09 -0800 (PST) (envelope-from lofi) Date: Sat, 28 Feb 2004 01:33:09 -0800 (PST) From: Michael Nottebrock Message-Id: <200402280933.i1S9X94E082569@freefall.freebsd.org> To: jazepeda@pacbell.net, lofi@FreeBSD.org, freebsd-threads@FreeBSD.org Subject: Re: bin/26307: libc_r aborts when using the KDE media player (noatun) with the sound server(aRts) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2004 09:33:09 -0000 Synopsis: libc_r aborts when using the KDE media player (noatun) with the sound server(aRts) State-Changed-From-To: open->closed State-Changed-By: lofi State-Changed-When: Sat Feb 28 01:32:00 PST 2004 State-Changed-Why: Fixed for ages. Approved by: Originator http://www.freebsd.org/cgi/query-pr.cgi?pr=26307