From: Sander Eikelenboom <linux@eikelenboom.it>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 3.14-mw regression: rtl8169 WARNING: DMA-API: exceeded 7 overlapping mappings of pfn 55ebe
Date: Thu, 6 Feb 2014 12:36:31 +0100 [thread overview]
Message-ID: <84816226.20140206123631@eikelenboom.it> (raw)
In-Reply-To: <CAA9_cme2hgJ=jCDkPh5n5RP8fiJE-dVwbFr-apKv1=mNGPHYZg@mail.gmail.com>
Hi Dan / Francois,
Didn't have time to test it before, but the patch doesn't seem to help.
I'm still getting the "DMA-API: exceeded 7 overlapping mappings of pfn 55ebe",
but i see now i forgot to mention i use r8169.use_dac=1 ...
Not using it seems to prevent the warning, but before 3.14 i have never seen this (with r8169.use_dac=1)
--
Sander
Wednesday, January 29, 2014, 4:06:24 AM, you wrote:
> On Sun, Jan 26, 2014 at 4:03 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
>> Sander Eikelenboom <linux@eikelenboom.it> :
>> [...]
>>> I have got a regression with a 3.14-mw kernel (last commit is 4ba9920e5e9c0e16b5ed24292d45322907bb9035):
>>> It looks like it's related to the rtl8169 ...
>>>
>>> --
>>> Sander
>>>
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.105537] ------------[ cut here ]------------
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.116779] WARNING: CPU: 0 PID: 0 at lib/dma-debug.c:491 add_dma_entry+0x103/0x130()
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.128148] DMA-API: exceeded 7 overlapping mappings of pfn 55ebe
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.139397] Modules linked in:
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.150535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-20140125-mw-pcireset+ #1
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.161784] Hardware name: MSI MS-7640/890FXA-GD70 (MS-7640) , BIOS V1.8B1 09/13/2010
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.172965] 0000000000000009 ffff88005f603838 ffffffff81acbcfa ffffffff822134e0
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.184156] ffff88005f603888 ffff88005f603878 ffffffff810bdf62 ffff880000000000
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.195186] 0000000000055ebe 00000000ffffffef 0000000000000200 ffff8800592ea098
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.206227] Call Trace:
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.217027] <IRQ> [<ffffffff81acbcfa>] dump_stack+0x46/0x58
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.227907] [<ffffffff810bdf62>] warn_slowpath_common+0x82/0xb0
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.238678] [<ffffffff810be031>] warn_slowpath_fmt+0x41/0x50
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.249336] [<ffffffff81471c5a>] ? active_pfn_read_overlap+0x3a/0x70
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.259904] [<ffffffff814729e3>] add_dma_entry+0x103/0x130
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.270416] [<ffffffff81472de6>] debug_dma_map_page+0x126/0x150
>>> Jan 26 11:36:26 serveerstertje kernel: [ 89.280840] [<ffffffff81714686>] rtl8169_start_xmit+0x216/0xa20
>> [r8169 and xen stuff]
>>
>> Dan, I miss the part of the debug code that tells where the mappings were
>> previously set.
> In this case it was a facepalm mistake on my part. The mappings were
> not being properly accounted in the last revision of the patch I sent.
> I copied you on the fix [1].
> --
> Dan
> [1]: http://marc.info/?l=linux-netdev&m=139096447627032&w=2
next prev parent reply other threads:[~2014-02-06 11:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 10:55 Sander Eikelenboom
2014-01-27 0:03 ` Francois Romieu
2014-01-29 3:06 ` Dan Williams
2014-02-06 11:36 ` Sander Eikelenboom [this message]
2014-02-06 13:09 ` Sander Eikelenboom
2014-02-06 14:26 ` Dan Williams
2014-02-06 14:27 ` Sander Eikelenboom
2014-02-06 19:12 ` Dan Williams
2014-02-07 10:21 ` Sander Eikelenboom
2014-02-11 19:56 ` Sander Eikelenboom
2014-02-11 21:28 ` Eric Dumazet
2014-02-11 22:53 ` Sander Eikelenboom
2014-02-12 22:52 ` Ben Hutchings
2014-02-12 2:07 ` Dan Williams
2014-02-12 4:17 ` Eric Dumazet
2014-02-12 14:56 ` Dan Williams
2014-02-13 20:14 ` Dan Williams
2014-02-13 21:49 ` Sander Eikelenboom
2014-02-25 17:45 ` Josh Boyer
2014-02-25 17:50 ` Dan Williams
2014-02-13 20:16 ` Dave Jones
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=84816226.20140206123631@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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
all inboxes | Powered by JetHome®