From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 23:53:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 364D216A400 for ; Wed, 20 Feb 2008 23:53:23 +0000 (UTC) (envelope-from ml@proficuous.com) Received: from mail.proficuous.com (www.proficuous.com [209.240.79.128]) by mx1.freebsd.org (Postfix) with ESMTP id 0AAE613C46E for ; Wed, 20 Feb 2008 23:53:22 +0000 (UTC) (envelope-from ml@proficuous.com) Received: from [192.168.3.99] (unknown [192.168.3.99]) by mail.proficuous.com (Postfix) with ESMTP id ECAA8298204; Wed, 20 Feb 2008 17:32:21 -0600 (CST) Message-ID: <47BCB886.8090900@proficuous.com> Date: Wed, 20 Feb 2008 17:32:22 -0600 From: Aaron Martinez User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Gil Bidon References: <2de9b4690802201459y7d916bc9i3a0d5548d3025327@mail.gmail.com> In-Reply-To: <2de9b4690802201459y7d916bc9i3a0d5548d3025327@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.3 update and process freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2008 23:53:23 -0000 Gil Bidon wrote: > Hi, > Since i've updated my machine to FreeBSD 6.3 some process randomly start > using 100% CPU or are locked to STOP state (in top). > > Is there a known solution / patch ? Except the rollback :) > > Regards, > > Gil > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Gil, You'll need to provide significantly more information before anyone will be able to help you. Some of which might be, a list of the offending processes, output from top, dmesg, what patchlevel you're running, any errors from syslog. Aaron