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>,
	"David Airlie" <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org
Subject: Re: Memory corruption starting in i915 code, in 3.2-rc5
Date: Sun, 11 Dec 2011 12:46:14 -0800	[thread overview]
Message-ID: <86bore4z1l.fsf@sumi.keithp.com> (raw)
In-Reply-To: <4EE4F82E.9010801@palosanto.com>


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

On Sun, 11 Dec 2011 13:36:30 -0500, Alex Villacís Lasso <a_villacis@palosanto.com> wrote:
> My system is a Fedora 16 x86_64 running self-compiled vanilla kernel 
> (.config attached for -rc5). I am getting an apparent memory corruption 
> that starts since linux 3.2-rc5. No such corruption was noticed in 
> 3.2-rc4. On the first instance, I eventually got a NULL pointer 
> dereference and the screen went black, the keyboard was unresponsive, 
> and I had to hard-reboot the machine. On the second instance, I managed 
> to reboot the machine normally. The full message log is attached. An 
> extract of the first WARNING:

The only patch in the i915 code between rc4 and rc5 is a tiny VT-d
workaround fix for ILK machines, which does fiddle with how the request
linked lists are managed.

Can you try reverting eb1711bb94991e93669c5a1b5f84f11be2d51ea1 and see
if your problem goes away?

-- 
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-11 20:53 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 [this message]
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

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=86bore4z1l.fsf@sumi.keithp.com \
    --to=keithp@keithp.com \
    --cc=a_villacis@palosanto.com \
    --cc=airlied@linux.ie \
    --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