Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Dec 1998 08:59:59 -0800 (PST)
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        green@unixhelp.org (Brian Feldman)
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: Crash dump howto?
Message-ID:  <199812021659.IAA41596@troutmask.apl.washington.edu>
In-Reply-To: <Pine.BSF.4.05.9812021144200.1525-100000@janus.syracuse.net> from Brian Feldman at "Dec 2, 1998 11:45: 3 am"

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812021659.IAA41596>