I just got this panic on my 11.0-CURRENT machine while building ports:
panic: uma_zalloc_arg: Returning an empty bucket.
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper(c113330c,2,1000,ee3fd850,ee3fd848,...) at
db_trace_self_wrapper+0x2d/frame 0xee3fd810
kdb_backtrace(c12f131f,0
fer:
> panic: uma_zalloc_arg: Returning an empty bucket.
Looks like this particular panic was caused by my local changes for draining
per-CPU caches in very low memory conditions.
> cpuid = 0
> KDB: stack backtrace:
> db_trace_self_wrapper() at 0x801b8b3a = db_trace_self_wrapper+0x2a
I've been doing some stress-testing for VM+ZFS on a kernel with
WITNESS+INVARIANTS and I have already stumbled into some curious panics.
Here's another one:
Unread portion of the kernel message buffer:
panic: uma_zalloc_arg: Returning an empty bucket.
cpuid = 0
KDB: stack
I just saw a strange panic on a dual CPU x86:
(kernel from Tuesday)
panic: uma_zalloc_arg: Returning an empty bucket.
cpuid = 0; lapic.id =
Debugger("panic")
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db> tr
Debugger(c03477a6,0,c035a2ba,d69b6bc0,1) at Debugg
