Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Heap corruption regression in 2.15.0
Date: Wed, 18 May 2011 10:54:26 -0500	[thread overview]
Message-ID: <4DD3EBB2.2080102@gmail.com> (raw)
In-Reply-To: <aefc95$6hdi@orsmga001.jf.intel.com>

On 05/18/2011 02:43 AM, Chris Wilson wrote:
> What sort of tasks do you do during the sessions that encounter this
> corruption? Is it limited to a single chipset?

It doesn't seem to take much ... I basically log in to KDE (startx), do
a bit of work, and logout.  I haven't been able to reproduce the problem
with anything less than full-on KDE started from startx, however.

I'm in the process of trying to bisect 2.14.0 - 2.15.0.

One thing I just noticed.  I'm using glxgears as part of my test work-
load, and I noticed that the vsync seems very messed up with 2.15.0 --
lots of "flickering"; doesn't happen with 2.14.0.  I have no idea if
this is related or not ...

Thanks for the response.  I will let you know if the bisect turns up
anything useful.

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
========================================================================

  reply	other threads:[~2011-05-18 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18  4:17 Heap corruption regression in 2.15.0 Ian Pilcher
2011-05-18  7:43 ` Chris Wilson
2011-05-18 15:54   ` Ian Pilcher [this message]
2011-05-18 18:23     ` Ian Pilcher
2011-05-21 16:04       ` Ian Pilcher

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=4DD3EBB2.2080102@gmail.com \
    --to=arequipeno@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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