From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100222] Hang regression with R7 M370, identified possible culprit commit
Date: Wed, 15 Mar 2017 23:29:16 +0000 [thread overview]
Message-ID: <bug-100222-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1604 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100222
Bug ID: 100222
Summary: Hang regression with R7 M370, identified possible
culprit commit
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: registo.mailling@gmail.com
Created attachment 130246
--> https://bugs.freedesktop.org/attachment.cgi?id=130246&action=edit
lspci -nnk and dmesg output
After updating from kernel 4.9 series to 4.10 series I have identified a
regression when using the discrete GPU on my laptop (Lenovo Thinkpad E560).
When running any demanding application with DRI_PRIME=1 the card will hang, one
example would be running 'DRI_PRIME=1 glmark2 -b texture'.
I have noticed that the content of /sys/kernel/debug/dri/1/radeon_pm_info has
changed between kernel 4.9 and 4.10 when running glmark2.
With 4.9:
power level 4 sclk: 75000 mclk: 80000 vddc: 1050 vddci: 0 pcie gen: 2
With 4.10:
power level 4 sclk: 87500 mclk: 90000 vddc: 1050 vddci: 0 pcie gen: 2
This led me to revert commit 3a69adfe5617ceba04ad3cff0f9ccad470503fb2 which
prevents the card from hanging.
You can find the output of lspci and dmesg in the attachment for the case with
commit 3a69adfe5617ceba04ad3cff0f9ccad470503fb2 reverted.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3041 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:[~2017-03-15 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 23:29 bugzilla-daemon [this message]
2017-03-16 1:15 ` [Bug 100222] Hang regression with R7 M370, identified possible culprit commit bugzilla-daemon
2017-03-16 1:15 ` bugzilla-daemon
2017-03-16 12:19 ` bugzilla-daemon
2017-03-16 13:03 ` bugzilla-daemon
2017-03-16 17:08 ` bugzilla-daemon
2019-11-19 9:26 ` 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-100222-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.