From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93784] Hybrid graphics: GPU lockup when running glxgears
Date: Sat, 21 May 2016 02:43:31 +0000 [thread overview]
Message-ID: <bug-93784-502-y9UrTCKsAv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93784-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 680 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93784
--- Comment #7 from Nicolas Koch <nioko1337@googlemail.com> ---
I could fix this problem by enabling DRI3 for the intel driver like this:
cat /etc/X11/xorg.conf.d/020-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "TearFree" "true"
Option "DRI" "3"
EndSection
No more GPU hangups and other funny stuff happening, at least glxgears works
now (no more black screen).
It would be nice, if someone found out why this is behaving strange when only
DRI2 is enabled, though.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1536 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:[~2016-05-21 2:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 2:54 [Bug 93784] Hybrid graphics: GPU lockup when running glxgears bugzilla-daemon
2016-01-20 3:00 ` bugzilla-daemon
2016-01-20 14:29 ` bugzilla-daemon
2016-01-20 15:05 ` bugzilla-daemon
2016-01-20 15:07 ` bugzilla-daemon
2016-02-22 18:23 ` bugzilla-daemon
2016-02-22 18:28 ` bugzilla-daemon
2016-05-21 2:43 ` bugzilla-daemon [this message]
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-93784-502-y9UrTCKsAv@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).