On Wed, Feb 21, 2018 at 7:43 AM, Christian König <christian.koenig at amd.com> 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. > > Apart from that I don't have any good idea any more why that shouldn't work. Does your platform properly handle DMA masks? Most radeon hw only supports a 40 bit DMA mask. If there are relevant bits in the upper bits of the address, they will be lost when the hw tries to use the address. On at least some powerpc hw, I believe there is some memory routing related info in the high bits. Alex > > 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
