I'm trying to debug OpenSolaris b44 cardbus on a SPARC machine with a cardbus controller in it (a TI PCI1510 in this case). The machine panics upon boot when a cardbus device is present.
Apparently the problem comes down to a call in cardbus_rootnext_map() to i_ddi_apply_range(). The i_ddi_apply_range wants to dereference the devi_parent_data member of the dev_info node for the pcic device, which at this point in time is NULL. Now, the TI device is directly connected to a Schizo PCI controller. The load is vanilla SXCR b44, right off the DVD. No Tadpole software is installed. My question is, what are the rules for establishing devi_parent_data? I would have guessed that this member would have been "private" to the parent driver (the schizo in this case) and that any interpretation by i_ddi_apply_range() would be strictly off-limits. Am I missing something here. I can hook up a serial port and catch the stack backtraces and such, but what I first wanted to do was get a better understanding on what the rules for the devi_parent_data member were (both when is it supposed to be established, and what are the legal uses of it.) Thanks! -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
