Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Apr 2012 17:06:18 -0400 (EDT)
From:      AN <andy@neu.net>
To:        freebsd-current@freebsd.org
Subject:   <jemalloc>: Conf string ends with key
Message-ID:  <alpine.BSF.2.00.1204171632500.30661@mail.neu.net>

next in thread | raw e-mail | index | archive | help
Copied from other message:

>Message: 4
>Date: Tue, 17 Apr 2012 10:42:13 +0200
>From: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de>
>Subject: <jemalloc>: Conf string ends with key
>To: "Free >> Current FreeBSD" <freebsd-current@freebsd.org>
>Message-ID: <4F8D2CE5.2030106@mail.zedat.fu-berlin.de>
Content-Type: text/plain; charset="iso-8859-1"

>Having just built world on 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r234370:
>Tue Apr 17 10:17:46 CEST 2012, gives me now a flooding of

<jemalloc>: Conf string ends with key

>on console, screens, xterms with almost everything I touch.
______________________________________________________________________________

# uname -a
<jemalloc>: Conf string ends with key
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #10 r234389: Tue Apr 17 
16:05:11 EDT 2012     root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64


I confirm I have this problem also.

I set up my system as follows:
(excerpt from kernel config)

  Debugging support.  Always need this:
#options 	KDB			# Enable kernel debugger support.
# For minimum debugger support (stable branch) use:
#options 	KDB_TRACE		# Print a stack trace for a panic.
# For full debugger support use this instead:
#options 	DDB			# Support DDB.
#options 	GDB			# Support remote GDB.
#options 	DEADLKRES		# Enable the deadlock resolver
#options 	INVARIANTS		# Enable calls of extra sanity 
checking
#options 	INVARIANT_SUPPORT	# Extra sanity checks of internal 
structures, required by INVARIANTS
#options 	WITNESS			# Enable checks to detect 
deadlocks and cycles
#options 	WITNESS_SKIPSPIN	# Don't run witness on spinlocks 
for speed
#options 	MALLOC_DEBUG_MAXZONES=8	# Separate malloc(9) zones
(All debug options turned off)

and from UPDATING i did:
ln -s aj /etc/malloc.conf

I read the latest entry in UPDATING.  Could someone please explain how to 
get back to what I had, it was working well.  The new jemalloc slows the 
system down considerably.

Thanks in advance



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1204171632500.30661>