From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31670] New: RV670 GPU lockup with OpenArena benchmark and kernel 2.6.37 rc1/rc2
Date: Tue, 16 Nov 2010 10:35:00 -0800 (PST) [thread overview]
Message-ID: <bug-31670-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31670
Summary: RV670 GPU lockup with OpenArena benchmark and kernel
2.6.37 rc1/rc2
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: alain.perrot@gmail.com
When running the OpenArena anholt benchmark on my Radeon HD 3870 (RV670, PCIe)
on my 64-bit Kubuntu 10.10 system with kernel 2.6.37 rc1 or rc2, and libdrm,
mesa, xorg-video-ati from git master, I often get a GPU lockup on the level
loading screen.
I can still log into the system through SSH and reboot it, but I cannot kill
the openarena process. There is nothing in dmesg when the lockup occurs.
There is no such issue with kernel 2.6.36 and the same versions of libdrm,
mesa, xorg-video-ati.
--
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:[~2010-11-16 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 18:35 bugzilla-daemon [this message]
2010-11-16 18:40 ` [Bug 31670] RV670 GPU lockup with OpenArena benchmark and kernel 2.6.37 rc1/rc2 bugzilla-daemon
2010-11-16 18:49 ` bugzilla-daemon
2010-11-21 15:27 ` bugzilla-daemon
2010-11-21 15:41 ` bugzilla-daemon
2010-11-21 16:22 ` bugzilla-daemon
2010-11-21 16:29 ` bugzilla-daemon
2010-11-22 16:32 ` bugzilla-daemon
2010-11-22 17:49 ` bugzilla-daemon
2010-11-22 18:37 ` bugzilla-daemon
2010-11-22 21:21 ` bugzilla-daemon
2010-12-07 19:12 ` bugzilla-daemon
2010-12-07 20:20 ` bugzilla-daemon
2010-12-07 22:21 ` bugzilla-daemon
2010-12-09 18:11 ` 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-31670-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.