All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Daniel Vetter <daniel@ffwll.ch>
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: Fri, 16 Dec 2011 11:22:45 -0800	[thread overview]
Message-ID: <86ty50pbi2.fsf@sumi.keithp.com> (raw)
In-Reply-To: <20111213182650.GD4125@phenom.ffwll.local>


[-- Attachment #1.1: Type: text/plain, Size: 1144 bytes --]

On Tue, 13 Dec 2011 19:26:50 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> 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.
> 
> I think the revert is trtd. But if you revert it, please also
> revert/disable the ilk vt-d workaound or apply one of Ben's patches,
> because that one _does_ blow up, too.

Only if VT-d is enabled though, and that patch is now old enough that
reverting it may cause additional problems.

Ben's patches still appear to have problems -- they don't appear to
resolve the infinite recursion issue for unknown reasons.

I'm going to revert the patch which causes the reported regression, then
wait for Eric to finish up his request queue cleanups and revisit this
problem after that.

-- 
keith.packard@intel.com

[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2011-12-16 19:21 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 [this message]
2011-12-16 22:04                 ` Ben Widawsky
2011-12-13 18:36             ` Daniel Vetter

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=86ty50pbi2.fsf@sumi.keithp.com \
    --to=keithp@keithp.com \
    --cc=a_villacis@palosanto.com \
    --cc=daniel@ffwll.ch \
    --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.