From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107381] radeon VCE init error (-110) -- AMD/Intel Mars Hybrid Graphics
Date: Sat, 07 May 2016 09:58:50 +0000 [thread overview]
Message-ID: <bug-107381-2300-kHu56dwmbk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-107381-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=107381
chico76 <cristian.chico76@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cristian.chico76@gmail.com
--- Comment #8 from chico76 <cristian.chico76@gmail.com> ---
I have the same problem, tested with 4.4.8-1-lts, 4.5.1 and I have recently
compiled the 4.5.3 kernel in Arch linux.
I have a hybrid set up the ARUBA card is working fine and the OLAND is the one
getting the VCE init error (-110).
maj 07 10:01:43 noname kernel: radeon 0000:01:00.0: VCE init error (-110).
maj 07 10:01:44 noname kernel: [drm:r600_ring_test [radeon]] *ERROR* radeon:
ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
maj 07 10:01:44 noname kernel: [drm:si_resume [radeon]] *ERROR* si startup
failed on resume
maj 07 10:01:44 noname acpid[554]: client connected from 666[0:1000]
if it helps, the error seems to be yielded from radeon/si.c after the comment:
/* allocate wb buffer */
But well, I am not qualified to look at this, haven't been programming for 10
years...
--
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 prev parent reply other threads:[~2016-05-07 17:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 17:09 [Bug 107381] New: radeon VCE init error (-110) -- AMD/Intel Mars Hybrid Graphics bugzilla-daemon
2015-11-24 20:10 ` [Bug 107381] " bugzilla-daemon
2015-11-24 20:11 ` bugzilla-daemon
2015-11-24 20:12 ` bugzilla-daemon
2016-03-03 15:05 ` bugzilla-daemon
2016-03-03 15:07 ` bugzilla-daemon
2016-03-04 10:34 ` bugzilla-daemon
2016-03-06 10:52 ` bugzilla-daemon
2016-05-07 9:58 ` bugzilla-daemon [this message]
2016-05-07 10:54 ` bugzilla-daemon
2016-05-11 19:47 ` bugzilla-daemon
2016-06-16 7:35 ` bugzilla-daemon
2016-10-02 19:05 ` bugzilla-daemon
2016-11-07 11:38 ` bugzilla-daemon
2016-12-01 12:29 ` bugzilla-daemon
2016-12-01 12:36 ` bugzilla-daemon
2016-12-30 20:01 ` bugzilla-daemon
2017-01-08 12:58 ` bugzilla-daemon
2017-01-24 8:41 ` bugzilla-daemon
2017-01-24 8:56 ` bugzilla-daemon
2018-12-29 15:34 ` bugzilla-daemon
2020-04-24 23:04 ` bugzilla-daemon
2020-04-27 14:40 ` bugzilla-daemon
2021-09-06 6:50 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2017-05-21 9:44 mesut kılıc
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-107381-2300-kHu56dwmbk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.