On 2018-02-21 07:43 AM, Christian König wrote:
>> The failed VCE resume (-22) seems to be caused by
>>
>> Â Â Â Â if (rdev->vce.vcpu_bo == NULL)
>> Â Â Â Â Â Â Â Â return -EINVAL;
>>
>> in radeon_vce.c line 226.
>
> Yeah, you don't seem to have the VCE firmware installed. But as long
> as you don't want to do any advanced video encoding with the hardware
> we can simply ignore that for now.
>
>> Any idea where to look from there?
>
> Unfortunately not the slightest.
>
> What's a bit suspicious is that the CPU addresses for the fence
> locations look odd:
>> [Â Â 11.350779] radeon 0001:01:00.0: fence driver on ring 0 use gpu
>> addr 0x0000000080000c00 and cpu addr 0x000000007408d6c9
>> [Â Â 11.360274] radeon 0001:01:00.0: fence driver on ring 1 use gpu
>> addr 0x0000000080000c04 and cpu addr 0x0000000013c11aeb
>> [Â Â 11.369770] radeon 0001:01:00.0: fence driver on ring 2 use gpu
>> addr 0x0000000080000c08 and cpu addr 0x00000000d4ddd131
>> [Â Â 11.379267] radeon 0001:01:00.0: fence driver on ring 3 use gpu
>> addr 0x0000000080000c0c and cpu addr 0x00000000263a4d29
>> [Â Â 11.388763] radeon 0001:01:00.0: fence driver on ring 4 use gpu
>> addr 0x0000000080000c10 and cpu addr 0x000000006ceb1503
>> [Â Â 11.399277] radeon 0001:01:00.0: fence driver on ring 5 use gpu
>> addr 0x0000000000075a18 and cpu addr 0x000000008935a463
> But could as well be that we don't correctly print them.
Starting in 4.15 printk("%p") doesn't print real pointers but a hash of
the address. I think that's part of the spectre/meltdown changes to make
it harder to guess the kernel mode address space layout. See
Documentation/core-api/printk-formats.rst for more details. And this commit:
> ad67b74 printk: hash addresses printed with %p
Regards,
 Felix
>
> Apart from that I don't have any good idea any more why that shouldn't
> work.
>
> Sorry,
> Christian.
>
> Am 21.02.2018 um 13:13 schrieb Bas Vermeulen:
>> I got a 4.15.0 up and running on the board; it needs pci=noaer, but
>> boots up and sees the E8860 apart from that.
>>
>> The relevant dmesg output:
>>
>> [Â Â 10.888426] [drm] radeon kernel modesetting enabled.
>> [Â Â 10.892170] radeon 0001:01:00.0: runtime IRQ mapping not provided
>> by arch
>> [Â Â 10.892407] [drm] initializing kernel modesetting (VERDE
>> 0x1002:0x6822 0x1002:0x031E 0x00).
>> [Â Â 11.138410] ATOM BIOS: E268
>> [Â Â 11.139916] [drm] GPU not posted. posting now...
>> [Â Â 11.168970] radeon 0001:01:00.0: VRAM: 2048M 0x0000000000000000 -
>> 0x000000007FFFFFFF (2048M used)
>> [Â Â 11.176546] radeon 0001:01:00.0: GTT: 2048M 0x0000000080000000 -
>> 0x00000000FFFFFFFF
>> [Â Â 11.182909] [drm] Detected VRAM RAM=2048M, BAR=256M
>> [Â Â 11.186488] [drm] RAM width 128bits DDR
>> [  11.189121] [TTM] Zone kernel: Available graphics memory: 1978102
>> kiB
>> [Â Â 11.194350] [TTM] Initializing pool allocator
>> [Â Â 11.197407] [TTM] Initializing DMA pool allocator
>> [Â Â 11.200858] [drm] radeon: 2048M of VRAM memory ready
>> [Â Â 11.204527] [drm] radeon: 2048M of GTT memory ready.
>> [Â Â 11.208211] [drm] Loading verde Microcode
>> [Â Â 11.225907] [drm] Internal thermal controller with fan control
>> [Â Â 11.230575] [drm] probing gen 2 caps for device 1957:830 = 73f443/e
>> [Â Â 11.247750] [drm] radeon: dpm initialized
>> [Â Â 11.268255] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
>> [Â Â 11.273152] [drm] GART: num cpu pages 524288, num gpu pages 524288
>> [Â Â 11.281061] [drm] probing gen 2 caps for device 1957:830 = 73f443/e
>> [Â Â 11.286060] [drm] PCIE gen 3 link speeds already enabled
>> [Â Â 11.342009] [drm] PCIE GART of 2048M enabled (table at
>> 0x00000000001D6000).
>> [Â Â 11.347883] radeon 0001:01:00.0: WB enabled
>> [Â Â 11.350779] radeon 0001:01:00.0: fence driver on ring 0 use gpu
>> addr 0x0000000080000c00 and cpu addr 0x000000007408d6c9
>> [Â Â 11.360274] radeon 0001:01:00.0: fence driver on ring 1 use gpu
>> addr 0x0000000080000c04 and cpu addr 0x0000000013c11aeb
>> [Â Â 11.369770] radeon 0001:01:00.0: fence driver on ring 2 use gpu
>> addr 0x0000000080000c08 and cpu addr 0x00000000d4ddd131
>> [Â Â 11.379267] radeon 0001:01:00.0: fence driver on ring 3 use gpu
>> addr 0x0000000080000c0c and cpu addr 0x00000000263a4d29
>> [Â Â 11.388763] radeon 0001:01:00.0: fence driver on ring 4 use gpu
>> addr 0x0000000080000c10 and cpu addr 0x000000006ceb1503
>> [Â Â 11.399277] radeon 0001:01:00.0: fence driver on ring 5 use gpu
>> addr 0x0000000000075a18 and cpu addr 0x000000008935a463
>> [Â Â 11.419084] radeon 0001:01:00.0: failed VCE resume (-22).
>> [Â Â 11.423181] [drm] Supports vblank timestamp caching Rev 2
>> (21.10.2013).
>> [Â Â 11.428502] [drm] Driver supports precise vblank timestamp query.
>> [Â Â 11.433301] radeon 0001:01:00.0: radeon: MSI limited to 32-bit
>> [Â Â 11.437896] radeon 0001:01:00.0: radeon: using MSI.
>> [Â Â 11.441499] [drm] radeon: irq initialized.
>> [Â Â 12.127423] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0
>> test failed (scratch(0x850C)=0xCAFEDEAD)
>> [Â Â 12.135788] radeon 0001:01:00.0: disabling GPU acceleration
>> [Â Â 12.320848] [drm] Radeon Display Connectors
>> [Â Â 12.323733] [drm] Connector 0:
>> [Â Â 12.325476] [drm]Â Â DP-1
>> [Â Â 12.326711] [drm]Â Â HPD1
>> [Â Â 12.327935] [drm]Â Â DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538
>> 0x653c 0x653c
>> [Â Â 12.334035] [drm]Â Â Encoders:
>> [Â Â 12.335691] [drm]Â Â Â DFP1: INTERNAL_UNIPHY1
>> [Â Â 12.338662] [drm] Connector 1:
>> [Â Â 12.340405] [drm]Â Â DP-2
>> [Â Â 12.341625] [drm]Â Â HPD4
>> [Â Â 12.342857] [drm]Â Â DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568
>> 0x656c 0x656c
>> [Â Â 12.348957] [drm]Â Â Encoders:
>> [Â Â 12.350622] [drm]Â Â Â DFP2: INTERNAL_UNIPHY1
>> [Â Â 12.353583] [drm] Connector 2:
>> [Â Â 12.355335] [drm]Â Â DP-3
>> [Â Â 12.356557] [drm]Â Â HPD5
>> [Â Â 12.357788] [drm]Â Â DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548
>> 0x654c 0x654c
>> [Â Â 12.363888] [drm]Â Â Encoders:
>> [Â Â 12.365543] [drm]Â Â Â DFP3: INTERNAL_UNIPHY2
>> [Â Â 12.368514] [drm] Connector 3:
>> [Â Â 12.370267] [drm]Â Â DP-4
>> [Â Â 12.371487] [drm]Â Â HPD6
>> [Â Â 12.372709] [drm]Â Â DDC: 0x6570 0x6570 0x6574 0x6574 0x6578 0x6578
>> 0x657c 0x657c
>> [Â Â 12.378808] [drm]Â Â Encoders:
>> [Â Â 12.380464] [drm]Â Â Â DFP4: INTERNAL_UNIPHY2
>> [Â Â 12.508848] [drm] Cannot find any crtc or sizes
>> [Â Â 12.512716] [drm] Initialized radeon 2.50.0 20080528 for
>> 0001:01:00.0 on minor 0
>> [Â Â 13.636810] [drm] Cannot find any crtc or sizes
>>
>> The failed VCE resume (-22) seems to be caused by
>>
>> Â Â Â Â if (rdev->vce.vcpu_bo == NULL)
>> Â Â Â Â Â Â Â Â return -EINVAL;
>>
>> in radeon_vce.c line 226. Any idea where to look from there?
>>
>> Bas Vermeulen
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
