[Bug 233414] [PowerPC64] OPTIONS DEBUG_MEMGUARD results in unbootable kernel
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Dec 12 12:33:02 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233414
--- Comment #9 from Leandro Lupori <leandro.lupori at gmail.com> ---
(In reply to Mark Johnston from comment #8)
With this new patch I was able to use memguard to guard the '128 Bucket' zone
for more than an hour of package building. Unfortunately, later I got this
panic:
panic: _mtx_lock_sleep: recursed on non-recursive mutex memguard arena @
/usr/src/sys/kern/subr_vmem.c:1184
cpuid = 40
time = 1544566934
KDB: stack backtrace:
0xe0000001dbb4e250: at .kdb_backtrace+0x5c
0xe0000001dbb4e380: at .vpanic+0x1b4
0xe0000001dbb4e440: at .panic+0x38
0xe0000001dbb4e4d0: at .__mtx_lock_sleep+0x178
0xe0000001dbb4e5c0: at .__mtx_lock_flags+0x160
0xe0000001dbb4e670: at .vmem_xalloc+0x2d0
0xe0000001dbb4e7b0: at .memguard_alloc+0xdc
0xe0000001dbb4e890: at .uma_zalloc_arg+0xe0
0xe0000001dbb4e950: at .uma_zalloc_pcpu_arg+0x178
0xe0000001dbb4e9f0: at .uma_zfree_arg+0x4c4
0xe0000001dbb4eaa0: at .uma_zfree_pcpu_arg+0xc8
0xe0000001dbb4eb30: at .uma_zalloc_arg+0x3c0
0xe0000001dbb4ebf0: at .uma_zalloc_pcpu_arg+0x178
0xe0000001dbb4ec90: at .uma_zalloc_arg+0x5a8
0xe0000001dbb4ed50: at .vmem_size+0x1400
0xe0000001dbb4ee10: at .vmem_xalloc+0x320
0xe0000001dbb4ef50: at .memguard_alloc+0xdc
0xe0000001dbb4f030: at .uma_zalloc_arg+0xe0
0xe0000001dbb4f0f0: at .uma_zalloc_pcpu_arg+0x178
0xe0000001dbb4f190: at .uma_zfree_arg+0x4c4
0xe0000001dbb4f240: at ._fdrop+0xa8
0xe0000001dbb4f2d0: at .closef+0x27c
0xe0000001dbb4f3d0: at .fdsetugidsafety+0x35c
0xe0000001dbb4f480: at .kern_close+0x1e8
0xe0000001dbb4f530: at .sys_close+0x18
0xe0000001dbb4f5b0: at .trap+0x664
0xe0000001dbb4f770: at .powerpc_interrupt+0x290
0xe0000001dbb4f810: user SC trap by 0x104829e8: srr1=0x900000000000f032
r1=0x3fffffffffff3aa0 cr=0x24824042 xer=0x20000000 ctr=0x103b9910
r2=0x10671858
KDB: enter: panic
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ppc
mailing list