From owner-freebsd-current Sat Mar 23 10:15:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 6681437B433; Sat, 23 Mar 2002 10:14:56 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id E9ECA5348; Sat, 23 Mar 2002 19:14:53 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Kris Kennaway Cc: current@FreeBSD.org, jeffr@FreeBSD.org Subject: Re: uma panic References: <20020323004158.A16726@xor.obsecurity.org> From: Dag-Erling Smorgrav Date: 23 Mar 2002 19:14:53 +0100 In-Reply-To: <20020323004158.A16726@xor.obsecurity.org> Message-ID: Lines: 15 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway writes: > I upgraded the bento package building cluster to a more recent > -current to try and get packages building again (every other snapshot > I've tried for the last week has either been broken or does not > build). One of the client machines panicked after about an hour under > load: Please add 'kern.sync_on_panic=0' to /etc/sysctl.conf (assuming all your filesystems are either synchronous or soft-updated). It won't stop the panics, but at least you'll avoid the second panic, which may make the first panic easier to debug. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message