All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
Date: Sat, 25 Jul 2020 07:35:43 +0000	[thread overview]
Message-ID: <bug-205089-2300-IvH01GCzRc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205089-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205089

Lech (vandalhj@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vandalhj@gmail.com

--- Comment #13 from Lech (vandalhj@gmail.com) ---
Jul 25 09:19:54 lech-ryzen-vega kernel: [37627.065966]
[drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences
timed out!
Jul 25 09:19:54 lech-ryzen-vega kernel: [37631.935858] [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1228554, emitted seq=1228556
Jul 25 09:19:54 lech-ryzen-vega kernel: [37631.935939] [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* Process information: process HeroesOfTheStor pid 28617 thread
HeroesOfTheStor pid 28691
Jul 25 09:19:54 lech-ryzen-vega kernel: [37631.935948] amdgpu 0000:0b:00.0: GPU
reset begin!
Jul 25 09:19:54 lech-ryzen-vega kernel: [37632.181860]
[drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences
timed out!
Jul 25 09:19:54 lech-ryzen-vega kernel: [37632.312215] amdgpu 0000:0b:00.0: GPU
BACO reset
Jul 25 09:19:55 lech-ryzen-vega kernel: [37632.888325] amdgpu 0000:0b:00.0: GPU
reset succeeded, trying to resume
Jul 25 09:19:55 lech-ryzen-vega kernel: [37632.888485] [drm] PCIE GART of 512M
enabled (table at 0x000000F400900000).
Jul 25 09:19:55 lech-ryzen-vega kernel: [37632.888509] [drm] VRAM is lost due
to GPU reset!
Jul 25 09:19:55 lech-ryzen-vega kernel: [37632.888833] [drm] PSP is resuming...
Jul 25 09:19:55 lech-ryzen-vega kernel: [37633.076488] [drm] reserve 0x400000
from 0xf5fe800000 for PSP TMR
Jul 25 09:19:55 lech-ryzen-vega kernel: [37633.255659] [drm] kiq ring mec 2
pipe 1 q 0
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373718] snd_hda_intel
0000:0b:00.1: azx_get_response timeout, switching to polling mode: last
cmd=0x00af2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373723] snd_hda_intel
0000:0b:00.1: spurious response 0x0:0x0, last cmd=0xaf2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373726] snd_hda_intel
0000:0b:00.1: spurious response 0x0:0x0, last cmd=0xaf2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373728] snd_hda_intel
0000:0b:00.1: spurious response 0x233:0x0, last cmd=0xaf2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373730] snd_hda_intel
0000:0b:00.1: spurious response 0x0:0x0, last cmd=0xaf2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373731] snd_hda_intel
0000:0b:00.1: spurious response 0x1:0x0, last cmd=0xaf2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373733] snd_hda_intel
0000:0b:00.1: spurious response 0x0:0x0, last cmd=0xaf2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373735] snd_hda_intel
0000:0b:00.1: spurious response 0x0:0x0, last cmd=0xaf2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373736] snd_hda_intel
0000:0b:00.1: spurious response 0x0:0x0, last cmd=0xaf2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373738] snd_hda_intel
0000:0b:00.1: spurious response 0x0:0x0, last cmd=0xaf2d00
Jul 25 09:19:56 lech-ryzen-vega kernel: [37634.373739] snd_hda_intel
0000:0b:00.1: spurious response 0x0:0x0, last cmd=0xaf2d00
Jul 25 09:19:57 lech-ryzen-vega kernel: [37635.377702] snd_hda_intel
0000:0b:00.1: No response from codec, disabling MSI: last cmd=0x00a72d01
Jul 25 09:19:58 lech-ryzen-vega kernel: [37636.393677] snd_hda_intel
0000:0b:00.1: No response from codec, resetting bus: last cmd=0x00a72d01
Jul 25 09:19:59 lech-ryzen-vega kernel: [37637.397658] snd_hda_intel
0000:0b:00.1: azx_get_response timeout, switching to single_cmd mode: last
cmd=0x00b77701
Jul 25 09:19:59 lech-ryzen-vega kernel: [37637.419432] [drm] UVD and UVD ENC
initialized successfully.
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519135] [drm] VCE initialized
successfully.
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519149] amdgpu 0000:0b:00.0:
ring gfx uses VM inv eng 0 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519151] amdgpu 0000:0b:00.0:
ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519153] amdgpu 0000:0b:00.0:
ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519155] amdgpu 0000:0b:00.0:
ring comp_1.2.0 uses VM inv eng 5 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519156] amdgpu 0000:0b:00.0:
ring comp_1.3.0 uses VM inv eng 6 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519158] amdgpu 0000:0b:00.0:
ring comp_1.0.1 uses VM inv eng 7 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519159] amdgpu 0000:0b:00.0:
ring comp_1.1.1 uses VM inv eng 8 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519161] amdgpu 0000:0b:00.0:
ring comp_1.2.1 uses VM inv eng 9 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519162] amdgpu 0000:0b:00.0:
ring comp_1.3.1 uses VM inv eng 10 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519164] amdgpu 0000:0b:00.0:
ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519166] amdgpu 0000:0b:00.0:
ring sdma0 uses VM inv eng 0 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519167] amdgpu 0000:0b:00.0:
ring page0 uses VM inv eng 1 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519169] amdgpu 0000:0b:00.0:
ring sdma1 uses VM inv eng 4 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519170] amdgpu 0000:0b:00.0:
ring page1 uses VM inv eng 5 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519171] amdgpu 0000:0b:00.0:
ring uvd_0 uses VM inv eng 6 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519173] amdgpu 0000:0b:00.0:
ring uvd_enc_0.0 uses VM inv eng 7 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519174] amdgpu 0000:0b:00.0:
ring uvd_enc_0.1 uses VM inv eng 8 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519176] amdgpu 0000:0b:00.0:
ring vce0 uses VM inv eng 9 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519177] amdgpu 0000:0b:00.0:
ring vce1 uses VM inv eng 10 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519179] amdgpu 0000:0b:00.0:
ring vce2 uses VM inv eng 11 on hub 1
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519180] [drm] ECC is not
present.
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.519182] [drm] SRAM ECC is not
present.
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.520993] [drm] recover vram bo
from shadow start
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522435] [drm] recover vram bo
from shadow done
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522437] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522438] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522466] amdgpu 0000:0b:00.0: GPU
reset(2) succeeded!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522477] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522479] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522481] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522482] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522484] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522485] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522487] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522488] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522489] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522491] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522492] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522493] [drm] Skip scheduling
IBs!
Jul 25 09:20:00 lech-ryzen-vega kernel: [37637.522770] [drm:amdgpu_cs_ioctl
[amdgpu]] *ERROR* Failed to initialize parser -125!
Jul 25 09:20:10 lech-ryzen-vega kernel: [37648.127879] [drm:amdgpu_cs_ioctl
[amdgpu]] *ERROR* Failed to initialize parser -125!
Jul 25 09:20:10 lech-ryzen-vega kernel: [37648.129190] [drm:amdgpu_cs_ioctl
[amdgpu]] *ERROR* Failed to initialize parser -125!
Jul 25 09:20:10 lech-ryzen-vega kernel: [37648.162337] [drm:amdgpu_cs_ioctl
[amdgpu]] *ERROR* Failed to initialize parser -125!
Jul 25 09:20:10 lech-ryzen-vega kernel: [37648.164145] [drm:amdgpu_cs_ioctl
[amdgpu]] *ERROR* Failed to initialize parser -125!
Jul 25 09:20:10 lech-ryzen-vega kernel: [37648.164261] [drm:amdgpu_cs_ioctl
[amdgpu]] *ERROR* Failed to initialize parser -125!
Jul 25 09:20:10 lech-ryzen-vega kernel: [37648.167924] [drm:amdgpu_cs_ioctl
[amdgpu]] *ERROR* Failed to initialize parser -125!
Jul 25 09:20:10 lech-ryzen-vega kernel: [37648.168801] [drm:amdgpu_cs_ioctl
[amdgpu]] *ERROR* Failed to initialize parser -125!

HW: 
Vega 56 
Ryzen 3600X

SW:
5.7.1-050701-generic x86_64
Mesa 20.2.0-devel (git-14a12b7 2020-07-24 focal-oibaf-ppa)

You can safely reopen it.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-07-25  7:35 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05 11:48 [Bug 205089] New: amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125 bugzilla-daemon
2019-10-07  3:16 ` [Bug 205089] " bugzilla-daemon
2019-10-08 17:50 ` bugzilla-daemon
2019-10-08 18:23 ` bugzilla-daemon
2019-10-08 20:15 ` bugzilla-daemon
2019-10-08 20:19 ` bugzilla-daemon
2019-10-12 19:05 ` bugzilla-daemon
2019-10-12 19:06 ` bugzilla-daemon
2019-10-14 17:20 ` bugzilla-daemon
2019-10-14 19:07 ` bugzilla-daemon
2020-04-27 16:58 ` bugzilla-daemon
2020-04-28  7:25 ` bugzilla-daemon
2020-04-28  8:01 ` bugzilla-daemon
2020-07-25  7:35 ` bugzilla-daemon [this message]
2021-07-26 20:35 ` bugzilla-daemon
2021-07-28 19:03 ` bugzilla-daemon
2021-08-01 19:43 ` bugzilla-daemon
2021-08-02 14:13 ` bugzilla-daemon
2021-08-02 14:24 ` bugzilla-daemon
2021-08-15 19:03 ` bugzilla-daemon
2021-08-25 16:03 ` bugzilla-daemon
2021-11-11 16:14 ` bugzilla-daemon
2021-11-11 16:15 ` bugzilla-daemon
2021-11-12  5:06 ` bugzilla-daemon
2021-11-12 19:29 ` bugzilla-daemon
2021-11-21 17:30 ` bugzilla-daemon
2021-11-22 14:50 ` bugzilla-daemon
2021-11-26 11:43 ` bugzilla-daemon
2021-11-27  2:51 ` bugzilla-daemon
2021-11-27 14:12 ` bugzilla-daemon
2021-11-28 14:32 ` bugzilla-daemon
2022-01-02  9:37 ` bugzilla-daemon
2022-03-06 12:34 ` bugzilla-daemon
2022-03-09 14:54 ` bugzilla-daemon
2022-03-13 17:46 ` bugzilla-daemon
2022-03-13 18:54 ` bugzilla-daemon
2022-03-21 17:07 ` bugzilla-daemon
2022-05-07  5:54 ` bugzilla-daemon
2022-05-07  6:28 ` bugzilla-daemon
2022-05-07  6:48 ` bugzilla-daemon
2022-05-08 19:23 ` bugzilla-daemon
2022-05-11  9:51 ` bugzilla-daemon
2022-05-27 11:22 ` bugzilla-daemon
2022-05-27 11:23 ` bugzilla-daemon
2022-05-30 12:39 ` bugzilla-daemon
2022-05-31 16:03 ` bugzilla-daemon
2022-05-31 18:34 ` bugzilla-daemon
2022-06-02 10:12 ` bugzilla-daemon
2022-09-09  4:08 ` bugzilla-daemon
2022-09-10  9:57 ` bugzilla-daemon
2022-10-07 21:41 ` bugzilla-daemon
2022-12-27  9:52 ` bugzilla-daemon
2022-12-27  9:53 ` bugzilla-daemon
2023-06-13 14:34 ` bugzilla-daemon
2023-07-01  5:10 ` bugzilla-daemon
2023-07-01  5:16 ` bugzilla-daemon
2023-07-11 13:14 ` bugzilla-daemon
2023-07-11 13:19 ` bugzilla-daemon
2023-09-07 17:31 ` bugzilla-daemon
2023-10-14 18:37 ` bugzilla-daemon
2023-10-15 12:09 ` bugzilla-daemon
2024-01-05 10:51 ` bugzilla-daemon
2024-12-13  1:06 ` bugzilla-daemon
2025-05-09 22:50 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-205089-2300-IvH01GCzRc@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.