From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36554] New: Amnesia game causes black screen or kernel locks
Date: Sun, 24 Apr 2011 16:46:59 -0700 (PDT) [thread overview]
Message-ID: <bug-36554-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36554
Summary: Amnesia game causes black screen or kernel locks
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: oreaus@gmail.com
When trying to play the game Amnesia, it causes a black screen after a few
audio stutters, or the audio continually stutters forever and the machine is
locked. If the screen is black and audio still playing, these messages are
spewn:
Apr 24 15:37:08 admin kernel: [ 250.786755] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(0).
Apr 24 15:37:08 admin kernel: [ 250.786762] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:08 admin kernel: [ 250.990053] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(1).
Apr 24 15:37:08 admin kernel: [ 250.990060] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:08 admin kernel: [ 251.197292] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(2).
Apr 24 15:37:08 admin kernel: [ 251.197298] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:08 admin kernel: [ 251.329062] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(3).
Apr 24 15:37:08 admin kernel: [ 251.329081] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:08 admin kernel: [ 251.423753] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(4).
Apr 24 15:37:08 admin kernel: [ 251.423760] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:09 admin kernel: [ 251.712296] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(5).
Apr 24 15:37:09 admin kernel: [ 251.712302] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:09 admin kernel: [ 251.935463] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(6).
Apr 24 15:37:09 admin kernel: [ 251.935469] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:09 admin kernel: [ 252.031268] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(7).
Apr 24 15:37:09 admin kernel: [ 252.031275] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:09 admin kernel: [ 252.478776] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(8).
Apr 24 15:37:09 admin kernel: [ 252.478783] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:10 admin kernel: [ 253.079451] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(9).
Apr 24 15:37:10 admin kernel: [ 253.079457] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:10 admin kernel: [ 253.679454] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(10).
Apr 24 15:37:10 admin kernel: [ 253.679460] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:11 admin kernel: [ 254.279886] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(11).
Apr 24 15:37:11 admin kernel: [ 254.279893] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:12 admin kernel: [ 254.880871] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(12).
Apr 24 15:37:12 admin kernel: [ 254.880878] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:12 admin kernel: [ 255.480850] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(13).
Apr 24 15:37:12 admin kernel: [ 255.480857] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:13 admin kernel: [ 256.081846] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(14).
Apr 24 15:37:13 admin kernel: [ 256.081852] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Apr 24 15:37:13 admin kernel: [ 256.681937] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(15).
Apr 24 15:37:13 admin kernel: [ 256.681943] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
I have tried several different kernel versions between 2.6.35 and 2.6.38 but
the result is the same. Sometimes the game will run but the majority of the
time it does not work. I have also tried several different combinations of game
settings and nothing seems to make much difference. I rebuilt mesa master and
libtxc_dxtn against it but it does not help.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-04-24 23:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 23:46 bugzilla-daemon [this message]
2011-04-25 0:08 ` [Bug 36554] Amnesia game causes black screen or kernel locks bugzilla-daemon
2011-04-25 12:23 ` bugzilla-daemon
2011-04-26 22:49 ` bugzilla-daemon
2011-04-27 11:13 ` bugzilla-daemon
2011-05-08 2:54 ` bugzilla-daemon
2011-05-09 9:43 ` bugzilla-daemon
2011-09-19 1:27 ` bugzilla-daemon
2011-09-20 18:29 ` bugzilla-daemon
2011-09-20 18:31 ` bugzilla-daemon
2012-12-03 22:54 ` bugzilla-daemon
2012-12-04 0:01 ` bugzilla-daemon
2012-12-04 15:54 ` bugzilla-daemon
2012-12-05 15:44 ` bugzilla-daemon
2012-12-05 15:46 ` bugzilla-daemon
2012-12-05 17:03 ` 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-36554-502@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 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.