https://bugs.freedesktop.org/show_bug.cgi?id=107296

Janpieter Sollie <janpieter.sollie@dommel.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #22 from Janpieter Sollie <janpieter.sollie@dommel.be> ---
using kernel 5.3.8 + firmware 22/10 instead of 5.3.6 with GCC 8.3.0 instead of
9.2.0:
[    3.421856] [drm] use_doorbell being set to: [true]
[    3.421888] amdgpu: [powerplay] hwmgr_sw_init smu backed is smu10_smu
[    3.423662] [drm] Found VCN firmware Version: 1.73 Family ID: 18
[    3.423667] [drm] PSP loading VCN firmware
[    3.444352] [drm] reserve 0x400000 from 0xf400c00000 for PSP TMR
[    3.458608] usb 1-5: reset high-speed USB device number 2 using xhci_hcd
[    3.620099] [drm] DM_PPLIB: values for F clock
[    3.620101] [drm] DM_PPLIB:   400000 in kHz, 3649 in mV
[    3.620102] [drm] DM_PPLIB:   933000 in kHz, 3974 in mV
[    3.620102] [drm] DM_PPLIB:   1067000 in kHz, 4174 in mV
[    3.620103] [drm] DM_PPLIB:   1200000 in kHz, 4325 in mV
[    3.620104] [drm] DM_PPLIB: values for DCF clock
[    3.620105] [drm] DM_PPLIB:   300000 in kHz, 3649 in mV
[    3.620106] [drm] DM_PPLIB:   600000 in kHz, 3974 in mV
[    3.620107] [drm] DM_PPLIB:   626000 in kHz, 4174 in mV
[    3.620107] [drm] DM_PPLIB:   654000 in kHz, 4325 in mV
[    3.708441] [drm] Display Core initialized with v3.2.35!
[    3.733737] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.733738] [drm] Driver supports precise vblank timestamp query.
[    3.735809] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using
xhci_hcd
[    3.745448] [drm] VCN decode and encode initialized successfully(under SPG
Mode).
[    3.746451] kfd kfd: Allocated 3969056 bytes on gart
[    3.747092] Topology: Add APU node [0x15dd:0x1002]
[    3.747094] kfd kfd: added device 1002:15dd
[    3.748312] [drm] fb mappable at 0xA1000000
[    3.748313] [drm] vram apper at 0xA0000000
[    3.748314] [drm] size 8294400
[    3.748314] [drm] fb depth is 24
[    3.748315] [drm]    pitch is 7680
[    3.748384] fbcon: amdgpudrmfb (fb0) is primary device
[    3.794386] Console: switching to colour frame buffer device 240x67
[    3.816030] amdgpu 0000:29:00.0: fb0: amdgpudrmfb frame buffer device
[    3.830110] amdgpu 0000:29:00.0: ring gfx uses VM inv eng 0 on hub 0
[    3.830113] amdgpu 0000:29:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[    3.830115] amdgpu 0000:29:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[    3.830117] amdgpu 0000:29:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[    3.830120] amdgpu 0000:29:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[    3.830121] amdgpu 0000:29:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[    3.830123] amdgpu 0000:29:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[    3.830125] amdgpu 0000:29:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[    3.830127] amdgpu 0000:29:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[    3.830129] amdgpu 0000:29:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[    3.830131] amdgpu 0000:29:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[    3.830132] amdgpu 0000:29:00.0: ring vcn_dec uses VM inv eng 1 on hub 1
[    3.830134] amdgpu 0000:29:00.0: ring vcn_enc0 uses VM inv eng 4 on hub 1
[    3.830136] amdgpu 0000:29:00.0: ring vcn_enc1 uses VM inv eng 5 on hub 1
[    3.830138] amdgpu 0000:29:00.0: ring vcn_jpeg uses VM inv eng 6 on hub 1
[    3.843923] [drm] Initialized amdgpu 3.33.0 20150101 for 0000:29:00.0 on
minor 0

Looks good, doesn't it? I don't know what actually changed the behaviour, but
it seems to work

-- 
You are receiving this mail because:
You are the assignee for the bug.