dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216525] New: amdgpu VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Date: Sat, 24 Sep 2022 13:23:58 +0000	[thread overview]
Message-ID: <bug-216525-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 216525
           Summary: amdgpu VM_L2_PROTECTION_FAULT_STATUS:0x00000000
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.0.0-rc4
          Hardware: AMD
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: ionut_n2001@yahoo.com
        Regression: No

Hi Kernel Team,


I notice today one issue with amdgpu driver.
This driver is crashed, but within 40 seconds it is recovered and my display
appears correctly.

Output Error:
[ 7706.167995] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168007] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f0000 from IH client 0x1b (UTCL2)
[ 7706.168014] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00241051
[ 7706.168018] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: TCP
(0x8)
[ 7706.168022] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x1
[ 7706.168024] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168028] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x5
[ 7706.168031] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168033] amdgpu 0000:04:00.0: amdgpu:      RW: 0x1
[ 7706.168039] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168047] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f1000 from IH client 0x1b (UTCL2)
[ 7706.168053] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 7706.168056] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: CB
(0x0)
[ 7706.168059] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 7706.168061] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168063] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 7706.168064] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168067] amdgpu 0000:04:00.0: amdgpu:      RW: 0x0
[ 7706.168070] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168075] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f0000 from IH client 0x1b (UTCL2)
[ 7706.168078] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 7706.168080] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: CB
(0x0)
[ 7706.168083] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 7706.168085] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168088] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 7706.168090] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168092] amdgpu 0000:04:00.0: amdgpu:      RW: 0x0
[ 7706.168094] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168099] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f0000 from IH client 0x1b (UTCL2)
[ 7706.168103] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 7706.168105] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: CB
(0x0)
[ 7706.168108] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 7706.168110] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168112] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 7706.168115] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168117] amdgpu 0000:04:00.0: amdgpu:      RW: 0x0
[ 7706.168119] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168124] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f0000 from IH client 0x1b (UTCL2)
[ 7706.168129] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 7706.168132] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: CB
(0x0)
[ 7706.168134] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 7706.168137] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168140] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 7706.168143] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168146] amdgpu 0000:04:00.0: amdgpu:      RW: 0x0
[ 7706.168149] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168155] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f1000 from IH client 0x1b (UTCL2)
[ 7706.168160] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 7706.168163] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: CB
(0x0)
[ 7706.168166] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 7706.168169] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168172] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 7706.168175] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168178] amdgpu 0000:04:00.0: amdgpu:      RW: 0x0
[ 7706.168181] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168188] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f1000 from IH client 0x1b (UTCL2)
[ 7706.168191] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 7706.168194] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: CB
(0x0)
[ 7706.168195] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 7706.168197] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168200] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 7706.168203] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168207] amdgpu 0000:04:00.0: amdgpu:      RW: 0x0
[ 7706.168211] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168218] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f1000 from IH client 0x1b (UTCL2)
[ 7706.168223] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 7706.168227] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: CB
(0x0)
[ 7706.168230] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 7706.168233] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168237] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 7706.168240] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168243] amdgpu 0000:04:00.0: amdgpu:      RW: 0x0
[ 7706.168248] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168254] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f4000 from IH client 0x1b (UTCL2)
[ 7706.168256] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 7706.168258] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: CB
(0x0)
[ 7706.168259] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 7706.168261] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168262] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 7706.168263] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168265] amdgpu 0000:04:00.0: amdgpu:      RW: 0x0
[ 7706.168268] amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault
(src_id:0 ring:40 vmid:2 pasid:32773, for process yandex_browser pid 63982
thread yandex_bro:cs0 pid 64029)
[ 7706.168273] amdgpu 0000:04:00.0: amdgpu:   in page starting at address
0x00008001191f3000 from IH client 0x1b (UTCL2)
[ 7706.168278] amdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 7706.168281] amdgpu 0000:04:00.0: amdgpu:      Faulty UTCL2 client ID: CB
(0x0)
[ 7706.168285] amdgpu 0000:04:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 7706.168287] amdgpu 0000:04:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 7706.168290] amdgpu 0000:04:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 7706.168293] amdgpu 0000:04:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 7706.168296] amdgpu 0000:04:00.0: amdgpu:      RW: 0x0
[ 7716.336698] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[ 7734.442406] fbcon: Taking over console
[ 7734.472820] Console: switching to colour frame buffer device 160x45


My OS: Ubuntu 22.10 (Kinetic Kudu)
Kernel: linux 6.0.0-rc4 #1 SMP PREEMPT_DYNAMIC Sat Sep 17 18:19:08 EEST 2022
x86_64 x86_64 x86_64 GNU/Linux

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-09-24 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 13:23 bugzilla-daemon [this message]
2022-09-24 13:24 ` [Bug 216525] amdgpu VM_L2_PROTECTION_FAULT_STATUS:0x00000000 bugzilla-daemon
2022-09-25 19:20 ` 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-216525-2300@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