All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201957] amdgpu: ring gfx timeout
Date: Sun, 10 Nov 2019 07:11:29 +0000	[thread overview]
Message-ID: <bug-201957-2300-bpjHfopiib@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201957-2300@https.bugzilla.kernel.org/>

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

jmstylr@gmail.com changed:

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

--- Comment #17 from jmstylr@gmail.com ---
(In reply to shallowaloe from comment #16)
> Created attachment 285665 [details]
> 5 second video clip that triggers a crash
> 
> Hi,
> 
> I think I'm having the same problem as you guys.  I run a mythbackend where
> I record cable television and those recordings often crash my system when
> hardware decoding is enabled.  Usually it's just the screen that freezes and
> I can still ssh to it.  
> 
> Kernel 5.1.6 was an exception for me too, with that kernel I'm able to
> restart the display manager and recover without having to reboot.
> 
> Attached is a short video that crashes my system.  I can trigger the alert
> by running:
> 
> mpv --vo=vaapi out.ts
> 
> I'm wondering if it crashes your systems too and if it's related.


Just to add a data point, I tried running `mpv --vo=vaapi out.ts` against your
file, and while it crashed the application, it did not freeze the system. 

My hardware is a Ryzen 3700X with a Radeon RX 5700, running Ubuntu 19.10 with
default kernel (5.3.0-19-generic).

The command did result in the following lines in /var/log/syslog repeated every
5 seconds:

Nov 10 07:04:23 redacted kernel: [ 2266.802162] gmc_v10_0_process_interrupt:
23900 callbacks suppressed
Nov 10 07:04:23 redacted kernel: [ 2266.802166] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802170] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802171] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.802176] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802178] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802179] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Nov 10 07:04:23 redacted kernel: [ 2266.802566] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802568] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802569] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.802573] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802575] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802576] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Nov 10 07:04:23 redacted kernel: [ 2266.802984] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802985] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802987] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.802993] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.802994] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.802995] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Nov 10 07:04:23 redacted kernel: [ 2266.803403] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.803404] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.803406] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.803410] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.803411] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.803412] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Nov 10 07:04:23 redacted kernel: [ 2266.803822] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.803824] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.803825] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x0000213D
Nov 10 07:04:23 redacted kernel: [ 2266.803831] amdgpu 0000:0b:00.0: [mmhub]
VMC page fault (src_id:0 ring:158 vmid:0 pasid:0)
Nov 10 07:04:23 redacted kernel: [ 2266.803833] amdgpu 0000:0b:00.0:   at page
0x0000000000000000 from 18
Nov 10 07:04:23 redacted kernel: [ 2266.803834] amdgpu 0000:0b:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000

-- 
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:[~2019-11-10  7:11 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11  4:52 [Bug 201957] New: amdgpu: ring gfx timeout bugzilla-daemon
2018-12-11 14:57 ` [Bug 201957] " bugzilla-daemon
2018-12-11 18:18 ` bugzilla-daemon
2019-03-07  5:20 ` bugzilla-daemon
2019-03-07  5:24 ` bugzilla-daemon
2019-03-12 13:15 ` bugzilla-daemon
2019-04-01 18:20 ` bugzilla-daemon
2019-04-01 18:44 ` bugzilla-daemon
2019-08-20 15:06 ` bugzilla-daemon
2019-09-11  8:36 ` bugzilla-daemon
2019-09-20 11:37 ` bugzilla-daemon
2019-10-02 10:39 ` bugzilla-daemon
2019-10-11 22:00 ` bugzilla-daemon
2019-10-14 17:18 ` bugzilla-daemon
2019-10-24 16:39 ` bugzilla-daemon
2019-10-24 16:40 ` bugzilla-daemon
2019-10-27 18:44 ` bugzilla-daemon
2019-11-10  7:11 ` bugzilla-daemon [this message]
2019-11-25  9:43 ` bugzilla-daemon
2019-12-03 15:53 ` bugzilla-daemon
2019-12-03 16:07 ` bugzilla-daemon
2019-12-03 21:34 ` bugzilla-daemon
2019-12-04  9:54 ` bugzilla-daemon
2019-12-08 17:32 ` bugzilla-daemon
2020-01-02  8:30 ` bugzilla-daemon
2020-01-02  9:11 ` bugzilla-daemon
2020-01-19 17:03 ` bugzilla-daemon
2020-01-19 17:04 ` bugzilla-daemon
2020-01-19 17:04 ` bugzilla-daemon
2020-01-19 17:13 ` bugzilla-daemon
2020-04-04 21:54 ` bugzilla-daemon
2020-05-01  9:03 ` bugzilla-daemon
2020-05-01 19:52 ` bugzilla-daemon
2020-05-25 12:21 ` bugzilla-daemon
2020-06-19 19:11 ` bugzilla-daemon
2020-08-10 23:49 ` bugzilla-daemon
2020-09-01 14:00 ` bugzilla-daemon
2020-09-13 11:14 ` bugzilla-daemon
2020-11-23 16:27 ` bugzilla-daemon
2021-01-24 19:37 ` bugzilla-daemon
2021-01-24 22:26 ` bugzilla-daemon
2021-01-24 22:51 ` bugzilla-daemon
2021-01-24 22:56 ` bugzilla-daemon
2021-01-25 22:24 ` bugzilla-daemon
2021-01-26  3:22 ` bugzilla-daemon
2021-02-14 19:48 ` bugzilla-daemon
2021-02-28 12:35 ` bugzilla-daemon
2021-03-28 13:19 ` bugzilla-daemon
2021-08-22 20:01 ` bugzilla-daemon
2021-11-17  7:14 ` bugzilla-daemon
2021-11-26  2:09 ` bugzilla-daemon
2021-12-12 21:59 ` bugzilla-daemon
2021-12-22 20:33 ` bugzilla-daemon
2022-01-01  4:29 ` bugzilla-daemon
2022-01-09 18:06 ` bugzilla-daemon
2022-01-22 23:54 ` bugzilla-daemon
2022-01-22 23:56 ` bugzilla-daemon
2022-01-24 23:17 ` bugzilla-daemon
2022-01-25  8:56 ` bugzilla-daemon
2022-01-25 18:19 ` bugzilla-daemon
2022-01-25 18:49 ` bugzilla-daemon
2022-02-02 11:39 ` bugzilla-daemon
2022-02-03  1:37 ` bugzilla-daemon
2022-02-03  1:39 ` bugzilla-daemon
2022-02-03  3:42 ` bugzilla-daemon
2022-02-11 12:23 ` bugzilla-daemon
2022-02-24 23:40 ` bugzilla-daemon
2022-02-25 14:20 ` bugzilla-daemon
2022-05-05 15:19 ` bugzilla-daemon
2022-05-05 19:14 ` bugzilla-daemon
2022-06-11 22:06 ` bugzilla-daemon
2022-06-13  1:20 ` bugzilla-daemon
2022-06-20 12:03 ` bugzilla-daemon
2022-06-20 12:06 ` bugzilla-daemon
2022-06-22 12:56 ` bugzilla-daemon
2022-06-23 10:04 ` bugzilla-daemon
2022-06-23 10:26 ` bugzilla-daemon
2022-06-23 11:05 ` bugzilla-daemon
2022-06-23 11:44 ` bugzilla-daemon
2022-06-23 22:12 ` bugzilla-daemon
2022-06-29  2:58 ` bugzilla-daemon
2022-07-14 10:17 ` bugzilla-daemon
2022-07-17 10:28 ` bugzilla-daemon
2022-07-17 20:08 ` bugzilla-daemon
2022-08-11  2:59 ` bugzilla-daemon
2023-01-11  1:13 ` bugzilla-daemon
2023-05-23 10:27 ` bugzilla-daemon
2023-05-24  8:55 ` bugzilla-daemon
2023-08-15 12:33 ` bugzilla-daemon
2023-08-24 15:52 ` bugzilla-daemon
2023-09-21 22:38 ` bugzilla-daemon
2023-09-23  1:52 ` bugzilla-daemon
2023-09-30 10:25 ` bugzilla-daemon
2023-09-30 18:57 ` bugzilla-daemon
2023-09-30 19:08 ` bugzilla-daemon
2023-09-30 19:35 ` bugzilla-daemon
2023-09-30 19:47 ` bugzilla-daemon
2023-10-21 14:29 ` bugzilla-daemon
2023-10-22 17:35 ` bugzilla-daemon
2023-10-23 17:22 ` 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-201957-2300-bpjHfopiib@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.