All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204145] amdgpu video playback causes host to hard reset (checkstop) on POWER9 with RX 580
Date: Wed, 17 Jul 2019 19:12:39 +0000	[thread overview]
Message-ID: <bug-204145-2300-3w6JF7Sql0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204145-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=204145

--- Comment #16 from Shawn Anastasio (shawn@anastas.io) ---
Created attachment 283799
  --> https://bugzilla.kernel.org/attachment.cgi?id=283799&action=edit
test patch #1

Though I'm not familiar with this code, a quick spot check shows what I believe 
to be an inconsistency with the commit's claim of functional identicality. 
Namely, the previous caller of __dma_get_coherent_pfn (now 
arch_dma_coherent_to_pfn) would explicitly modify the vm_area to mark it as 
uncacheable in the !coherent case. It seems the new caller (dma_common_mmap)
does not do this. I have written a small patch to restore the previous 
behavior (I think). Note that this probably isn't upstreamable since this fix 
should probably go somewhere in the powerpc arch code rather than the dma core.

Tim, since you're the only one who can easily reproduce this,
would you mind giving this patch a shot?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-07-17 19:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  2:43 [Bug 204145] New: amdgpu video playback causes host to hard reset (checkstop) on POWER9 with RX 580 bugzilla-daemon
2019-07-12  2:44 ` [Bug 204145] " bugzilla-daemon
2019-07-12  2:44 ` bugzilla-daemon
2019-07-12  2:59 ` bugzilla-daemon
2019-07-13 13:40 ` bugzilla-daemon
2019-07-14 15:35 ` bugzilla-daemon
2019-07-16  0:13 ` bugzilla-daemon
2019-07-16  0:16 ` bugzilla-daemon
2019-07-16  9:49 ` bugzilla-daemon
2019-07-16 13:01 ` bugzilla-daemon
2019-07-16 18:54 ` bugzilla-daemon
2019-07-16 18:55 ` bugzilla-daemon
2019-07-16 20:18 ` bugzilla-daemon
2019-07-16 20:20 ` bugzilla-daemon
2019-07-16 20:26 ` bugzilla-daemon
2019-07-17  9:36 ` bugzilla-daemon
2019-07-17 19:12 ` bugzilla-daemon [this message]
2019-07-17 19:42 ` bugzilla-daemon
2019-07-17 20:02 ` bugzilla-daemon
2019-07-17 20:30 ` bugzilla-daemon
2019-07-17 22:09 ` bugzilla-daemon
2019-07-17 23:20 ` bugzilla-daemon
2019-07-17 23:58 ` bugzilla-daemon
2019-07-18  0:39 ` bugzilla-daemon
2019-07-18  0:49 ` bugzilla-daemon
2019-07-18  0:50 ` bugzilla-daemon
2019-07-22 23:11 ` bugzilla-daemon
2019-07-30  5:28 ` bugzilla-daemon

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=bug-204145-2300-3w6JF7Sql0@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.