From: "Darrick J. Wong" <djwong@us.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: akpm@linux-foundation.org, linux-scsi@vger.kernel.org, "Moore,
Eric" <Eric.Moore@lsi.com>
Subject: Re: [patch 03/13] mptbase: reset ioc initiator during PCI resume
Date: Thu, 7 Feb 2008 17:23:24 -0800 [thread overview]
Message-ID: <20080208012324.GA3601@tree.beaverton.ibm.com> (raw)
In-Reply-To: <1202431285.3171.46.camel@localhost.localdomain>
On Thu, Feb 07, 2008 at 06:41:25PM -0600, James Bottomley wrote:
> On Mon, 2008-02-04 at 23:53 -0800, akpm@linux-foundation.org wrote:
> > From: "Darrick J. Wong" <djwong@us.ibm.com>
> >
> > It appears that the LSI SAS 1064E chip needs to be reset after a
> > suspend/resume cycle before the driver attempts further communications with
> > the chip. Without this patch, resuming the chip results in this error
> > message being printed repeatedly and no more disk I/O.
> >
> > mptbase: ioc0: ERROR - Invalid IOC facts reply, msgLength=0 offsetof=6!
> >
> > So far it seems to fix suspend/resume on all the MPT Fusion cards I have
> > (SAS and U320 SCSI) but since I don't know the internals of that chip I
> > can't say for sure if this is a proper fix.
> >
> > Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>
> Ping on this, please Eric.
As far as I can tell, Eric isn't really involved with this patch
anymore, and handed it over to Sathya.Prakash@lsi.com. I received email
from him (her? Apologies, I'm not sufficiently familiar with Indian
names) this morning saying that a modified version of it would go out to
linux-scsi in a day or two.
--D
prev parent reply other threads:[~2008-02-08 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 7:53 [patch 03/13] mptbase: reset ioc initiator during PCI resume akpm
2008-02-08 0:41 ` James Bottomley
2008-02-08 1:23 ` Darrick J. Wong [this message]
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=20080208012324.GA3601@tree.beaverton.ibm.com \
--to=djwong@us.ibm.com \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--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.