From owner-freebsd-current Wed Oct 14 06:01:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20273 for freebsd-current-outgoing; Wed, 14 Oct 1998 06:01:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20267 for ; Wed, 14 Oct 1998 06:00:59 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id IAA02078; Wed, 14 Oct 1998 08:00:10 -0500 (CDT) Message-Id: <199810141300.IAA02078@ns.tar.com> From: "Richard Seaman, Jr." To: "John Birrell" Cc: "info@highwind.com" , "current@FreeBSD.ORG" Date: Wed, 14 Oct 98 08:00:09 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Oct 1998 08:00:27 +1000 (EST), John Birrell wrote: >Providing a ktrace without a thread status dump is >useless IMO. All that you've shown is that the thread scheduler can't >find a thread to run. The thread status dump should tell you why. 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message