All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107898] "kfd: Failed to resume IOMMU for device 1002:15dd" on Raven Ridge
Date: Wed, 14 Nov 2018 10:44:37 +0000	[thread overview]
Message-ID: <bug-107898-502-2wXA7T6lHH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107898-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107898

Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTOURBUG                   |---

--- Comment #13 from Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> ---
I have the same issue on Dell Latitude 5495 with Linux kernel 4.19.1 and
iommu=pt is a workaround here too.

But as AMD is working around other BIOS bugs[1] (rather than getting them fixed
quickly with their business partners), I think this bug report should be left
open for now.

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=44d8cc6f1a905e4bb1d4221a898abb0d7e9d100a

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2655 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-11-14 10:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  7:33 [Bug 107898] "kfd: Failed to resume IOMMU for device 1002:15dd" on Raven Ridge bugzilla-daemon
2018-09-11  8:49 ` bugzilla-daemon
2018-09-11  8:53 ` bugzilla-daemon
2018-09-11 20:48 ` bugzilla-daemon
2018-09-12  5:19 ` bugzilla-daemon
2018-09-12  5:21 ` bugzilla-daemon
2018-09-12 10:16 ` bugzilla-daemon
2018-09-12 10:17 ` bugzilla-daemon
2018-09-13 20:05 ` bugzilla-daemon
2018-09-14  7:40 ` bugzilla-daemon
2018-09-20  9:00 ` bugzilla-daemon
2018-09-20  9:01 ` bugzilla-daemon
2018-10-01 18:40 ` bugzilla-daemon
2018-10-10 12:07 ` bugzilla-daemon
2018-11-14 10:44 ` bugzilla-daemon [this message]
2019-11-19  7:53 ` 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-107898-502-2wXA7T6lHH@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.