From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 52491] radeon massive screen corruption BARTS HD6870
Date: Tue, 15 Jan 2013 19:26:08 +0000 (UTC) [thread overview]
Message-ID: <20130115192608.F154C11FBAA@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-52491-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=52491
--- Comment #10 from Bruno Jacquet <maxijac@free.fr> 2013-01-15 19:26:08 ---
(In reply to comment #8)
> (In reply to comment #6)
> > ==> So maybe dd54fef DID fix the kernel crash but replaced it with the
> > corruption I'm seeing ?
>
> Does the corruption also occur with dd54fee7d440c4a9756cce2c24a50c15e4c17ccb
> applied manually on top of 0d0b3e7443bed6b49cb90fe7ddc4b5578a83a88d?
g0d0b3e7 with patch dd54fee7d I see no corruption
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-01-15 19:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 18:42 [Bug 52491] New: radeon massive screen corruption BARTS HD6870 bugzilla-daemon
2013-01-08 18:45 ` [Bug 52491] " bugzilla-daemon
2013-01-08 18:45 ` bugzilla-daemon
2013-01-10 23:00 ` bugzilla-daemon
2013-01-12 18:27 ` bugzilla-daemon
2013-01-12 22:27 ` bugzilla-daemon
2013-01-12 22:41 ` bugzilla-daemon
2013-01-12 23:15 ` bugzilla-daemon
2013-01-12 23:19 ` bugzilla-daemon
2013-01-15 14:36 ` bugzilla-daemon
2013-01-15 17:37 ` bugzilla-daemon
2013-01-15 19:26 ` bugzilla-daemon [this message]
2013-01-15 19:38 ` bugzilla-daemon
2013-01-15 20:57 ` bugzilla-daemon
2013-01-16 22:31 ` bugzilla-daemon
2013-01-17 0:20 ` bugzilla-daemon
2013-01-17 19:26 ` bugzilla-daemon
2013-01-26 10:50 ` bugzilla-daemon
2013-01-27 14:04 ` bugzilla-daemon
2013-03-05 14:41 ` 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=20130115192608.F154C11FBAA@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.