From owner-freebsd-stable Mon Apr 12 6:56:52 1999 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 9887014A14 for ; Mon, 12 Apr 1999 06:56:43 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA14844; Mon, 12 Apr 1999 06:56:59 -0700 Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by point.osg.gov.bc.ca, id smtpda14842; Mon Apr 12 06:56:45 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id GAA11304; Mon, 12 Apr 1999 06:54:05 -0700 (PDT) Message-Id: <199904121354.GAA11304@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdO11300; Mon Apr 12 06:54:00 1999 X-Mailer: exmh version 2.0.2 2/24/98 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 2.2.8-RELEASE X-Sender: cy To: "Andrew Reilly" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: CRON in malloc(): warning: pointer to wrong page. In-reply-to: Your message of "Mon, 12 Apr 1999 11:15:29 +1000." <19990412011529.634.qmail@areilly.bpc-users.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Apr 1999 06:54:00 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe your problem is related to a similar problem I had with inetd, where it complained about garbage pointers, see PR 6858. I too had 32MB of RAM at the time. I noticed that the inetd problems had started to occur just around the time that tripwire, which uses ~ 30MB of VM, was run. My scan rate exceeded 20,000 pages per second at times when tripwire was run and my pageout rate averaged at 7-10 pages per second. There was also a high number of reclaims too. In short I was short of memory. Increasing my RAM from 32MB to 80MB solved the problem. Having said that however, the fact that some long running processes cannot allocate or free memory after the system has been in a severe memory shortage condition points to a bug in VM or libc. Whether there is a bug in VM/libc or not, you probably still have a severe memory shortage when you run netscape. When you run netscape, open up an xterm and run "vmstat 5". Track sr (scan rate), po (pageouts), and re (reclaims). If you notice that sr is > 200 (I'm more comfortable with 200, however I haven't seen any adverse affects when scan rate exceeds 300 for a while either) pages per second for a long period of time, or you notice that sr > 5000 pages for 20 seconds or more, or you notice that sr is obscenely high, like the 20000+ I was experiencing, you are short of RAM. If you notice that po is > 7-10 during these periods when sr is high, you are definitely short of RAM. I hope this helps. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" In message <19990412011529.634.qmail@areilly.bpc-users.org>, "Andrew Reilly" wr ites: > > Hi, > > I'm running a FreeBSD 3.1-STABLE #4: Fri Apr 9 08:39:18 EST 1999 > system with 32M RAM and about 140M of swap split across two SCSI disks > connected to the on-board ahc7850 controller. I've been running > FreeBSD-stable on this system since about '95. The problem arrived > with the upgrade to 3.1, and hasn't shifted through the three or four > rebuilds I've done since then. > > The particular problem I've found at the moment is that sometimes when > I'm doing a lot (netscape 4.5, window movement, xemacs) something > breaks in cron, and I get messages like the one below whenever cron > attempts to run a job. > > Any thoughts? > > ------ Forwarded message ------ > From: root@areilly.bpc-users.org (Cron Daemon) > Subject: Cron /usr/libexec/atrun > Date: 12 Apr 1999 00:45:01 -0000 > To: root@areilly.bpc-users.org > > CRON in malloc(): warning: pointer to wrong page. > > > > > Thanks in advance, > > -- > Andrew > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message