It could be any of the following two bugs. If you can share the crash 
dump, I can certainly take a look.

6668816 6738489.

Thanks
- Cathy

> Hi all,
> 
> I tried to look for a bug related to this, but was unable to find  
> anything.
> 
> When I  execute `dladm show-link` on my x64 snv_104 machine it hangs  
> and I am unable to kill the process:
> 
> # dladm show-link
> LINK        CLASS    MTU    STATE    OVER
> e1000g0     phys     1500   down     --
> ce3         phys     1500   down     --
> ce0         phys     1500   up       --
> ce1         phys     1500   down     --
> ce2         phys     1500   down     --
> <hang>
> 
> `dladm show-dev` works fine:
> # dladm show-dev
> LINK            STATE  SPEED    DUPLEX
> e1000g0         down   0Mb      half
> ce0             up     1000Mb   full
> ce1             down   0Mb      unknown
> ce2             down   0Mb      unknown
> ce3             down   0Mb      unknown
> 
> 
> Here is where it seems to got stuck:
>  > ::pgrep dladm | ::walk thread | ::findstack
> stack pointer for thread ffffff02d13a91e0: ffffff00103ae8f0
> [ ffffff00103ae8f0 _resume_from_idle+0xf1() ]
>    ffffff00103aea30 rw_enter+0x2b()
>    ffffff00103aeb90 softmac_hold_device+0x16d()
>    ffffff00103aebd0 stubs_common_code+0x51()
>    ffffff00103aec30 drv_ioc_phys_attr+0x4b()
>    ffffff00103aecc0 drv_ioctl+0x128()
>    ffffff00103aed00 cdev_ioctl+0x45()
>    ffffff00103aed40 spec_ioctl+0x83()
>    ffffff00103aedc0 fop_ioctl+0x7b()
>    ffffff00103aeec0 ioctl+0x18e()
> 
> The system has a quad cassini card and an Intel gigabit PCI pro GT  
> PWLA8391GT adapter.
> 
> Have I missed an open bug for this or should I file one?
> 
> Regards
> 
> Henrik Johansson
> http://sparcv9.blogspot.com
> 
> 
> 
> _______________________________________________
> networking-discuss mailing list
> [email protected]

_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to