Bug 105030 - `radeon_ib_ring_tests()` takes 1.5 s during resume
Summary: `radeon_ib_ring_tests()` takes 1.5 s during resume
Status: RESOLVED NOTABUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-10 11:20 UTC by Paul Menzel
Modified: 2018-03-24 10:34 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Linux 4.14.13 messages (33.93 KB, text/plain)
2018-02-10 11:20 UTC, Paul Menzel
no flags Details

Description Paul Menzel 2018-02-10 11:20:01 UTC
Created attachment 137254 [details]
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
Comment 1 Christian König 2018-02-11 10:06:11 UTC
You could bisect, but I would say in general that is desired behavior.

We must make sure that the hardware is correctly powered up before continuing here.
Comment 2 Paul Menzel 2018-03-24 10:34:35 UTC
(In reply to Christian König from comment #1)
> You could bisect, but I would say in general that is desired behavior.
> 
> We must make sure that the hardware is correctly powered up before
> continuing here.

Are you sure, that the hardware is correctly probed and this is not some kind of error? It would be a really buggy hardware design, if it had to take that long. That’s longer then coreboot takes on devices, and you will have big problems to meet Google Chromebook and -boxes standards, and to be chosen as a probable device.

Also, debugging such issues should be made easier.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.