* [Bug 200667] [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg
2018-07-27 11:54 [Bug 200667] New: [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg bugzilla-daemon
@ 2018-07-27 11:55 ` bugzilla-daemon
2018-07-27 11:56 ` bugzilla-daemon
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2018-07-27 11:55 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #1 from Christian Widmer (CWidmer@umbrox.de) ---
Created attachment 277571
--> https://bugzilla.kernel.org/attachment.cgi?id=277571&action=edit
Kernel configuration
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug 200667] [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg
2018-07-27 11:54 [Bug 200667] New: [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg bugzilla-daemon
2018-07-27 11:55 ` [Bug 200667] " bugzilla-daemon
@ 2018-07-27 11:56 ` bugzilla-daemon
2018-07-27 12:03 ` bugzilla-daemon
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2018-07-27 11:56 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #2 from Christian Widmer (CWidmer@umbrox.de) ---
Created attachment 277573
--> https://bugzilla.kernel.org/attachment.cgi?id=277573&action=edit
lspci
I am using an RX 580.
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug 200667] [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg
2018-07-27 11:54 [Bug 200667] New: [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg bugzilla-daemon
2018-07-27 11:55 ` [Bug 200667] " bugzilla-daemon
2018-07-27 11:56 ` bugzilla-daemon
@ 2018-07-27 12:03 ` bugzilla-daemon
2018-07-27 14:41 ` bugzilla-daemon
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2018-07-27 12:03 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #3 from Christian Widmer (CWidmer@umbrox.de) ---
I might add simply booting the kernel is all that is needed to trigger the
issue. The stacktraces automatically appear during the boot process.
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug 200667] [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg
2018-07-27 11:54 [Bug 200667] New: [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg bugzilla-daemon
` (2 preceding siblings ...)
2018-07-27 12:03 ` bugzilla-daemon
@ 2018-07-27 14:41 ` bugzilla-daemon
2018-07-27 17:47 ` bugzilla-daemon
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2018-07-27 14:41 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=200667
Alex Deucher (alexdeucher@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #4 from Alex Deucher (alexdeucher@gmail.com) ---
Can you bisect?
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug 200667] [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg
2018-07-27 11:54 [Bug 200667] New: [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg bugzilla-daemon
` (3 preceding siblings ...)
2018-07-27 14:41 ` bugzilla-daemon
@ 2018-07-27 17:47 ` bugzilla-daemon
2018-07-27 17:55 ` bugzilla-daemon
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2018-07-27 17:47 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #5 from Christian Widmer (CWidmer@umbrox.de) ---
The bisect identified commit 9168c089a2122606e2c01f6fbeda85ff950ac189 (Revert
"drm/amd/display: Don't return ddc result and read_bytes in same return value",
upstream commit 5292221d6ddfed75e5b46cd42237a677094b99f3). And a quick test
with reverting this change in my distribution's 4.17.10 kernel and in the
mainline 4.18-rc6 kernel indeed made the stacktrace disappear.
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug 200667] [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg
2018-07-27 11:54 [Bug 200667] New: [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg bugzilla-daemon
` (4 preceding siblings ...)
2018-07-27 17:47 ` bugzilla-daemon
@ 2018-07-27 17:55 ` bugzilla-daemon
2018-07-27 18:39 ` bugzilla-daemon
2018-10-22 21:14 ` bugzilla-daemon
7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2018-07-27 17:55 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #6 from Alex Deucher (alexdeucher@gmail.com) ---
The warning is harmless. As per the commit message, this is fixed properly for
4.19 with the following patches:
This breaks DDC in certain cases. Revert for 4.18 and previous kernels.
For 4.19, this is fixed with the following more extensive patches:
drm/amd/display: Serialize is_dp_sink_present
drm/amd/display: Break out function to simply read aux reply
drm/amd/display: Return aux replies directly to DRM
drm/amd/display: Right shift AUX reply value sooner than later
drm/amd/display: Read AUX channel even if only status byte is returned
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug 200667] [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg
2018-07-27 11:54 [Bug 200667] New: [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg bugzilla-daemon
` (5 preceding siblings ...)
2018-07-27 17:55 ` bugzilla-daemon
@ 2018-07-27 18:39 ` bugzilla-daemon
2018-10-22 21:14 ` bugzilla-daemon
7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2018-07-27 18:39 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #7 from Christian Widmer (CWidmer@umbrox.de) ---
For the sake of completeness I have just tested linux-next which contains all
those patches and the warning is indeed gone. Thank you for your responses!
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug 200667] [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg
2018-07-27 11:54 [Bug 200667] New: [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg bugzilla-daemon
` (6 preceding siblings ...)
2018-07-27 18:39 ` bugzilla-daemon
@ 2018-10-22 21:14 ` bugzilla-daemon
7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2018-10-22 21:14 UTC (permalink / raw)
To: dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #8 from Christian Widmer (CWidmer@umbrox.de) ---
As expected, the warning is indeed gone with the recently released stable
kernel 4.19.
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread