From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 96588] [regression] [amdgpu] Errors scheduling IBs
Date: Fri, 24 Jun 2016 19:50:08 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0131185446=="
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 309A66E030
for ; Fri, 24 Jun 2016 19:50:08 +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
--===============0131185446==
Content-Type: multipart/alternative; boundary="14667978080.b321Ded0.17285";
charset="UTF-8"
--14667978080.b321Ded0.17285
Date: Fri, 24 Jun 2016 19:50:08 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D96588
--- Comment #14 from Christian K=C3=B6nig ---
Created attachment 124708
--> https://bugs.freedesktop.org/attachment.cgi?id=3D124708&action=3Dedit
Additional fix.
Alex suspend/resume idea was the right approach.
I was able to reproduce the issue and so find a pretty fundamental bug in o=
ne
of my recent patches.
Please see the additional fix, together with the first patch it should reso=
lve
the issue.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--14667978080.b321Ded0.17285
Date: Fri, 24 Jun 2016 19:50:08 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Created attachment 124708[details][review]
Additional fix.
Alex suspend/resume idea was the right approach.
I was able to reproduce the issue and so find a pretty fundamental bug in o=
ne
of my recent patches.
Please see the additional fix, together with the first patch it should reso=
lve
the issue.