From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199633] Stable kernel regression after 4.16.3: startxfce4 no longer works: X startup seems to hang
Date: Sun, 20 May 2018 23:52:15 +0000 [thread overview]
Message-ID: <bug-199633-2300-Lo95lUCJUS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199633-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199633
Ant (untaintableangel@hotmail.co.uk) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |untaintableangel@hotmail.co
| |.uk
--- Comment #5 from Ant (untaintableangel@hotmail.co.uk) ---
I've recently had the same issue caused by that very patch you mentioned
(random: fix crng_ready() test) and had exactly the same problem.
https://bugzilla.kernel.org/show_bug.cgi?id=199567
I installed rng-tools and turned back on options in my custom kernel that lead
to more entropy generation (for example CONFIG_ATH9K_HWRNG) and can
successfully use kernels past 4.17-rc1 (just before the patch was applied)
again without any hang or lasting black screen.
--
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:[~2018-05-20 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 10:37 [Bug 199633] New: Stable kernel regression after 4.16.3: startxfce4 no longer works: X startup seems to hang bugzilla-daemon
2018-05-07 10:12 ` [Bug 199633] " bugzilla-daemon
2018-05-07 10:28 ` bugzilla-daemon
2018-05-09 5:01 ` bugzilla-daemon
2018-05-20 10:52 ` bugzilla-daemon
2018-05-20 23:52 ` bugzilla-daemon [this message]
2018-05-20 23:55 ` bugzilla-daemon
2018-05-21 8:44 ` bugzilla-daemon
2018-05-22 8:26 ` bugzilla-daemon
2018-05-22 11:09 ` 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-199633-2300-Lo95lUCJUS@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 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).