All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93721] Tonga [drm:amdgpu_vm_init [amdgpu]] *ERROR* Cannot allocate memory for page table array
Date: Thu, 14 Jan 2016 23:10:24 +0000	[thread overview]
Message-ID: <bug-93721-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 93721
           Summary: Tonga [drm:amdgpu_vm_init [amdgpu]] *ERROR* Cannot
                    allocate memory for page table array
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: adf.lists@gmail.com

Created attachment 121052
  --> https://bugs.freedesktop.org/attachment.cgi?id=121052&action=edit
dmesg showing mem  fail

Been testing the latest agd5f drm-next-4.5 with powerplay=1.

Nothings changed from previously reported issues, uvd still breaks powerplay
and it's self, lockups with uvd possible.

This particular boot I hadn't touched uvd or anything gl excepting glamor is
always used.

Was testing/benching vce which was going OK (apart from previously reported
issue with UHD content).

After I had finished testing I turned auto/down GPU/CPU which had been set
high.

memclk stayed stuck high. I then tried glxgears just to see if it would change
the clocks.

I got - 

libGL error: failed to open drm device: Cannot allocate memory
libGL error: failed to load driver: radeonsi

tried as user = same, tried glxinfo = same, did free =

              total        used        free      shared  buff/cache   available
Mem:        8139284      244600      340524     1519216     7554160     6314420
Swap:       4605948           0     4605948

Looks OK but as I had 1.5Gig in a ramdisk I deleted the file and then gl
started working again - strange as I've done many tests with 6Gig in there and
it just doesn't look like I was low on mem. Maybe you can see why from the
memdumps in the dmesg. 

I haven't been able to reproduce this.

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

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

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

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

             reply	other threads:[~2016-01-14 23:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 23:10 bugzilla-daemon [this message]
2016-01-14 23:27 ` [Bug 93721] Tonga [drm:amdgpu_vm_init [amdgpu]] *ERROR* Cannot allocate memory for page table array bugzilla-daemon
2016-01-15  0:53 ` bugzilla-daemon
2016-01-15  3:45 ` bugzilla-daemon
2016-01-15  8:37 ` bugzilla-daemon
2016-01-15 12:37 ` bugzilla-daemon
2016-01-15 12:41 ` bugzilla-daemon
2016-02-05  2:06 ` 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-93721-502@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.