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, 24 Mar 2018 10:34:35 +0000 [thread overview]
Message-ID: <bug-105030-502-6RP0TqU8TJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105030-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 815 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105030
--- Comment #2 from Paul Menzel <pmenzel+bugs.freedesktop@molgen.mpg.de> ---
(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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1754 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
prev parent reply other threads:[~2018-03-24 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 11:20 [Bug 105030] `radeon_ib_ring_tests()` takes 1.5 s during resume bugzilla-daemon
2018-02-11 10:06 ` bugzilla-daemon
2018-03-24 10:34 ` bugzilla-daemon [this message]
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-6RP0TqU8TJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox