From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104439] intel_do_flush_locked failed: Invalid argument
Date: Sun, 07 Jan 2018 17:06:50 +0000 [thread overview]
Message-ID: <bug-104439-502-ZJL8iwI5rd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104439-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2488 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104439
--- Comment #4 from Urs Fleisch <urs_fleisch@yahoo.de> ---
I have probably the same problem with a HP Compaq dc7800p Small Form Factor
having Intel Corporation 82Q35 Express Integrated Graphics Controller (Intel
GMA 3100 graphics, Mesa DRI Intel(R) Q35, OpenGL 2.1, DRI driver: i915).
The problem appeared since Arch Linux switched to kernel 4.14 (but not with the
4.9 LTS kernel), I have also reproduced it on Ubuntu using mainline kernels
(http://kernel.ubuntu.com/~kernel-ppa/mainline). The problems do not appear
with 4.13.16-041316, but starting with 4.14.0-041400rc1, 4.14.0-041400-generic,
4.14.12-041412-generic, and also with the latest kernel available there
4.15.0-041500rc6-generic the problem still exists.
The easiest way to reproduce the problem is starting Chromium and going to
maps.google.com. On Arch Linux (both with KDE and LxQt) the address bar
disappears and the map tiles are totally distorted. On Ubuntu 17.10 (Gnome),
the address bar disappears as soon as I start Chromium, but the contents of
Google Maps is not distorted. On both distributions, I can see
(EE) intel(0): Failed to submit rendering commands (Invalid argument),
disabling acceleration.
in /var/log/Xorg.0.log (Arch) or in journalctl (Ubuntu). In journalctl, there
is also the following log entry
intel_do_flush_locked failed: Invalid argument
I have looked into the kernel source of the current Arch Linux kernel
(4.14.12-1-ARCH), the commit 1d033b mentioned above is included.
With chrome://gpu, some messages are displayed
GpuProcessHostUIShim: The GPU process exited with code 256.
[970:970:0107/073806.982205:ERROR:gles2_cmd_decoder.cc(17977)]
[.DisplayCompositor-0x10da87b96000]GL ERROR :GL_INVALID_OPERATION :
glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[970:970:0107/073806.982610:ERROR:gles2_cmd_decoder.cc(9881)]
[.DisplayCompositor-0x10da87b96000]RENDER WARNING: texture bound to texture
unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture
filtering.
[970:970:0107/073807.029877:ERROR:gles2_cmd_decoder.cc(9881)]
[.DisplayCompositor-0x10da87b96000]RENDER WARNING: texture bound to texture
unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture
filtering.
...a lot more of these
Please let me know if I can provide more information.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3325 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
next prev parent reply other threads:[~2018-01-07 17:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 17:33 [Bug 104439] intel_do_flush_locked failed: Invalid argument bugzilla-daemon
2018-01-04 13:34 ` bugzilla-daemon
2018-01-04 13:45 ` bugzilla-daemon
2018-01-04 17:50 ` bugzilla-daemon
2018-01-07 17:06 ` bugzilla-daemon [this message]
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-ZJL8iwI5rd@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).