Issue #2181 has been updated by Magliano Andrea . Status changed from New to Closed
Solved by commit 79d182b0d3dee841326d364c0e92e46c405765e6 This issue was triggered by X server, i.e. an application starting far after kernel memory setup at boot time: it's likely vm.dma_reserved=..m is needed in /boot/loader.conf too. With vm.dma_reserved=64m this issue is solved for me (radeon Xorg driver is requesting 32m in this case). ---------------------------------------- Bug #2181: contigmalloc_map() failure http://bugs.dragonflybsd.org/issues/2181 Author: Magliano Andrea Status: Closed Priority: Normal Assignee: Category: Target version: Somewhere between v2.13.0-39-gc3ec66..v2.13.0-204-gdf5ed code changes cause now xorg radeon driver to fail memory allocation, falling back to sw operation; this mean no dri and no Xv (guess how long windows scrolling takes with a full HD monitor...) >From dmesg: contigmalloc_map: failed size 33554432 low=0 high=ffffffff align=4096 boundary=0 flags=00000102 Happens everytime at system startup where no heavy memory load / fragmentation should happen. Allocation size is 1/127 of low--high range (so not a terrific one), flags are NOWAIT|ZERO. kldunload radeon and drm (latter causes calling contigmalloc thru ioctl) doesn't help. I'm running v2.13.0.207.gdae741-DEVELOPMENT x86_64 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
