From owner-freebsd-questions Tue Apr 11 15:12:18 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id A4A5A37B655 for ; Tue, 11 Apr 2000 15:12:13 -0700 (PDT) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id KAA00861; Wed, 12 Apr 2000 10:12:05 +1200 (NZST) Message-Id: <200004112212.KAA00861@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: Guy Helmer Date: Wed, 12 Apr 2000 10:12:04 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: CRON in malloc(): warning: pointer to wrong page. Reply-To: dan@freebsddiary.org Cc: freebsd-questions@FreeBSD.ORG References: <200004112006.IAA04082@ducky.nz.freebsd.org> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Apr 00, at 16:59, Guy Helmer wrote: > On Wed, 12 Apr 2000, Dan Langille wrote: > > > The following type of mail message is arriving on a regular basis. They > > are related to each cron job that starts up. > > > > Date sent: Wed, 12 Apr 2000 07:55:01 +1200 (NZST) > > From: root (Cron Daemon) > > To: root > > Subject: Cron /usr/libexec/atrun > > > > CRON in malloc(): warning: pointer to wrong page. > > > > I can't see anything in /var/log/messages related to this. > > > > Coincidentally (or not), the box rebooted itself yesterday. Any clues > > for me please? > > This isn't the first report of CRON spewing these messages (see GNATS PRs > bin/11169 and bin/9722) so I have been looking at the problem. I have > patches for cron that might solve the problem but I am unable to duplicate > the problem and thus unable to prove my patches solve it. If you would > like to try the patches, please let me know and I will send them. > > As for the reboot, I would suggest enabling crash dumps by setting dumpdev > in /etc/rc.conf and building & installing a debugging kernel. With these > steps. it would be possible to capture the machine state and get a > traceback (via gdb -k) if the reboot is due to a kernel panic. I would not > expect that the reboot would be due to cron, but a crash dump would verify > what process was running when the crash took place. > > I'll try to get the cron patches reviewed and checked into the source tree > soon... I would be quite happy to do a traceback etc, but this is a 486 with 16MB of ram. It takes 3 days to make world. -- Dan Langille - DVL Software Limited [I'm looking for more work] http://www.dvl-software.com/ | http://www.unixathome.org/ http://www.racingsystem.com/ | http://www.freebsddiary.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message