Aubrey Li<> wrote:
> guoqing zhu - Sun Microsystems - Beijing China<> wrote:
>> If possible, can you set a breakpoint at the failure point in mdb and see
>> the calling stack?
>>
>> You can get it like:
>> hubd_bus_config+0x204:          leaq   +0x2e9dd(%rip),%rsi
>> <0xfffffffff7bb8e88>
>> hubd_bus_config+0x20b:          movl   $0x2,%edi
>> hubd_bus_config+0x210:          movq   -0xd8(%rbp),%rdx
>> hubd_bus_config+0x217:          xorl   %eax,%eax
>> hubd_bus_config+0x219:          call   +0x423675a       <cmn_err>
>> <=========find the cmn_err line in the hubd_bus_config()
>>
>>
>> then  set a breakpoint athubd_bus_config+0x219, then $C
>
> I'll try this on Monday, I leave the usb-disk in the office.
>

I inserted a breakpoint at hubd_bus_config+0x1f9, different from yours.
===============================================
usba`hubd_bus_config+0x1eb:     movl   $0x2,%edi
usba`hubd_bus_config+0x1f0:     movq   -0xd8(%rbp),%rdx
usba`hubd_bus_config+0x1f7:     xorl   %eax,%eax
usba`hubd_bus_config+0x1f9:     call   +0x3fe3daa       <cmn_err>
usba`hubd_bus_config+0x1fe:     movl   $-0x1,%ebx       <0xffffffff>
usba`hubd_bus_config+0x203:     jmp    -0x35    <usba`hubd_bus_config+0x1d0>
===============================================
Here is what I got:
================================
$C
fffffffffbc4ea30 usba`hubd_bus_config+0x1f9(ffffff01406f5518, 4080, 1,
ffffff0140816880, fffffffffbc4ead8)
fffffffffbc4eaa0 ndi_devi_config_one+0x9c(ffffff01406f5518, ffffff0140816880,
fffffffffbc4ead8, 4080)
fffffffffbc4eb50 resolve_pathname+0x164(ffffff01409a1420, fffffffffbc4eb68, 0, 0
)
fffffffffbc4eb80 e_ddi_hold_devi_by_path+0x23(ffffff01409a1420, 0)
fffffffffbc4ec40 e_devid_cache_to_devt_list+0x2b9(ffffff014119deb0,
ffffff01407ad068, fffffffffbc4ecb0, fffffffffbc4ecb8)
fffffffffbc4ec90 ddi_lyr_devid_to_devlist+0x3d(ffffff014119deb0,
ffffff01407ad068, fffffffffbc4ecb0, fffffffffbc4ecb8)
fffffffffbc4ed00 ldi_vp_from_devid+0x5d(ffffff014119deb0, ffffff01407ad068,
fffffffffbc4ed18)
fffffffffbc4ed80 ldi_open_by_devid+0x56(ffffff014119deb0, ffffff01407ad068, 1,
ffffff014079dd88, fffffffffbc4edb0, ffffff01408cf108)
fffffffffbc4ee10 zfs`vdev_disk_read_rootlabel+0x67(fffffffffbc00f58,
ffffff01407ac0c0, fffffffffbc4ee20)
fffffffffbc4ee60 zfs`spa_generate_rootconf+0x26(fffffffffbc00f58,
ffffff01407ac0c0, fffffffffbc4ee78)
fffffffffbc4eed0 zfs`spa_import_rootpool+0x31(fffffffffbc00f58,
ffffff01407ac0c0)
fffffffffbc4ef30 zfs`zfs_mountroot+0xeb(fffffffffbcb1460, 0)
fffffffffbc4ef50 fsop_mountroot+0x1a(fffffffffbcb1460, 0)
fffffffffbc4ef80 rootconf+0x12d()
fffffffffbc4efc0 vfs_mountroot+0x63()
fffffffffbc4eff0 main+0xf0()
fffffffffbc4f000 _locore_start+0x92()
[0]>
=====================================================
Hope it's helpful.

Thanks,
-Aubrey
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to