Date: Sun, 13 Apr 2003 17:09:42 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Christoph P. Kukulies" <kuku@physik.rwth-aachen.de> Cc: freebsd-current@freebsd.org Subject: Re: kernel: bad malloc : 4 Message-ID: <939.1050246582@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 13 Apr 2003 16:06:47 %2B0200." <20030413140647.GA18474@gilberto.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20030413140647.GA18474@gilberto.physik.rwth-aachen.de>, "Christoph P. Kukulies" writes: >On Sun, Apr 13, 2003 at 01:53:11PM +0200, Christoph Kukulies wrote: >> >> 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. >> >> 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 This means that malloc() was called with M_DONTWAIT which is a mbuf allocator flags. >Stack backtrace: >backtrace(...) >malloc(..) >ng_ksocket(...) I can't find a function called just "ng_ksocket()" but there are a bunch called "ng_ksocket_BLA()" I guess it must be one of them. A cursory glance doesn't reveal a culprit to me. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?939.1050246582>