All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Intel-gfx@lists.freedesktop.org" <Intel-gfx@lists.freedesktop.org>
Cc: "Meng, Mengmeng" <mengmeng.meng@intel.com>
Subject: Re: [Piketon bisected]TIMEOUT when running gem_tiled_blits
Date: Fri, 11 Feb 2011 09:15:12 +0000	[thread overview]
Message-ID: <0d30dc$l1qi38@orsmga001.jf.intel.com> (raw)
In-Reply-To: <6E3BC7F7C9A4BF4286DD4C043110F30B40C674E3CC@shsmsx502.ccr.corp.intel.com>

On Fri, 11 Feb 2011 16:02:45 +0800, "Meng, Mengmeng" <mengmeng.meng@intel.com> wrote:
> Hi,
> There is something wrong about gem_tiled_blits. Timeout when running Intel_gpu_tools/gem_tiled_blits.
> It's case regression. By bisected,371f87f2d825900484e34a8ec78272b9e62cbc02 is the first bad commit.

Takes around 30s to run the exercise on my i3. The fun part is that it
tries to allocate 3+ GiB of memory in order to cause the aperture
thrashing and so test evicting tiled buffers. If you don't have that much
memory available, then you get swap thrashing or even the dreaded OOM.

[I thought about limiting it to total available memory...]

Is your machine making any progress? Did the kernel send any warnings over
netconsole? How much memory do you have and what is your timeout?
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2011-02-11  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11  8:02 [Piketon bisected]TIMEOUT when running gem_tiled_blits Meng, Mengmeng
2011-02-11  9:15 ` Chris Wilson [this message]
2011-02-11 10:47   ` Meng, Mengmeng

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='0d30dc$l1qi38@orsmga001.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=mengmeng.meng@intel.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 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.