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, 16 Apr 2019 02:29:19 +0000 [thread overview]
Message-ID: <bug-110360-502-Hxx3MH8rKw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110360-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 478 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110360
--- Comment #10 from Daniel Drake <dan@reactivated.net> ---
Thanks Alex. We will have to return this unit to the vendor at some point, but
we will try to hold onto it for another month so that we can run any tests you
request.
Alternatively, we may be able to get an affected unit shipped to you on a
1-month loan. Would that be useful?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1326 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 prev parent reply other threads:[~2019-04-16 2:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 5:37 [Bug 110360] AMD system hits AMD-Vi: Completion-Wait loop timed out on Acer Squirtle_SR laptop bugzilla-daemon
2019-04-09 5:38 ` 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 [this message]
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-Hxx3MH8rKw@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