Date: Wed, 14 Oct 98 08:00:09 -0500 From: "Richard Seaman, Jr." <lists@tar.com> To: "John Birrell" <jb@cimlogic.com.au> Cc: "info@highwind.com" <info@highwind.com>, "current@FreeBSD.ORG" <current@FreeBSD.ORG> Subject: Re: Recent 3.0's are Depressing Message-ID: <199810141300.IAA02078@ns.tar.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810141300.IAA02078>