dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: "Alex Villací­s Lasso" <a_villacis@palosanto.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Memory corruption starting in i915 code, in 3.2-rc5
Date: Mon, 12 Dec 2011 08:41:35 -0800	[thread overview]
Message-ID: <86pqftivy8.fsf@sumi.keithp.com> (raw)
In-Reply-To: <4EE614E7.4010908@palosanto.com>


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

On Mon, 12 Dec 2011 09:51:19 -0500, Alex Villací­s Lasso <a_villacis@palosanto.com> wrote:

> Ran kernel with reverted patch for 6 hours without issues so far. Will
> keep testing after work (issue happens with my home machine).

Thanks much. Let me know if it's still stable this evening; I can send a
revert along if you don't find any problems.

-- 
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-12 16:41 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 [this message]
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

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=86pqftivy8.fsf@sumi.keithp.com \
    --to=keithp@keithp.com \
    --cc=a_villacis@palosanto.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox