From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 79980] Random radeonsi crashes
Date: Wed, 03 Sep 2014 09:15:59 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1129534018=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id BE7DC6E4F1
for ; Wed, 3 Sep 2014 02:15:59 -0700 (PDT)
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
--===============1129534018==
Content-Type: multipart/alternative; boundary="1409735759.Dcd1534.28962"; charset="us-ascii"
--1409735759.Dcd1534.28962
Date: Wed, 3 Sep 2014 09:15:59 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
https://bugs.freedesktop.org/show_bug.cgi?id=3D79980
--- Comment #125 from Christian K=C3=B6nig ---
(In reply to comment #124)
> I can very quickly, almost deterministically, hang the GPU (radeonsi, Cape
> Verde) with the following command:
>=20
> > LIBGL_ALWAYS_SOFTWARE=3D1 mpv --fs --vo=3Dopengl:sw /path/to/some_video
>=20
> this works on both 3.16.0 and 3.17rc3. Try seeking, it often happens
> directly after a seek. In most cases, the hang is unrecoverable and crash=
es
> the kernel after some "atombios stuck in a loop" messages. Very strange
> indeed, software rendered glxgears doesn't cause this.
>=20
> Can anyone verify? A somewhat reliable test case might be a good start to
> finally fixing this.
Well this is interesting, so you're saying that using software rendering on=
the
client side can crash the GPU? That only leaves glamor and maybe the compos=
itor
as the only one using the hardware driver.
--=20
You are receiving this mail because:
You are the assignee for the bug.
--1409735759.Dcd1534.28962
Date: Wed, 3 Sep 2014 09:15:59 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Comme=
nt # 125
on bug 79980<=
/a>
from Christian K=C3=B6nig
(In reply to comment =
#124)
> I can very quickly, almost deterministically, ha=
ng the GPU (radeonsi, Cape
> Verde) with the following command:
>=20
> > LIBGL_ALWAYS_SOFTWARE=3D1 mpv --fs --vo=3Dopengl:sw /path/to/some=
_video
>=20
> this works on both 3.16.0 and 3.17rc3. Try seeking, it often happens
> directly after a seek. In most cases, the hang is unrecoverable and cr=
ashes
> the kernel after some "atombios stuck in a loop" messages. V=
ery strange
> indeed, software rendered glxgears doesn't cause this.
>=20
> Can anyone verify? A somewhat reliable test case might be a good start=
to
> finally fixing this.
Well this is interesting, so you're saying that using software rendering on=
the
client side can crash the GPU? That only leaves glamor and maybe the compos=
itor
as the only one using the hardware driver.
You are receiving this mail because:
=20=20=20=20=20=20
- You are the assignee for the bug.
--1409735759.Dcd1534.28962--
--===============1129534018==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--===============1129534018==--