Date: Mon, 29 Jun 1998 23:38:33 +0000 From: Niall Smart <rotel@indigo.ie> To: jher <jher@io.com>, rotel@indigo.ie Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense. Message-ID: <199806292238.XAA03220@indigo.ie> In-Reply-To: jher <jher@io.com> "Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense." (Jun 29, 5:11pm)
index | next in thread | previous in thread | raw e-mail
On Jun 29, 5:11pm, jher wrote: } Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low > On Mon, Jun 29, 1998 at 08:26:20PM +0000, Niall Smart wrote: > > 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. It sounds like sshd's and inetd's address spaces are getting corrupted during the expire. I'm no kernel hacker, but it really sounds like some kernel data structure is getting hosed. Perhaps the filesystem on which the news resides is corrupted and causing junk pointers to be thrown around the place? This is really a bit of a wild guess, but if you can newfs the disks it's probably worth trying. Another possibility is that your RAM is bad.. have you tried replacing it? Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the messagehelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806292238.XAA03220>