Date: Mon, 15 Feb 1999 17:44:25 +0000 From: Geoff Buckingham <geoffb@demon.net> To: tcobb@staff.circle.net, current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: panics & deciphering VMSTAT output Message-ID: <19990215174425.L27192@gti.noc.demon.net> In-Reply-To: <A0CFA284C004D211B7EE0060082F32A412E1DA@freya.circle.net>; from tcobb@staff.circle.net on Sun, Feb 14, 1999 at 09:37:01PM -0500 References: <A0CFA284C004D211B7EE0060082F32A412E1DA@freya.circle.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Previously on Sun, Feb 14, 1999 at 09:37:01PM -0500, tcobb@staff.circle.net wrote: : I've been trying to track down a regular, but not : manually reproducible crash in 3.0-BETA (19990205). : : I can't get a crashdump due to a DSCHECK negative : number bug. I think my swap space of 3+GB is : too large for it. So, I've been having it send We have seen this too <DANGER> editing your disklabel to have only 2GB swap, without displacing the other partitions fixes this</DANGER>[1] : me the output of vmstat -m every 15 minutes to : try to track it down. The couple of times I've : seen the panic message on the console, it was : typically, but not always: : pipeinit: cannot allocate pipe - out of kvm We were also seeing this Matt (Frost) found an outstanding PR with a suggested fix that reordered some code, we haven't seen this crash since (5 days). (Vague I know maybe Matt will be along in a bit.) [1] Do not atempt ot do this unlest you are **VERY*** ***VERY*** sure you know what you are doing ***AND*** what will happen if you do it wrong. -- GeoffB 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?19990215174425.L27192>