tws bug ? (LSI SAS 9750)

[Jim Harris]

On Fri, Sep 21, 2012 at 3:11 PM, Mike Tancsa <mike at sentex.net> wrote:
> On 9/21/2012 4:59 PM, Jim Harris wrote:

<snip>

> Thanks, that allows it to boot up now!
>
> pci2: <ACPI PCI bus> on pcib2
> LSI 3ware device driver for SAS/SATA storage controllers, version:
> 10.80.00.003
> tws0: <LSI 3ware SAS/SATA Storage Controller> port 0x4000-0x40ff mem
> 0xc2460000-0xc2463fff,0xc2400000-0xc243ffff irq 17 at device 0.0 on pci2
> tws0: Using MSI
> tws0: Controller details: Model 9750-4i, 8 Phys, Firmware FH9X
> 5.12.00.007, BIOS BE9X 5.11.00.006
> em0: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0x5040-0x505f mem
> 0xc2500000-0xc251ffff,0xc2570000-0xc2570fff irq 19 at device 25.0 on pci0
> .
> then a lot of
> .
> (probe65:tws0:0:65:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe65:tws0:0:65:0): CAM status: Invalid Target ID
> (probe65:tws0:0:65:0): Error 22, Unretryable error
> (probe1:tws0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe1:tws0:0:1:0): CAM status: Invalid Target ID
> (probe1:tws0:0:1:0): Error 22, Unretryable error
> (probe2:tws0:0:2:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe2:tws0:0:2:0): CAM status: Invalid Target ID
> .
> .
> .
> (probe63:tws0:0:63:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe63:tws0:0:63:0): CAM status: Invalid Target ID
> (probe63:tws0:0:63:0): Error 22, Unretryable error
> (probe64:tws0:0:64:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe64:tws0:0:64:0): CAM status: Invalid Target ID
> (probe64:tws0:0:64:0): Error 22, Unretryable error

These can be ignored.  CAM is just telling you that there are no
devices attached at these target IDs.

> da0 at tws0 bus 0 scbus0 target 0 lun 0
> da0: <LSI 9750-4i    DISK 5.12> Fixed Direct Access SCSI-5 device
> da0: 6000.000MB/s transfers
> da0: 953654MB (1953083392 512 byte sectors: 255H 63S/T 121573C)
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #4 Launched!
>

<snip>

>
> Any thoughts on msi vs no msi ?  Time to run some stress tests.  Its
> certainly a fast little controller for the money!
>

Typically MSI is preferred to INTx for performance reasons.  I can't
speak for why the original author made INTx the default though.

Regards,

-Jim