::stacks doesn't work for me, but ::threadlist -v seems to do the trick...
sorry, this dcmd is only added in snv_109.
> Then there is this...
000002a1001c7ca0 185ee40 0 0 60 6002ba55940
PC: cv_wait+0x3c TASKQ: system_taskq
stack pointer for thread 2a1001c7ca0: 2a1001c6801
[ 000002a1001c6801 cv_wait+0x3c() ]
mac_flow_wait+0x50()
mac_rx_srs_quiesce+0xb8()
mac_rx_classify_flow_quiesce+0x2c()
mac_rx_client_quiesce+0x20()
mac_rx_set+0x10()
vsw_set_if_hw_addr+0x124()
vsw_mac_client_init+0x64()
vsw_m_start+0x4c()
mac_start+0x20()
mac_promisc_add+0x14()
dls_promisc+0x48()
proto_promiscon_req+0x100()
dld_wput_nondata_task+0x70()
taskq_d_thread+0x9c()
thread_start+4()
This seems to be the problematic thread, someone is holding the refcnt of
the flow. Looks like bug 6792871.
Thanks
- Cathy
_______________________________________________
networking-discuss mailing list
[email protected]
