| Bug ID | 108542 |
|---|---|
| Summary | hdmi issues with kernel 4.18 |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | davide26079@gmail.com |
- since 4.18, the hdmi output says "12 bit" - since 4.18.8 there's no video output !! You can find more details in this thread https://bbs= .archlinux.org/viewtopic.php?id=3D241212 I did a bisection to find the bad commit for the first regression already, = and that's the result: e03fd3f300f6184c1264186a4c815e93bf658abb is the first bad commit commit e03fd3f300f6184c1264186a4c815e93bf658abb Author: Mikita Lipski <miki= ta.lipski@amd.com> Date: Wed May 16 16:46:18 2018 -0400 drm/amd/display: Do not limit color depth to 8bpc Delete if statement that would force any display's color depth higher than 8 bpc to 8 Signed-off-by: Mikita Lipski <mikita.lipski@amd.com> Reviewed-by: Harry Wentland <Harry.Wentland@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> :040000 040000 57c7a743a10059addbfdd1a122f90c4053d377fa 13139317e62ef56db1748bf48f31f81eb986c7f8 M drivers
Thanks for the bisection. Would you mind posting a full dmesg log for your 4.18.8 kernel?
Created attachment 142207 [details]<=
/span>
dmesg
(In reply to Nicholas Kazlauskas from comment #1) > Thanks for the bisection. >=20 > Would you mind posting a full dmesg log for your 4.18.8 kernel? done. Dunno if that's what you asked for, I am just a newbie... I did start bisecting the second issue as well, but my free time is limited= . I think I'll finish this weekend though. May I hope to get things fixed in a few weeks?
(In reply to davide26079 from comment #3) > (In reply to Nicholas Kazlauskas from comment #1) > > Thanks for the bisection. > >=20 > > Would you mind posting a full dmesg log for your 4.18.8 kernel? >=20 > done. Dunno if that's what you asked for, I am just a newbie... >=20 > I did start bisecting the second issue as well, but my free time is li= mited. > I think I'll finish this weekend though. >=20 > May I hope to get things fixed in a few weeks? The log you posted should be sufficient. I'm not sure about a timeline for a fix, however.
> The log you posted should be suffic= ient. I'm not sure about a timeline for a > fix, however. Couldn't you just reverse the commits ? I did complete the bisection btw: 691f2d763d0731224439686ecf2d440df8fe910e is the first bad commit commit 691f2d763d0731224439686ecf2d440df8fe910e Author: Mikita Lipski <miki= ta.lipski@amd.com> Date: Fri Jul 13 09:07:35 2018 -0400 drm/amd/display: update clk for various HDMI color depths commit 81aca8e75c1b046865fb2badef95a0dcff6f73de upstream. [why] When programming tonga's connector's backend we didn't take in account that HDMI's colour depth might be more than 8bpc therefore we need to add a switch statement that would adjust the pixel clock accordingly. [how] Add a switch statement updating clock by its appropriate coefficient. Signed-off-by: Mikita Lipski <mikita.lipski@amd.com> Reviewed-by: Charlene Liu <Charlene.Liu@amd.com> Acked-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Cc: stable@vger.kerne= l.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> :040000 040000 ef9f989910439dc8749f1440863e3e26646d5fa1 c9ae9b8a137f9ef9d62147fcc28ea25fc4ffbc1e M drivers
Built 4.19 reverting both commits, everything works fine.
Created attachment 142278 [details] [review] 0001-Fix-unsigned-short-unsigned-long-mixup-for-usSymCloc.patch Does applying this patch help? Try this on top of the tree without reverting the other patches.
(In reply to Nicholas Kazlauskas from comment #7) > Created attachment 142278 [details] [review= ] [review] > 0001-Fix-unsigned-short-unsigned-long-mixup-for-usSymCloc.patch >=20 > Does applying this patch help? >=20 > Try this on top of the tree without reverting the other patches. Just tried, unfortunately it does not.
The patchset from: https://patchwo= rk.freedesktop.org/patch/260799/ ...will likely resolve this issue. It has been merged into amd-staging-drm-next branch at: https://cgit.freedesk= top.org/~agd5f/linux
(In reply to Nicholas Kazlauskas from comment #9) > The patchset from: >=20 > https://pa= tchwork.freedesktop.org/patch/260799/ >=20 > ...will likely resolve this issue. >=20 > It has been merged into amd-staging-drm-next branch at: >=20 > https://cgit.fre= edesktop.org/~agd5f/linux Tried amd-staging-drm-next, it works!
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/568.