From root@turing.morons.org  Wed Jul 20 01:48:28 2005
Return-Path: <root@turing.morons.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 32D0B16A41F
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 20 Jul 2005 01:48:28 +0000 (GMT)
	(envelope-from root@turing.morons.org)
Received: from turing.morons.org (turing.morons.org [209.237.229.34])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F1EF443D49
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 20 Jul 2005 01:48:27 +0000 (GMT)
	(envelope-from root@turing.morons.org)
Received: by turing.morons.org (Postfix, from userid 0)
	id 4ED51A94A; Tue, 19 Jul 2005 18:49:01 -0700 (PDT)
Message-Id: <20050720014901.4ED51A94A@turing.morons.org>
Date: Tue, 19 Jul 2005 18:49:01 -0700 (PDT)
From: Nick Johnson <freebsd@spatula.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: vm-related panic: blst_radix_free: freeing free block
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         83761
>Category:       kern
>Synopsis:       [panic] vm-related panic: blst_radix_free: freeing free block
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 20 01:50:21 GMT 2005
>Closed-Date:    Sun Mar 02 02:31:04 UTC 2008
>Last-Modified:  Sun Mar 02 02:31:04 UTC 2008
>Originator:     Nick Johnson
>Release:        FreeBSD 4.11-STABLE i386
>Organization:
morons.org
>Environment:
System: FreeBSD turing.morons.org 4.11-STABLE FreeBSD 4.11-STABLE #3: Sat Dec 18 16:12:51 PST 2004 root@turing.morons.org:/usr/obj/usr/src/sys/TURING i386


	
>Description:
Not sure what happened here, but the box crashed when I exited a vim session that had been running (stopped) for 
a few weeks.  I use vm.swap_enabled, so the entire process was likely swapped out and would have swapped in and then 
been freed after I exited.  From the look of the stack trace, the crash occurred during process exit.

Fortunately I have dumpon in use, although my kernel has no debugging symbols.  Here's the pertinent information from gdb -k:

IdlePTD at physical address 0x0033e000
initial pcb at physical address 0x002a7c00

panicstr: blst_radix_free: freeing free block
panic messages:
---
panic: blst_radix_free: freeing free block

(kgdb) bt
#0  0xc015c81e in dumpsys ()
#1  0xc015c5ef in boot ()
#2  0xc015ca2d in panic ()
#3  0xc0169f53 in blst_leaf_free ()
#4  0xc016a04c in blst_meta_free ()
#5  0xc016a06f in blst_meta_free ()
#6  0xc016a06f in blst_meta_free ()
#7  0xc016a06f in blst_meta_free ()
#8  0xc0169cd2 in blist_free ()
#9  0xc020466a in swp_pager_meta_free_all ()
#10 0xc0203232 in swap_pager_dealloc ()
#11 0xc020fc0f in vm_pager_deallocate ()
#12 0xc020b224 in vm_object_terminate ()
#13 0xc020b0c0 in vm_object_deallocate ()
#14 0xc0208390 in vm_map_entry_delete ()
#15 0xc0208549 in vm_map_delete ()
#16 0xc02085d6 in vm_map_remove ()
#17 0xc01542e4 in exit1 ()
#18 0xc01540b8 in exit1 ()
#19 0xc0236199 in syscall2 ()
#20 0xc0229a75 in Xint0x80_syscall ()
Cannot access memory at address 0xbfbfee90.

	
>How-To-Repeat:
	Unknown.  This is the first time I've witnessed this on this machine in
	3+ years of operation.

	
>Fix:

	Unknown.

	


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: kmacy 
State-Changed-When: Fri Nov 16 01:43:11 UTC 2007 
State-Changed-Why:  

This is likely stale and 4.x is EOL. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=83761 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Sun Mar 2 02:30:51 UTC 2008 
State-Changed-Why:  
Feedback timeout (> 3 months). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=83761 
>Unformatted:
Have you ever seen this again?
