linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: poma <pomidorabelisima@gmail.com>
To: Clemens Ladisch <clemens@ladisch.de>, Takashi Iwai <tiwai@suse.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Mailing-List fedora-kernel <kernel@lists.fedoraproject.org>
Subject: Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline
Date: Thu, 17 Apr 2014 19:18:19 +0200	[thread overview]
Message-ID: <53500CDB.8050802@gmail.com> (raw)
In-Reply-To: <534F858B.4060208@ladisch.de>

On 17.04.2014 09:40, Clemens Ladisch wrote:
> poma wrote:
>> Sound whispers,
> 
> ???
> 
>>  WARNING: CPU: 3 PID: 900 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=0x03014000]
>>  ...
>>  Mapped at:
>>   [<c074ec12>] debug_dma_alloc_coherent+0x22/0x70
> 
> "Coherent" means "touching DMA mappings is allowed".
> Why does dma-debug complain about that?
> 
> 
> Regards,
> Clemens
> 

Thanks for comment.
Waiting for rc2 to be sure!


poma



  reply	other threads:[~2014-04-17 17:18 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 [this message]
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
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=53500CDB.8050802@gmail.com \
    --to=pomidorabelisima@gmail.com \
    --cc=clemens@ladisch.de \
    --cc=kernel@lists.fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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).