Re: panic: kmem_slab_alloc(): kernel_map ran out of space!

看板DFBSD_bugs作者時間16年前 (2010/01/16 02:01), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串4/4 (看更多)
:Perhaps related to :http://leaf.dragonflybsd.org/mailarchive/kernel/2010-01/msg00002.html :and :http://leaf.dragonflybsd.org/mailarchive/commits/2010-01/msg00061.html : :I just got a panic tonight: :Reading symbols from /home/var.crash/kern.27...done. : :----------------------------------------------- :Total empty space: 184K :Total used space: 1048392K : :Indeed it appears to be out of memory. Are 32-bit users hosed? : :Kernel and core are being uploaded to leaf:~pavalos/crash/*27 : :--Peter I've got my work cut out for me today. At the very least we will be able to move some of the zalloc zones used by the network over to just using kmalloc(). That is certainly a contributor as ZONE_INTERRUPT zalloc zones reserve KVA (aka the maxfiles change). I want to keep the maxfiles change itself. tcpcb, udpcb, and ripcb are eating a ton of KVA (tcpcb mainly). tcpcb alone is eating 80MB of KVA. -Matt
文章代碼(AID): #1BKAriI9 (DFBSD_bugs)
文章代碼(AID): #1BKAriI9 (DFBSD_bugs)