All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95427] gem_userptr_blits@mlocked-* should skip due to memory pre-condition not met
Date: Sun, 19 Jun 2016 16:42:36 +0000	[thread overview]
Message-ID: <bug-95427-502-rjIHciz4bR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95427-502@http.bugs.freedesktop.org/>


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

https://bugs.freedesktop.org/show_bug.cgi?id=95427

--- Comment #2 from Humberto Israel Perez Rodriguez <humberto.i.perez.rodriguez@intel.com> ---
even with 16GB of ram in APL the following tests keeps failing :

Tests cases
=============
igt@gem_userptr_blits@mlocked-unsync-normal
igt@gem_userptr_blits@mlocked-normal-sync


output :
============
IGT-Version: 1.15-g3ce58b6 (x86_64) (Linux:
4.7.0-rc2-drm-intel-nightly-ww24-commit-55d1291+ x86_64)
(gem_userptr_blits:1332) drmtest-DEBUG: Test requirement passed: fd >= 0
(gem_userptr_blits:1332) ioctl-wrappers-DEBUG: Test requirement passed: !(ret
== ENODEV && (flags & LOCAL_I915_USERPTR_UNSYNCHRONIZED) == 0 && !read_only)
(gem_userptr_blits:1332) DEBUG: Test requirement passed: !(ret == 0)
Aperture size is 268435456 MiB
Total RAM is 15,884 MiB
Not enough RAM to run test, reducing buffer count.
Testing unsynchronized mappings...
(gem_userptr_blits:1332) igt-core-DEBUG: Starting subtest:
mlocked-unsync-normal
(gem_userptr_blits:1332) intel-os-DEBUG: Checking 256 surfaces of size
1,048,576 bytes (total 268,566,528) against RAM
(gem_userptr_blits:1332) intel-os-DEBUG: Test requirement passed:
__intel_check_memory(count, size, mode, &required, &total)
(gem_userptr_blits:1332) igt-core-DEBUG: Test requirement passed:
!igt_run_in_simulation()
(gem_userptr_blits:1332) DEBUG: Test requirement passed: pin > sz
(gem_userptr_blits:1332) DEBUG: Pinning [15,428, 15,684] MiB
Killed

relevant kernel messages:
=============================
kern  :err   : [Sat Jun 18 16:18:55 2016] 32 and 0 pages still available in the
bound and unbound GPU page lists.
kern  :err   : [Sat Jun 18 16:18:55 2016] Out of memory: Kill process 1348
(gem_userptr_bli) score 1762 or sacrifice child
kern  :err   : [Sat Jun 18 16:18:55 2016] Killed process 1348 (gem_userptr_bli)
total-vm:16169932kB, anon-rss:15988692kB, file-rss:4kB, shmem-rss:0kB


looks like that is something wrong in the test itself of the test needs much
more memory ?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3027 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-06-19 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-95427-502@http.bugs.freedesktop.org/>
2016-06-15 15:49 ` [Bug 95427] gem_userptr_blits@mlocked-* should skip due to memory pre-condition not met bugzilla-daemon
2016-06-19 16:42 ` bugzilla-daemon [this message]
2016-06-19 17:45 ` bugzilla-daemon
2016-07-29 13:41 ` bugzilla-daemon
2016-07-29 16:17 ` bugzilla-daemon
2016-07-29 16:25 ` bugzilla-daemon
2016-09-15 13:40 ` bugzilla-daemon

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=bug-95427-502-rjIHciz4bR@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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 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.