Date: Thu, 24 Nov 2011 18:06:32 +0100 From: Mark Martinec <Mark.Martinec+freebsd@ijs.si> To: freebsd-current@freebsd.org Subject: Re: iSCSI initiator: iscontrol cannot be stopped or killed Message-ID: <201111241806.32212.Mark.Martinec%2Bfreebsd@ijs.si> In-Reply-To: <201111240225.48154.Mark.Martinec%2Bfreebsd@ijs.si> References: <201111240126.21470.Mark.Martinec%2Bfreebsd@ijs.si> <CAFMmRNzM6Cb2D9Nuw01b0Xmfu%2BUgYBv67zEkc%2BD7_twNm%2B1kKA@mail.gmail.com> <201111240225.48154.Mark.Martinec%2Bfreebsd@ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201111241806.32212.Mark.Martinec%2Bfreebsd>