From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105030] `radeon_ib_ring_tests()` takes 1.5 s during resume
Date: Sat, 10 Feb 2018 11:20:01 +0000 [thread overview]
Message-ID: <bug-105030-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1181 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105030
Bug ID: 105030
Summary: `radeon_ib_ring_tests()` takes 1.5 s during resume
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: pmenzel+bugs.freedesktop@molgen.mpg.de
Created attachment 137254
--> https://bugs.freedesktop.org/attachment.cgi?id=137254&action=edit
Linux 4.14.13 messages
On a Asus F2A85-M PRO with an AMD A6-6400K APU with Radeon HD Graphics and
Linux 4.14.13 there is a regression, that resume time of the radeon module is
two seconds. `sleepgraph.py` [1] is used to benchmark this.
> radeon @ 0000:00:01.0 {radeon} async_device (Total Suspend: 304.076 ms Total Resume: 2138.431 ms)
The call below causes this.
> radeon_ib_ring_tests [radeon] (1589.415 ms @ 6905.136004)
[1] https://01.org/suspendresume
[2] https://github.com/01org/pm-graph
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2776 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-02-10 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 11:20 bugzilla-daemon [this message]
2018-02-11 10:06 ` [Bug 105030] `radeon_ib_ring_tests()` takes 1.5 s during resume bugzilla-daemon
2018-03-24 10:34 ` 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-105030-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.