From owner-freebsd-current@FreeBSD.ORG Sun Apr 13 07:06:50 2003 Return-Path: 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 BD4AD37B401 for ; Sun, 13 Apr 2003 07:06:50 -0700 (PDT) Received: from accms33.physik.rwth-aachen.de (accms33.physik.RWTH-Aachen.DE [137.226.46.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8963643FBF for ; Sun, 13 Apr 2003 07:06:49 -0700 (PDT) (envelope-from kuku@accms33.physik.rwth-aachen.de) Received: (from kuku@localhost) by accms33.physik.rwth-aachen.de (8.11.6/8.9.3) id h3DE6lp18522; Sun, 13 Apr 2003 16:06:47 +0200 Date: Sun, 13 Apr 2003 16:06:47 +0200 From: "Christoph P. Kukulies" To: Christoph Kukulies Message-ID: <20030413140647.GA18474@gilberto.physik.rwth-aachen.de> References: <200304131153.h3DBrB916669@accms33.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <200304131153.h3DBrB916669@accms33.physik.rwth-aachen.de> User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: kernel: bad malloc : 4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2003 14:06:51 -0000 On Sun, Apr 13, 2003 at 01:53:11PM +0200, Christoph Kukulies wrote: >=20 > During boot, I suspect when an interface goes up (ng0?, wi0?) - > I'm using mpd (vpn) and thought I'd better recompile mpd but the > message is still there with a yesterday cvsuped kernel and -current. >=20 > The message isn't logged in total, so I'll probably have to write > it down next time unless someone knows already the culprit. Here is what I could type off the screen: Bad malloc flags: 4 Stack backtrace: backtrace(...) malloc(..) ng_ksocket(...) ng_apply_item(...) ngc_send(...) sosend(...)=08 sendit(...) sendto(...) Xint0x80(...) --- syscall (133) Could be it happens during mpd startup. -- Chris Christoph P. U. Kukulies kukulies@rwth-aachen.de