From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108562] Radeon R5 M330 freezes when dpm enabled
Date: Fri, 26 Oct 2018 11:04:35 +0000 [thread overview]
Message-ID: <bug-108562-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1006 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108562
Bug ID: 108562
Summary: Radeon R5 M330 freezes when dpm enabled
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: masterxakep@gmail.com
Radeon R5 M330 gpu hungs when dpm enabled and running gpu intensive programs
with DRI_PRIME=1. If amdgpu.dpm disabled no freezes happens, but gpu always on
same clock speed. This happens on every linux ditro I tried. Oldest kernel I
tryed was 4.9, now I'm using amd-staging-drm-next kernel and still have
problem.
Also this happens with radeon module with radeon.dpm=1 but just before hung lot
of texture/shader artifacts appears on screen
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2293 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-10-26 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 11:04 bugzilla-daemon [this message]
2018-10-26 14:28 ` [Bug 108562] Radeon R5 M330 freezes when dpm enabled bugzilla-daemon
2018-10-26 16:41 ` bugzilla-daemon
2018-10-26 16:43 ` bugzilla-daemon
2018-10-26 16:45 ` bugzilla-daemon
2018-12-08 21:15 ` bugzilla-daemon
2019-11-19 9:00 ` 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-108562-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.