From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
Date: Sun, 13 Mar 2022 18:54:13 +0000 [thread overview]
Message-ID: <bug-205089-2300-MJl6xdfEfj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205089-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205089
--- Comment #35 from Christine Lemmer-Webber (cwebber@dustycloud.org) ---
Here's the dmesg output that appears to be associated with when everything
broke:
[ 51.645260] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645272] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x0000032a02a2a000 from IH client 0x1b (UTCL2)
[ 51.645278] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645280] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645282] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645283] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645284] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645285] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645286] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 51.645302] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645305] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x000002a2a0202000 from IH client 0x1b (UTCL2)
[ 51.645310] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645312] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645314] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645316] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645318] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645319] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645321] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 51.645335] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645338] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x0000030320203000 from IH client 0x1b (UTCL2)
[ 51.645342] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645343] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645345] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645346] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645348] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645349] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645350] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 51.645368] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645371] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x0000202032320000 from IH client 0x1b (UTCL2)
[ 51.645375] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645376] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645377] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645379] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645380] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645382] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645383] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 51.645404] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645407] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x0000320303202000 from IH client 0x1b (UTCL2)
[ 51.645411] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645413] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645414] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645416] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645418] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645419] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645421] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 51.645435] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645438] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x0000032020323000 from IH client 0x1b (UTCL2)
[ 51.645442] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645444] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645445] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645447] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645448] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645450] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645452] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 51.645465] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645469] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x0000323203032000 from IH client 0x1b (UTCL2)
[ 51.645473] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645475] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645477] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645479] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645481] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645482] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645484] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 51.645501] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645504] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x00002a0202a0a000 from IH client 0x1b (UTCL2)
[ 51.645510] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645513] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645515] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645516] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645518] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645520] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645522] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 51.645534] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645537] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x0000203232030000 from IH client 0x1b (UTCL2)
[ 51.645542] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645544] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645545] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645546] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645547] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645548] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645549] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 51.645593] amdgpu 0000:05:00.0: amdgpu: [gfxhub0] retry page fault
(src_id:0 ring:0 vmid:4 pasid:32774, for process blender pid 1724 thread
blender:cs0 pid 1754)
[ 51.645595] amdgpu 0000:05:00.0: amdgpu: in page starting at address
0x0000a02032320000 from IH client 0x1b (UTCL2)
[ 51.645599] amdgpu 0000:05:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00401431
[ 51.645601] amdgpu 0000:05:00.0: amdgpu: Faulty UTCL2 client ID: SQC
(data) (0xa)
[ 51.645602] amdgpu 0000:05:00.0: amdgpu: MORE_FAULTS: 0x1
[ 51.645603] amdgpu 0000:05:00.0: amdgpu: WALKER_ERROR: 0x0
[ 51.645604] amdgpu 0000:05:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 51.645605] amdgpu 0000:05:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 51.645606] amdgpu 0000:05:00.0: amdgpu: RW: 0x0
[ 61.685353] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=4230, emitted seq=4232
[ 61.685637] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process blender pid 1724 thread blender:cs0 pid 1754
[ 61.685887] amdgpu 0000:05:00.0: amdgpu: GPU reset begin!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-03-13 18:54 UTC|newest]
Thread overview: 62+ 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
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 [this message]
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
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-MJl6xdfEfj@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).