Bug 110994 - [vega10] *ERROR* Failed to initialize parser -125! , running libreoffice
Summary: [vega10] *ERROR* Failed to initialize parser -125! , running libreoffice
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-25 12:36 UTC by Tom Englund
Modified: 2019-10-04 18:27 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Englund 2019-06-25 12:36:07 UTC
when running libreoffice 6.3.0.0beta1-1 everything freezes and shows a blurred screen.

and this starts spamming in the journal.

jun 25 14:25:30 tom-pc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
jun 25 14:25:30 tom-pc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
jun 25 14:25:30 tom-pc sx[662]: amdgpu: The CS has been cancelled because the context is lost.
jun 25 14:25:30 tom-pc sx[662]: amdgpu: The CS has been cancelled because the context is lost.
jun 25 14:25:30 tom-pc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
jun 25 14:25:30 tom-pc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
jun 25 14:25:31 tom-pc sx[662]: amdgpu: The CS has been cancelled because the context is lost.
jun 25 14:25:31 tom-pc sx[662]: amdgpu: The CS has been cancelled because the context is lost.
jun 25 14:25:31 tom-pc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
jun 25 14:25:31 tom-pc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
jun 25 14:25:31 tom-pc sx[662]: amdgpu: The CS has been cancelled because the context is lost.
jun 25 14:25:31 tom-pc sx[662]: amdgpu: The CS has been cancelled because the context is lost.


sx is the bash script launching my window manager. instead of "startx" and i have its output piped into systemd journal.

systeminfo:

libdrm-git 2.4.98.r33.g08bd098d-1
xf86-video-amdgpu-git 19.0.1.5-1
llvm-git 9.0.0_r319552.a4876282704-1
mesa-git 19.2.0_devel.112106.188dbb1679b-1
linux-zen 5.1.12.zen1-1

amd vega 56
Comment 1 Alex Deucher 2019-06-25 12:59:58 UTC
The GPU has been reset.  You need to restart your desktop environment to recover.
Comment 2 Jason Playne 2019-06-26 08:40:36 UTC
This is has just started effecting me too. Playing "Hellblade: Senuas Sacrifice" on steam (so steam play / radv / dxvk)

mesa via pkppa

kernel 5.1.15-050115-generic (ubuntu kernel ppa)
libdrm-amdgpu1:amd64                2.4.98+git1906260630.4
mesa-vulkan-drivers:amd64           19.2~git1906240730.3b6

this wasn't happening 2 days ago, now it happens consistantly
Comment 3 Jason Playne 2019-06-26 08:46:07 UTC
(In reply to Jason Playne from comment #2)
> This is has just started effecting me too. Playing "Hellblade: Senuas
> Sacrifice" on steam (so steam play / radv / dxvk)
> 
> mesa via pkppa
> 
> kernel 5.1.15-050115-generic (ubuntu kernel ppa)
> libdrm-amdgpu1:amd64                2.4.98+git1906260630.4
> mesa-vulkan-drivers:amd64           19.2~git1906240730.3b6
> 
> this wasn't happening 2 days ago, now it happens consistantly

dropping back to the previous kernel that workse (5.1.14-050114-generic) didn't help me
Comment 4 Jason Playne 2019-06-26 08:51:10 UTC
(In reply to Jason Playne from comment #2)
> This is has just started effecting me too. Playing "Hellblade: Senuas
> Sacrifice" on steam (so steam play / radv / dxvk)
> 
> mesa via pkppa
> 
> kernel 5.1.15-050115-generic (ubuntu kernel ppa)
> libdrm-amdgpu1:amd64                2.4.98+git1906260630.4
> mesa-vulkan-drivers:amd64           19.2~git1906240730.3b6
> 
> this wasn't happening 2 days ago, now it happens consistantly

Sorry, its via the oibaf ppa.
Comment 5 Jason Playne 2019-06-26 09:08:42 UTC
(In reply to Jason Playne from comment #4)
> (In reply to Jason Playne from comment #2)
> > This is has just started effecting me too. Playing "Hellblade: Senuas
> > Sacrifice" on steam (so steam play / radv / dxvk)
> > 
> > mesa via pkppa
> > 
> > kernel 5.1.15-050115-generic (ubuntu kernel ppa)
> > libdrm-amdgpu1:amd64                2.4.98+git1906260630.4
> > mesa-vulkan-drivers:amd64           19.2~git1906240730.3b6
> > 
> > this wasn't happening 2 days ago, now it happens consistantly
> 
> Sorry, its via the oibaf ppa.

changing over to the padoka-stable ppa the problem still exists...
Comment 6 Jason Playne 2019-06-30 05:57:09 UTC
So, restarted the game (hellblade) from new and was able to play, until the same (ish) point in the game.

Even blew away the shader cache incase that got corrupted.

Still experiencing the same problem
Comment 7 Jason Playne 2019-06-30 06:00:40 UTC
here is the dmesg log for all things amdgpu

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.15-050115-generic root=UUID=2ba5c512-4d8f-11e7-b210-b3322d3f791f ro quiet splash idle=nomwait amdgpu.ppfeaturemask=0xffffffff vt.handoff=1
[    0.147115] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.1.15-050115-generic root=UUID=2ba5c512-4d8f-11e7-b210-b3322d3f791f ro quiet splash idle=nomwait amdgpu.ppfeaturemask=0xffffffff vt.handoff=1
[    1.482810] [drm] amdgpu kernel modesetting enabled.
[    1.483007] fb0: switching to amdgpudrmfb from VESA VGA
[    1.483097] amdgpu 0000:0c:00.0: vgaarb: deactivate vga console
[    1.483360] amdgpu 0000:0c:00.0: No more image in the PCI ROM
[    1.483400] amdgpu 0000:0c:00.0: VRAM: 8176M 0x000000F400000000 - 0x000000F5FEFFFFFF (8176M used)
[    1.483401] amdgpu 0000:0c:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[    1.483402] amdgpu 0000:0c:00.0: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
[    1.483477] [drm] amdgpu: 8176M of VRAM memory ready
[    1.483478] [drm] amdgpu: 8176M of GTT memory ready.
[    1.993612] fbcon: amdgpudrmfb (fb0) is primary device
[    2.014145] amdgpu 0000:0c:00.0: fb0: amdgpudrmfb frame buffer device
[    2.028499] amdgpu 0000:0c:00.0: ring gfx uses VM inv eng 0 on hub 0
[    2.028500] amdgpu 0000:0c:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[    2.028501] amdgpu 0000:0c:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[    2.028502] amdgpu 0000:0c:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[    2.028503] amdgpu 0000:0c:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[    2.028504] amdgpu 0000:0c:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[    2.028505] amdgpu 0000:0c:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[    2.028506] amdgpu 0000:0c:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[    2.028507] amdgpu 0000:0c:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[    2.028508] amdgpu 0000:0c:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[    2.028509] amdgpu 0000:0c:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[    2.028509] amdgpu 0000:0c:00.0: ring sdma1 uses VM inv eng 1 on hub 1
[    2.028510] amdgpu 0000:0c:00.0: ring uvd_0 uses VM inv eng 4 on hub 1
[    2.028511] amdgpu 0000:0c:00.0: ring uvd_enc_0.0 uses VM inv eng 5 on hub 1
[    2.028512] amdgpu 0000:0c:00.0: ring uvd_enc_0.1 uses VM inv eng 6 on hub 1
[    2.028513] amdgpu 0000:0c:00.0: ring vce0 uses VM inv eng 7 on hub 1
[    2.028514] amdgpu 0000:0c:00.0: ring vce1 uses VM inv eng 8 on hub 1
[    2.028515] amdgpu 0000:0c:00.0: ring vce2 uses VM inv eng 9 on hub 1
[    2.029090] [drm] Initialized amdgpu 3.30.0 20150101 for 0000:0c:00.0 on minor 0
[  441.574435] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574443] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f701000 from 27
[  441.574447] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
[  441.574454] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574457] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f701000 from 27
[  441.574459] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  441.574465] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574469] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f700000 from 27
[  441.574472] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  441.574479] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574481] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f701000 from 27
[  441.574483] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  441.574491] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574494] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f707000 from 27
[  441.574497] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  441.574504] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574507] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f708000 from 27
[  441.574510] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  441.574516] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574520] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f709000 from 27
[  441.574523] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  441.574530] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574534] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f700000 from 27
[  441.574536] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  441.574545] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574548] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f709000 from 27
[  441.574550] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  441.574557] amdgpu 0000:0c:00.0: [gfxhub] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494)
[  441.574560] amdgpu 0000:0c:00.0:   in page starting at address 0x000080012f701000 from 27
[  441.574563] amdgpu 0000:0c:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  451.593803] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=74980, emitted seq=74982
[  451.593842] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HellbladeGame-W pid 13494 thread HellbladeGame-W pid 13494
[  451.593846] amdgpu 0000:0c:00.0: GPU reset begin!
[  451.935808] amdgpu 0000:0c:00.0: GPU BACO reset
[  452.446323] amdgpu 0000:0c:00.0: GPU reset succeeded, trying to resume
[  452.446595] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is lost!
[  452.499322] amdgpu: [powerplay] Failed to send message: 0x46, ret value: 0xffffffff
[  452.956495] amdgpu 0000:0c:00.0: GPU reset(2) succeeded!
[  452.957220] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[  452.957383] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[  452.964084] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[  452.964232] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
...
Comment 8 Kimmo 2019-10-04 18:27:07 UTC
(In reply to Jason Playne from comment #2)
> This is has just started effecting me too. Playing "Hellblade: Senuas
> Sacrifice" on steam (so steam play / radv / dxvk)
> 
> mesa via pkppa
> 
> kernel 5.1.15-050115-generic (ubuntu kernel ppa)
> libdrm-amdgpu1:amd64                2.4.98+git1906260630.4
> mesa-vulkan-drivers:amd64           19.2~git1906240730.3b6
> 
> this wasn't happening 2 days ago, now it happens consistantly

Distro: Arch linux with latest mesa/git/valve aco builds

Experiencing the same hangups with World of Warcraft / Lutris / radv /dxvk

mesa-aco-git 1:19.3.0_devel.115981.f2bed9b344c-1

Was using libdrm-2.4.99-1 stable build but dont know if there is any difference to that. Installed just latest libdrm-git from valve-repository

Kernel 5.3.1-arch1-1-ARCH

Hardware: RX480 4GB


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.