From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110360] AMD system hits AMD-Vi: Completion-Wait loop timed out on Acer Squirtle_SR laptop
Date: Tue, 09 Apr 2019 05:37:41 +0000 [thread overview]
Message-ID: <bug-110360-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1541 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110360
Bug ID: 110360
Summary: AMD system hits AMD-Vi: Completion-Wait loop timed out
on Acer Squirtle_SR laptop
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: jian-hong@endlessm.com
Created attachment 143905
--> https://bugs.freedesktop.org/attachment.cgi?id=143905&action=edit
The error log
We have an Acer Squirtle_SR laptop equipped with AMD A9-9420e RADEON R5, 5
COMPUTE CORES 2C+3G and [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 /
M440/M445] [1002:6900]. We test it with Linux kernel 5.1.0-rc4. The system
hits the following error and makes system hang up:
Apr 09 11:28:57 endless kernel: AMD-Vi: Completion-Wait loop timed out
Apr 09 11:28:57 endless kernel: iwlwifi 0000:03:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0xff814000 flags=0x0050]
The worst case is the disk's block may be disrupted, then we have to re-install
the system if it cannot be recovered by fsck.
If we blacklist the amdgpu module, then system will not hit the error. But
system has no GUI, and only shows console.
If iommu=soft is appended to the boot command, system works fine.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2967 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-04-09 5:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 5:37 bugzilla-daemon [this message]
2019-04-09 5:38 ` [Bug 110360] AMD system hits AMD-Vi: Completion-Wait loop timed out on Acer Squirtle_SR laptop bugzilla-daemon
2019-04-09 6:00 ` bugzilla-daemon
2019-04-09 14:14 ` bugzilla-daemon
2019-04-09 14:22 ` bugzilla-daemon
2019-04-10 9:19 ` bugzilla-daemon
2019-04-10 15:48 ` bugzilla-daemon
2019-04-10 15:51 ` bugzilla-daemon
2019-04-11 5:04 ` bugzilla-daemon
2019-04-11 15:21 ` bugzilla-daemon
2019-04-12 2:36 ` bugzilla-daemon
2019-04-15 2:37 ` bugzilla-daemon
2019-04-15 4:31 ` bugzilla-daemon
2019-04-15 4:32 ` bugzilla-daemon
2019-04-16 2:29 ` bugzilla-daemon
2019-11-19 9:18 ` 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-110360-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