| 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 [details]
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.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
