From owner-freebsd-hackers@FreeBSD.ORG Sat May 30 00:00:29 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 456131065670 for ; Sat, 30 May 2009 00:00:29 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outS.internet-mail-service.net (outs.internet-mail-service.net [216.240.47.242]) by mx1.freebsd.org (Postfix) with ESMTP id 296768FC08 for ; Sat, 30 May 2009 00:00:29 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 754BDE3FC7; Fri, 29 May 2009 17:00:29 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id AAC482D6006; Fri, 29 May 2009 17:00:28 -0700 (PDT) Message-ID: <4A20771C.9040008@elischer.org> Date: Fri, 29 May 2009 17:00:28 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Sergio Tam References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org Subject: Re: Log message 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: Sat, 30 May 2009 00:00:29 -0000 Sergio Tam wrote: > Hi > > On the /var/log/messages show this: > > kernel: pid 33785: corrected slot count (4->1) > > ¿Whats means? > > > Thanks for your time. > > Regards > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" It means that you are running an old system, using M:N threads and that the threading code somehow lost track of how may threads were running on that process. The system scheduler corrected it. I never figured out the situation when this occured but it goes away if you move to a newer version of the OS and go to linking with libthr.