From owner-freebsd-questions Tue Apr 11 14:59:59 2000 Delivered-To: freebsd-questions@freebsd.org Received: from css-1.cs.iastate.edu (css-1.cs.iastate.edu [129.186.3.24]) by hub.freebsd.org (Postfix) with ESMTP id 08A2D37B997 for ; Tue, 11 Apr 2000 14:59:51 -0700 (PDT) (envelope-from ghelmer@cs.iastate.edu) Received: from popeye.cs.iastate.edu (ghelmer@popeye.cs.iastate.edu [129.186.3.4]) by css-1.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id QAA16558; Tue, 11 Apr 2000 16:59:47 -0500 (CDT) Received: from localhost (ghelmer@localhost) by popeye.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id QAA11656; Tue, 11 Apr 2000 16:59:43 -0500 (CDT) X-Authentication-Warning: popeye.cs.iastate.edu: ghelmer owned process doing -bs Date: Tue, 11 Apr 2000 16:59:43 -0500 (CDT) From: Guy Helmer To: Dan Langille Cc: freebsd-questions@FreeBSD.ORG Subject: Re: CRON in malloc(): warning: pointer to wrong page. In-Reply-To: <200004112006.IAA04082@ducky.nz.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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... Guy Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message