From owner-freebsd-scsi@FreeBSD.ORG  Tue Apr  3 17:17:23 2007
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
X-Original-To: freebsd-scsi@freebsd.org
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id C118816A403
	for <freebsd-scsi@freebsd.org>; Tue,  3 Apr 2007 17:17:23 +0000 (UTC)
	(envelope-from ale@FreeBSD.org)
Received: from lab.alexdupre.com (lab.alexdupre.com [81.174.31.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 0B1BE13C469
	for <freebsd-scsi@freebsd.org>; Tue,  3 Apr 2007 17:17:22 +0000 (UTC)
	(envelope-from ale@FreeBSD.org)
Received: (qmail 59865 invoked from network); 3 Apr 2007 16:50:41 -0000
Received: from unknown (HELO ?192.168.178.2?) (192.168.178.2)
	by lab.alexdupre.com with SMTP; 3 Apr 2007 16:50:41 -0000
Message-ID: <461285E0.8000008@FreeBSD.org>
Date: Tue, 03 Apr 2007 18:50:40 +0200
From: Alex Dupre <ale@FreeBSD.org>
User-Agent: Thunderbird 1.5.0.10 (X11/20070310)
MIME-Version: 1.0
To: Scott Long <scottl@samsco.org>
References: <46126585.8080204@FreeBSD.org> <46127DF4.5080703@samsco.org>
In-Reply-To: <46127DF4.5080703@samsco.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org
Subject: Re: targclose doesn't return
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2007 17:17:23 -0000

Scott Long wrote:
> Are there any other console messages from the targ driver?  Can you
> turn on CAMDEBUG and send us the trace of what is going on?

CAMDEBUG is already on, but simply opening/closing the targ device,
without sending any ioctl to enable it, shouldn't produce any CAM
message. I traced the kernel thread and I found that it doesn't return
from the destroy_devl() function: csw->d_purge is NULL and
dev->si_threadcount is '1'. The thread enters the following block
(kern_conf.c, row 690) and never exits.


	while (dev->si_threadcount != 0) {
		/* Use unique dummy wait ident */
		msleep(&csw, &devmtx, PRIBIO, "devdrn", hz / 10);
	}


--
Alex Dupre