From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Prakash, Sathya" <Sathya.Prakash@lsi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Moore, Eric" <Eric.Moore@lsi.com>
Subject: Re: Fix for problems introduced by enabling MSI by default for MPT SPI controllers
Date: Wed, 09 Jul 2008 09:10:37 -0500 [thread overview]
Message-ID: <1215612637.3293.1.camel@localhost.localdomain> (raw)
In-Reply-To: <6A4D764DC1BDE14495DA8DC60A3D69531E95D72239@hkgmail01.lsi.com>
On Wed, 2008-07-09 at 14:54 +0800, Prakash, Sathya wrote:
> Recently there are some issues posted in the list with regards to failure of booting or failure of driver loading when the MSI is enabled by default for MPT SPI controllers.
>
> James has already provided the patch for fixing the panic.
>
> But the reason for IOC bring up failure is enabling the MSI by default for SPI controllers. The issue is introduced by the following patch. Which is intended for enabling the MSI only for SAS controllers but enables MSI for SPI, FC and SAS controllers.
> http://marc.info/?l=linux-scsi&m=120488594802569&w=4
>
> I have already posted another patch to rectify this so that MSI will not be enabled by default for SPI and FC controllers. The link for the correction patch is as below.
> http://marc.info/?l=linux-scsi&m=121131228827682&w=4
Is there an actual fault in the MSI controller on the SPI and FC fusion?
I'm asking because usually we just follow the platform defaults unless
there's a specific reason to blacklist the individual device.
James
next prev parent reply other threads:[~2008-07-09 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 6:54 Fix for problems introduced by enabling MSI by default for MPT SPI controllers Prakash, Sathya
2008-07-09 14:10 ` James Bottomley [this message]
2008-07-10 8:38 ` Prakash, Sathya
2008-07-10 13:56 ` James Bottomley
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=1215612637.3293.1.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Eric.Moore@lsi.com \
--cc=Sathya.Prakash@lsi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox