From owner-freebsd-current Wed Dec 2 08:52:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12344 for freebsd-current-outgoing; Wed, 2 Dec 1998 08:52:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12339 for ; Wed, 2 Dec 1998 08:52:08 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id IAA41596; Wed, 2 Dec 1998 08:59:59 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812021659.IAA41596@troutmask.apl.washington.edu> Subject: Re: Crash dump howto? In-Reply-To: from Brian Feldman at "Dec 2, 1998 11:45: 3 am" To: green@unixhelp.org (Brian Feldman) Date: Wed, 2 Dec 1998 08:59:59 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brian Feldman: > Upgrade to a more current -CURRENT. I could've sworn the reallocblk bug was > fixed. If not, there's also a sysctl oid to turn it off. > I have sources from 2 days ago. I have version 1.74 of vfs_cluster.c which is alleged to have fixed the problem. It doesn't. My sources are cvsup'd from cvsup.freebsd.org. I can kill the system under heavy load with either and ELF or aout kernel. I can not get the system to produce a crash dump. So, the question remains how does one force a dump? -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message