[Bug 108729] [Kaveri CIK 7400K] [regression, works on radeon] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!!

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Nov 13 14:34:34 UTC 2018


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

Vedran Miletić <vedran at miletic.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |regression
            Summary|[Kaveri CIK 7400K]          |[Kaveri CIK 7400K]
                   |[drm:vce_v2_0_start         |[regression, works on
                   |[amdgpu]] *ERROR* VCE not   |radeon] [drm:vce_v2_0_start
                   |responding, trying to reset |[amdgpu]] *ERROR* VCE not
                   |the ECPU!!!                 |responding, trying to reset
                   |                            |the ECPU!!!

--- Comment #1 from Vedran Miletić <vedran at miletic.net> ---
dmesg with radeon for comparison:

[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.18.18-300.fc29.x86_64
root=UUID=6721d330-05e1-4b6d-a862-ccc514fd41ff ro rhgb quiet
radeon.cik_support=1 amdgpu.cik_support=0 LANG=hr_HR.UTF-8
[    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.18.18-300.fc29.x86_64
root=UUID=6721d330-05e1-4b6d-a862-ccc514fd41ff ro rhgb quiet
radeon.cik_support=1 amdgpu.cik_support=0
LANG=hr_HR.UTF-8
[    1.934388] [drm] radeon kernel modesetting enabled.
[    1.934429] fb: switching to radeondrmfb from EFI VGA
[    1.934855] radeon 0000:00:01.0: VRAM: 512M 0x0000000000000000 -
0x000000001FFFFFFF (512M used)                                                  
[    1.934857] radeon 0000:00:01.0: GTT: 2048M 0x0000000020000000 -
0x000000009FFFFFFF
[    1.941593] [drm] radeon: 512M of VRAM memory ready
[    1.941594] [drm] radeon: 2048M of GTT memory ready.
[    1.945188] [drm] radeon: dpm initialized
[    1.989743] radeon 0000:00:01.0: WB enabled
[    1.989761] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr
0x0000000020000c00 and cpu addr 0x(____ptrval____)                              
[    1.989764] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr
0x0000000020000c04 and cpu addr 0x(____ptrval____)                              
[    1.989766] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr
0x0000000020000c08 and cpu addr 0x(____ptrval____)                              
[    1.989768] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr
0x0000000020000c0c and cpu addr 0x(____ptrval____)                              
[    1.989770] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr
0x0000000020000c10 and cpu addr 0x(____ptrval____)                              
[    1.990188] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr
0x0000000000078d30 and cpu addr 0x(____ptrval____)                              
[    1.990342] radeon 0000:00:01.0: fence driver on ring 6 use gpu addr
0x0000000020000c18 and cpu addr 0x(____ptrval____)                              
[    1.990344] radeon 0000:00:01.0: fence driver on ring 7 use gpu addr
0x0000000020000c1c and cpu addr 0x(____ptrval____)                              
[    1.990394] radeon 0000:00:01.0: radeon: using MSI.
[    1.990418] [drm] radeon: irq initialized.
[    3.419140] [drm] Initialized radeon 2.50.0 20080528 for 0000:00:01.0 on
minor 0
[    3.624369] [drm] amdgpu kernel modesetting enabled.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20181113/a7eddc29/attachment-0001.html>


More information about the dri-devel mailing list