From: Jiri Slaby <jslaby@suse.cz>
To: daniel@ffwll.ch
Cc: Keith Packard <keithp@keithp.com>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, Jiri Slaby <jirislaby@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: g33: tiled output
Date: Thu, 01 Dec 2011 17:01:13 +0100 [thread overview]
Message-ID: <4ED7A4C9.601@suse.cz> (raw)
In-Reply-To: <4ED7A213.3010900@suse.cz>
On 12/01/2011 04:49 PM, Jiri Slaby wrote:
> On 12/01/2011 04:42 PM, Daniel Vetter wrote:
>> On Thu, Dec 01, 2011 at 03:37:44PM +0100, Jiri Slaby wrote:
>>> For some time, I'm seeing a tiled output like:
>>> http://www.fi.muni.cz/~xslaby/sklad/panics/bad_tile.png
>>>
>>> This happens sometimes when I open selected pages in firefox. Like
>>> maps above.
>>>
>>> Currently I'm running 3.2.0-rc3-next-20111130. This started appearing
>>> after I switched to desktop fx. Will anything from the debugfs help to
>>> track this down? Or better to report this to freedesktop.org?
>>
>> Please test the patch Chris already replied with to your first mail. It
>> might fix your issue here (if it's just a fence being stolen a bit too
>> early). If that does not help, I'll have to stare at the picture some more
>> to decode the type of tiling/swizzling going on. Maybe different pictures
>> of corruptions might help for that.
More of them:
http://www.fi.muni.cz/~xslaby/sklad/panics/bad_tile1.png
http://www.fi.muni.cz/~xslaby/sklad/panics/bad_tile2.png
http://www.fi.muni.cz/~xslaby/sklad/panics/bad_tile3.png
> thanks,
--
js
suse labs
next prev parent reply other threads:[~2011-12-01 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 14:37 g33: tiled output Jiri Slaby
2011-12-01 15:42 ` Daniel Vetter
2011-12-01 15:49 ` Jiri Slaby
2011-12-01 16:01 ` Jiri Slaby [this message]
2011-12-01 16:22 ` Daniel Vetter
2011-12-01 18:55 ` Jiri Slaby
2011-12-01 18:55 ` Jiri Slaby
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=4ED7A4C9.601@suse.cz \
--to=jslaby@suse.cz \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jirislaby@gmail.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.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.