From owner-freebsd-current@FreeBSD.ORG  Fri May 28 00:43:29 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3921F16A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 28 May 2004 00:43:29 -0700 (PDT)
Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3CC7943D41
	for <freebsd-current@freebsd.org>;
	Fri, 28 May 2004 00:43:28 -0700 (PDT)	(envelope-from wjw@withagen.nl)
Received: from dual (dual [212.61.27.71])
	by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i4S7cl67083333
	for <freebsd-current@freebsd.org>;
	Fri, 28 May 2004 09:38:47 +0200 (CEST)
	(envelope-from wjw@withagen.nl)
Message-ID: <077001c44486$ddd75640$471b3dd4@dual>
From: "Willem Jan Withagen" <wjw@withagen.nl>
To: <freebsd-current@freebsd.org>
References: <074501c44449$3ab41bc0$471b3dd4@dual>
	<20040528011551.GB48226@xor.obsecurity.org>
Date: Fri, 28 May 2004 09:39:10 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Subject: Re: Possible bug in malloc-code
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2004 07:43:29 -0000

----- Original Message ----- 
From: "Kris Kennaway" <kris@obsecurity.org>
On Fri, May 28, 2004 at 02:17:57AM +0200, Willem Jan Withagen wrote:

> > The bad thing is that calling free() at this point will freeze the box....
> 
> amd64 seems to have a bug that causes it to pause while accessing
> swap.  Make sure this isn't what you're seeing - i.e. wait a few
> minutes before hitting the reset button.

Interesting point.
I'll run the box and go to the gym...
That should give it enough time to recover.

And we'll see.

I'did see such behaviour, but that was more like stalling for a 
1-2 sec period, Which I atributed to zeroing 500Mb of RAM.

--WjW