dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102301] 4.12, AMD A10-9600P, AMD-Vi: Completion-Wait loop timed out.
Date: Fri, 18 Aug 2017 18:44:26 +0000	[thread overview]
Message-ID: <bug-102301-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 102301
           Summary: 4.12, AMD A10-9600P, AMD-Vi: Completion-Wait loop
                    timed out.
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: ahammington@mail.ru

Created attachment 133615
  --> https://bugs.freedesktop.org/attachment.cgi?id=133615&action=edit
dmesg, showing a boot without iommu=soft

Hello amd devs,
and whomever it might affect or who is interested.


Kernel: 4.12.8
linux-firmware-amd-20170622
xf86-video-amdgpu-1.3.0
CPU: AMD A10-9600P
GPU: Radeon R7 (M440 or sth.)

After boot when presented with the login screen, the system repeatedly outputs
"AMD-Vi: Completion-Wait loop timed out." and most of the time this corrupts
the file system while doing this.
Booting the kernel with iommu=soft circumvents the problem, but introduces
other issues on this machine.

I am following this issue for some time now.
A have a fairly recent notebook (yes, I know. it's a lot to ask for support on
too recent hardware).
But i see hope, as there already has been succesfull patching by the amd crew!


I found a bugreport on launchpad [1] (strange enough they posted it there),
which led to a patch on freedesktop [2], and i happily got it to work with
4.11. System was bootable without the iommu=soft command.

With linux now advancing to 4.12, the patch is not applyable anymore, so here i
am now, reporting the issue again, in the hope to get new info and a tiny bit
of help/advice.


Thanks in advance.


[1]: https://bugs.freedesktop.org/show_bug.cgi?id=101029
[2]: https://patchwork.freedesktop.org/series/21684/



_________________


# lspci -vv | grep -A 3 -i "display"
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT
[Radeon R7 M260/M265 / M340/M360 / M440/M445] (rev ff) (prog-if ff)
        !!! Unknown header type 7f
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

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

[-- Attachment #1.2: Type: text/html, Size: 4035 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

             reply	other threads:[~2017-08-18 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 18:44 bugzilla-daemon [this message]
2017-08-31  6:26 ` [Bug 102301] AMD A10-9600P, AMD-Vi: Completion-Wait loop timed out bugzilla-daemon
2019-11-19  8:21 ` 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-102301-502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox