From owner-freebsd-current@FreeBSD.ORG Fri Jul 8 11:47:09 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57FA2106566B; Fri, 8 Jul 2011 11:47:09 +0000 (UTC) (envelope-from matpockuh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0A0738FC08; Fri, 8 Jul 2011 11:47:08 +0000 (UTC) Received: by pzk27 with SMTP id 27so1862568pzk.13 for ; Fri, 08 Jul 2011 04:47:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+fT/Y8FcEJNH8lg8q4bfLG50UBLgD5zhwHDrcC66bJc=; b=oVdvyZfJxSKLdHgydP32ne45JySqOUvvwHFKyXqU1oqHR0UqJ152huZrnHEVNg8glJ S0bBT3VeaEEgnj7M1kBW6hFssnRs+fL2rJ0yB8H1SjYEXj3bXsauOidpcJ1QkYAfCcRv 1U+bkHZs0iC+QyvQrx4YSbnpDv0Ha3Gql/RTY= MIME-Version: 1.0 Received: by 10.68.36.129 with SMTP id q1mr2746908pbj.374.1310125628421; Fri, 08 Jul 2011 04:47:08 -0700 (PDT) Received: by 10.68.62.97 with HTTP; Fri, 8 Jul 2011 04:47:08 -0700 (PDT) In-Reply-To: <20110707154958.GK14797@alchemy.franken.de> References: <20110629134140.GF14797@alchemy.franken.de> <4E0B8F25.7090107@FreeBSD.org> <20110707100446.GJ14797@alchemy.franken.de> <20110707154958.GK14797@alchemy.franken.de> Date: Fri, 8 Jul 2011 15:47:08 +0400 Message-ID: From: KOT MATPOCKuH To: Marius Strobl Content-Type: text/plain; charset=ISO-8859-1 Cc: Doug Barton , FreeBSD Current Subject: Re: named crashes on assertion in rbtdb.c on sparc64/SMP 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: Fri, 08 Jul 2011 11:47:09 -0000 2011/7/7 Marius Strobl : > That's not the patch I was referring to. I did a second one which just > entirely disables the use of atomic operations on sparc64: > http://people.freebsd.org/~marius/sparc64_isc_disable_atomic.diff Omg. I'm sorry. I applied this patch and restarted named, but named crashed immediatly after start: 08-Jul-2011 15:29:54.631 found 2 CPUs, using 2 worker threads 08-Jul-2011 15:29:54.633 using up to 4096 sockets Segmentation fault (core dumped) core's backtrace: #0 0x0000000040953ba8 in __sparc_utrap_install () from /lib/libc.so.7 (gdb) bt #0 0x0000000040953ba8 in __sparc_utrap_install () from /lib/libc.so.7 #1 0x0000000040953ccc in __sparc_utrap_install () from /lib/libc.so.7 #2 0x0000000040953f70 in __sparc_utrap_install () from /lib/libc.so.7 #3 0x00000000409537ac in __sparc_utrap_install () from /lib/libc.so.7 #4 0x00000000407c2d54 in pthread_mutex_lock () from /lib/libthr.so.3 #5 0x0000000000228dcc in ?? () Previous frame identical to this frame (corrupt stack?) Could this be a sign to a problem in libthr? PS. Also one month ago I got a problems with another multithreaded application from ports (www/oops). oops was crashed with stack's backtrace: #0 0x0000000040d8fc88 in __sparc_utrap_install () from /lib/libc.so.7 #1 0x0000000040d8fdac in __sparc_utrap_install () from /lib/libc.so.7 #2 0x0000000040d90050 in __sparc_utrap_install () from /lib/libc.so.7 #3 0x0000000040d8f88c in __sparc_utrap_install () from /lib/libc.so.7 #4 0x0000000040d64044 in _malloc_thread_cleanup () from /lib/libc.so.7 #5 0x0000000040c039b8 in fork () from /lib/libthr.so.3 #6 0x0000000040c03d38 in fork () from /lib/libthr.so.3 #7 0x0000000040c03f50 in pthread_exit () from /lib/libthr.so.3 #8 0x0000000040c04414 in pthread_detach () from /lib/libthr.so.3 #9 0x0000000040c04710 in pthread_create () from /lib/libthr.so.3 But on yesterday's world's build oops works properly. I think it may be related to r223228 (?) Or I incorrectly analyze stack for multithreaded applications? -- MATPOCKuH