From owner-freebsd-stable@FreeBSD.ORG Fri Jan 9 15:27:19 2009 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 EFA281065673 for ; Fri, 9 Jan 2009 15:27:18 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from cetus.palisadesys.com (cetus.palisadesys.com [205.237.115.21]) by mx1.freebsd.org (Postfix) with ESMTP id BFF188FC23 for ; Fri, 9 Jan 2009 15:27:18 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from cancer.palisadesys.com (serverwatch [172.16.1.98]) by cetus.palisadesys.com (8.14.3/8.14.3) with ESMTP id n09FRIln052025; Fri, 9 Jan 2009 09:27:18 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.2.242] (cetus.palisadesys.com [205.237.115.21]) (authenticated bits=0) by cancer.palisadesys.com (8.14.2/8.14.2) with ESMTP id n09FRBgW052227; Fri, 9 Jan 2009 09:27:11 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Message-ID: <49676CCE.30706@palisadesys.com> Date: Fri, 09 Jan 2009 09:27:10 -0600 From: Guy Helmer User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Pete French References: In-Reply-To: X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (cancer.palisadesys.com [205.237.115.20]); Fri, 09 Jan 2009 09:27:11 -0600 (CST) X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-Palisade-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-4.398, required 6, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, HTML_MESSAGE 0.00) X-Palisade-MailScanner-From: ghelmer@palisadesys.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Big problems with 7.1 locking up :-( 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: Fri, 09 Jan 2009 15:27:20 -0000 Pete French wrote: >> Are you using the same disk controller as Peter ? Do both of you run >> with quotas on the file system ? By lockup, do you mean it doesnt >> respond to the network either or just anything that needs disk IO ? >> > > I dont think he can be using yhe same controller, as mine is an > embedded HPO unit. they do make a separate plugin one though - P400 > SAS controller. > > My symptoms are that the thing locks hard and respionds to nothing, no > keypresses or anything. I am assuming that the disc is the first thing to > go though, ebcause I see data which was being written to a file and a > processes reading from that file to the network. more of the file comes > over the network than makes it phyiscally onto the disc > > The only useful error I ever saw was the message about spin > lock / turnstile locks being held for too long. > > -pete. > OK, perhaps my issue is different then. My symptoms seem to be a hang from anything that triggers a fork(), such as entering a command at a shell prompt or entering a user name at the console's login prompt. Network activity still works -- all the TCP connections stay up until I drop into the kernel debugger or power cycle. Guy -- Guy Helmer, Ph.D. Chief System Architect Palisade Systems, Inc.