http://serverfault.com/questions/525923/lsi-3ware-tw-cli-and-tdm2-segfault-with-debian-linux-kernels-after-3-8?answertab=votes#tab-topThe problem isn’t the date, it’s that tw_cli is looking for X.Y.Z(-R-arch) in the release and it’s only getting X.Y(-R-arch) - 3.2.0-4-amd64 vs 3.10-2-amd64. When the release is set to 3.10.0-2-amd64 it runs fine. They may be doing a sscanf() with limited formats, and little or no error checking.jam:~# uname -r3.10-2-amd64jam:~# tw_cli /c0 show firmwareSegmentation faultjam:~# echo 3.10.0-2-amd64 > /sys/module/utsname/parameters/releasejam:~# uname -r3.10.0-2-amd64jam:~# tw_cli /c0 show firmware/c0 Firmware Version = FE9X 4.10.00.027If the binary was dynamic you could see about a uname() replacement with LD_PRELOAD but it’s static. There’s no source code so our options are limited:LSI/3ware fixes tw_cli, hopefully removing all the uname() nonsenseGet Debian to use X.Y.Z-R-arch in releaseSomeone good with assembly comes up with a binary patch or something similarRun a custom kernelRun an older kernelDitch 3wareI like my 9650 but this is crap.竟然是因为版本号的问题！