From: David Daney <ddaney@caviumnetworks.com>
To: Zhuang Yuyao <mlistz@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [BUG?] cavium cn56xx and dma_map_single warning
Date: Mon, 22 Mar 2010 09:44:25 -0700 [thread overview]
Message-ID: <4BA79E69.1040803@caviumnetworks.com> (raw)
In-Reply-To: <e732b6801003220001m7e08bbf7w20ba62d42f30a190@mail.gmail.com>
On 03/22/2010 12:01 AM, Zhuang Yuyao wrote:
> Hi,
>
> I've got a strange dma error on my cavium cn56xx board.
>
> ......
> dma_map_single: Warning: Mapping memory address that might conflict
> with devices 0xfbb8f000-0xfbb8ffff
> dma_map_single: Warning: Mapping memory address that might conflict
> with devices 0xfb2ef000-0xfb2f0fff
> dma_map_single: Warning: Mapping memory address that might conflict
> with devices 0xfb3de000-0xfb3defff
> dma_map_single: Warning: Mapping memory address that might conflict
> with devices 0xfb3dd000-0xfb3ddfff
> dma_map_single: Warning: Mapping memory address that might conflict
> with devices 0xfac28000-0xfac29fff
> dma_map_single: Warning: Mapping memory address that might conflict
> with devices 0xfad1a000-0xfad1bfff
> .....
>
> this error appeared when I plugged 4G or 8G ram on the board, if there
> is only 2G ram on the board, the error never happened.
>
> an adaptec 3405 pci-e raid card is plugged on the board, and a
> harddisk attached. the program i am running is a postgresql server
> with more than 20 million record, so do a count(*) will let postgresql
> consume almost all of the available memory. while there is 4G ram, the
> 'free' command reported that the free memory is below 18M.
>
> then the error kept printing on the console for a while, then kernel panic.
>
> the warning message is come from arch/mips/cavium-octeon/dma-octeon.c
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=arch/mips/cavium-octeon/dma-octeon.c;h=be531ec1f2064b590b58dfe8b4db4f5534999bab;hb=HEAD
>
> i tried several raid card from different producer, including LSI and
> Adaptec. the same error always happened while there are more than or
> equal to 4G memory on the board.
>
> Would you please give some advice on this issue? any help will be appreciated.
This is a known issue.
passing mem==3072M will restrict kernel memory usage thus avoiding the
issue.
David Daney
>
> Thanks.
>
> Zhuang Yuyao
>
next prev parent reply other threads:[~2010-03-22 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 7:01 [BUG?] cavium cn56xx and dma_map_single warning Zhuang Yuyao
2010-03-22 9:31 ` Zhuang Yuyao
2010-03-22 16:44 ` David Daney [this message]
2010-03-23 1:30 ` Zhuang Yuyao
2010-03-23 1:39 ` David Daney
2010-03-23 1:45 ` Zhuang Yuyao
2010-03-24 16:27 ` David Daney
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=4BA79E69.1040803@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=mlistz@gmail.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