From owner-freebsd-current@FreeBSD.ORG  Mon Nov 28 12:24:12 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3C658106566B
	for <freebsd-current@freebsd.org>; Mon, 28 Nov 2011 12:24:12 +0000 (UTC)
	(envelope-from freebsd-current@m.gmane.org)
Received: from lo.gmane.org (lo.gmane.org [80.91.229.12])
	by mx1.freebsd.org (Postfix) with ESMTP id E86578FC16
	for <freebsd-current@freebsd.org>; Mon, 28 Nov 2011 12:24:11 +0000 (UTC)
Received: from list by lo.gmane.org with local (Exim 4.69)
	(envelope-from <freebsd-current@m.gmane.org>) id 1RV0Fn-0004kt-10
	for freebsd-current@freebsd.org; Mon, 28 Nov 2011 13:24:11 +0100
Received: from lara.cc.fer.hr ([161.53.72.113])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <freebsd-current@freebsd.org>; Mon, 28 Nov 2011 13:24:11 +0100
Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <freebsd-current@freebsd.org>; Mon, 28 Nov 2011 13:24:11 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-current@freebsd.org
From: Ivan Voras <ivoras@freebsd.org>
Date: Mon, 28 Nov 2011 13:23:58 +0100
Lines: 24
Message-ID: <javugv$k41$1@dough.gmane.org>
References: <201111240126.21470.Mark.Martinec+freebsd@ijs.si>
	<CAFMmRNzM6Cb2D9Nuw01b0Xmfu+UgYBv67zEkc+D7_twNm+1kKA@mail.gmail.com>
	<201111240225.48154.Mark.Martinec+freebsd@ijs.si>
	<201111241806.32212.Mark.Martinec+freebsd@ijs.si>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@dough.gmane.org
X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:8.0) Gecko/20111116 Thunderbird/8.0
In-Reply-To: <201111241806.32212.Mark.Martinec+freebsd@ijs.si>
Subject: Re: iSCSI initiator: iscontrol cannot be stopped or killed
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>
X-List-Received-Date: Mon, 28 Nov 2011 12:24:12 -0000

On 24/11/2011 18:06, Mark Martinec wrote:
>>> If you can get it back into this state,
>>
>> Sure, *every* time.
>>
>>> a procstat -k -k<iscontrol pid>  would be very helpful.
>>> (the second -k is not a typo).
>>
>> # procstat -k -k 5896
>>    PID    TID COMM             TDNAME           KSTACK
>>   5896 102364 iscontrol        -                mi_switch+0x174
>> sleepq_timedwait+0x42 _sleep+0x301 ic_init+0x2f1 iscsi_ioctl+0x525
>> devfs_ioctl_f+0x7b kern_ioctl+0x115 sys_ioctl+0xfd amd64_syscall+0x450
>> Xfast_syscall+0xf7
>
> Additional info: the process is blocking on 'ffp', unresponsive to signals:
>
>    UID   PID  PPID CPU PRI NI    VSZ    RSS MWCHAN STAT  TT         TIME COMMAND
>      0  5896     1   0  20  0  16424   1264 ffp    Ds    ??      0:00.04 iscontrol -c /etc/iscsi.conf -n xxx
>

You should probably ask at the freebsd-scsi@ mailing list. From looking 
at the code it looks like "ffp" is used for LUN scan timeout.