From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56743] New: Invalid command stream (bad START_3D) on DIS gpu
Date: Sun, 04 Nov 2012 16:51:22 +0000 [thread overview]
Message-ID: <bug-56743-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1155 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=56743
Priority: medium
Bug ID: 56743
Assignee: dri-devel@lists.freedesktop.org
Summary: Invalid command stream (bad START_3D) on DIS gpu
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: intergalactic.anonymous@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 69522
--> https://bugs.freedesktop.org/attachment.cgi?id=69522&action=edit
dmesg output
On my muxed hybrid system (Lenovo IdeaPad U455) X works fine with IGD gpu
(RS780M), but screen gets garbled when DIS gpu (RV710) is active. In dmesg
output there are lots of following messages:
[drm:r600_packet3_check] *ERROR* bad START_3D
[drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
My system is:
Lenovo IdeaPad U455 with RS780M and RV710 gpus.
linux-3.7.0-rc3+
libdrm-2.4.39
xf86-video-ati-6.14.6
mesa-9.0
glu-9.0
xorg-server-1.12.3
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2574 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2012-11-04 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 16:51 bugzilla-daemon [this message]
2012-11-04 16:53 ` [Bug 56743] Invalid command stream (bad START_3D) on DIS gpu bugzilla-daemon
2012-11-04 17:00 ` bugzilla-daemon
2012-11-04 17:39 ` bugzilla-daemon
2019-11-19 8:30 ` 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-56743-502@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 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.