From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 86267] [drm:evergreen_resume] *ERROR* evergreen startup failed on resume Date: Wed, 19 Nov 2014 06:40:27 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2012418398==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 485946E84F for ; Tue, 18 Nov 2014 22:40:27 -0800 (PST) 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 --===============2012418398== Content-Type: multipart/alternative; boundary="1416379227.Ee337000.13127"; charset="UTF-8" --1416379227.Ee337000.13127 Date: Wed, 19 Nov 2014 06:40:27 +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=3D86267 --- Comment #4 from Michel D=C3=A4nzer --- (In reply to jbart from comment #3) > As for bisection I can definitely give it a shot, but it's pointless unti= l I > can reproduce the issue at will... Not really, if you can get a feeling for how many times you need to test be= fore you can be confident that the problem is not present. Anyway, were you using older kernels before where the problem never occurre= d? What was the newest kernel where that was the case? --=20 You are receiving this mail because: You are the assignee for the bug. --1416379227.Ee337000.13127 Date: Wed, 19 Nov 2014 06:40:27 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comment= # 4 on bug 86267<= /a> from Michel D=C3=A4nzer 
(In reply to jbart from comment #3)
> As for bisection I can definitely give it a shot=
, but it's pointless until I
> can reproduce the issue at will...

Not really, if you can get a feeling for how many times you need to test be=
fore
you can be confident that the problem is not present.

Anyway, were you using older kernels before where the problem never occurre=
d?
What was the newest kernel where that was the case?

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1416379227.Ee337000.13127-- --===============2012418398== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============2012418398==--