From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59982] Radeon: evergreen Atombios in loop during initialization on ppc64
Date: Wed, 20 Feb 2013 15:33:41 +0000 [thread overview]
Message-ID: <bug-59982-502-c3fngAjg0r@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-59982-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 641 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=59982
--- Comment #18 from Jerome Glisse <glisse@freedesktop.org> ---
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.
[-- Attachment #1.2: Type: text/html, Size: 1451 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-02-20 15:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 18:37 [Bug 59982] New: Radeon: evergreen Atombios in loop during initialization on ppc64 bugzilla-daemon
2013-01-28 18:38 ` [Bug 59982] " bugzilla-daemon
2013-01-29 3:45 ` bugzilla-daemon
2013-01-29 3:46 ` bugzilla-daemon
2013-01-29 12:42 ` bugzilla-daemon
2013-01-29 12:50 ` bugzilla-daemon
2013-01-30 19:49 ` bugzilla-daemon
2013-01-31 10:57 ` bugzilla-daemon
2013-01-31 15:12 ` bugzilla-daemon
2013-02-06 17:07 ` bugzilla-daemon
2013-02-06 17:08 ` bugzilla-daemon
2013-02-08 17:17 ` bugzilla-daemon
2013-02-08 17:20 ` bugzilla-daemon
2013-02-09 14:40 ` bugzilla-daemon
2013-02-13 13:38 ` bugzilla-daemon
2013-02-13 14:08 ` bugzilla-daemon
2013-02-18 16:22 ` bugzilla-daemon
2013-02-18 16:29 ` bugzilla-daemon
2013-02-20 14:47 ` bugzilla-daemon
2013-02-20 15:33 ` bugzilla-daemon [this message]
2013-02-20 15:34 ` bugzilla-daemon
2013-02-20 16:33 ` bugzilla-daemon
2013-02-20 18:54 ` bugzilla-daemon
2013-02-20 22:03 ` bugzilla-daemon
2013-02-22 12:52 ` bugzilla-daemon
2013-02-22 15:04 ` bugzilla-daemon
2013-02-27 14:24 ` bugzilla-daemon
2013-02-27 14:26 ` bugzilla-daemon
2013-02-27 15:08 ` bugzilla-daemon
2013-02-27 15:47 ` bugzilla-daemon
2013-02-27 16:29 ` bugzilla-daemon
2013-02-27 17:21 ` bugzilla-daemon
2013-02-27 17:44 ` bugzilla-daemon
2013-02-28 17:34 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-59982-502-c3fngAjg0r@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox