From adsharma@sharma-home.net  Fri Feb  7 22:39:37 2003
Return-Path: <adsharma@sharma-home.net>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 53E4E37B40E; Fri,  7 Feb 2003 22:39:37 -0800 (PST)
Received: from eagle.sharma-home.net (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 77E2143F75; Fri,  7 Feb 2003 22:39:36 -0800 (PST)
	(envelope-from adsharma@sharma-home.net)
Received: from astra.mirabella.net (astra.mirabella.net [192.168.1.3])
	by eagle.sharma-home.net (Postfix) with ESMTP
	id 9C509800E; Fri,  7 Feb 2003 22:44:23 -0800 (PST)
Received: by astra.mirabella.net (Postfix, from userid 1001)
	id 9D5F13B; Fri,  7 Feb 2003 22:39:28 -0800 (PST)
Message-Id: <20030208063928.9D5F13B@astra.mirabella.net>
Date: Fri,  7 Feb 2003 22:39:28 -0800 (PST)
From: Arun Sharma <adsharma@sharma-home.net>
Reply-To: Arun Sharma <adsharma@sharma-home.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc: smp@freebsd.org
Subject: Enabling mutex profiling panics the kernel
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         48081
>Category:       kern
>Synopsis:       Enabling mutex profiling panics the kernel
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Feb 07 22:40:06 PST 2003
>Closed-Date:    Sat Nov 01 17:18:10 PST 2003
>Last-Modified:  Sat Nov 01 17:18:10 PST 2003
>Originator:     Arun Sharma
>Release:        FreeBSD 5.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD astra.mirabella.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Jan 25 18:25:49 PST 2003 root@astra.mirabella.net:/usr/src/sys/i386/compile/astra i386

>Description:
	Enabling mutex profiling panics the kernel.

>How-To-Repeat:
	# sysctl debug.mutex.profiling.enable=1
	# sysctl debug.mutex
>Fix:

	The problem is caused by holding the mprof_mtx and calling
	printf, which results in a blockable malloc().

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: kris 
State-Changed-When: Fri Oct 10 22:42:25 PDT 2003 
State-Changed-Why:  
Does this problem persist?  I think other people are 
successfully using mutex profiling thesedays. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=48081 
State-Changed-From-To: feedback->closed 
State-Changed-By: kris 
State-Changed-When: Sat Nov 1 17:16:39 PST 2003 
State-Changed-Why:  
Feedback timeout 

http://www.freebsd.org/cgi/query-pr.cgi?pr=48081 
>Unformatted:
