I've see similar behavior with cheaper cards. It seems there is a bug that messes up the process by which Solaris probes the devices; the bug causes the probe proccess to hang.
I think this is the bug: <http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6414472> On 6/7/07, Gary Gendel <gary at genashor.com> wrote: > I need some assistance in order to get my new archive storage up and running. > > I have a Sunfire v20z that I installed a Sil 3124 PCI-X controller on (SXCE > b64). The installation went fine, and the OS sees the controller. > > gary at phoenix[~]109#modinfo|grep 3124 > 167 fffffffff7d80000 6988 195 1 si3124 (si3124 driver v1.4) > > I have a 5-500Gb stat disk stack connected via a 5->1 Sata (SiI 3726) > multiplexer. The disks don't show up on the scans. Well, that's not exactly > true... I do see one disk in the prtconf list. The stack is connected via > port 0 of the controller > > gary at phoenix[~]110#cfgadm -l > > SATA_CFGA_GET_MODULE_INFO ioctl failed > SATA_CFGA_GET_MODULE_INFO ioctl failed > Ap_Id Type Receptacle Occupant > Condition > sata0/0.1 sata-port empty unconfigured ok > sata0/0.2 sata-port empty unconfigured ok > sata0/0.3 sata-port empty unconfigured ok > sata0/1 sata-port empty unconfigured ok > sata0/2 sata-port empty unconfigured ok > sata0/3 sata-port empty unconfigured ok > > Finally, the relevant portion of prtconf -v: > > Device Minor Nodes: > dev=(84,767) > dev_path=/pci at 0,0/pci1022,7450 at b:devctl > spectype=chr type=minor > pci1095,3124, instance #0 > Driver properties: > name='sata' type=int items=1 dev=none > value=00000001 > name='initiator-interconnect-type' type=string items=1 > dev=(195,0) > value='SPI' > name='scsi-selection-timeout' type=int items=1 dev=(195,0) > value=000000fa > name='scsi-options' type=int items=1 dev=(195,0) > value=00107ff8 > name='scsi-watchdog-tick' type=int items=1 dev=(195,0) > value=0000000a > name='scsi-tag-age-limit' type=int items=1 dev=(195,0) > value=00000002 > name='scsi-reset-delay' type=int items=1 dev=(195,0) > value=00000bb8 > Hardware properties: > name='assigned-addresses' type=int items=15 > > value=83030810.00000000.fe108000.00000000.00000080.83030818.00000000.fe100000.00000000.00008000.81030820.00000000.00003000.00000000.00000010 > name='reg' type=int items=20 > > value=00030800.00000000.00000000.00000000.00000000.03030810.00000000.00000000.00000000.00000080.03030818.00000000.00000000.00000000.00008000.01030820.00000000.00000000.00000000.00000010 > name='compatible' type=string items=7 > value='pci1095,3124.1095.3124.2' + > 'pci1095,3124.1095.3124' + 'pci1095,3124' + 'pci1095,3124.2' + 'pci1095,3124' > + 'pciclass,018000' + 'pciclass,0180' > name='model' type=string items=1 > value='Mass storage controller' > name='power-consumption' type=int items=2 > value=00000001.00000001 > name='66mhz-capable' type=boolean > name='devsel-speed' type=int items=1 > value=00000001 > name='interrupts' type=int items=1 > value=00000001 > name='max-latency' type=int items=1 > value=00000000 > name='min-grant' type=int items=1 > value=00000000 > name='subsystem-vendor-id' type=int items=1 > value=00001095 > name='subsystem-id' type=int items=1 > value=00003124 > name='unit-address' type=string items=1 > value='1' > name='class-code' type=int items=1 > value=00018000 > name='revision-id' type=int items=1 > value=00000002 > name='vendor-id' type=int items=1 > value=00001095 > name='device-id' type=int items=1 > value=00003124 > name='pci-msi-capid-pointer' type=int items=1 > value=00000054 > name='pcix-capid-pointer' type=int items=1 > value=00000040 > Interrupt Specifications: > Interrupt Priority=0x5 (ipl 5), vector=0xa (10) > Device Minor Nodes: > dev=(195,0) > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:devctl > spectype=chr type=minor > dev=(195,1024) > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:0 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/0 > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:0.5 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/0.5 > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:0.4 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/0.4 > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:0.3 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/0.3 > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:0.2 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/0.2 > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:0.1 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/0.1 > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:0.0 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/0.0 > dev=(195,1025) > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:1 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/1 > dev=(195,1026) > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:2 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/2 > dev=(195,1027) > dev_path=/pci at 0,0/pci1022,7450 at b/pci1095,3124 at > 1:3 > spectype=chr type=minor > dev_link=/dev/cfg/sata0/3 > disk (driver not attached) > Hardware properties: > name='compatible' type=string items=4 > value='scsiclass,00.vATA.pMaxtor_7H500F0.r1DD0' + > 'scsiclass,00.vATA.pMaxtor_7H500F0' + 'scsiclass,00' + 'scsiclass' > name='lun' type=int items=1 > value=00000000 > name='target' type=int items=1 > value=00000200 > name='device-type' type=string items=1 > value='scsi' > > Does this mean that the Solaris driver can't deal with the Sata multiplexer? > I thought that this was a transparent property of the 3124 controller chip. > > > This message posted from opensolaris.org > _______________________________________________ > opensolaris-help mailing list > opensolaris-help at opensolaris.org >
