From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 56139] [bisected] kernel 3.7.0-rc1 breaks 6950 (boot/grub2 and suspend/resume) (CAYMAN) Date: Mon, 12 Nov 2012 23:31:20 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1091162584==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 4C4479E76A for ; Mon, 12 Nov 2012 15:31:20 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1091162584== Content-Type: multipart/alternative; boundary="1352763080.D1A4bEf00.26794"; charset="us-ascii" --1352763080.D1A4bEf00.26794 Date: Mon, 12 Nov 2012 23:31:20 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=56139 --- Comment #28 from Alexandre Demers --- Alex, a simple question: you said bit 0 in EVERGREEN_CRTC_CONTROL stops the CRTC sync. With the culprit commit, when is it set? I mean, I had a quick look in the driver's code and I couldn't find it. When going in suspend state, shouldn't it be set to 0? Then, on resume, shouldn't it be set to 1? I may just have missed it, but could this be something missing? Same questions goes for GPU soft reset. Before the culprit commit, we were setting bit 0 to 0 on stop and setting it back to 1 on resume, which was working great. Why aren't we doing it anymore when suspending and resuming? -- You are receiving this mail because: You are the assignee for the bug. --1352763080.D1A4bEf00.26794 Date: Mon, 12 Nov 2012 23:31:20 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 28 on bug 56139 from 
Alex, a simple question: you said bit 0 in EVERGREEN_CRTC_CONTROL stops the
CRTC sync. With the culprit commit, when is it set? I mean, I had a quick look
in the driver's code and I couldn't find it. When going in suspend state,
shouldn't it be set to 0? Then, on resume, shouldn't it be set to 1? I may just
have missed it, but could this be something missing? Same questions goes for
GPU soft reset.

Before the culprit commit, we were setting bit 0 to 0 on stop and setting it
back to 1 on resume, which was working great. Why aren't we doing it anymore
when suspending and resuming?

You are receiving this mail because:
  • You are the assignee for the bug.
--1352763080.D1A4bEf00.26794-- --===============1091162584== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1091162584==--