Is sas2ircu package outdated?

[ryanlovett]

The version of sas2ircu in the hwraid repo is 16.00.00.00. I found version 20.00.00.00.at https://datacentersupport.lenovo.com/us/en/downloads/ds117061.

[lelutin]

Also the download link on the broadcom site : https://docs.broadcom.com/docs/12351735

the 20.00.00.00 version was released on sept. 25th 2014 -- so it might help support later LSI (Avago) SAS2 devices if this was upgraded.

We've been having issues with 16.00.00.00 on a device (info below) with debian stretch:

sudo ./sas2ircu 0 display
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18) 
Copyright (c) 2008-2014 LSI Corporation. All rights reserved. 

Read configuration has been initiated for controller 0
------------------------------------------------------------------------
Controller information
------------------------------------------------------------------------
  Controller type                         : SAS2008
  BIOS version                            : 0.00.00.00
  Firmware version                        : 7.15.08.00
  Channel description                     : 1 Serial Attached SCSI
  Initiator ID                            : 0
  Maximum physical devices                : 39
  Concurrent commands supported           : 2607
  Slot                                    : 1
  Segment                                 : 0
  Bus                                     : 1
  Device                                  : 0
  Function                                : 0
  RAID Support                            : Yes
------------------------------------------------------------------------

sas2ircu usually works find, but from time to time it crashes with this message:

*** glibc detected *** /usr/sbin/sas2ircu: munmap_chunk(): invalid pointer: 0x555c5008 ***
======= Backtrace: =========
[0x8084c65]
[0x805955b]
[0x8069bb9]
[0x8066fd0]
[0x805486c]
[0x8048b6e]
[0x804e14f]
[0x804e3bb]
[0x8048862]
[0x806a3c8]
[0x8048131]
======= Memory map: ========

We've overwritten the binary with version 20.00.00.00 to try and see for a while if those free-after-free error messages go away.