Date: Mon, 20 Jul 2009 22:45:58 +0200 From: Peter Schuller <peter.schuller@infidyne.com> To: Julian Elischer <julian@elischer.org> Cc: freebsd-current@freebsd.org Subject: Re: Getting crashdumps to work (trying to submit crash report) Message-ID: <20090720204558.GB96793@hyperion.scode.org> In-Reply-To: <4A64D1FF.1010207@elischer.org> References: <20090720201332.GA95896@hyperion.scode.org> <4A64D1FF.1010207@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--5/uDoXvLw7AC5HRs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > hopefuly a bit BIGGER than ram size... not by much but exactly equal=20 > wouldn't work.. It's actually very close to RAM size unfortunately (since I didn't know about the not-on-gmirror/gstripe/etc limitation when setting it up I didn't really care about making each individual dump dev larger). But my understanding has been that one expects some bios reservation anyway. In any case: % dumpon -v /dev/ad16s1b || echo fail kernel dumps on /dev/ad16s1b Should not dumpon be complaining if it is considered too small? I definitely did check dumpon output last time when I thought I fixed the problem (I meant dumpon, not dumpdev, in my other post - sorry). --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@infidyne.com>' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --5/uDoXvLw7AC5HRs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpk14UACgkQDNor2+l1i31DUwCgqByHXym6l4bnA6ZPM8LtOffP 5s4AnRBjb0EdlFfbmrOCUUrNhs88JkvS =6iFP -----END PGP SIGNATURE----- --5/uDoXvLw7AC5HRs--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090720204558.GB96793>