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: Tue, 02 Dec 2014 01:48:39 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1266842099==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CBFDF6E44C for ; Mon, 1 Dec 2014 17:48:38 -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 --===============1266842099== Content-Type: multipart/alternative; boundary="1417484918.6Eb271e10.27826"; charset="UTF-8" --1417484918.6Eb271e10.27826 Date: Tue, 2 Dec 2014 01:48:38 +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 #7 from stefanscheffler@gmx.net --- Same here with a Radeon HD 5670 512MB GDDR5 using Arch Linux. It also happe= ns without starting X. This error only shows up when the card successfully resumes not when it fai= ls: [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low. Disabling DPM seems to prevent the startup failures. Another observation. According to /proc/interrupts the card generates thous= ands of interrupts per seconds after a failed resume, which might explain why the system feels extremely sluggish afterwards. Bisecting brought me to this commit. It's from early in the 3.17 cycle. I=20 thought this was happening with 3.16 already, but maybe I remember wrong. commit a3eb06dbca08e3fdad7039021ae03b46b215f22a Author: Michel D=C3=83=C2=A4nzer Date: Wed Jul 9 20:15:42 2014 +0200 drm/radeon: Remove radeon_gart_restore() Doesn't seem necessary, the GART table memory should be persistent. Signed-off-by: Michel D=C3=83=C2=A4nzer Reviewed-by: Christian K=C3=83=C2=B6nig Signed-off-by: Alex Deucher --=20 You are receiving this mail because: You are the assignee for the bug. --1417484918.6Eb271e10.27826 Date: Tue, 2 Dec 2014 01:48:38 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comment= # 7 on bug 86267<= /a> from stefansc= heffler@gmx.net 
Same here with a Radeon HD 5670 512MB GDDR5 using Arch Linux. =
It also happens
without starting X.

This error only shows up when the card successfully resumes not when it fai=
ls:

  [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low.

Disabling DPM seems to prevent the startup failures.

Another observation. According to /proc/interrupts the card generates thous=
ands
of interrupts per seconds after a failed resume, which might explain why the
system feels extremely sluggish afterwards.


Bisecting brought me to this commit. It's from early in the 3.17 cycle. I=20
thought this was happening with 3.16 already, but maybe I remember wrong.

commit a3eb06dbca08e3fdad7039021ae03b46b215f22a
Author: Michel D=C3=83=C2=A4nzer <michel.daenzer@amd.com>
Date:   Wed Jul 9 20:15:42 2014 +0200

    drm/radeon: Remove radeon_gart_restore()

    Doesn't seem necessary, the GART table memory should be persistent.

    Signed-off-by: Michel D=C3=83=C2=A4nzer <michel.daenzer@amd.com>
    Reviewed-by: Christian K=C3=83=C2=B6nig <christian.koenig@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

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