Hi all, If use ::cpuinfo -v ,In my live environment, you can find a surprise
that the thread which lasts big ticks is not switch off . I'm sorry the following info is too larger ,but I hope your idea.

ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 0 0000180c000 1b 2 0 0 no no t-0 30001ed4d00 mdb | | RUNNING <--+ +--> PRI THREAD PROC READY 0 3000116a6c0 sshd EXISTS 0 30001ef92e0 java ENABLE

ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 2 30001054000 1b 5 0 60 no no [b]t-525557[/b] 2a100371cc0 sched | | RUNNING <--+ +--> PRI THREAD PROC READY 59 300011f2000 nscd EXISTS 59 300011f2320 nscd ENABLE 0 30001f166a0 java 0 30001f05300 syslogd 0 30001044660 mdb

ADDR STATE FLG PFLG SFLG PRI EPRI PIL INTR 000002a100371cc0 onproc 8 0 13 60 99 0 n/a

We can see that the thread is belongs to FCP module.

stack pointer for thread 2a100371cc0: 2a100370d61 [ 000002a100370d61 ktl0+0x48() ] 000002a100370eb1 ssfcp_outstanding_lun_cmds+0x18(60001918fd8, 0, 60003081a40,
60003590228, 1, 100000) 000002a100370f61 ssfcp_handle_devices+0x444(12b9ff0, 60001918fd8, 2,
60005c977b8, 1, 60001918ff0) 000002a100371071 ssfcp_statec_callback+0x614(60005c977b8, 1606d, 2,
60000205000, 600019433a8, 404) 000002a100371141 fctl_ulp_statec_cb+0x250(1, 2, 6000015d1d8, 6000577d188,
60000106000, ff000000) 000002a100371201 taskq_thread+0x1a4(60000010f90, 60000010f38, 50000,
5208a1333c14, 2a100371aca, 2a100371ac8) 000002a1003712d1 thread_start+4(60000010f38, 0, 0, 0, 0, 0)

This message posted from opensolaris.org