Re: out of swap space causing panic?

On Thursday, September 20, 2012 4:17:52 am Anton Shterenlikht wrote:
> It is expected that running out of swap space
> causes panic?
> 
> This is on ia64 r235474.
> 
> Mark, I'll add another swap disk,
> so there will be ~85 GB of swap space.
> Will let you know when done.
> 
> 
> - - - - - - - - - - Prior Console Output - - - - - - - - - -
> swap_pager_getswapspace(16): failed
> Sep 19 04:12:20 mech-as28 kernel: pid 36179 (tst_fmt_usr), uid 0, was killed: out of swap space
> Sep 19 10:54:01 mech-as28 su: mexas to root on /dev/pts/0
> panic: _mtx_lock_sleep: recursed on non-recursive mutex process lock _at_ /usr/src/sys/ia64/ia64/trap.c:562
> 
> cpuid = 1
> KDB: enter: panic
> [ thread pid 25199 tid 100332 ]
> Stopped at      kdb_enter+0x92: [I2]    addl r14=0xffffffffffe25000,gp ;;
> db> 
> db> bt
> Tracing pid 25199 tid 100332 td 0xe0000001d44088a0
> kdb_enter(0x9ffc000000c52c38, 0x9ffc000000c52c38, 0x9ffc0000004eb6b0, 0x793) at kdb_enter+0x92
> panic(0x9ffc000000c50e98, 0x9ffc000000c50f40, 0x9ffc000000c93830, 0x232) at panic+0x420
> _mtx_lock_sleep(0xe0000000159c6e90, 0xe0000001d44088a0, 0x0, 0x9ffc000000c93830, 0x232) at _mtx_lock_sleep+0xb0
> _mtx_lock_flags(0xe0000000159c6e90, 0x0, 0x9ffc000000c93830, 0x232, 0x9ffc00000097dcc0, 0x716, 0x14022d4c0) at _mtx_lock_flags+0x1a0
> trap(0x14, 0xa0000000f88fb000) at trap+0x940
> ivt_Data_TLB() at ivt_Data_TLB+0x1d0
> --- trapframe at 0xa0000000f88fb000
> crhold() at crhold+0x10

No, your problem is here.  You should never get a trap in crhold().  Something
else is wrong.

> cred_update_thread(0xe0000001d44089d0, 0xe0000000159c6dd8, 0xe0000000159c6e90, 0x9ffc000000c51cf0) at cred_update_thread+0x70
> syscall(0xe0000000159c6d98, 0x1408aa000, 0x1c, 0xe0000001d44088a0, 0x140849630, 0x0, 0x9ffc000000979a40, 0x8) at syscall+0xd0
> epc_syscall_return() at epc_syscall_return

Note that this is not a thread in vm_pageout_oom(), so this is not in the code
handling the out-of-swap condition.

-- 
John Baldwin