public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Moore, Eric Dean" <emoore@lsil.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-scsi@vger.kernel.org, James.Bottomley@steeleye.com,
	Alexander.Stohr@gmx.de, rddunlap@osdl.org
Subject: Re: [PATCH 2.6 ] MPT Fusion driver 3.01.02 update
Date: Wed, 17 Mar 2004 18:38:51 -0700	[thread overview]
Message-ID: <001201c40c89$c4fcef20$221015ac@ericmoore> (raw)
In-Reply-To: 20040318020948.2f884e89.ak@suse.de

Andi -

The fix in 3.01.02 was your request for commenting out the
"queue is full message" which you posted to the
mailing list earlier in the last week.  This has nothing to do with
with todays issue.

Regarding todays issue.  There is a work around for your
issue which I have already suggested earlier today. That is
to modify the mpt fusion Makefile, by uncommenting out
the FIFO FIX define.  This work around will set a dma mask
for less 4GB, thus we don't hit the error condition in PrimeFifo's
when the two memory allocation are on different 4gb boundaries, and
the failure displays "-3" error code as yours did in the original dmesg.

I have provided this temp fix to HP a few weeks ago.
I plan to start work soon to solve this issue by combining these three
FIFOs into one memory allocation( the third FIFO allocation is
in mptscsih.c, that is the chain buffers).

Eric Moore




----- Original Message ----- 
From: "Andi Kleen" <ak@suse.de>
To: "Moore, Eric Dean" <Emoore@lsil.com>
Cc: <linux-scsi@vger.kernel.org>; <James.Bottomley@steeleye.com>;
<Alexander.Stohr@gmx.de>; <rddunlap@osdl.org>
Sent: Wednesday, March 17, 2004 6:09 PM
Subject: Re: [PATCH 2.6 ] MPT Fusion driver 3.01.02 update


> On Wed, 17 Mar 2004 14:43:21 -0500
> "Moore, Eric Dean" <Emoore@lsil.com> wrote:
>
> > This is an update for the MPT Fusion drivers 2.6 kernel.
> > Version 3.01.02.
> >
> This doesn't seem to fix the bug I'm running into all the time:
>
> you set a 64bit consistent dma mask, but assume in PrimeIocFifos
> that two calls to pci_alloc_consistent() end in the same 4GB
> segment, which cannot work.
>
> As a workaround i just reverted it to a 4GB consistent mask for now.
>
> -Andi
>
>
>


  reply	other threads:[~2004-03-18  1:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 19:43 [PATCH 2.6 ] MPT Fusion driver 3.01.02 update Moore, Eric Dean
2004-03-17 20:20 ` Jeff Garzik
2004-03-18  1:09 ` Andi Kleen
2004-03-18  1:38   ` Moore, Eric Dean [this message]
2004-03-18  1:58     ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-03-17 22:02 Moore, Eric Dean
2004-03-17 22:15 ` Jeff Garzik
2004-03-17 23:49 Moore, Eric Dean

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='001201c40c89$c4fcef20$221015ac@ericmoore' \
    --to=emoore@lsil.com \
    --cc=Alexander.Stohr@gmx.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=ak@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rddunlap@osdl.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