public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Bas Wijnen <wijnen@debian.org>
To: intel-gfx@lists.freedesktop.org, 724944@bugs.debian.org
Subject: Bug#724944: [Intel-gfx] Patch for crashing intel server
Date: Sun, 3 Nov 2013 16:15:18 +0100	[thread overview]
Message-ID: <20131103151517.GA24887@fmf.nl> (raw)
In-Reply-To: <20131016152243.GB11319@nuc-i3427.alporthouse.com>

Hi Chris,

I got a black screen while using your patch.
/sys/kernel/debug/dri/0/i915_gem_objects contents are shown below.  The first
time is while the video is running; the second after stopping it.  AFAICS,
there is no difference between them.

However, after starting a new video, there is a difference in active objects;
not sure if it is related (I don't really know what any of it means).  That is
the third one.

Thanks,
Bas

root@star:/sys/kernel/debug/dri/0# cat i915_gem_objects 
220 objects, 36782080 bytes
131 [131] objects, 34430976 [34430976] bytes in gtt
  0 [0] active objects, 0 [0] bytes
  131 [131] inactive objects, 34430976 [34430976] bytes
49 unbound objects, 638976 bytes
1 purgeable objects, 4096 bytes
6 pinned mappable objects, 15884288 bytes
118 fault mappable objects, 27901952 bytes
536870912 [268435456] gtt total

Xorg: 217 objects, 36642816 bytes (0 active, 30703616 inactive, 5922816 unbound)
root@star:/sys/kernel/debug/dri/0# cat i915_gem_objects 
220 objects, 36782080 bytes
131 [131] objects, 34430976 [34430976] bytes in gtt
  0 [0] active objects, 0 [0] bytes
  131 [131] inactive objects, 34430976 [34430976] bytes
49 unbound objects, 638976 bytes
1 purgeable objects, 4096 bytes
6 pinned mappable objects, 15884288 bytes
118 fault mappable objects, 27901952 bytes
536870912 [268435456] gtt total

Xorg: 217 objects, 36642816 bytes (0 active, 30703616 inactive, 5922816 unbound)
root@star:/sys/kernel/debug/dri/0# cat i915_gem_objects 
220 objects, 36782080 bytes
131 [131] objects, 34430976 [34430976] bytes in gtt
  2 [2] active objects, 32768 [32768] bytes
  129 [129] inactive objects, 34398208 [34398208] bytes
49 unbound objects, 638976 bytes
1 purgeable objects, 4096 bytes
6 pinned mappable objects, 15884288 bytes
118 fault mappable objects, 27901952 bytes
536870912 [268435456] gtt total

Xorg: 217 objects, 36642816 bytes (32768 active, 30670848 inactive, 5922816 unbound)

  parent reply	other threads:[~2013-11-03 15:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 19:24 Patch for crashing intel server Bas Wijnen
2013-10-12 20:46 ` Chris Wilson
2013-10-13  3:49   ` Bug#724944: [Intel-gfx] " Bas Wijnen
2013-10-13  9:43     ` Chris Wilson
2013-10-15  1:46       ` Bug#724944: [Intel-gfx] " Bas Wijnen
2013-10-15  8:25         ` Chris Wilson
2013-10-16 14:30           ` Bas Wijnen
2013-10-16 15:22             ` Chris Wilson
2013-10-23  0:30               ` Bas Wijnen
2013-10-23  8:28                 ` Chris Wilson
2013-10-25  3:46                   ` Bas Wijnen
2013-10-25  8:33                     ` Bug#724944: [Intel-gfx] " Chris Wilson
2013-11-03 15:15               ` Bas Wijnen [this message]
2013-11-04  9:45                 ` Chris Wilson

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=20131103151517.GA24887@fmf.nl \
    --to=wijnen@debian.org \
    --cc=724944@bugs.debian.org \
    --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