From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 197327] New: radeon 0000:01:00.0: failed VCE resume (-110).
Date: Thu, 19 Oct 2017 20:59:34 +0000 [thread overview]
Message-ID: <bug-197327-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=197327
Bug ID: 197327
Summary: radeon 0000:01:00.0: failed VCE resume (-110).
Product: Drivers
Version: 2.5
Kernel Version: 4.13.8
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: mad_sam@bk.ru
Regression: No
Created attachment 260297
--> https://bugzilla.kernel.org/attachment.cgi?id=260297&action=edit
dmesg log
Have some trouble on my laptop with Radeon HD 8550G + Radeon HD 8750M
I have error message radeon 0000:01:00.0: failed VCE resume (-110) in boot
time, and i think my discrette card Radeon HD 8750M possibly not work (3D with
DRI_PRIME=1 gives a worse or the same FPS than without it)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-10-19 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 20:59 bugzilla-daemon [this message]
2017-10-20 8:57 ` [Bug 197327] radeon 0000:01:00.0: failed VCE resume (-110) bugzilla-daemon
2017-10-20 14:57 ` bugzilla-daemon
2018-01-23 14:22 ` bugzilla-daemon
2018-02-08 20:23 ` bugzilla-daemon
2018-02-08 20:26 ` bugzilla-daemon
2018-04-03 8:06 ` bugzilla-daemon
2018-06-18 19:11 ` bugzilla-daemon
2019-04-15 8:18 ` bugzilla-daemon
2019-07-14 21:02 ` bugzilla-daemon
2019-08-23 6:49 ` bugzilla-daemon
2021-02-16 5:11 ` 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-197327-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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;
as well as URLs for NNTP newsgroup(s).