dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104439] intel_do_flush_locked failed: Invalid argument
Date: Mon, 01 Jan 2018 17:33:01 +0000	[thread overview]
Message-ID: <bug-104439-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 104439
           Summary: intel_do_flush_locked failed: Invalid argument
           Product: Mesa
           Version: unspecified
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i915
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: fturco@fastmail.fm
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 136471
  --> https://bugs.freedesktop.org/attachment.cgi?id=136471&action=edit
git bisect log

The Qutebrowser web browser crashes after a while with the following error
message:

> intel_do_flush_locked failed: Invalid argument

If I restart Qutebrowser afterwards I obtain some sort of graphical corruption.

This only happens with 4.14.x kernels. No problem with 4.13.x kernels.

I'm running Gentoo Linux (~amd64) on a desktop machine with an Intel GPU:

> # lspci | grep VGA
> 00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated
> Graphics Controller (rev 02)

Packages:
- www-client/qutebrowser-1.0.4
- x11-apps/mesa-progs-8.3.0
- x11-drivers/xf86-video-intel-2.99.917_p20171018
- x11-libs/libdrm-2.4.88

This is the result of my first attempt at bisecting a kernel:

> fe91f28138e730790db014812623cfaadd318fa6 is the first bad commit

Please also see: https://bugzilla.kernel.org/show_bug.cgi?id=198115

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

[-- Attachment #1.2: Type: text/html, Size: 3254 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:[~2018-01-01 17:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01 17:33 bugzilla-daemon [this message]
2018-01-04 13:34 ` [Bug 104439] intel_do_flush_locked failed: Invalid argument bugzilla-daemon
2018-01-04 13:45 ` bugzilla-daemon
2018-01-04 17:50 ` bugzilla-daemon
2018-01-07 17:06 ` bugzilla-daemon
2018-02-14 13:52 ` bugzilla-daemon
2018-02-14 20:26 ` bugzilla-daemon
2018-02-14 20:27 ` bugzilla-daemon
2018-02-17 11:04 ` bugzilla-daemon
2018-02-21 12:19 ` bugzilla-daemon
2018-04-20 12:13 ` bugzilla-daemon
2018-04-20 12:41 ` bugzilla-daemon
2018-05-17 18:09 ` 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-104439-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 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).