Re: panic on current during shutdown: panic: racct_adjust_resource: resource 4 usage < 0

On 20/01/2017 02:09, Larry Rosenman wrote:
> Thu Jan 19 18:03:38 CST 2017
> 
> FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #13 r311997: Sat Jan
> 14 22:35:29 CST 2017     root_at_borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER  amd64
> 
> panic: racct_adjust_resource: resource 4 usage < 0
[snip]

Very interesting.
Could you please contribute this information to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210315
?
These could be related issues.

> Unread portion of the kernel message buffer:
> <118>.
> <118>Terminated
> <118>Jan 19 17:54:50 192.168.200.11 last message repeated 13 times
> <118>Jan 19 17:54:59 borg syslogd: exiting on signal 15
> panic: racct_adjust_resource: resource 4 usage < 0
> cpuid = 1
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe2eb7c18830
> vpanic() at vpanic+0x186/frame 0xfffffe2eb7c188b0
> kassert_panic() at kassert_panic+0x126/frame 0xfffffe2eb7c18920
> racct_adjust_resource() at racct_adjust_resource+0xca/frame 0xfffffe2eb7c18950
> racct_set_locked() at racct_set_locked+0xec/frame 0xfffffe2eb7c18990
> racct_set() at racct_set+0x54/frame 0xfffffe2eb7c189c0
> vmspace_exit() at vmspace_exit+0x147/frame 0xfffffe2eb7c18a00
> exit1() at exit1+0x56b/frame 0xfffffe2eb7c18a60
> sys_sys_exit() at sys_sys_exit+0xd/frame 0xfffffe2eb7c18a70
> amd64_syscall() at amd64_syscall+0x2ea/frame 0xfffffe2eb7c18bf0
> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe2eb7c18bf0
> --- syscall (1, FreeBSD ELF64, sys_sys_exit), rip = 0x8025c916a, rsp =
> 0x7fffffffebd8, rbp = 0x7fffffffebf0 ---
> Uptime: 4d4h19m38s
> Dumping 12670 out of 64463 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
[snip]
> __curthread () at ./machine/pcpu.h:222
> 222             __asm("movq %%gs:%1,%0" : "=r" (td)
> (kgdb) #0  __curthread () at ./machine/pcpu.h:222
> #1  doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:318
> #2  0xffffffff80a2ffb5 in kern_reboot (howto=<optimized out>)
>     at /usr/src/sys/kern/kern_shutdown.c:386
> #3  0xffffffff80a30590 in vpanic (fmt=<optimized out>, ap=0xfffffe2eb7c188f0)
>     at /usr/src/sys/kern/kern_shutdown.c:779
> #4  0xffffffff80a303c6 in kassert_panic (
>     fmt=0xffffffff813ee4fb "%s: resource %d usage < 0")
>     at /usr/src/sys/kern/kern_shutdown.c:669
> #5  0xffffffff80a21eca in racct_adjust_resource (racct=0xfffff8001b7c00d0,
>     resource=4, amount=<optimized out>) at /usr/src/sys/kern/kern_racct.c:528
> #6  0xffffffff80a21acc in racct_set_locked (p=0xfffff80055f41528,
>     resource=<optimized out>, amount=0, force=0)
>     at /usr/src/sys/kern/kern_racct.c:718
> #7  0xffffffff80a21994 in racct_set (p=0xfffff80055f41528, resource=4,
>     amount=0) at /usr/src/sys/kern/kern_racct.c:741
> #8  0xffffffff80d0f8e7 in vmspace_container_reset (p=<optimized out>)
>     at /usr/src/sys/vm/vm_map.c:311
> #9  vmspace_exit (td=<optimized out>) at /usr/src/sys/vm/vm_map.c:420
> #10 0xffffffff809f01ab in exit1 (td=<optimized out>, rval=<optimized out>,
>     signo=<optimized out>) at /usr/src/sys/kern/kern_exit.c:399
> #11 0xffffffff809efc3d in sys_sys_exit (td=<unavailable>, uap=<optimized out>)
>     at /usr/src/sys/kern/kern_exit.c:178
> #12 0xffffffff80e9a98a in syscallenter (td=0xfffff80055de6000,
>     sa=<optimized out>)
>     at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:135
> #13 amd64_syscall (td=0xfffff80055de6000, traced=0)
>     at /usr/src/sys/amd64/amd64/trap.c:902
> #14 <signal handler called>
> Can't read data for section '.eh_frame' in file '/'
> (kgdb)
> 
> vmcore IS available.
> 
> 


-- 
Andriy Gapon