From owner-freebsd-questions@FreeBSD.ORG Tue Dec 30 12:35:04 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4B1B16A4CE for ; Tue, 30 Dec 2003 12:35:04 -0800 (PST) Received: from web21105.mail.yahoo.com (web21105.mail.yahoo.com [216.136.227.107]) by mx1.FreeBSD.org (Postfix) with SMTP id B098A43D3F for ; Tue, 30 Dec 2003 12:35:01 -0800 (PST) (envelope-from materribile@yahoo.com) Message-ID: <20031230203501.37628.qmail@web21105.mail.yahoo.com> Received: from [64.19.133.100] by web21105.mail.yahoo.com via HTTP; Tue, 30 Dec 2003 12:35:01 PST From: Mark Terribile To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Target-mode drivers under 5.2: no /dev/targ0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Tue, 30 Dec 2003 20:35:04 -0000 X-Original-Date: Tue, 30 Dec 2003 12:35:01 -0800 (PST) X-List-Received-Date: Tue, 30 Dec 2003 20:35:04 -0000 I wrote: > I'm trying to bring up the target-mode interface on a QLogic 2300 FC > card. ... > What I do not have is /dev/targ0, /dev/targ1, etc. They are simply not > being created. This is 5.2, so they should just be there, no? I will be > grateful for any help you can give me in finding out why, and getting them > started. To my astonishment, after tracing some things in the driver, I see that the devices aren't created UNTIL they are opened! This is not the behavior I expected, to say the least. I'm having other problems with target mode, and with the sample program provided: First, although camcontrol devlist -v does show a target on the bus, the other side of the FC loop isn't seeing it. Second, when I send it the DEL signal, it doesn't shut down. It hangs on an IOCTL (TARGIOCDISABLE) and I have traced the stoppage (via printf()s in the driver, UGH!) to scsi_target.c: abort_all_pending(), which waits (presumably) on what it has aborted. Now I'm trying to figure out what that was. As before, any help will be welcome. Mark Terribile materribile@yahoo.com __________________________________ Do you Yahoo!? Find out what made the Top Yahoo! Searches of 2003 http://search.yahoo.com/top2003