From owner-freebsd-bugs Tue May 22 19:49:28 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from gabion.asci.com (gabion.asci.com [24.234.52.45]) by hub.freebsd.org (Postfix) with SMTP id DDE7F37B42C for ; Tue, 22 May 2001 19:49:23 -0700 (PDT) (envelope-from ray@asci.com) Received: (qmail 24114 invoked from network); 23 May 2001 02:49:21 -0000 Received: from user187.net061.lv.sprint-hsd.net (HELO asci.com) (206.107.221.187) by gabion.asci.com with SMTP; 23 May 2001 02:49:21 -0000 Message-ID: <3B0B2531.48A4C31@asci.com> Date: Tue, 22 May 2001 19:49:21 -0700 From: Ray Tripamer X-Mailer: Mozilla 4.73 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-bugs@freebsd.org Subject: 3.4-RELEASE rlist_free panic Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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