Summary: | `radeon_ib_ring_tests()` takes 1.5 s during resume | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Paul Menzel <pmenzel+bugs.freedesktop.org> | ||||
Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||
Status: | RESOLVED NOTABUG | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | medium | ||||||
Version: | DRI git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Paul Menzel
2018-02-10 11:20:01 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. (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.