From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196777] Virtual guest using video device QXL does not reach GDM
Date: Thu, 14 Sep 2017 17:23:13 +0000 [thread overview]
Message-ID: <bug-196777-2300-e2cJ6oCtmV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196777-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196777
Justin M. Forbes (jmforbes@linuxtx.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jmforbes@linuxtx.org
--- Comment #7 from Justin M. Forbes (jmforbes@linuxtx.org) ---
(In reply to Gerd Hoffmann from comment #4)
> Retested 4.13 + comment #2 patch.
>
> plymouth (aka graphical boot) hangs the machine indeed.
>
> when disabling rhgb gdm comes up just fine though, in both wayland and xorg
> mode.
> so apparently we have two issues here, and the patch fixes only one of them.
>
> The plymouth hang appears to be pretty serious, the whole machine appears to
> be toast. I can't login over network to see what is going on, so it's not
> only the display which is f*cked up. Nothing written to the logs either.
> When enabling the serial console to see the logs plymouth skips the splash
> screen though, so the issue doesn't trigger any more. Hmm, I'm running out
> of ideas ...
I dropped the patch into the 4.12.12 update for Fedora kernels. The complaints
I am seeing are screen strobing with this patch, it has been backed out for
now. The plymouth issue is also a big one.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-14 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 8:28 [Bug 196777] New: Virtual guest using video device QXL does not reach GDM bugzilla-daemon
2017-08-26 13:04 ` [Bug 196777] " bugzilla-daemon
2017-09-10 14:41 ` bugzilla-daemon
2017-09-11 8:43 ` bugzilla-daemon
2017-09-12 18:44 ` bugzilla-daemon
2017-09-13 10:31 ` bugzilla-daemon
2017-09-13 12:51 ` bugzilla-daemon
2017-09-13 13:23 ` bugzilla-daemon
2017-09-14 17:23 ` bugzilla-daemon [this message]
2017-09-15 10:50 ` bugzilla-daemon
2017-09-17 8:50 ` bugzilla-daemon
2017-09-19 14:37 ` bugzilla-daemon
2017-09-19 15:23 ` bugzilla-daemon
2017-10-02 16:24 ` bugzilla-daemon
2017-10-04 10:37 ` bugzilla-daemon
2017-10-19 7:07 ` 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-196777-2300-e2cJ6oCtmV@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.