From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 14:47:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BC3F16A4DE for ; Fri, 28 Jul 2006 14:47:53 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1116643DA3 for ; Fri, 28 Jul 2006 14:47:42 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k6SEko1D057915; Fri, 28 Jul 2006 08:46:50 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 28 Jul 2006 08:47:09 -0600 (MDT) Message-Id: <20060728.084709.-135504445.imp@bsdimp.com> To: scheidell@secnap.net From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 28 Jul 2006 08:46:50 -0600 (MDT) Cc: freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 14:47:53 -0000 In message: "Michael Scheidell" writes: : > -----Original Message----- : > From: M. Warner Losh [mailto:imp@bsdimp.com] : > Sent: Thursday, July 27, 2006 9:39 PM : > To: Michael Scheidell : > Cc: freebsd-hackers@freebsd.org : > Subject: Re: FBSD 5.5 and software timers : : > libc_r depends on absolute system time to do its sleeps and : > timeouts, and has since FreeBSD 3.4. This dependency has : : Could be, but it worked up to and including 5.4. It worked for the one simple test case that you had. I'm not sure what changed between 5.4 and 5.5 to break it. I've hit similar test cases as far back as 3.4. : > been the result of many conversations over time, and has had : > several patches posted. Since libc_r is dead technology, : > there's little chance they will be adopted. : : I replaced libc_r with libthr and two things happen: : One of my threads doesn't run, and it won't die (kill -9 doesn't even : kill it) : : I replaced libc_r with libpthread and it immediately reboots the system! Neither of these is good! Does it happen on 6? : I am going to try to nail down just what and why this happens and post : that. : (reminder: even if this change happened in 3.4, it didn't affect me till : 5.5) It might be useful to find the change. Warner