From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 47481] Random blank screen: radeon_cs_ib_chunk Failed to schedule IB on AMD PALM
Date: Tue, 18 Sep 2012 14:41:47 +0000 (UTC) [thread overview]
Message-ID: <20120918144147.1EB0E11FB08@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-47481-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=47481
--- Comment #6 from Alex Deucher <alexdeucher@gmail.com> 2012-09-18 14:41:46 ---
This bug sounds kind of like the bugs that
375849ce878f1a2dfac12ea2a62b361ab6b7f9a5 fixes. Can you see if this is fixed
in my drm-next-3.7-wip branch:
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.7-wip
I have a more complete set of patches to properly disable MC clients when
changing the MC.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-09-18 14:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 17:15 [Bug 47481] New: Random blank screen: radeon_cs_ib_chunk Failed to schedule IB on AMD PALM bugzilla-daemon
2012-09-13 17:18 ` [Bug 47481] " bugzilla-daemon
2012-09-13 17:19 ` bugzilla-daemon
2012-09-13 17:27 ` bugzilla-daemon
2012-09-14 10:16 ` bugzilla-daemon
2012-09-14 15:29 ` bugzilla-daemon
2012-09-17 17:41 ` bugzilla-daemon
2012-09-18 14:41 ` bugzilla-daemon [this message]
2012-09-18 16:46 ` bugzilla-daemon
2012-09-18 17:00 ` bugzilla-daemon
2012-10-09 7:53 ` bugzilla-daemon
2012-11-25 19:03 ` bugzilla-daemon
2012-11-25 22:23 ` bugzilla-daemon
2012-11-26 3:01 ` bugzilla-daemon
2012-11-27 20:17 ` bugzilla-daemon
2012-12-16 23:22 ` bugzilla-daemon
2012-12-17 0:34 ` bugzilla-daemon
2012-12-17 16:11 ` bugzilla-daemon
2012-12-18 22:23 ` 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=20120918144147.1EB0E11FB08@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.