From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67825] New: Screen corruption/lockups on Northern Islands (BARTS) with dpm active
Date: Tue, 06 Aug 2013 12:51:28 +0000 [thread overview]
Message-ID: <bug-67825-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1922 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67825
Priority: medium
Bug ID: 67825
Assignee: dri-devel@lists.freedesktop.org
Summary: Screen corruption/lockups on Northern Islands (BARTS)
with dpm active
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: Alexander@Schwarz-Regensburg.de
Hardware: x86-64 (AMD64)
Status: NEW
Version: DRI CVS
Component: DRM/Radeon
Product: DRI
Created attachment 83713
--> https://bugs.freedesktop.org/attachment.cgi?id=83713&action=edit
Greps from dmesg for "drm" and "radeon"
I'm receiving massive screen corruptions on my Radeon HD 6870 when I use dpm on
an rc1/2/3/4 kernel with the following symptoms:
There's flickering all over the screen, artifacts and after trying to open
anything related to graphics (glxgears, animated menus in KDE, etc...) the
machine freezes and can only be revived with a hard reset. Sometimes the
machine doesn't even get so far and freezes immediately before. This is
accompanied by a black screen or blue lines on the screen.
The huge issue is: there's absolutely no error in dmesg and dpm is also
automatically set in power_method
I'm including grep'd dmesg's for "drm" and "radeon" anyways, to illustrate that
everything seems to load fine.
More information about the card and my system: XFX Radeon HD 6870 Black Edition
with stock bios on an Arch Linux 64 bit system.
I'm using the newest mesa-git, libdrm, xf86-video-ati-git and ati-dri-git.
It's nearly impossible to gather more information than dmesg, because the
system is extremely unstable when using dpm.
When I'm NOT setting radeon.dpm=1 the system boots fine, has 3D acceleration
and I've not a single issue with my graphics stack.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3476 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:[~2013-08-06 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 12:51 bugzilla-daemon [this message]
2013-08-06 13:31 ` [Bug 67825] Screen corruption/lockups on Northern Islands (BARTS) with dpm active bugzilla-daemon
2013-08-06 13:58 ` bugzilla-daemon
2013-08-06 13:59 ` bugzilla-daemon
2019-11-19 8:36 ` 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-67825-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;
as well as URLs for NNTP newsgroup(s).