From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 78221] 3.16 RC1: AMD R9 270 GPU locks up on some heavy 2D
activity - GPU VM fault occurs. (possibly DMA copying issue strikes back?)
Date: Wed, 25 Jun 2014 01:05:17 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from mail.kernel.org (mail.kernel.org [198.145.19.201])
by gabe.freedesktop.org (Postfix) with ESMTP id 1CF296E5CE
for ; Tue, 24 Jun 2014 18:05:20 -0700 (PDT)
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 2686020380
for ; Wed, 25 Jun 2014 01:05:19 +0000 (UTC)
Received: from bugzilla2.web.kernel.org (bugzilla2.web.kernel.org
[172.20.200.52])
by mail.kernel.org (Postfix) with ESMTP id A65BD2037B
for ; Wed, 25 Jun 2014 01:05:17 +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
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #12 from t3st3r@mail.ru ---
And what I'm supposed to test if patch is against 3.15? Because 3.15 release is
fine "on its own" and does not exposes this bug. So its impossible to see if
bug appears -> apply patch -> check that bug is gone (which looks most logical
course of actions to me, unless I got something wrong). Because 3.15 lacks this
bug even before patch.
Bug appears to be fixed between 3.15-rc8 and 3.15 as result of mentioned merge.
Then bug reappeared at 3.16-rc1 (and up) as result of other merges. So it would
be logical if patch is against some 3.15-rc* or 3.16-rc*? Unfortunately, they
have so many changes related to VM management that it's not like if I'm cool
enough to port patch to these versions myself (most notably, radeon_vm.c
changes are quite complicated). So I cant see if GPU lockup is gone after
patching some "known-bad" version.
Or you mean something like this: take 3.15 (which is ok) and check that patch
does not breaks anything? But it wouldn't be direct check if bug is actually
gone, right?
--
You are receiving this mail because:
You are watching the assignee of the bug.