public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Chuck Ebbert <cebbert@redhat.com>,
	linux-kernel@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: b44 driver causes panic when using swiotlb
Date: Mon, 31 Jan 2011 18:54:21 -0600	[thread overview]
Message-ID: <4D4759BD.2000006@gmail.com> (raw)
In-Reply-To: <20110131163639.GA32095@tassilo.jf.intel.com>

On 01/31/2011 10:36 AM, Andi Kleen wrote:
> On Mon, Jan 31, 2011 at 10:54:12AM -0500, Chuck Ebbert wrote:
>> The b44 driver is triggering this panic in swiotlb_map_page():
>>
>>          if (!dma_capable(dev, dev_addr, size))
>>                  panic("map_single: bounce buffer is not DMA'ble");
>>
>> The kernel log says the bounce buffers are at 0xdb400000, but b44 can
>> only do DMA to the first 1GB of memory:
>
> b44 needs to use GFP_DMA then and do its own custom bouncing.
> The standard pci_map_* bounce buffering is only designed for at least
> 32bit capable devices.

That seems wrong - it's a documented API and that restriction isn't 
documented. Either it should comply with the request or return a failure 
if it can't accomodate it, not just blow up internally. There's no 
reason the driver should have to deal with this on its own.

In this case the DMA mapping code  should really be falling back to 
GFP_DMA automatically if the IOMMU aperture is outside the DMA mask of 
the device.

>
> BTW I'm pretty sure this worked at some point, must have regressed
> somehow.


  reply	other threads:[~2011-02-01  0:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 15:54 b44 driver causes panic when using swiotlb Chuck Ebbert
2011-01-31 16:36 ` Andi Kleen
2011-02-01  0:54   ` Robert Hancock [this message]
2011-02-01  1:28     ` FUJITA Tomonori
2011-02-01  3:22       ` Robert Hancock
2011-02-01  5:22         ` FUJITA Tomonori
2011-02-15  0:47           ` Robert Hancock
2011-02-01 21:18       ` Chuck Ebbert
2011-02-02  0:06         ` FUJITA Tomonori
2011-02-02  0:09           ` FUJITA Tomonori
2011-02-01 18:07     ` Andi Kleen
2011-02-01 21:44       ` Robert Hancock
2011-02-01 13:54 ` FUJITA Tomonori
2011-02-14 11:59   ` FUJITA Tomonori
2011-02-14 16:41     ` Arkadiusz Miśkiewicz
2011-02-15  0:39       ` FUJITA Tomonori
2011-02-15 22:03     ` Chuck Ebbert
     [not found] <4D478EDC.4070004@lwfinger.net>
2011-02-01  4:53 ` Larry Finger

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=4D4759BD.2000006@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=cebbert@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@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