linux-kernel - MVSAS 1669:mvs_abort

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200910091141.52303.tfjellstrom@shaw.ca>
Date:	Fri, 9 Oct 2009 11:41:52 -0600
From:	Thomas Fjellstrom <tfjellstrom@...w.ca>
To:	linux-kernel@...r.kernel.org
Cc:	linux-raid@...r.kernel.org,
	"linux-scsi" <linux-scsi@...r.kernel.org>
Subject: MVSAS 1669:mvs_abort_task:rc= 5

Hi,

I've been trying to get an AOC-SASLP-MV8 card (pcie x4 2 port SAS card) to 
work with linux for the past month or so. I've recently just RMAed my first 
card, and tested the new one under linux, and I see the same problems.

The very first time I made a new array off the controller, formated (with xfs) 
and mounted the volume, it seemed to work. ioozone even seemed to run for a 
while. Sadly after a few minutes I got a stream of mvs_abort_task messages in 
dmesg, and any accesses to the volume, or any disks connected to the 
controller lock up.

After that I updated my 2.6.31 kernel to 2.6.32-rc3-git2 off of kernel.org, 
and the volume fails to mount with the same mvs_abort_task messages.

I've attached my dmesg log from both attempts. dmesg1 is the first attempt, 
dmesg2 is the second attempt on the newer kernel.

I would really appreciate some help with this.

-- 
Thomas Fjellstrom
tfjellstrom@...w.ca

View attachment "test-data.dmesg1" of type "text/plain" (69663 bytes)

View attachment "test-data.dmesg2" of type "text/plain" (68901 bytes)