Arch Linux

rettw78

Member

Registered: 2011-10-25

Posts: 6

3ware tw_cli segfaults after a recent round of updates

Hi

I have a couple of machines with 3ware 9650SE cards in them that I like to manage with the tw_cli command line client.  I know that the package for this is in AUR and not officially part of Arch, but I figured I would start here anyway to see if anyone else has seen this problem.

The current AUR 9.5.3 version and newest 10.2.1 version result in immediate segfaults when you attempt to run them with the latest arch x86_64 packages - the 9.5.3 version worked up until a couple of weeks ago.  I suspect the problem may be do to something in the newest glibc.  Any one have any ideas how I might be able to track this down and resolve it?  I am going to send a message to 3ware support as well, but I have a feeling they will tell me Arch isn't supported.  Debugging is going to be tough since I don't have source and the executable is statically linked with no debugging symbols.

I have a third machine I want to move to Arch (Its on Ubuntu) but I won't if I can't manage my RAID from within the OS.

I am running the following HW/SW combination:

C2Q Q6600 @ 3.2Ghz EVGA 780I-FTW
Corsair H100 Cooler
4x2GB Corsair Dominator PC2-8500@1066
EVGA GTX 460 1GB
3Ware 96508LP w/4 WD 320GB RAID5

Arch Linux x86_64 with using KDE desktop and latest kernel and system libs.
Nvidia proprietary drivers

kraM

Member

Registered: 2011-10-31

Posts: 3

Re: 3ware tw_cli segfaults after a recent round of updates

Error messages would be fine

I've the same problem but never had a situation where it worked, both with 9.N and 10.2 binaries (AUR).

strace -f tw_cli show all
execve("/usr/sbin/tw_cli", ["tw_cli", "show", "all"], [/* 55 vars */]) = 0
uname({sys="Linux", node="noez", ...})  = 0
brk(0)                                  = 0x1892000
brk(0x18b3000)                          = 0x18b3000
uname({sys="Linux", node="noez", ...})  = 0
--- {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} (Segmentation fault) ---
+++ killed by SIGSEGV +++

I do not think that there is too much to read out of this but if so please let me know where I can start.
I know that binary working in any versions of Linux kernel within Debian.

strings on /usr/sbin/tw_cli does not provide usable information to me as well. Anyway, if anyone has an idea where to start, please share!

Thanks,

# kraM

rettw78

Member

Registered: 2011-10-25

Posts: 6

Re: 3ware tw_cli segfaults after a recent round of updates

I was able to figure out that the problem appears to be with kernel 3.x.  Falling back to Kernel 2.6 appears to fix the issue.

I guess we will have to wait for 3ware to start supporting 3.x

Rett

kraM

Member

Registered: 2011-10-31

Posts: 3

Re: 3ware tw_cli segfaults after a recent round of updates

Hi,

this could be related to Archs naming "3.0-ARCH", but it is not related to 3.N. I've seen 10.2 working with 3.0.8 in Debian.

# kraM

rettw78

Member

Registered: 2011-10-25

Posts: 6

Re: 3ware tw_cli segfaults after a recent round of updates

Looks like I will have to compile a custom arch kernel and specify a different version more like 3.x.x to see if that helps.  I will let you know what I come up with.

kraM

Member

Registered: 2011-10-31

Posts: 3

Re: 3ware tw_cli segfaults after a recent round of updates

Right,

"renaming" the kernel works. I used /var/abs/core/linux, modified config.x86_64:

diff -Nru /var/abs/core/linux/config.x86_64 config.x86_64 
--- /var/abs/core/linux/config.x86_64	2011-11-01 05:06:40.000000000 +0100
+++ config.x86_64	2011-11-02 20:16:35.522696321 +0100
@@ -62,7 +62,7 @@
 CONFIG_EXPERIMENTAL=y
 CONFIG_INIT_ENV_ARG_LIMIT=32
 CONFIG_CROSS_COMPILE=""
-CONFIG_LOCALVERSION="-ARCH"
+CONFIG_LOCALVERSION=".7"
 CONFIG_LOCALVERSION_AUTO=y
 CONFIG_HAVE_KERNEL_GZIP=y
 CONFIG_HAVE_KERNEL_BZIP2=y

tw_cli is running fine once uname reports kernel version as "3.0.7".

I had to rebuild nvidia drivers as well, but who cares.

# kraM

Last edited by kraM (2011-11-03 06:48:31)