From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 111244] amdgpu kernel 5.2 blank display after resume from suspend
Date: Mon, 29 Jul 2019 09:50:49 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1855220098=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id E2A6789CBC
for ; Mon, 29 Jul 2019 09:50:48 +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
--===============1855220098==
Content-Type: multipart/alternative; boundary="15643938481.7983C4C.29336"
Content-Transfer-Encoding: 7bit
--15643938481.7983C4C.29336
Date: Mon, 29 Jul 2019 09:50:48 +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=3D111244
--- Comment #5 from Michel D=C3=A4nzer ---
(In reply to cspack from comment #4)
> The first bisect pointed to a merge commit so the second was done to bise=
ct
> within the merged commits.
That doesn't invalidate my previous comment. :) git bisect identifying a me=
rge
commit already indicates the same thing by itself. In particular, the fact =
that
it identified a merge commit means that you declared all of its parent comm=
its
good.
(There *are* rare cases where a problem is actually introduced by a merge
commit itself, but then the second bisection should have either identified =
the
same merge commit again (if you tested it again), or failed, because all the
other commits you tested should have been good again.)
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15643938481.7983C4C.29336
Date: Mon, 29 Jul 2019 09:50:48 +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
Commen=
t # 5
on bug 11124=
4
from Michel D=C3=A4nzer
(In reply to cspack from comment #4)
> The first bisect pointed to a merge commit so th=
e second was done to bisect
> within the merged commits.
That doesn't invalidate my previous comment. :) git bisect identifying a me=
rge
commit already indicates the same thing by itself. In particular, the fact =
that
it identified a merge commit means that you declared all of its parent comm=
its
good.
(There *are* rare cases where a problem is actually introduced by a merge
commit itself, but then the second bisection should have either identified =
the
same merge commit again (if you tested it again), or failed, because all the
other commits you tested should have been good again.)
You are receiving this mail because:
- You are the assignee for the bug.
=
--15643938481.7983C4C.29336--
--===============1855220098==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs
--===============1855220098==--