iSCSI initiator: iscontrol cannot be stopped or killed

Mark Martinec Mark.Martinec+freebsd at
Thu Nov 24 01:25:51 UTC 2011

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


More information about the freebsd-current mailing list