From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 12:21:41 2003 Return-Path: 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 6886B37B401 for ; Thu, 22 May 2003 12:21:41 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95E8843F93 for ; Thu, 22 May 2003 12:21:40 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h4MJLTwQ005965; Thu, 22 May 2003 15:21:29 -0400 (EDT) Received: from localhost (eischen@localhost)h4MJLTsT005961; Thu, 22 May 2003 15:21:29 -0400 (EDT) Date: Thu, 22 May 2003 15:21:29 -0400 (EDT) From: Daniel Eischen To: Julian Elischer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Dan Nelson Subject: Re: libkse and SMP (was Re: USB bulk read & pthreads) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2003 19:21:41 -0000 On Thu, 22 May 2003, Julian Elischer wrote: > > On Thu, 22 May 2003, Dan Nelson wrote: > > > In the last episode (May 22), Terry Lambert said: > > > Make sure you use SCHED_4BSD, rather than SCHED_ULE, if you are using > > > one of the kernel threads libraries, for now. > > > > > > You really should read the -current archives before attempting any of > > > this, if you don't follow -current closely enough to have caught > > > Jeff's message on this, or which kernel threading libraries are > > > available. > > > > I do read -current, and I'm definitely not going anywhere near > > SCHED_ULE. I just tested both libraries with today's kernel and > > libraries, and was able to get a hard lockup with both libthr and > > libkse. Mysql seems to run okay. Starting a threaded pike process > > seems to be the killer. Unfortunately, pike's a pretty large app so > > it's not easy to get a stripped-down testcase. > > Ok so we need to get a description of this 'lockup'. In my experience with the ACE test MT_SOCK_Test: > 1/ does teh whole system lock up? Yes. > 2/ is this SMP? (how many cpus)? No. > 3/ does the system respond to pings? No. > 4/ do you have teh kernel dbugger installed, and if you do, does it > respond on the console to . You may have to start you > app from outside X11 on a console to be able to see the console once it > has frozen if it si an X app. Haven't been able to do this. > 5/ if it DOES go into ddb, what does 'ps' show? > 6/ got a serial console? No :( You can repeat it by downloading and building the ACE tests. David and I can tell you how. It doesn't happen all the time, so it is not easily repeatable. Though, it's only been the last few weeks that I've had the problem. -- Dan Eischen