From: Andi Kleen <ak@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: linux-scsi@vger.kernel.org, emoore@lsil.com,
James.Bottomley@HansenPartnership.com
Subject: Re: Fusion problems with 2.6.5rc1 on AMD x86-64 IV
Date: Wed, 17 Mar 2004 10:06:57 +0100 [thread overview]
Message-ID: <20040317100657.28c4bdbe.ak@suse.de> (raw)
In-Reply-To: <20040317100040.28304c12.ak@suse.de>
On Wed, 17 Mar 2004 10:00:40 +0100
Andi Kleen <ak@suse.de> wrote:
> On Wed, 17 Mar 2004 06:03:32 +0100
> Andi Kleen <ak@suse.de> wrote:
>
>
> > The actual problem is the recent consistent_dma_mask change from James. For some reason
> > the x86-64 pci_alloc_consistent always sees an 0xffffffffffffffff dma mask now
> > and that breaks Fusion.
>
> I found some bugs in x86-64 code now that explained the problem. For some reason
> the consistent mask patchkit seems to have triggered them. It's fixed now.
Sorry for the many follow ups to myself :-)
Anyways the consistent mask problem is still with us. I just have a workaround that
works (force it to 4GB) and there were related bugs in the x86-64 IOMMU code.
James, can you take a look at that please? From a first look i didn't find the place
where it is set to 0xffffffffffffffff. It isn't the driver.
-Andi
next prev parent reply other threads:[~2004-03-17 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040317024917.630dcb86.ak@suse.de>
[not found] ` <20040317060332.36d492ab.ak@suse.de>
2004-03-17 9:00 ` Fusion problems with 2.6.5rc1 on AMD x86-64 III Andi Kleen
2004-03-17 9:06 ` Andi Kleen [this message]
2004-03-17 15:58 Fusion problems with 2.6.5rc1 on AMD x86-64 IV Moore, Eric Dean
2004-03-17 15:53 ` Andi Kleen
2004-03-17 16:34 ` 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=20040317100657.28c4bdbe.ak@suse.de \
--to=ak@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=emoore@lsil.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