dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93101] GPU Fault almost burned the CPU
Date: Wed, 09 Dec 2015 05:45:03 +0000	[thread overview]
Message-ID: <bug-93101-502-0LkIvYqk3P@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93101-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1766 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=93101

--- Comment #8 from Thomas DEBESSE <dev@illwieckz.net> ---
OK, so, about the hang itself, it looks like related to VDPAU if I read fine
these lines (see after), may I create a special thread for this one or do we
talk about that in the current thread (and have I to edit the title) ?

---8<-------------
Nov 24 22:58:06 gollum gnome-session[3720]: [0000000001ae7140] core libvlc:
Lancement de vlc avec l'interface par defaut. Utilisez «cvlc» pour demarrer VLC
sans interface.
Nov 24 22:58:15 gollum gnome-session[3720]: libdvdnav: Using dvdnav version
5.0.1
Nov 24 22:58:15 gollum gnome-session[3720]: libdvdnav: DVD disk reports itself
with Region mask 0x00c00000. Regions: 1 2 3 4 5 6
Nov 24 22:58:17 gollum gnome-session[3720]: libdvdread: Found 2 VTS's
Nov 24 22:58:17 gollum gnome-session[3720]: [00007f135c0011c0] core input
error: ES_OUT_RESET_PCR called
Nov 24 22:58:18 gollum gnome-session[3720]: [00007f134c173c20] avcodec decoder:
Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding
Nov 24 22:58:18 gollum gnome-session[3720]: [00007f13300cd7c0] deinterlace
filter error: unsupported chroma VDV0
Nov 24 22:58:18 gollum kernel: [97035.599447] radeon 0000:01:00.0: GPU fault
detected: 146 0x04c4880c
Nov 24 22:58:18 gollum kernel: [97035.599456] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00002126
Nov 24 22:58:18 gollum kernel: [97035.599460] radeon 0000:01:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0408800C
Nov 24 22:58:18 gollum kernel: [97035.599465] VM fault (0x0c, vmid 2) at page
8486, read from 'TC4' (0x54433400) (136)
------------->8---

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2521 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-12-09  5:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 10:00 [Bug 93101] GPU Fault almost burned the CPU bugzilla-daemon
2015-11-25 10:00 ` bugzilla-daemon
2015-11-25 10:04 ` bugzilla-daemon
2015-11-25 10:09 ` bugzilla-daemon
2015-11-25 10:15 ` bugzilla-daemon
2015-11-25 10:15 ` bugzilla-daemon
2015-11-25 10:42 ` bugzilla-daemon
2015-12-08  2:49 ` bugzilla-daemon
2015-12-08  9:03 ` bugzilla-daemon
2015-12-09  5:45 ` bugzilla-daemon [this message]
2015-12-09 18:32 ` bugzilla-daemon
2015-12-09 21:01 ` bugzilla-daemon
2015-12-10  2:47 ` bugzilla-daemon
2015-12-10  2:47 ` bugzilla-daemon
2015-12-10  2:48 ` bugzilla-daemon
2015-12-10  2:48 ` bugzilla-daemon
2015-12-10  2:50 ` bugzilla-daemon
2015-12-10  2:52 ` [Bug 93101] Radeon hang on VLC DVD playback (GL deinterlace filter?) bugzilla-daemon
2019-09-25 17:53 ` 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-93101-502-0LkIvYqk3P@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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