Bug 108542

Thanks for the bisection.

Would you mind posting a full dmesg log for your 4.18.8 kernel?

Created attachment 142207 [details]
dmesg

(In reply to Nicholas Kazlauskas from comment #1)
> Thanks for the bisection.
> 
> 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.
> > 
> > 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?

The log you posted should be sufficient. I'm not sure about a timeline for a fix, however.

> The log you posted should be sufficient. 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 <mikita.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.kernel.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
> 
> Does applying this patch help?
> 
> Try this on top of the tree without reverting the other patches.

Just tried, unfortunately it does not.

The patchset from:

https://patchwork.freedesktop.org/patch/260799/

...will likely resolve this issue.

It has been merged into amd-staging-drm-next branch at:

https://cgit.freedesktop.org/~agd5f/linux

(In reply to Nicholas Kazlauskas from comment #9)
> The patchset from:
> 
> https://patchwork.freedesktop.org/patch/260799/
> 
> ...will likely resolve this issue.
> 
> It has been merged into amd-staging-drm-next branch at:
> 
> https://cgit.freedesktop.org/~agd5f/linux

Tried amd-staging-drm-next, it works!

-- 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.