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: Sun, 25 Nov 2012 19:03:33 +0000 (UTC) [thread overview]
Message-ID: <20121125190333.7E8EC11FB82@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-47481-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=47481
Andre <andros@all-ein.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andros@all-ein.net
--- Comment #10 from Andre <andros@all-ein.net> 2012-11-25 19:03:33 ---
I can confirm this bug on my AMD A8-3550-m
Kernel 3.5.7 and 3.6.6 -> radeon.modeset=1
The trouble began about tree days ago, as i updated my Gentoo system (stable
branch) and the following updates where installed:
xorg-server 1.12.4 => 1.13.0-r1
mesa 8.0.4-r1 => 9.0
xf86-video-ati 6.14.6-r1 => 7.0.0
After that i had strange artifacts in X and random crashes of the X-server.
Where the mouse is movable but the windows are frozen and the screen turns
black after a a short time.
I have test-installed 3 other linux distributions, all came out with the same
bug, after upgrading the installations to the latest stable releases.
Sadly only after tree days of experimenting, i came to the conclusion that this
error only occurs when the VGA output is active.
With the LVDA or HDMI output i have no problems so far.
It's really sad to see, that this bug is two months old and now shows up in
major Linux Distributions, in the >>stable-branches<<.
--
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-11-25 19:03 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
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 [this message]
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=20121125190333.7E8EC11FB82@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.