From owner-freebsd-stable Wed Jan 5 6: 8:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 7F13E151D0 for ; Wed, 5 Jan 2000 06:08:51 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA09405; Wed, 5 Jan 2000 06:08:22 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda09403; Wed Jan 5 06:08:11 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA40266; Wed, 5 Jan 2000 06:08:09 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdy40264; Wed Jan 5 06:07:23 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id GAA30015; Wed, 5 Jan 2000 06:07:23 -0800 (PST) Message-Id: <200001051407.GAA30015@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdX30009; Wed Jan 5 06:06:39 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Alwyn Schoeman Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Error after upgrading to 3.4 + maybe 2000? In-reply-to: Your message of "Wed, 05 Jan 2000 11:31:58 +0200." <20000105113157.A4140@littlecruncher.prizm.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Jan 2000 06:06:39 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105113157.A4140@littlecruncher.prizm.dhs.org>, Alwyn Schoeman writes: > Hi, > > I'm using 3.4 on a 486DX2-66 with 8 Mb ram. Just before the end of last > year I started getting the following error messages as mail: > > CRON in malloc(): warning: pointer to wrong page. > > This happens for atrun, newsyslog and adjkerntz? > > Can anyone shine any light on a solution or maybe fixes in later versions? I had this problem under 3.1. I also had inetd get into a confused state where it too would print messages of junk pointers, then close connections. Upgrading the machine from 32 MB to 80 MB fixed the problem for me. From what I could tell, heavy VM load, e.g. high scan & page out rates, not necessarily at the time of the error, usually prior to, would usually precede the errors. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message