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 (CAYMAN)
Date: Wed, 31 Oct 2012 18:29:13 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1807828713=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id DE49EA0E4F
for ;
Wed, 31 Oct 2012 11:29:12 -0700 (PDT)
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
--===============1807828713==
Content-Type: multipart/alternative; boundary="1351708152.cf6a1AE30.22012"; charset="us-ascii"
--1351708152.cf6a1AE30.22012
Date: Wed, 31 Oct 2012 18:29:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
https://bugs.freedesktop.org/show_bug.cgi?id=56139
--- Comment #7 from Alexandre Demers ---
Alex, would it be possible to print what is going on or if an error occurred in
evergreen_mc_stop()?
I see four things that could be going on:
1- we are not using the right path for CAYMAN -> (ASIC_IS_DCE6(rdev));
2- lock mechanism synced with vblank is not working properly;
3- all the registers should be locked at the same time, then all modified and
finally unlocked together, which is not done with the for loop where we move
through each at a time;
4- we are not setting the right registers.
What do you think?
I can test and investigate 1, 3 and 4. But what about 2?
--
You are receiving this mail because:
You are the assignee for the bug.
--1351708152.cf6a1AE30.22012
Date: Wed, 31 Oct 2012 18:29:12 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Comment # 7
on bug 56139
from Alexandre Demers
Alex, would it be possible to print what is going on or if an error occurred in
evergreen_mc_stop()?
I see four things that could be going on:
1- we are not using the right path for CAYMAN -> (ASIC_IS_DCE6(rdev));
2- lock mechanism synced with vblank is not working properly;
3- all the registers should be locked at the same time, then all modified and
finally unlocked together, which is not done with the for loop where we move
through each at a time;
4- we are not setting the right registers.
What do you think?
I can test and investigate 1, 3 and 4. But what about 2?
You are receiving this mail because:
- You are the assignee for the bug.
--1351708152.cf6a1AE30.22012--
--===============1807828713==
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
--===============1807828713==--