| 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= [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
| What | Removed | Added |
|---|---|---|
| Resolution | --- | NOTABUG |
| Status | NEW | RESOLVED |
You could bisect, but I would say in general that is desired b= ehavior. We must make sure that the hardware is correctly powered up before continui= ng here.
(In reply to Christian K=C3=B6nig from comment #1) > You could bisect, but I would say in general tha= t is desired behavior. >=20 > 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 ki= nd of error? It would be a really buggy hardware design, if it had to take that long. That=E2=80=99s longer then coreboot takes on devices, and you will ha= ve big problems to meet Google Chromebook and -boxes standards, and to be chosen a= s a probable device. Also, debugging such issues should be made easier.