From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: b44 driver causes panic when using swiotlb
Date: Mon, 14 Feb 2011 17:41:54 +0100 [thread overview]
Message-ID: <ijbm0i$n7h$1@dough.gmane.org> (raw)
In-Reply-To: 20110214205945W.fujita.tomonori@lab.ntt.co.jp
FUJITA Tomonori wrote:
> On Tue, 1 Feb 2011 22:54:56 +0900
> FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
>
>> On Mon, 31 Jan 2011 10:54:12 -0500
>> Chuck Ebbert <cebbert@redhat.com> 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:
>>
>> Can you try this? b44 has the own bouncing mechanism so if swiotlb
>> returns an error, the driver can allocate an appropriate buffer.
>>
>> diff --git a/lib/swiotlb.c b/lib/swiotlb.c
>> index c47bbe1..93ca08b 100644
>> --- a/lib/swiotlb.c
>> +++ b/lib/swiotlb.c
>> @@ -686,8 +686,10 @@ dma_addr_t swiotlb_map_page(struct device *dev,
>> struct page *page,
>> /*
>> * Ensure that the address returned is DMA'ble
>> */
>> - if (!dma_capable(dev, dev_addr, size))
>> - panic("map_single: bounce buffer is not DMA'ble");
>> + if (!dma_capable(dev, dev_addr, size)) {
>> + swiotlb_tbl_unmap_single(dev, map, size, dir);
>> + dev_addr = swiotlb_virt_to_bus(dev,
io_tlb_overflow_buffer);
>> + }
>>
>> return dev_addr;
>> }
>
> Ping, any chance to try this?
Friend machine oopsed on network with b44 on 2.6.37, so we tried this patch
and network card was detected nicely and was actually usable. The oops
started to happen after he upgraded memory from 2GB to 4GB in his dell
vostro 1500 notebook.
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev
02)
# grep b44 dmesg.log
[ 8.524297] b44 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 8.576838] b44: b44.c:v2.0
[ 8.593920] b44 ssb1:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet
00:1c:23:9b:3f:5f
[ 55.350228] b44 ssb1:0: eth0: Link is up at 100 Mbps, full duplex
[ 55.350233] b44 ssb1:0: eth0: Flow control is off for TX and off for RX
> Thanks,
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next prev parent reply other threads:[~2011-02-14 16:42 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
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 [this message]
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='ijbm0i$n7h$1@dough.gmane.org' \
--to=arekm@maven.pl \
--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