From: Ke Wei <kecore@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jeff Garzik <jeff@garzik.org>,
kewei@marvell.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH scsi-rc-fixes-2.6] mvsas: fix error handling.
Date: Tue, 29 Apr 2008 00:05:17 +0800 [thread overview]
Message-ID: <4815F5BD.5030804@gmail.com> (raw)
In-Reply-To: <1209139637.3087.12.camel@localhost.localdomain>
James Bottomley wrote:
> On Fri, 2008-04-25 at 11:51 -0400, Jeff Garzik wrote:
>> Ke Wei wrote:
>>> Changed error handling: Add a internal queue to send command in mvs_task_abort function.
>>> Set max_id and max_lun to a valid value. It's good for 64xx chip.
>>> BTW, DVD-ROM compatibility needs to test carefully.
>>>
>>>
>>> Signed-off-by: Ke Wei <kewei@marvell.com>
>> James, ping?
>>
>> Did this get missed? Are we waiting on Marvell to update this patch?
>
> Actually, the patch contains a red flag:
>
>> - mvi->shost->max_id = 21;
>> - mvi->shost->max_lun = ~0;
>> + mvi->shost->max_id = 128;
>> + mvi->shost->max_lun = 1;
>
> Setting max_lun to 1 can't be right. My suspicion is that it's done to
> turn off the REPORT_LUN scan that I've already said twice is necessary.
>
> The DVD that's showing the problems needs to be blacklisted.
>
> So, it's on my list to check carefully to see what else might have been
> quietly slipped in there ... unfortunately, I haven't had much time
> recently (and probably won't until the merge window closes) to give this
> patch the thorough scrutiny it needs.
>
First, Thank you for your help, Jeff and James.
I am investigating whether other devices have the same issue as my testing DVD caused by REPORT_LUNS command.
So I think I doesn't need to add this device to blacklists before I check. My colleague is working on the libsas module so that we hope SAS transport is more powerful and stable.
Ke
next prev parent reply other threads:[~2008-04-28 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 10:31 [PATCH scsi-rc-fixes-2.6] mvsas: fix error handling Ke Wei
2008-04-25 15:51 ` Jeff Garzik
2008-04-25 16:07 ` James Bottomley
2008-04-28 16:05 ` Ke Wei [this message]
2008-05-07 10:34 ` Ke Wei
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=4815F5BD.5030804@gmail.com \
--to=kecore@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jeff@garzik.org \
--cc=kewei.mv@gmail.com \
--cc=kewei@marvell.com \
--cc=linux-scsi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.