From owner-freebsd-current Fri Sep 22 13:31:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id CB0D137B423 for ; Fri, 22 Sep 2000 13:31:17 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA18511; Fri, 22 Sep 2000 22:35:39 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009222035.WAA18511@freebsd.dk> Subject: Re: -CURRENT crashes under heavy disk activity In-Reply-To: from Kenneth Wayne Culver at "Sep 22, 2000 03:37:32 pm" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Fri, 22 Sep 2000 22:35:39 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kenneth Wayne Culver wrote: > I will try to build a debug kernel, and get a backtrace of what's > happening to send to the list, but basically what happened is that I was > running a cvsup of the cvs source repository and the ports repository and > it just crashed and rebooted (I'm doing this remotely, so I can't really > catch any messeges that get sent to the screen right now, not until I go > home from work). The second time it happened was doing the cvs update of > my source tree and ports tree, and it just crashed and rebooted.. I will > make a debug kernel and do a backtrace and send it as soon as I possibly > can. I see that too, and more frequently just total hangs, remember -current is not close to being stable due to the SMPng work, so if you need decent stability go back to the PRE_SMPNG tag (I have, and I'm happy)... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message