dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Keith Packard <keithp@keithp.com>
Cc: "Alex Villací­s Lasso" <a_villacis@palosanto.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: Memory corruption starting in i915 code, in 3.2-rc5
Date: Tue, 13 Dec 2011 19:36:20 +0100	[thread overview]
Message-ID: <20111213183620.GF4125@phenom.ffwll.local> (raw)
In-Reply-To: <86borcibjd.fsf@sumi.keithp.com>

On Tue, Dec 13, 2011 at 10:14:46AM -0800, Keith Packard wrote:
> On Tue, 13 Dec 2011 10:14:15 -0500, Alex Villací­s Lasso <a_villacis@palosanto.com> wrote:
> 
> > By using a bootable USB stick, I could check the logs, which
> > showed many segfaults at /lib64/ld-2.14.90.so .
> 
> Ouch!
> 
> Please let me know if you find anything further; I'd like to get a
> revert sent upstream in the next day or so.

Another patch to try is "drm/i915: Only clear the GPU domains upon a
successful finish" from the my-next branch available at:

http://cgit.freedesktop.org/~danvet/drm/log/?h=my-next

Or just the raw patch:

http://cgit.freedesktop.org/~danvet/drm/patch/?id=389a55581e30607af0fcde6cdb4e54f189cf46cf

Thanks, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

      parent reply	other threads:[~2011-12-13 18:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-11 18:36 Memory corruption starting in i915 code, in 3.2-rc5 Alex Villacís Lasso
2011-12-11 20:46 ` Keith Packard
2011-12-11 21:29   ` Alex Villacís Lasso
2011-12-12 14:51     ` Alex Villací­s Lasso
2011-12-12 16:41       ` Keith Packard
2011-12-13 15:14         ` Alex Villací­s Lasso
2011-12-13 18:14           ` Keith Packard
2011-12-13 18:26             ` Daniel Vetter
2011-12-16 19:22               ` Keith Packard
2011-12-16 22:04                 ` Ben Widawsky
2011-12-13 18:36             ` Daniel Vetter [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=20111213183620.GF4125@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=a_villacis@palosanto.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    /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