From: poma <pomidorabelisima@gmail.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Clemens Ladisch <clemens@ladisch.de>,
Takashi Iwai <tiwai@suse.de>,
Mailing-List fedora-kernel <kernel@lists.fedoraproject.org>,
Dan Williams <dan.j.williams@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sander Eikelenboom <linux@eikelenboom.it>,
Dave Jones <davej@redhat.com>,
Sander Eikelenboom <linux@eikelenboom.it>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Francois Romieu <romieu@fr.zoreil.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Wei Liu <wei.liu2@citrix.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline
Date: Wed, 23 Apr 2014 02:53:51 +0200 [thread overview]
Message-ID: <53570F1F.1000709@gmail.com> (raw)
In-Reply-To: <53500CDB.8050802@gmail.com>
This one comes and goes...
------------[ cut here ]------------
WARNING: CPU: 2 PID: 521 at lib/dma-debug.c:593
debug_dma_assert_idle+0x159/0x1d0()
snd_hda_intel 0000:00:07.0: DMA-API: cpu touching an active dma mapped
cacheline [cln=0x03019000]
------------[ cut here ]------------
WARNING: CPU: 3 PID: 927 at lib/dma-debug.c:593
debug_dma_assert_idle+0x159/0x1d0()
snd_hda_intel 0000:00:07.0: DMA-API: cpu touching an active dma mapped
cacheline [cln=0x03019000]
CPU: 3 PID: 927 Comm: firewalld Not tainted 3.15.0-0.rc2.git1.1.fc21.i686 #1
Call Trace:
[<c0ae29dd>] dump_stack+0x48/0x60
[<c0454402>] warn_slowpath_common+0x82/0xa0
[<c0750e09>] ? debug_dma_assert_idle+0x159/0x1d0
[<c0750e09>] ? debug_dma_assert_idle+0x159/0x1d0
[<c045445e>] warn_slowpath_fmt+0x3e/0x60
[<c0750e09>] debug_dma_assert_idle+0x159/0x1d0
[<c0586189>] ? anon_vma_prepare+0x29/0x140
[<c057a5be>] do_wp_page+0xce/0x890
[<c0640065>] ? ext4_releasepage+0x95/0x130
[<c057cbc2>] handle_mm_fault+0x662/0xb70
[<c0640065>] ? ext4_releasepage+0x95/0x130
[<c0aee997>] __do_page_fault+0x1a7/0x5d0
[<c04adcac>] ? trace_hardirqs_on_caller+0x13c/0x1e0
[<c04ff83c>] ? __audit_syscall_entry+0x8c/0xe0
[<c04add5b>] ? trace_hardirqs_on+0xb/0x10
[<c04adcac>] ? trace_hardirqs_on_caller+0x13c/0x1e0
[<c04adcac>] ? trace_hardirqs_on_caller+0x13c/0x1e0
[<c0aeedc0>] ? __do_page_fault+0x5d0/0x5d0
[<c0aeedda>] do_page_fault+0x1a/0x20
[<c0aeb7b4>] error_code+0x6c/0x74
---[ end trace 0464944e27da06b8 ]---
Mapped at:
[<c074eeb2>] debug_dma_alloc_coherent+0x22/0x70
[<f839de90>] snd_dma_alloc_pages+0x170/0x260 [snd_pcm]
[<f839dfe2>] snd_dma_alloc_pages_fallback+0x62/0x90 [snd_pcm]
[<f839e3b0>] snd_malloc_sgbuf_pages+0xf0/0x211 [snd_pcm]
[<f839df23>] snd_dma_alloc_pages+0x203/0x260 [snd_pcm]
CPU: 2 PID: 521 Comm: firewalld Tainted: G W
3.15.0-0.rc2.git1.1.fc21.i686 #1
Call Trace:
[<c0ae29dd>] dump_stack+0x48/0x60
[<c0454402>] warn_slowpath_common+0x82/0xa0
[<c0750e09>] ? debug_dma_assert_idle+0x159/0x1d0
[<c0750e09>] ? debug_dma_assert_idle+0x159/0x1d0
[<c045445e>] warn_slowpath_fmt+0x3e/0x60
[<c0750e09>] debug_dma_assert_idle+0x159/0x1d0
[<c0586189>] ? anon_vma_prepare+0x29/0x140
[<c057a5be>] do_wp_page+0xce/0x890
[<c0640065>] ? ext4_releasepage+0x95/0x130
[<c057cbc2>] handle_mm_fault+0x662/0xb70
[<c0640065>] ? ext4_releasepage+0x95/0x130
[<c0aee997>] __do_page_fault+0x1a7/0x5d0
[<c04ff83c>] ? __audit_syscall_entry+0x8c/0xe0
[<c04add5b>] ? trace_hardirqs_on+0xb/0x10
[<c04adcac>] ? trace_hardirqs_on_caller+0x13c/0x1e0
[<c0aeedc0>] ? __do_page_fault+0x5d0/0x5d0
[<c0aeedda>] do_page_fault+0x1a/0x20
[<c0aeb7b4>] error_code+0x6c/0x74
---[ end trace 0464944e27da06b9 ]---
Mapped at:
[<c074eeb2>] debug_dma_alloc_coherent+0x22/0x70
[<f839de90>] snd_dma_alloc_pages+0x170/0x260 [snd_pcm]
[<f839dfe2>] snd_dma_alloc_pages_fallback+0x62/0x90 [snd_pcm]
[<f839e3b0>] snd_malloc_sgbuf_pages+0xf0/0x211 [snd_pcm]
[<f839df23>] snd_dma_alloc_pages+0x203/0x260 [snd_pcm]
https://bugzilla.redhat.com/attachment.cgi?id=888686
dma debug: account for cachelines and read-only mappings in overlap tracking
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/lib/dma-debug.c?id=3b7a6418c7494b8bf0bf0537ddee1dedbca10f51
Are these two in some relation?
poma
next prev parent reply other threads:[~2014-04-23 0:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 22:18 debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline poma
2014-04-17 7:40 ` Clemens Ladisch
2014-04-17 17:18 ` poma
2014-04-23 0:53 ` poma [this message]
2014-04-23 5:33 ` poma
2014-05-01 5:07 ` poma
2014-05-06 1:57 ` poma
2014-05-07 10:14 ` poma
2014-05-11 10:02 ` poma
2014-08-30 0:48 ` debug_dma_assert_idle - ahci " poma
2014-09-18 2:55 ` debug_dma_assert_idle - ohci " poma
2014-05-01 17:24 ` debug_dma_assert_idle - snd_hda_intel " Dan Williams
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=53570F1F.1000709@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=clemens@ladisch.de \
--cc=dan.j.williams@intel.com \
--cc=davej@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=kernel@lists.fedoraproject.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=romieu@fr.zoreil.com \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=wei.liu2@citrix.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).