From: Tarkan Erimer <tarkan.erimer@f-secure.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] i915 crashes X Server Constantly on Linux-3.1-rc4 to .rc6
Date: Tue, 20 Sep 2011 10:55:17 +0300 [thread overview]
Message-ID: <4E7846E5.1010909@f-secure.com> (raw)
In-Reply-To: <e39f63$1l0gme@fmsmga002.fm.intel.com>
On 09/20/2011 10:34 AM, Chris Wilson wrote:
> I've tried this on a few 32/64 bit machines (using different chips just
> in case) on a few different distros. No instant death, I'll keep poking just
> in case. Since flash is a sw rasteriser and uses ShmPutImage to update
> its screen contents, these are typically an invalid memcpy. Having the
> debug symbols would help confirm that and pinpoint which path.
>
> Going back and checking your Xorg.log, I think you need this fix:
>
> commit 3565c48c4bb77c836d817de75d098791dbb529d3
> Author: Chris Wilson<chris@chris-wilson.co.uk>
> Date: Wed Sep 14 17:45:41 2011 +0100
>
> sna: Yet another s/x/y/ typo
>
> Every time I do a transformation into pixmap space I like to include one
> of these copy'n'paste errors.
>
> Reported-by: Paul Neumann<paul104x@yahoo.de>
> Bugzilla:https://bugs.freedesktop.org/show_bug.cgi?id=40850
> Signed-off-by: Chris Wilson<chris@chris-wilson.co.u
Chris,
Many thanks for your help and debugging. I will try that and then will
let you know.
Cheers,
Tarkan
--
Tarkan Erimer
IT Service Deployment / 3rd Level Support / Snr. Linux Engineer
prev parent reply other threads:[~2011-09-20 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 9:48 [BUG] i915 crashes X Server Constantly on Linux-3.1-rc4 to .rc6 Tarkan Erimer
2011-09-19 10:10 ` Chris Wilson
2011-09-19 13:06 ` Tarkan Erimer
2011-09-19 13:33 ` Chris Wilson
2011-09-20 6:02 ` Tarkan Erimer
2011-09-20 7:34 ` Chris Wilson
2011-09-20 7:55 ` Tarkan Erimer [this message]
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=4E7846E5.1010909@f-secure.com \
--to=tarkan.erimer@f-secure.com \
--cc=chris@chris-wilson.co.uk \
--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.