Date: Thu, 24 Nov 2011 02:25:48 +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: <201111240225.48154.Mark.Martinec%2Bfreebsd@ijs.si> In-Reply-To: <CAFMmRNzM6Cb2D9Nuw01b0Xmfu%2BUgYBv67zEkc%2BD7_twNm%2B1kKA@mail.gmail.com> References: <201111240126.21470.Mark.Martinec%2Bfreebsd@ijs.si> <CAFMmRNzM6Cb2D9Nuw01b0Xmfu%2BUgYBv67zEkc%2BD7_twNm%2B1kKA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday November 24 2011 01:35:28 Ryan Stone 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 Thanks Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201111240225.48154.Mark.Martinec%2Bfreebsd>