From owner-freebsd-current Mon Jul 30 6:32:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 338E337B401 for ; Mon, 30 Jul 2001 06:32:20 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id XAA01316; Mon, 30 Jul 2001 23:32:13 +1000 Date: Mon, 30 Jul 2001 23:29:51 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Darren Reed Cc: current@FreeBSD.ORG Subject: Re: (ref5) kdump: Cannout allocate memory In-Reply-To: <200107300001.KAA24098@avalon.reed.wattle.id.au> Message-ID: 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 On Mon, 30 Jul 2001, Darren Reed wrote: > Using ktrace ref5, I created ~darrenr/ktrace.out with "ktrace -i cc ..." > but trying to print it I get: > % kdump -f ~/ktrace.out > lout > kdump: Cannot allocate memory > > Is this stack corruption by kdump? ref5:~darrenr/ktrace.out is available > for anyone who wants to diagnose this further. This is probably a corrupt ktrace record. Atomic writing of ktrace records seems to have been broken in rev.1.37 of kern_ktrace.c. I've only seen this problem when the output file is written to an nfs filesystem. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message