From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36435] New: [r600g] GPU lockup CP stall
Date: Wed, 20 Apr 2011 12:04:57 -0700 (PDT) [thread overview]
Message-ID: <bug-36435-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36435
Summary: [r600g] GPU lockup CP stall
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: ojab@ojab.ru
Created an attachment (id=45872)
--> (https://bugs.freedesktop.org/attachment.cgi?id=45872)
dmesg log
Sometimes I have errors like "GPU lockup CP stall for more than 10000msec", you
can find dmesg output in the attached file. I'm already have drm.debug=15,
dmesg output for 10 sec prior to debug will be in the following comment (I
already have a plenty of those). This has happened since I have this system, so
cannot bisect.
Really don't know what additional info is needed in such cases, please ask if
anything else is needed for investigation/fix.
RADEON(0): Chipset: "ATI Radeon HD 3300 Graphics" (ChipID = 0x9614)
linux-2.6 master git (2.6.39-rc4-00089-g2f666bc)
OpenGL renderer string: Gallium 0.4 on AMD RS780
OpenGL version string: 2.1 Mesa 7.11-devel (git-f41e1db)
xf86-video-ati-6.14.99 (git-903e90c)
--
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-20 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 19:04 bugzilla-daemon [this message]
2011-04-20 19:09 ` [Bug 36435] [r600g] GPU lockup CP stall bugzilla-daemon
2011-04-20 19:21 ` bugzilla-daemon
2011-04-21 2:05 ` bugzilla-daemon
2011-06-23 12:18 ` 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-36435-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox