Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 May 2001 19:49:21 -0700
From:      Ray Tripamer <ray@asci.com>
To:        freebsd-bugs@freebsd.org
Subject:   3.4-RELEASE rlist_free panic
Message-ID:  <3B0B2531.48A4C31@asci.com>

next in thread | raw e-mail | index | archive | help
We are running 3.4-RELEASE on a 600mhz AMD machine with 128MB RAM and 2
8GB scsi disks.  It runs our mail server, stronghold web server, dns,
etc.

The machine has been fine since we got it (a hosted machine at
rackspace.com) - 0 downtime for about 4 straight moths, until we added a
relatively high volume (but by no means crippling) site to it.  Since
then, the machine panics fairly regulary (sometimes several times a day,
other times it may go several days without crashing).  With nothing
helpful appearing in the dmesg buffer, I finally started doing
savecore's and gdb'ing the result to find this:

panicstr: rlist_free: free start overlaps already freed area
panic messages:
---
panic: rlist_free: free start overlaps already freed area

syncing disks... 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12
12 12 giving up
[...]

I've checked the message archives, and found a similar report but for
FreeBSD 3.3.  Looking into the source reveals that it is panicing while
managing the swap/free space from the best that I can tell.  I'm hoping
that this is a known problem with FreeBSD 3.x in general and that a fix
or some sort of workaround is available.  If not, are there pre-emptive
measures I can take to avoid this panic?  Add more memory?  More swap
space?  I suppose I would also considering upgrading to the latest
FreeBSD 4.3 if I could figure out how to upgrade a system remotely while
3.4 is still running (ie not booting from a cd and running some sort of
upgrade utility).

Any help would be greatly appreciated.  Thanks
--
Ray Tripamer
ray@asci.com
"The Smart Money was on Goliath"



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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B0B2531.48A4C31>