public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Vilhelm <christian.vilhelm@univ-lille2.fr>
To: "Meena Shanmugam, TLS-Chennai" <smeena@hcl.in>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"tfjellstrom@shaw.ca" <tfjellstrom@shaw.ca>
Subject: Re: MVSAS 1669:mvs_abort_task:rc= 5
Date: Thu, 15 Oct 2009 08:01:03 +0200	[thread overview]
Message-ID: <4AD6BA9F.1060704@univ-lille2.fr> (raw)
In-Reply-To: <3CD4E24D4F537D439B71EB28963F98F46815EA2115@CHN-HCLT-EVS06.HCLT.CORP.HCL.IN>

Meena Shanmugam, TLS-Chennai wrote:
> Hi,
> 
> I am also facing the same problem with this driver. I'm using Adaptec ASC-1045 which uses the Marvell 88SE6440 chip. In my case, this could be reproduced with RAID-5 configured with 3 SATA drives. While analysing the problem, it looks like the prd table is getting corrupted in the SATA path triggers the issue.
> 
> ----mvs_sas.c---
>  726 #ifndef DISABLE_HOTPLUG_DMA_FIX
>  727         if (task->data_dir == DMA_FROM_DEVICE)
>  728                 MVS_CHIP_DISP->dma_fix(asi->bulk_buffer_dma,
>  729                         TRASH_BUCKET_SIZE, tei->n_elem, buf_prd);
>  730 #endif
> -----------
> 
> The hang issue doesn't occur after enabling DISABLE_HOTPLUG_DMA_FIX in mvs_sas.h file. Please let me know if this fix solves the issue. Btw, I'm not sure about the reason why this macro is disabled by default. Someone who is aware about this change can throw light on this. Meanwhile, I'm running some overnight test to see if this workaround/fix is harmless.

I just tried that, enabling DISABLE_HOTPLUG_DMA_FIX. I still get the 
error when creating an array, it just worked a little further (building 
for two minutes before hanging instead of immediately).

Christian Vilhelm.

-- 
/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\
|       Christian Vilhelm : christian.vilhelm@univ-lille2.fr         |
|            Reality is for people who lack imagination              |
\____________________________________________________________________/

  reply	other threads:[~2009-10-15  6:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CA9DA403FFEC64AA62B3C295F8D47B72126836F2E@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
2009-10-14 15:39 ` MVSAS 1669:mvs_abort_task:rc= 5 Meena Shanmugam, TLS-Chennai
2009-10-15  6:01   ` Christian Vilhelm [this message]
     [not found]     ` <e938503f0910142326i54f12756m11c28d5c4b61edf3@mail.gmail.com>
2009-10-15  7:27       ` Christian Vilhelm
     [not found] <e938503f0910142007k7fca9ebcx856a19010feb812b@mail.gmail.com>
2009-10-15  6:44 ` Meena Shanmugam, TLS-Chennai
2009-10-09 17:41 Thomas Fjellstrom
2009-10-10 15:56 ` Thomas Fjellstrom
     [not found]   ` <20091010164422.GA8896@linux-dev>
2009-10-10 19:18     ` Thomas Fjellstrom
2009-10-11 18:34 ` Christian Vilhelm
2009-10-11 22:58   ` Thomas Fjellstrom
2009-10-14  1:39     ` Thomas Fjellstrom
     [not found]       ` <e938503f0910132151p20b42459v96800d889f3f63eb@mail.gmail.com>
2009-10-14  7:18         ` Thomas Fjellstrom
2009-10-14  7:55           ` Christian Vilhelm
     [not found]             ` <73e903670910140147oafebad7h6c68849e0599c21b@mail.gmail.com>
2009-10-14  8:51               ` Kristleifur Daðason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AD6BA9F.1060704@univ-lille2.fr \
    --to=christian.vilhelm@univ-lille2.fr \
    --cc=linux-scsi@vger.kernel.org \
    --cc=smeena@hcl.in \
    --cc=tfjellstrom@shaw.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox