From owner-freebsd-current@FreeBSD.ORG Tue Apr 17 21:06:28 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C868106566B for ; Tue, 17 Apr 2012 21:06:28 +0000 (UTC) (envelope-from andy@neu.net) Received: from mail.neu.net (unknown [IPv6:2607:fc50:0:d300:216:3eff:fe54:f1c6]) by mx1.freebsd.org (Postfix) with ESMTP id 0F6048FC14 for ; Tue, 17 Apr 2012 21:06:27 +0000 (UTC) Received: from neu.net (neu.net [199.48.129.194]) by mail.neu.net (8.14.5/8.14.5) with ESMTP id q3HL6IrR030745 for ; Tue, 17 Apr 2012 17:06:23 -0400 (EDT) (envelope-from andy@neu.net) Date: Tue, 17 Apr 2012 17:06:18 -0400 (EDT) From: AN To: freebsd-current@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-0.0 required=5.0 tests=T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.neu.net Subject: : Conf string ends with key X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2012 21:06:28 -0000 Copied from other message: >Message: 4 >Date: Tue, 17 Apr 2012 10:42:13 +0200 >From: "O. Hartmann" >Subject: : Conf string ends with key >To: "Free >> Current FreeBSD" >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 : Conf string ends with key >on console, screens, xterms with almost everything I touch. ______________________________________________________________________________ # uname -a : 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