From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100891] failed to send pre message kernel output delays booting/suspending/resuming
Date: Wed, 22 Aug 2018 09:37:07 +0000 [thread overview]
Message-ID: <bug-100891-502-SFMWv7JDsb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100891-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 754 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100891
--- Comment #8 from MichaelLong <harn-solo@gmx.de> ---
Created attachment 141239
--> https://bugs.freedesktop.org/attachment.cgi?id=141239&action=edit
dmesg output of kernel 4.18.4
Regular test of the card's working status, this time probably including some
more interesting bits (a few excerpts):
10.138008] [drm] dce110_link_encoder_construct: Failed to get encoder_cap_info
from VBIOS with error code 4!
[ 18.912142] [drm:amdgpu_uvd_ring_test_ib [amdgpu]] *ERROR* amdgpu: (0)IB
test timed out.
[ 18.932321] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed
testing IB on ring 12 (-110).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1735 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 prev parent reply other threads:[~2018-08-22 9:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 15:40 [Bug 100891] failed to send pre message kernel output delays booting/suspending/resuming bugzilla-daemon
2017-04-30 15:41 ` bugzilla-daemon
2017-05-01 8:41 ` bugzilla-daemon
2017-05-01 8:42 ` bugzilla-daemon
2017-05-14 15:55 ` bugzilla-daemon
2018-04-30 15:00 ` bugzilla-daemon
2018-04-30 15:00 ` bugzilla-daemon
2018-04-30 15:02 ` bugzilla-daemon
2018-08-22 9:37 ` bugzilla-daemon [this message]
2018-10-01 12:12 ` bugzilla-daemon
2019-11-19 8:15 ` 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-100891-502-SFMWv7JDsb@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