From owner-freebsd-hackers  Wed Sep  9 22:52:29 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA04594
          for freebsd-hackers-outgoing; Wed, 9 Sep 1998 22:52:29 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from MAIL1 ([195.216.60.4])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04589
          for <freebsd-hackers@freebsd.org>; Wed, 9 Sep 1998 22:52:27 -0700 (PDT)
          (envelope-from daniel.sundin@engelholm.se)
Received: from compaq.engelholm.se - 195.216.40.87 by engelholm.se with Microsoft SMTPSVC;
	 Thu, 10 Sep 1998 07:50:45 +0200
Message-Id: <2.2.32.19980910053944.0091ea6c@pop.engelholm.se>
X-Sender: 199706aZHerOgH@pop.engelholm.se
X-Mailer: Windows Eudora Pro Version 2.2 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 10 Sep 1998 07:39:44 +0200
To: freebsd-hackers@FreeBSD.ORG
From: Daniel Sundin <daniel.sundin@engelholm.se>
Subject: panic: free: multiple frees 
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

We're having a strange problem with FreeBSD 2.2.6.
Earlier today the box rebooted once, came back after
a long harddrive check (had an uptime of 62 days, lots to
check probably).

After that reboot, it has continued to reboot exactly
every 47 minutes (almost on the second) with the following
error message:
PANIC: FREE: Multiple frees

To me it seems like that should be memory related
as that error occurs in a free(). It's in kern_malloc.c it
happens.

The server is an Intel P2 333, 512mb ram, 4.55gb Seagate
Cheetah, approximately 2 months old. 

No new software has been installed on the server in
the last days. We're mainly running 3 custom daemons
on the server, and a SQL server (MySQL). This setup
has been running the last 62 days w/o any major problems,

The 3 daemons are recieving connections (about 200/second
at peak) and doing statistical services. They use
about 200mb ram, and we're never down to the swap.


I'd appriciate it alot if someone could tell me anything
about why this might be happening. 


Thanks in advance,
Daniel



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message