From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107947] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif line:563 during boot
Date: Tue, 30 Oct 2018 01:24:06 +0000 [thread overview]
Message-ID: <bug-107947-502-TKceNIVgnA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107947-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1752 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107947
Kent Ross <root.main@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |root.main@gmail.com
--- Comment #3 from Kent Ross <root.main@gmail.com> ---
I have this issue, or one very like it. I have a system with both a Vega64 and
a GTX 980ti. The 980ti is controlled by the vfio-pci driver (preempting
nouveau, nvidiafb, etc. on boot) and is therefore not in use by this host
system.
If a display is plugged into the 980ti at boot time, booting will always fail
with a black screen and more failures from drm. If a display is not plugged in,
booting will almost always work without a problem, with fewer errors from drm.
Even with no display plugged into the 980ti, when the system's displays
(plugged into the vega64) resume when they have been sleeping (such as on the
lock screen) there is a substantial chance all displays will be completely
black and drm failures can be seen in dmesg. If a display is plugged into the
980ti when the main displays wake, the outcome is much less likely to be good.
In the case where the system is returning from sleeping screens it fortunately
does not fully necessitate a complete reboot, as the displays will sleep again
in a few seconds and it can be tried again until success. Nonetheless, as this
system is intended to be used as a VM host with a passed-through monitor, this
bug is a showstopper.
I have full dmesg logs from boot to an unusable black screen, and from boot to
a login screen.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3150 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
next prev parent reply other threads:[~2018-10-30 1:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 6:34 [Bug 107947] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif line:563 during boot bugzilla-daemon
2018-09-24 19:52 ` bugzilla-daemon
2018-09-24 19:53 ` bugzilla-daemon
2018-10-30 1:24 ` bugzilla-daemon [this message]
2018-10-30 1:26 ` bugzilla-daemon
2018-10-30 1:26 ` bugzilla-daemon
2018-10-31 7:53 ` bugzilla-daemon
2018-10-31 15:04 ` bugzilla-daemon
2018-11-06 9:20 ` bugzilla-daemon
2019-11-19 8:56 ` 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-107947-502-TKceNIVgnA@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;
as well as URLs for NNTP newsgroup(s).