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 17:45:15 +0000	[thread overview]
Message-ID: <bug-95427-502-3s36XqEnG2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95427-502@http.bugs.freedesktop.org/>


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

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

--- Comment #3 from Emil Velikov <emil.l.velikov@gmail.com> ---
Guys have you actually looked at the following line ?
Aperture size is 268435456 MiB -- That is 256 TiB !!!

That's rather impossible amount if you ask me. So there's either a bug in IGT's
gem_aperture_size() or one of the two ioctls (I915_GEM_CONTEXT_GETPARAM
I915_GEM_GET_APERTURE) that it uses.

With a couple of print statements you should be able to quickly track the exact
offender. Good luck !

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

[-- Attachment #1.2: Type: text/html, Size: 1453 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 17:45 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
2016-06-19 17:45 ` bugzilla-daemon [this message]
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-3s36XqEnG2@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.