From owner-freebsd-stable Mon Jul 2 2:49:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id AD08A37B401; Mon, 2 Jul 2001 02:49:46 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by dilbert.firstcallgroup.co.uk with local (Exim 3.22 #1) id 15H0Kk-000344-00; Mon, 02 Jul 2001 10:49:34 +0100 To: freebsd-stable@freebsd.org, ohartman@klima.physik.uni-mainz.de Subject: Re: HELP! Server crashes since last cvsupdate! Cc: freebsd-questions@freebsd.org In-Reply-To: Message-Id: From: Pete French Date: Mon, 02 Jul 2001 10:49:34 +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Since our last update Friday, 29th June, both SMP machines run > into a "stuck" condition after a while. This happened now two times > and I do not know what happens. I've been seeing this effect since 4.3-RELEASE actually. WIth pretty much identical symptoms to the ones you descibe. Asking here earlier people seemed to think that it was the disc controllers getting locked up as this will lead to the effects described. Sometimes the machine will run for weeks at a time, sometimes it will freeze after a few hours. The easiest way I can make it lockup is to try and access a very large file from two processes at once. I'm currently trying to find time to work out how to use the kernel debugging stuff to connect over the network and see what sort of state the kernels in (which it is apparently posssible to do). But not really got anywhere with that yet. I'd be intyerested in knowing what sort of machine you have and what the components are to see if theres anything that both systems have in common (other than the SMP bits). cheers, -pcf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message