From owner-freebsd-current Wed Oct 14 06:12:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22058 for freebsd-current-outgoing; Wed, 14 Oct 1998 06:12:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22053 for ; Wed, 14 Oct 1998 06:12:09 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id JAA12654; Wed, 14 Oct 1998 09:11:19 -0400 (EDT) Date: Wed, 14 Oct 1998 09:11:19 -0400 (EDT) Message-Id: <199810141311.JAA12654@highwind.com> From: HighWind Software Information To: lists@tar.com CC: jb@cimlogic.com.au, current@FreeBSD.ORG In-reply-to: <199810141300.IAA02078@ns.tar.com> (lists@tar.com) Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rich, >I would have thought that if the scheduler can't find a thread to run >then "select" would get called. The kernel trace provided didn't show >select being called, so I would have assumed that a thread *is* being >scheduled. It would appear to me that a thread or threads are just hard >looping into the thread scheduler, as might be the case if pthread_yield >is being called repeatedly. But, you know more about this than I do. I can certainly say that we don't call "pthread_yield" anywhere. Also, the fact that the static linked version also doesn't work on these new FreeBSD's is EXTREMELY troubling. We are going to get that status dump today. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message