From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73947] New: [DPM] Cape Verde PRO - GPU lockup when dpm is enabled
Date: Wed, 22 Jan 2014 21:04:13 +0000 [thread overview]
Message-ID: <bug-73947-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73947
Priority: medium
Bug ID: 73947
Assignee: dri-devel@lists.freedesktop.org
Summary: [DPM] Cape Verde PRO - GPU lockup when dpm is enabled
Severity: normal
Classification: Unclassified
OS: All
Reporter: alexander@tsoy.me
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 92619
--> https://bugs.freedesktop.org/attachment.cgi?id=92619&action=edit
dmesg.log
Running Unigine Heaven 3.0 causes GPU lockup after 1-2 seconds. This happens
only if dpm is enabled. GPU can be restored to a normal operation only via
system reboot.
My software:
linux-3.12.8 && linux-3.13.0
mesa-10.0.2
llvm-3.4
xf86-video-ati-9999 (latest git)
glamor-9999 (latest git)
libdrm-2.4.50
xorg-server-1.14.3
My hardware:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Cape Verde PRO [Radeon HD 7750] [1002:683f]
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2563 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-01-22 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 21:04 bugzilla-daemon [this message]
2014-01-22 21:04 ` [Bug 73947] [DPM] Cape Verde PRO - GPU lockup when dpm is enabled bugzilla-daemon
2014-01-22 22:12 ` bugzilla-daemon
2014-01-23 20:03 ` bugzilla-daemon
2014-01-23 21:49 ` bugzilla-daemon
2014-01-26 20:36 ` bugzilla-daemon
2014-01-26 20:37 ` 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-73947-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.