|
Description
|
Ran a test that unconfigures and configures an IB HCA (on the PCI attachment point) in a loop. Stopped the test after running for a few hours. When apparently no activity the on the system, got the following panic.
assertion failed: ph != 0L, file: ../../common/os/sunmdi.c, line: 2702
000002a108747e11 vpanic(13765c0, 1384d98, 1384888, a8e, 0, 0)
000002a108747ec1 assfail+0x78(1384d98, 1384888, a8e, 1889400, 1376400, 0)
000002a108747f71 mdi_pi_alloc_compatible+0x10c(60012a149d0, 6001018fc60, 1384c00, 1384800, 0, 0)
000002a108748031 mdi_pi_alloc+0x24(60012a149d0, 6001018fc60, 6001018fc80,
6001018fc80, 0, 2a1087489a8)
000002a1087480f1 ibnex_pseudo_create_pi_pdip+0x38(30014ae42c0, 60012a149d0,
1a30400, 0, 7b7f0000, 7b7ef000)
000002a1087481b1 ibnex_pseudo_config_one+0x190(30014ae42c0, 600109d786e,
60012a149d0, 1a30400, 7b7efc00, 7b7ef3e0)
000002a108748261 ibnex_bus_config+0x358(1a30400, 4000, 1, 6001a989946,
2a108748d98, 60012a149d0)
000002a108748431 ndi_devi_config_one+0xe8(60012a149d0, 6001a989946, 2a108748d98
, 4000, 2f, ffffffffffffffff)
000002a1087484e1 bus_config_one_phci_child+0x40(6001a989920, 0, 6001a989946,
60012a149d0, ffffffffffffffff, 8)
000002a1087485a1 config_client_paths+0xd4(600100ea018, 2a108749660, 6001018fc80
, 60010164f18, 1, 600138d2440)
000002a108748661 mdi_vhci_bus_config+0x104(30014f3cc70, 4000, 40, 2a108749660,
2a108749300, 6001018fc80)
000002a108748711 ibnex_pseudo_mdi_config_one+0x104(4000, 2a108749660,
2a108749300, 1a30400, 1a30400, 7b7f0000)
000002a1087487c1 ibnex_bus_config+0x314(0, 4000, 1a30400, 2a108749660,
2a108749300, 30014f3cc70)
000002a108748991 ndi_devi_config_one+0xe8(30014f3cc70, 2a108749660, 2a108749300
, 4000, 3a000000, ffffffffffffffff)
000002a108748a41 dv_find+0x230(6001381b078, 2a108749660, 2a108749658,
2a108749940, 6001005fb00, 60010372030)
000002a108748b11 devfs_lookup+0x5c(60016005e00, 2a108749660, 2a108749658,
2a108749940, 2, 6001005fb00)
000002a108748bd1 fop_lookup+0x108(60016005e00, 2a108749660, 2a108749658,
2a108749940, 0, 6001005fb00)
000002a108748cc1 lookuppnvp+0x380(2a108749940, 0, 1, 60016005e00, 19152f8,
6001005fb00)
000002a108748f91 lookuppnat+0x10c(6001005fb00, 0, 1, 0, 2a108749ad8, 0)
000002a108749051 lookupnameat+0x5c(ffbff196, 0, 1, 0, 2a108749ad8, 0)
000002a108749161 cstatat_getvp+0x16c(1915000, ffbff196, 1, 1, 2a108749ad8, 0)
000002a108749221 cstatat32+0x58(ffffffffffd19553, ffbff196, 1, ffbfed04, 0, 10)
000002a1087492e1 syscall_trap32+0x1e4(ffbff196, ffbfed04, 26558, 80808080,
ff0000, 80808080)
In another test, the system paniced due to hitting the following assertion in sunmdi.c, function name mdi_vhci_register().
ASSERT(DEVI_BUSY_OWNED(ddi_get_parent(vdip)));
In this test run, the system was booted without IB hardware. Later on an IB HCA was dynamically hot-plugged. This resulted in this panic.
|
