From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199567] [amdgpu] just a black screen irrespective of amdgpu.dc=1 or 0 at boot on kernels 4.17-rc2 and onwards
Date: Thu, 17 May 2018 01:26:51 +0000 [thread overview]
Message-ID: <bug-199567-2300-7DfSSS14xX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199567-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199567
--- Comment #3 from Ant (untaintableangel@hotmail.co.uk) ---
Sorry for the delay. OK, so lots of news:
I did see a patch in amd-staging-drm-next
354ee4815f52219fcd97d91269917261aac0518a ("drm/amd/display: Fix bug that causes
black screen") that sounded ideal but I couldn't apply it cleanly since it's
too out of sync.
After a git bisect, I was pleasantly surprised that the 3 main patches between
rc-1-rc2 for amd/display stuff were all fine. Looks like it's something else
entirely.
I tested out an ubuntu mainline kernel and it worked fine, so the problem is
something different in my custom .config, I guess. Something that has been fine
for 4.17-rc1 and kernels before that but suddenly needs to change for rc2
onwards.
(Bug still present on 4.17-rc5 btw)
last good: 5e747dd9be54be190dd6ebeebf4a4a01ba765625
first bad: 43838a23a05fbd13e47d750d3dfd77001536dd33
commit 43838a23a05fbd13e47d750d3dfd77001536dd33
Author: Theodore Ts'o <tytso@mit.edu>
Date: Wed Apr 11 13:27:52 2018 -0400
random: fix crng_ready() test
The crng_init variable has three states:
0: The CRNG is not initialized at all
1: The CRNG has a small amount of entropy, hopefully good enough for
early-boot, non-cryptographical use cases
2: The CRNG is fully initialized and we are sure it is safe for
cryptographic use cases.
The crng_ready() function should only return true once we are in the
last state. This addresses CVE-2018-1108.
Reported-by: Jann Horn <jannh@google.com>
Fixes: e192be9d9a30 ("random: replace non-blocking pool...")
Cc: stable@kernel.org # 4.8+
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reviewed-by: Jann Horn <jannh@google.com>
I'm looking into my config options for RNG/random stuff, but this bug can
probably be bounced somewhere more appropriate now :)
--
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-17 1:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 18:56 [Bug 199567] New: [amdgpu] just a black screen irrespective of amdgpu.dc=1 or 0 at boot on kernels 4.17-rc2 and onwards bugzilla-daemon
2018-04-29 20:06 ` [Bug 199567] " bugzilla-daemon
2018-04-30 9:03 ` bugzilla-daemon
2018-05-17 1:26 ` bugzilla-daemon [this message]
2018-05-20 23:36 ` bugzilla-daemon
2018-05-20 23:37 ` [Bug 199567] black screen irrespective of amdgpu.dc=1 or 0 at boot on kernels 4.17-rc2 and onwards caused by low entropy 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-199567-2300-7DfSSS14xX@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