mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: poma <pomidorabelisima@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Clemens Ladisch <clemens@ladisch.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>,
	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: Sun, 11 May 2014 12:02:50 +0200	[thread overview]
Message-ID: <536F4ACA.3040300@gmail.com> (raw)
In-Reply-To: <536A0777.1050407@gmail.com>


------------[ cut here ]------------
WARNING: CPU: 2 PID: 628 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=0x03074000]
CPU: 2 PID: 628 Comm: lightdm Not tainted 3.15.0-0.rc5.git0.1.fc21.i686+debug #1
Call Trace:
 [<c0ae737d>] dump_stack+0x48/0x60
 [<c04547b2>] warn_slowpath_common+0x82/0xa0
 [<c0754d99>] ? debug_dma_assert_idle+0x159/0x1d0
 [<c0754d99>] ? debug_dma_assert_idle+0x159/0x1d0
 [<c045480e>] warn_slowpath_fmt+0x3e/0x60
 [<c0754d99>] debug_dma_assert_idle+0x159/0x1d0
 [<c058a149>] ? anon_vma_prepare+0x29/0x140
 [<c057e56e>] do_wp_page+0xce/0x890
 [<c0580b72>] handle_mm_fault+0x662/0xb70
 [<c0af3667>] __do_page_fault+0x1a7/0x5d0
 [<c04e1057>] ? SyS_futex+0x97/0x180
 [<c04b1b00>] ? trace_hardirqs_on_caller+0x1c0/0x1e0
 [<c04b1a7c>] ? trace_hardirqs_on_caller+0x13c/0x1e0
 [<c0af3a90>] ? __do_page_fault+0x5d0/0x5d0
 [<c0af3aaa>] do_page_fault+0x1a/0x20
 [<c0af0484>] error_code+0x6c/0x74
---[ end trace b400a64c04aed387 ]---
Mapped at:
 [<c0752e42>] debug_dma_alloc_coherent+0x22/0x70
 [<f80c3e90>] snd_dma_alloc_pages+0x170/0x260 [snd_pcm]
 [<f80c3fe2>] snd_dma_alloc_pages_fallback+0x62/0x90 [snd_pcm]
 [<f80c43b0>] snd_malloc_sgbuf_pages+0xf0/0x211 [snd_pcm]
 [<f80c3f23>] snd_dma_alloc_pages+0x203/0x260 [snd_pcm]


poma



  reply	other threads:[~2014-05-11 10:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 22:18 poma
2014-04-17  7:40 ` Clemens Ladisch
2014-04-17 17:18   ` poma
2014-04-23  0:53     ` poma
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 [this message]
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=536F4ACA.3040300@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

Powered by JetHome