From owner-freebsd-bugs Sat Feb 17 4:10: 7 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 735A237B491 for ; Sat, 17 Feb 2001 04:10:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f1HCA5P74522; Sat, 17 Feb 2001 04:10:05 -0800 (PST) (envelope-from gnats) Date: Sat, 17 Feb 2001 04:10:05 -0800 (PST) Message-Id: <200102171210.f1HCA5P74522@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: bin/25153: kdump gets malloc error Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/25153; it has been noted by GNATS. From: Bruce Evans To: Jim.Pirzyk@disney.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/25153: kdump gets malloc error Date: Sat, 17 Feb 2001 23:01:48 +1100 (EST) On Fri, 16 Feb 2001 Jim.Pirzyk@disney.com wrote: > >Description: > > running kdump on this output file, it fails with Cannot allocate memory > after accessing the last break call . Here is the kdump on the kdump: This may be caused by breakage of atomic writing of ktrace records in rev.1.37 of kern_ktrace.c. Perhaps there is only a problem when the ktrace output file is on an nfs filesystem. There must be multiple processes writing to the same file to cause problems. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message