From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200045] New: i2c-algo-bit: black screen on 'radeon' module probing
Date: Tue, 12 Jun 2018 21:00:45 +0000 [thread overview]
Message-ID: <bug-200045-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=200045
Bug ID: 200045
Summary: i2c-algo-bit: black screen on 'radeon' module probing
Product: Drivers
Version: 2.5
Kernel Version: 4.16
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: cerg2010cerg2010@mail.ru
Regression: No
Created attachment 276499
--> https://bugzilla.kernel.org/attachment.cgi?id=276499&action=edit
lspci -v
Hi,
After updating to the 4.16 kernel I started to get a black screen on boot,
without something useful in log. This bug also happens in latest version
(4.17.1). I'm using HP Pavilion dv6-3090er laptop with an exotic ATI/AMD
switchable graphics (radeon 4250 integrated/5650 discrete).
I bisected the issue down to commit 3e5f06bed72fe72166a6778f630241a893f67799
("i2c: algo-bit: init the bus to a known state") and reverting this fixes the
problem. Also loading radeon module with hw_i2c=1 gives me working display with
full brightness, and attempt to change it results in reboot.
Thanks.
--
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 reply other threads:[~2018-06-12 21:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 21:00 bugzilla-daemon [this message]
2018-06-13 8:09 ` [Bug 200045] black screen on 'radeon' module probing bugzilla-daemon
2018-06-13 8:13 ` bugzilla-daemon
2018-06-13 9:35 ` bugzilla-daemon
2018-06-13 10:47 ` bugzilla-daemon
2018-06-13 14:12 ` bugzilla-daemon
2018-06-14 1:30 ` bugzilla-daemon
2018-06-14 1:33 ` bugzilla-daemon
2018-06-14 13:09 ` bugzilla-daemon
2018-06-14 13:58 ` bugzilla-daemon
2018-06-14 15:27 ` bugzilla-daemon
2018-06-14 15:47 ` bugzilla-daemon
2018-06-15 5:19 ` bugzilla-daemon
2018-06-15 6:03 ` bugzilla-daemon
2018-06-15 13:28 ` bugzilla-daemon
2018-06-15 14:59 ` bugzilla-daemon
2018-06-16 12:25 ` bugzilla-daemon
2018-06-16 13:22 ` 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-200045-2300@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).