From owner-freebsd-bugs Mon Jun 29 15:12:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19809 for freebsd-bugs-outgoing; Mon, 29 Jun 1998 15:12:32 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from dillinger.io.com (dillinger.io.com [199.170.88.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19731 for ; Mon, 29 Jun 1998 15:12:12 -0700 (PDT) (envelope-from jher@dillinger.io.com) Received: (from jher@localhost) by dillinger.io.com (8.8.7/8.8.5) id RAA11284; Mon, 29 Jun 1998 17:11:28 -0500 (CDT) Message-ID: <19980629171127.09719@io.com> Date: Mon, 29 Jun 1998 17:11:27 -0500 From: jher To: rotel@indigo.ie Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense. References: <199806291926.UAA02478@indigo.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199806291926.UAA02478@indigo.ie>; from Niall Smart on Mon, Jun 29, 1998 at 08:26:20PM +0000 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jun 29, 1998 at 08:26:20PM +0000, Niall Smart wrote: > On Jun 29, 9:40am, jher wrote: > } Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low > > The following reply was made to PR kern/6858; it has been noted by GNATS. > > I've done the ln -s h /etc/malloc.conf and i'm still seeing > > inetd in realloc(): warning: junk pointer, too low to make sense. > > sshd also still has malloc problem and cron ceases to run. In addition, > > i've upped the > > physical ram to 512M which at least allows "expire" to run in 15 minutes > > instead of 6 hours. > Weird problem. Have you tried to write any testcases which exercise your > memory and disk systems? I presume this is a problem in the kernel.. > Does it happen every time you run expire? > Niall Yes. It happens basically everytime I run the expire (which usually runs in cron). As soon as it runs that, cron ceases to run, the expire dies (I don't get any mail from it and the logs don't rotate), sshd tries to malloc 1+gig of ram during incoming connections and inetd reports that error. I am open to the idea of letting someone from freebsd telnet/ssh into the box and replicating the situation. I can cause it to happen pretty much at will by simply running the news.daily script. -- Today is Setting Orange, day 34 in the season of Confusion, 3164. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message