From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 60879] [radeonsi] X11 can't start with acceleration enabled
Date: Thu, 10 Mar 2016 10:01:09 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0327049528=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id ECBBC6E92D
for ; Thu, 10 Mar 2016 10:01:09 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0327049528==
Content-Type: multipart/alternative; boundary="14576040693.2632.22824";
charset="UTF-8"
--14576040693.2632.22824
Date: Thu, 10 Mar 2016 10:01:09 +0000
MIME-Version: 1.0
Content-Type: text/plain
https://bugs.freedesktop.org/show_bug.cgi?id=60879
--- Comment #138 from Marek Olšák ---
I don't think we should use X if we know that the GPU driver is totally broken.
Piglit should be used for such testing.
How to build it:
1) Mesa should be built with:
--with-egl-platforms=x11,drm
This is also required for X acceleration, so it should be set already.
2) Build and install waffle:
git://github.com/waffle-gl/waffle
3) Build piglit (no install):
https://cgit.freedesktop.org/piglit/
Configure it with ccmake and enable waffle.
How to get ready:
1) Boot with the "text" kernel parameter (disables X) and also add
"radeon.lockup_timeout=0" to prevent the kernel driver from trying to recover
from GPU hangs.
2) Go to the piglit/bin directory.
3) Type: export PIGLIT_PLATFORM=gbm
Tests to run:
1) If this works, most things will work:
./fbo-generatemipmap-formats -auto
2) Something simpler:
./ext_transform_feedback-position -auto
3) You can invoke very simple internal driver tests by setting GALLIUM_TESTS=1.
This will exit before the program can do something, so the executable doesn't
matter. For example:
GALLIUM_TESTS=1 ./ext_transform_feedback-position
Diagnosing GPU hangs:
If the GPU hangs during these tests, you can see errors in dmesg. I recommend
using radeontop for overview of which GPU hw blocks are busy. If some blocks
report 100% activity for no reason, they are stuck.
Which blocks are stuck is the first piece of information we need to know. Then,
we need to know if any internal driver tests pass if you run something with
GALLIUM_TESTS=1 (see above).
--
You are receiving this mail because:
You are the assignee for the bug.
--14576040693.2632.22824
Date: Thu, 10 Mar 2016 10:01:09 +0000
MIME-Version: 1.0
Content-Type: text/html
Comment # 138
on bug 60879
from Marek Olšák
I don't think we should use X if we know that the GPU driver is totally broken.
Piglit should be used for such testing.
How to build it:
1) Mesa should be built with:
--with-egl-platforms=x11,drm
This is also required for X acceleration, so it should be set already.
2) Build and install waffle:
git://github.com/waffle-gl/waffle
3) Build piglit (no install):
https://cgit.freedesktop.org/piglit/
Configure it with ccmake and enable waffle.
How to get ready:
1) Boot with the "text" kernel parameter (disables X) and also add
"radeon.lockup_timeout=0" to prevent the kernel driver from trying to recover
from GPU hangs.
2) Go to the piglit/bin directory.
3) Type: export PIGLIT_PLATFORM=gbm
Tests to run:
1) If this works, most things will work:
./fbo-generatemipmap-formats -auto
2) Something simpler:
./ext_transform_feedback-position -auto
3) You can invoke very simple internal driver tests by setting GALLIUM_TESTS=1.
This will exit before the program can do something, so the executable doesn't
matter. For example:
GALLIUM_TESTS=1 ./ext_transform_feedback-position
Diagnosing GPU hangs:
If the GPU hangs during these tests, you can see errors in dmesg. I recommend
using radeontop for overview of which GPU hw blocks are busy. If some blocks
report 100% activity for no reason, they are stuck.
Which blocks are stuck is the first piece of information we need to know. Then,
we need to know if any internal driver tests pass if you run something with
GALLIUM_TESTS=1 (see above).
You are receiving this mail because:
- You are the assignee for the bug.
--14576040693.2632.22824--
--===============0327049528==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0327049528==--