While carrying out PIT testing of snv_96 NWS build the following panic was encountered during a SAN mpathadm test;
panic[cpu1]/thread=ffffff0003ed1c80: assertion failed: (path_instance == 0) || (path_instance == mdi_pi_get_path_instance(vpkt-)vpkt_path)), file: ../../common/io/scsi/adapters/scsi_vhci/scsi_vhci.c, line: 2390
ffffff0003ed1970 genunix:assfail+7e ()
ffffff0003ed1a10 scsi_vhci:vhci_bind_transport+867 ()
ffffff0003ed1a80 scsi_vhci:vhci_scsi_start+182 ()
ffffff0003ed1ad0 scsi:scsi_transport+ca ()
ffffff0003ed1b50 sd:sd_start_cmds+44c ()
ffffff0003ed1b80 sd:sd_start_retry_command+8d ()
ffffff0003ed1bd0 genunix:callout_execute+bf ()
ffffff0003ed1c60 genunix:taskq_thread+1cb ()
ffffff0003ed1c70 unix:thread_start+8 ()
syncing file systems... done
The assertion looked identical to that reported in CR 6723122, but a closer look by the dev team discovered otherwise.
"A quick look at one of the core files shows that it was trying to select path instance 7 but got path instance 2. This is not the same as the previous bug where the path_instance was uninitialized."
cores are available from;
/net/cesspit.ireland/export/crash/snv_96/NWS/mpathadm/corntail
The machine the panic occurred on was as follows;
SunFire X2100 with Summit HBA