From owner-freebsd-stable Thu Dec 9 13:29: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ulstu.ru (ns.ulstu.ru [62.76.34.36]) by hub.freebsd.org (Postfix) with ESMTP id 3346614F05 for ; Thu, 9 Dec 1999 13:28:47 -0800 (PST) (envelope-from vlad@high.net.ru) Received: from siemens.ulstu.ru (siemens.ulstu.ru [62.76.34.44]) by mail.ulstu.ru (8.8.5-MVC-230198/8.8.7) with ESMTP id AAA90264 for ; Fri, 10 Dec 1999 00:28:37 +0300 (MSK) (envelope-from vlad@high.net.ru) Received: from hq.spc.high (ip181.link-ul.ru [195.151.42.181]) by siemens.ulstu.ru (Postfix) with ESMTP id D638C1741D for ; Fri, 10 Dec 1999 00:27:41 +0300 (MSK) Received: by hq.spc.high (Postfix, from userid 1000) id 73A873FB; Thu, 9 Dec 1999 12:10:52 +0300 (MSK) Date: Thu, 9 Dec 1999 12:10:52 +0300 From: Vlad Skvortsov To: freebsd-stable@FreeBSD.ORG Subject: Re: CRON in malloc(): warning: pointer to wrong page. Message-ID: <19991209121051.B1277@high.net.ru> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 08:49:15PM -0500, Bosko Milekic wrote: > !>On a probably related matter we had a lot of processes die with signal 4 > !>(one or two a day). We swapped the RAM and I thought it had stopped but > !>one died yesterday (telnetd). Previously running make index in /usr/ports > !>would always die with sig4 but since the RAM swap its been fine... > !> > !>Any suggestions? I assume sig4 indicates that there is corruption in > !>either the memory, cache or bus but I have no idea why or what causes the > !>CRON error. > !> > Well, are the processes dying with signal 4 dumping core? If so, have > you tried debugging from the core dump? > Your malloc() problem could be related to something that you discover > this way. After all, the default action on receipt of signal 4 would be > to dump core. I've got similar problem with CRON, but the system itself is definintively stable with good uptime and no processes dying even at high load rates. I've swapped everything starting from motherboard and ending with RAM - nothing helps. Kinda weird. Any suggestions ? -- Vlad Skvortsov, vss@ulstu.ru, vlad@high.net.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message