Bug 201585 - 144Hz 2560x1440 no longer works (caps at 120Hz)
Summary: 144Hz 2560x1440 no longer works (caps at 120Hz)
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-01 12:13 UTC by Dan Acristinii
Modified: 2018-12-21 10:31 UTC (History)
4 users (show)

See Also:
Kernel Version: 4.18
Tree: Mainline
Regression: No


Attachments
dmesg.log on 4.18 (91.70 KB, text/plain)
2018-11-01 13:51 UTC, Dan Acristinii
Details
144Hz working dmesg on 4.17.19 (88.59 KB, text/plain)
2018-11-01 14:09 UTC, Dan Acristinii
Details
4.18 with drm.debug=4 (76.49 KB, text/plain)
2018-11-01 17:21 UTC, Dan Acristinii
Details
applied patch to amd-staging-drm-next (1.30 MB, image/jpeg)
2018-11-08 10:04 UTC, Dan Acristinii
Details

Description Dan Acristinii 2018-11-01 12:13:35 UTC
> Using the default driver on Ubuntu 18.10 starting from the 4.18 kernel and
> up, results in the maximum frame rate being limited to 120Hz at 2560x1440.
> Downgrading to 4.17.19 increases it back to 144Hz.


sudo lshw -c video,
  *-display                 
       description: VGA compatible controller
       product: Vega 10 XT [Radeon RX Vega 64]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:28:00.0
       version: c1
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:70 memory:e0000000-efffffff memory:f0000000-f01fffff ioport:e000(size=256) memory:fe600000-fe67ffff memory:fe680000-fe69ffff
Comment 1 Nicholas Kazlauskas 2018-11-01 13:26:06 UTC
Please attach a full dmesg log as well as an xorg log if applicable.
Comment 2 Dan Acristinii 2018-11-01 13:27:21 UTC
for which kernel version, 4.18 or 4.19?
Comment 3 Nicholas Kazlauskas 2018-11-01 13:31:16 UTC
The kernel you're experiencing the issue on, 4.18.

It might be worth trying 4.19 to see if you can still reproduce the issue there, however.
Comment 4 Dan Acristinii 2018-11-01 13:51:54 UTC
Created attachment 279285 [details]
dmesg.log on 4.18
Comment 5 Dan Acristinii 2018-11-01 13:53:19 UTC
The issue persists on 4.19
Comment 6 Dan Acristinii 2018-11-01 14:09:49 UTC
Created attachment 279287 [details]
144Hz working dmesg on 4.17.19
Comment 7 Nicholas Kazlauskas 2018-11-01 14:11:19 UTC
It may also help to have a dmesg log for 4.18 with drm.debug=4 as part of your bootline.

Thanks for all the logs.
Comment 8 Dan Acristinii 2018-11-01 17:21:47 UTC
Created attachment 279289 [details]
4.18 with drm.debug=4

I think I added it in the right way
Comment 9 Nicholas Kazlauskas 2018-11-07 15:23:23 UTC
These patches should fix your issue:

https://patchwork.freedesktop.org/series/52164/
Comment 10 Nicholas Kazlauskas 2018-11-07 15:27:26 UTC
(In reply to Nicholas Kazlauskas from comment #9)
> These patches should fix your issue:
> 
> https://patchwork.freedesktop.org/series/52164/

I suppose I should mention that these are for amd-staging-drm-next, they probably won't cleanly apply on Linus' tree.
Comment 11 Dan Acristinii 2018-11-08 10:04:13 UTC
Created attachment 279377 [details]
applied patch to amd-staging-drm-next
Comment 12 Dan Acristinii 2018-11-08 10:05:00 UTC
(In reply to Nicholas Kazlauskas from comment #10)
> (In reply to Nicholas Kazlauskas from comment #9)
> > These patches should fix your issue:
> > 
> > https://patchwork.freedesktop.org/series/52164/
> 
> I suppose I should mention that these are for amd-staging-drm-next, they
> probably won't cleanly apply on Linus' tree.

I would like to mention that revision 2 of the patch is incompatible with amd-staging-drm-next
Comment 13 Nicholas Kazlauskas 2018-11-08 15:47:11 UTC
(In reply to Dan Acristinii from comment #12)
> (In reply to Nicholas Kazlauskas from comment #10)
> > (In reply to Nicholas Kazlauskas from comment #9)
> > > These patches should fix your issue:
> > > 
> > > https://patchwork.freedesktop.org/series/52164/
> > 
> > I suppose I should mention that these are for amd-staging-drm-next, they
> > probably won't cleanly apply on Linus' tree.
> 
> I would like to mention that revision 2 of the patch is incompatible with
> amd-staging-drm-next

Are you on the amd-staging-drm-next branch? ie.

git checkout --track origin/amd-staging-drm-next
Comment 14 Alexander Walker 2018-12-13 14:12:50 UTC
Also experiencing this on AMD Vega 56 on 4.20.

Note You need to log in before you can comment on or make changes to this bug.