From owner-freebsd-current@FreeBSD.ORG  Wed May 16 21:25:56 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 42CCB16A401
	for <freebsd-current@freebsd.org>; Wed, 16 May 2007 21:25:56 +0000 (UTC)
	(envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net
	[66.23.211.162])
	by mx1.freebsd.org (Postfix) with ESMTP id C8AF413C43E
	for <freebsd-current@freebsd.org>; Wed, 16 May 2007 21:25:55 +0000 (UTC)
	(envelope-from jhb@freebsd.org)
Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1])
	(authenticated bits=0)
	by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l4GLPpVc054772;
	Wed, 16 May 2007 17:25:51 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: "David Christensen" <davidch@broadcom.com>
User-Agent: KMail/1.9.6
References: <09BFF2FA5EAB4A45B6655E151BBDD90303DE3A51@NT-IRVA-0750.brcm.ad.broadcom.com>
	<200705151914.56433.jhb@freebsd.org>
	<09BFF2FA5EAB4A45B6655E151BBDD90303ECF26B@NT-IRVA-0750.brcm.ad.broadcom.com>
In-Reply-To: <09BFF2FA5EAB4A45B6655E151BBDD90303ECF26B@NT-IRVA-0750.brcm.ad.broadcom.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200705161325.20879.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]);
	Wed, 16 May 2007 17:25:51 -0400 (EDT)
X-Virus-Scanned: ClamAV 0.88.3/3263/Wed May 16 15:32:05 2007 on
	server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00,
	DATE_IN_PAST_03_06 autolearn=ham version=3.1.3
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx
Cc: freebsd-current@freebsd.org
Subject: Re: Releasing MSI Resources in a Module Causes Kernel Panic on
	-CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
Date: Wed, 16 May 2007 21:25:56 -0000
X-Original-Date: Wed, 16 May 2007 13:25:20 -0400
X-List-Received-Date: Wed, 16 May 2007 21:25:56 -0000

On Tuesday 15 May 2007 08:25:14 pm David Christensen wrote:
> > 
> > Can you print out the rid being passed to 
> > bus_release_resource()?  Also, 
> > having 'debug.bootverbose' on (sysctl) during the 
> > kldload/kldunload would be 
> > helpful.
> > 
> Thanks John but I finally found the problem.  An internal flag I use
> to track the rid was being cleared incorrectly, so I was trying to
> release an IRQ rather than the MSI vectors, thus the error.

Ah, ok.

-- 
John Baldwin