Re: r249939+ not detecting ata trim

On 04/27/13 19:13, Steven Hartland wrote:
>
> Thats correct, the mps controllers I have here announce UNMAP support for
> SATA disks that support TRIM and then do firmware translation on the
> commands sent from the OS before passing them to the disks.
>
> This is why I was expecting your controller to still do support delete's
> eventhough ATA_TRIM wasn't enabled yet.
>
>
> I'd be interested to see the details of your controller e.g.
> Apr 28 01:36:17 host01 kernel: mps0: <LSI SAS2008> port 0xf000-0xf0ff
> mem 0xfbe00000-0xfbe03fff,0xfbd80000-0xfbdbffff irq 56 at device 0.0
> on pci129
> Apr 28 01:36:17 host01 kernel: mps0: Reserved 0x4000 bytes for rid
> 0x14 type 3 at 0xfbe00000
> Apr 28 01:36:17 host01 kernel: mps0: Firmware: 14.00.00.00, Driver:
> 14.00.00.01-fbsd
> Apr 28 01:36:17 host01 kernel: mps0: IOCCapabilities:
> 185c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,IR>
> Apr 28 01:36:17 host01 kernel: mps0: attempting to allocate 1 MSI-X
> vectors (15 supported)
>
>    Regards
>    Steve
>
> ================================================
> This e.mail is private and confidential between Multiplay (UK) Ltd.
> and the person or entity to whom it is addressed. In the event of
> misdirection, the recipient is prohibited from using, copying,
> printing or otherwise disseminating it or any information contained in
> it.
> In the event of misdirection, illegible or incomplete transmission
> please telephone +44 845 868 1337
> or return the E.mail to postmaster_at_multiplay.co.uk.
>
>
Here are the delete methods:
deleteflag: ATA_TRIM (2) = 1
da4: Delete methods: <ATA_TRIM(*)>
deleteflag: ATA_TRIM (2) = 1
da3: Delete methods: <ATA_TRIM(*)>
deleteflag: ATA_TRIM (2) = 1

Here is a truncated dmesg | fgrep mps
mps0: <LSI SAS2008> port 0xb000-0xb0ff mem
0xfe83c000-0xfe83ffff,0xfe840000-0xfe87ffff irq 32 at device 0.0 on pci3
mps0: Firmware: 15.00.00.00, Driver: 14.00.00.02-fbsd
mps0: IOCCapabilities:
1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
mps0: attempting to allocate 1 MSI-X vectors (15 supported)
mps0: using IRQ 263 for MSI-X

My firmware is ahead of the driver, and the card itself is an IBM M1015
cross-flashed to what is supposedly identical to a 9210-8i.

Thanks,
Matt