From: Malahal Naineni <malahal@us.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
Date: Tue, 28 Sep 2010 17:42:14 -0700 [thread overview]
Message-ID: <20100929004213.GA9978@us.ibm.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D5301605546A7@orsmsx505.amr.corp.intel.com>
Luck, Tony [tony.luck@intel.com] wrote:
> > Let me know if this fixes the problem. Thank you very much.
>
> No it doesn't :-(
>
> I still end up with 0xffffffff from the *host_dev->dma_mask
> later in that function.
>
> Just for two devices though ... stack traces lead back to
> usb_stor_scan_thread() for these two.
What is the USB host controller's PCI device and vendor IDs? I see
ehci-ps3.c and ohci-ps3.c setting it to DMA_BIT_MASK(32). That may
present another bug???
I don't know USB much, but someone seems to be lying that they can't do DMA
beyond 4GB!
How much memory you have on the system? This probably doesn't matter but
good to know.
Thanks, Malahal.
next prev parent reply other threads:[~2010-09-29 0:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 22:13 [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory Luck, Tony
2010-09-28 22:59 ` Malahal Naineni
2010-09-28 23:40 ` Luck, Tony
2010-09-29 0:42 ` Malahal Naineni [this message]
2010-09-29 4:47 ` Luck, Tony
2010-09-29 5:55 ` Malahal Naineni
2010-09-29 16:00 ` Luck, Tony
-- strict thread matches above, loose matches on Subject: below --
2010-09-21 22:22 Malahal Naineni
2010-09-22 23:06 ` Malahal Naineni
2010-09-24 13:58 ` Jens Axboe
2010-09-24 17:05 ` Malahal Naineni
2010-09-24 18:28 ` Jens Axboe
2010-09-24 19:20 ` Malahal Naineni
2010-09-24 19:26 ` Jens Axboe
2010-10-01 2:30 ` Malahal Naineni
2010-10-01 12:46 ` Jens Axboe
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=20100929004213.GA9978@us.ibm.com \
--to=malahal@us.ibm.com \
--cc=jaxboe@fusionio.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).