From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 38622] [radeon cayman regresion] artefacts on screen
Date: Mon, 4 Jul 2011 17:54:38 GMT [thread overview]
Message-ID: <201107041754.p64Hsc2n017463@demeter2.kernel.org> (raw)
In-Reply-To: <bug-38622-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=38622
--- Comment #7 from Michel Dänzer <michel@daenzer.net> 2011-07-04 17:54:32 ---
(In reply to comment #5)
> skips were entered when xserver didn't even start properly - there was no way
> to test if there are artefacts
Can you provide Xorg.0.log and dmesg for such a failure?
Your log narrows things down somewhat, but I'm afraid there's still a couple of
potentially relevant changes in there.
(In reply to comment #6)
> Would it help anything if I record video how the artifact change when using
> system?
Possibly.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-07-04 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 9:35 [Bug 38622] New: [radeon cayman regresion] artefacts on screen bugzilla-daemon
2011-07-01 10:07 ` [Bug 38622] " bugzilla-daemon
2011-07-01 10:40 ` bugzilla-daemon
2011-07-01 10:52 ` bugzilla-daemon
2011-07-01 10:53 ` bugzilla-daemon
2011-07-01 19:18 ` bugzilla-daemon
2011-07-03 21:20 ` bugzilla-daemon
2011-07-04 17:54 ` bugzilla-daemon [this message]
2011-07-04 21:44 ` bugzilla-daemon
2011-07-04 21:46 ` bugzilla-daemon
2011-07-04 21:46 ` bugzilla-daemon
2011-07-04 21:48 ` bugzilla-daemon
2011-07-04 22:32 ` bugzilla-daemon
2011-09-02 21:17 ` bugzilla-daemon
2012-02-12 16:50 ` bugzilla-daemon
2012-08-24 15:06 ` 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=201107041754.p64Hsc2n017463@demeter2.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