[Bug 93721] Tonga [drm:amdgpu_vm_init [amdgpu]] *ERROR* Cannot allocate memory for page table array
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Jan 14 15:10:24 PST 2016
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 at lists.freedesktop.org
Reporter: adf.lists at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20160114/5be40b14/attachment.html>
More information about the dri-devel
mailing list