On 13-Mar-2010, at 3:46 PM, John Martin wrote: > On 03/13/10 05:34 PM, Rick McNeal wrote: >> I've got a driver which runs on a domU that communicates with another OS on >> a different domU. Right now I can get the driver attached and see 30+ SCSI >> INQUIRY commands sent to the driver and receive responses. Unfortunately the >> kernel then panic's in ddi_get_soft_state() which is called by >> sd:xdfs_probe(). ddi_get_soft_state() will panic if either the state pointer >> is NULL or the instance number is less than 0. From the stack information >> the instance number is -1. xdfs_probe() calls ddi_get_instance() which is >> returning the -1, so I looked at the dip value. >> >> >>> ffffff00ee825540::devinfo >>> >> ffffff00ee825540 sd (driver not attached) >> System properties at ffffff00ee826c80: >> name='lun' type=int items=1 >> value=00000000 >> name='target' type=int items=1 >> value=00000000 >> name='class' type=string items=1 >> value='scsi' >> >>> >> The sd driver isn't attached which seems to be a big problem. >> >> > Hi Rick, > > According to "man -s 9e probe": > > probe() determines whether the device corresponding to dip > actually exists and is a valid device for this driver. > probe() is called after identify(9E) and before attach(9E) > for a given dip. > > Probe being called before attach is expected behavior. >
True, I should have asked why is ddi_get_instance(dip) returning -1 on the 'sd' driver? I guessing there's something that I've done or not done with my driver, but what? ---- Rick McNeal [email protected] I say to myself "That's it God! I have got to get through here before the sun sets! No more pics unless I see something totally amazing!!!" Word to the wise; don't challenge God when you are on a quest for spiritual enlightenment. 300 feet later, just around the bend, I enter "Monument Valley." -- Anonymous Biker _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
