From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26535] New: drm-radeon-testing regression: "r600/r700 command stream checker" lock up
Date: Thu, 11 Feb 2010 13:21:53 -0800 (PST) [thread overview]
Message-ID: <bug-26535-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26535
Summary: drm-radeon-testing regression: "r600/r700 command stream
checker" lock up
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: zajec5@gmail.com
Starting with "drm/radeon/kms: r600/r700 command stream checker" I get lock up
on every init 5 (KDE in my case) start. I can start in init 3 (with KMS) but
that's it.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
next reply other threads:[~2010-02-11 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 21:21 bugzilla-daemon [this message]
2010-02-11 21:22 ` [Bug 26535] drm-radeon-testing regression: "r600/r700 command stream checker" lock up bugzilla-daemon
2010-02-11 21:25 ` bugzilla-daemon
2010-02-11 21:26 ` bugzilla-daemon
2010-02-11 21:29 ` bugzilla-daemon
2010-02-11 21:35 ` bugzilla-daemon
2010-02-13 15:45 ` bugzilla-daemon
2010-02-13 15:46 ` bugzilla-daemon
2010-02-14 9:08 ` bugzilla-daemon
2010-03-08 20:26 ` 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-26535-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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.