From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 59982] Radeon: evergreen Atombios in loop during initialization
on ppc64
Date: Wed, 20 Feb 2013 15:33:41 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0600401276=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id BA242E67CF
for ;
Wed, 20 Feb 2013 07:33:41 -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
--===============0600401276==
Content-Type: multipart/alternative; boundary="1361374421.63db71.18851"; charset="us-ascii"
--1361374421.63db71.18851
Date: Wed, 20 Feb 2013 15:33:41 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
https://bugs.freedesktop.org/show_bug.cgi?id=59982
--- Comment #18 from Jerome Glisse ---
So when all register return 0xffffffff it's because something went horribly
wrong. Either the GPU memory controller is lockup or in bad or the IOMMU is
blocking things.
My guess is that enabling the crtc to start scanning trigger request to the GPU
memory controller and those request points to bad address. I would tripple
check the memory controller setup and that the crtc base register points to
valid vram inside the GPU memory address space.
--
You are receiving this mail because:
You are the assignee for the bug.
--1361374421.63db71.18851
Date: Wed, 20 Feb 2013 15:33:41 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Comment # 18
on bug 59982
from Jerome Glisse
So when all register return 0xffffffff it's because something went horribly
wrong. Either the GPU memory controller is lockup or in bad or the IOMMU is
blocking things.
My guess is that enabling the crtc to start scanning trigger request to the GPU
memory controller and those request points to bad address. I would tripple
check the memory controller setup and that the crtc base register points to
valid vram inside the GPU memory address space.
You are receiving this mail because:
- You are the assignee for the bug.
--1361374421.63db71.18851--
--===============0600401276==
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
--===============0600401276==--