linux-kernel - Re: 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-prev] [day] [month] [year] [list]

Message-ID: <4AD583DB.2070806@univ-lille2.fr>
Date:	Wed, 14 Oct 2009 09:55:07 +0200
From:	Christian Vilhelm <christian.vilhelm@...v-lille2.fr>
To:	tfjellstrom@...w.ca
CC:	andy yan <andyysj@...il.com>, linux-kernel@...r.kernel.org,
	linux-raid@...r.kernel.org,
	linux-scsi <linux-scsi@...r.kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@...e.de>, kewei@...vell.com
Subject: Re: MVSAS 1669:mvs_abort_task:rc= 5

Thomas Fjellstrom wrote:
> On Tue October 13 2009, andy yan wrote:
>> I will send you a patch for debugging this issue, please help to try and
>> send back the log, thanks!
> 
> I will do whatever I can to help get this resolved :) I have some C skills, 
> but no kernel/device driver experience, so at the very least I should be able 
> to do builds and make small changes if needed, in addition to patching and 
> endless reboots ;D

I'm also willing to help.
The card is not on a production server and the disks connected to the 
card do not contain any valuable data so I can make any test wanted.

When the problem occurs it seems the devices (disks) are hosed. Deleting 
them from the system (echo 1 > /sys/block/sdh/device/delete), removing 
the mvsas module (rmmod -f) and reloading it doesn't work. The card 
seems correctly initialised after reloading the module, it correctly 
responds to commands (in /sys/class/sas_phy/ and sas_ports, I can reset 
ports/phys, I can ask for a rescan of disks). But the disks themselves 
do not seem to answer to the scan and are not detected, all I get is :

Oct 13 15:17:33 almery kernel: [29162.468218] sas: sas_ata_phy_reset: 
Found ATA device.
Oct 13 15:17:33 almery kernel: [29162.470279] ata19.00: both IDENTIFYs 
aborted, assuming NODEV
Oct 13 15:17:33 almery kernel: [29162.470321] sas: sas_ata_phy_reset: 
Found ATA device.
Oct 13 15:17:33 almery kernel: [29162.472391] ata19.00: both IDENTIFYs 
aborted, assuming NODEV
Oct 13 15:17:33 almery kernel: [29162.472433] sas: sas_ata_phy_reset: 
Found ATA device.
Oct 13 15:17:33 almery kernel: [29162.474492] ata19.00: both IDENTIFYs 
aborted, assuming NODEV
Oct 13 15:17:33 almery kernel: [29162.474533] ata19.00: disabled
Oct 13 15:17:33 almery kernel: [29162.474572] sas: sas_ata_phy_reset: 
Found ATA device.
Oct 13 15:17:33 almery kernel: [29162.474627] scsi_alloc_sdev: 
Allocation failure during SCSI scanning, some SCSI devices might not be 
configured

Is there a way to get a disk to reinitialize itself without a reboot ?

Drives are SAMSUNG HD501LJ
Linux almery 2.6.31.1-vs2.3.0.36.14 #7 SMP Mon Oct 12 12:58:07 CEST 2009 
x86_64 GNU/Linux
with or withous vserver patch applied : same problem, kernel not tainted.

The problem occurs also when the disks are not in an md array.

Christian Vilhelm.

-- 
/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\
|       Christian Vilhelm : christian.vilhelm@...v-lille2.fr         |
|            Reality is for people who lack imagination              |
\____________________________________________________________________/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/