All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103529] [GM45] GPU hang with mpv fullscreen (bisected)
Date: Tue, 31 Oct 2017 17:11:14 +0000	[thread overview]
Message-ID: <bug-103529-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 103529
           Summary: [GM45] GPU hang with mpv fullscreen (bisected)
           Product: Mesa
           Version: 17.2
          Hardware: x86 (IA32)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i915
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: adeshk@hotmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Complete graphics freeze when watching videos in mpv fullscreen mode with
hardware acceleration enabled (vaapi), which results in GPU hang. Video plays
just fine in normal windowed mode.

After mpv crashes, following is printed on the terminal:
intel_do_flush_locked failed: Input/output errord: 47

I bisected mesa between 17.1.8 and 17.2.0 to find first bad commit to be
79f2a5541f92920d35d3621179f7377c97cc75e1

Relevant thread on Arch Linux forums:
https://bbs.archlinux.org/viewtopic.php?id=230688

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

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

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

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

             reply	other threads:[~2017-10-31 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 17:11 bugzilla-daemon [this message]
2017-10-31 18:07 ` [Bug 103529] [GM45] GPU hang with mpv fullscreen (bisected) 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-103529-502@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 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.