Comment # 40
on bug 55692
from Alexandre Demers
(In reply to comment #36) > (In reply to comment #35) > > I've been playing a bit (booting and restarting with kernel 3.7-rc1) and > > strangely, what I see is very similar to what I was observing in bug 43655. > > It was then merged with bug 42373. At the time, attachment 64759 [details] [review] [review] > > [review] was proposed and a similar patch ended up being commited that fixed > > bug 43655 for me (but it never fixed bug 42373 on NI CAICOS). > > > > I'll try the workaround used at the time to see if it is really related to > > bug 43655 (comments 8 and 10) and I'll begin bisecting kernel right after. > > I think what you really want for your caicos is this patch: > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit; > h=62444b7462a2b98bc78d68736c03a7c4e66ba7e2 kernel bisected. Here is the culprit commit from what I see here: 62444b7462a2b98bc78d68736c03a7c4e66ba7e2 is the first bad commit commit 62444b7462a2b98bc78d68736c03a7c4e66ba7e2 Author: Alex Deucher <alexander.deucher@amd.com> Date: Wed Aug 15 17:18:42 2012 -0400 drm/radeon: properly handle mc_stop/mc_resume on evergreen+ (v2) - Stop the displays from accessing the FB - Block CPU access - Turn off MC client access This should fix issues some users have seen, especially with UEFI, when changing the MC FB location that result in hangs or display corruption. v2: fix crtc enabled check noticed by Luca Tettamanti Signed-off-by: Alex Deucher <alexander.deucher@amd.com> :040000 040000 3e0d33c9b4eda29ced814fe9a863efe63e53f14c 4932561607b160734ec1eade927a9fe18c9f3f1b M drivers So it may not be the same bug I'm hitting as Serkan is. Where should I track this faulty commit/bug? In the NI CAICOS bug or in a new one?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
