From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@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
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1672955715=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id 34E626E150
for ; Tue, 30 Oct 2018 01:24:06 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1672955715==
Content-Type: multipart/alternative; boundary="15408626461.9f1301D59.23809"
Content-Transfer-Encoding: 7bit
--15408626461.9f1301D59.23809
Date: Tue, 30 Oct 2018 01:24:06 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D107947
Kent Ross changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |root.main@gmail.com
--- Comment #3 from Kent Ross ---
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 fa=
il
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 d=
rm.
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 t=
he
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 t=
he
980ti when the main displays wake, the outcome is much less likely to be go=
od.
In the case where the system is returning from sleeping screens it fortunat=
ely
does not fully necessitate a complete reboot, as the displays will sleep ag=
ain
in a few seconds and it can be tried again until success. Nonetheless, as t=
his
system is intended to be used as a VM host with a passed-through monitor, t=
his
bug is a showstopper.
I have full dmesg logs from boot to an unusable black screen, and from boot=
to
a login screen.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15408626461.9f1301D59.23809
Date: Tue, 30 Oct 2018 01:24:06 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Kent Ross
changed
bug 10794=
7
| What |
Removed |
Added |
| CC |
|
root.main@gmail.com
|
Commen=
t # 3
on bug 10794=
7
from Kent Ross
I have this issue, or one very like it. I have a system with b=
oth 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 fa=
il
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 d=
rm.
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 t=
he
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 t=
he
980ti when the main displays wake, the outcome is much less likely to be go=
od.
In the case where the system is returning from sleeping screens it fortunat=
ely
does not fully necessitate a complete reboot, as the displays will sleep ag=
ain
in a few seconds and it can be tried again until success. Nonetheless, as t=
his
system is intended to be used as a VM host with a passed-through monitor, t=
his
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.
=
--15408626461.9f1301D59.23809--
--===============1672955715==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1672955715==--