From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199619] screen stays dark for long on bootup since kernel 4.17.0-rc2+
Date: Tue, 11 Sep 2018 11:00:06 +0000 [thread overview]
Message-ID: <bug-199619-2300-GK2Rb7EIk7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199619-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199619
--- Comment #12 from Ant (untaintableangel@hotmail.co.uk) ---
Elmar, did you have a look at my bug report from comment 4?
Does installing something like rng-tools fix the problem?
If it does, then you are suffering from the same, widespread, well-documented
issue that began with 4.17-rc2 with
commit43838a23a05fbd13e47d750d3dfd77001536dd33 (random: fix crng_ready() test).
The kernel is waiting for enough entropy to have been generated and it causes a
long hang until you mash on random keys or something else helps generate it.
Until then, you get a nice black screen.
Unfortunately, this has the side effect of slightly lengthening the shutdown
and restart time by a few seconds, but the boot/login time is returned to
normal.
I used to have an ath9k based wireless card and there is an option in the
kernel to use it to help add to the entropy pool. This solved the problem
completely for me on my custom kernels, but then I went and got a new wireless
card that isn't so fortunate as to have this option in the kernel config and
I'm back to waiting for a more permanent fix too.
At least give it a try, it sounds like the same problem.
--
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-09-11 11:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 7:34 [Bug 199619] New: screen stays dark for long on bootup since kernel 4.17.0-rc2+ bugzilla-daemon
2018-05-07 10:23 ` [Bug 199619] " bugzilla-daemon
2018-05-07 11:03 ` bugzilla-daemon
2018-05-12 8:00 ` bugzilla-daemon
2018-05-20 23:43 ` bugzilla-daemon
2018-06-08 17:01 ` bugzilla-daemon
2018-06-08 17:32 ` bugzilla-daemon
2018-06-11 16:34 ` bugzilla-daemon
2018-06-11 16:35 ` bugzilla-daemon
2018-06-19 19:51 ` bugzilla-daemon
2018-06-20 8:44 ` bugzilla-daemon
2018-09-11 6:52 ` bugzilla-daemon
2018-09-11 11:00 ` bugzilla-daemon [this message]
2018-09-12 8:00 ` bugzilla-daemon
2018-11-28 13: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-199619-2300-GK2Rb7EIk7@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).