From owner-freebsd-current@FreeBSD.ORG Thu Dec 26 20:43:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 97659F20 for ; Thu, 26 Dec 2013 20:43:41 +0000 (UTC) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4D4D610B8 for ; Thu, 26 Dec 2013 20:43:41 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id fa1so8540565pad.24 for ; Thu, 26 Dec 2013 12:43:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=onR8rAGuFhoYtlVFiqUenroUMeZKY/Rxhtl5SaGr0jo=; b=co9H9U8xxuXr3/a4mDivSvKQ7mv3XyNvwbQEV7wXo3s4Klxgdv1Vuk0At7RBhDqxeB 3auODLpcQFSaWEPFZEgCnz6qzvYnam1fclnA3I8ZCOVfPhMpwVz+FzCzc51PxZFb7dcB 14FAtHvcIILYWGScDF12LdfKnaegRY1i05NS0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=onR8rAGuFhoYtlVFiqUenroUMeZKY/Rxhtl5SaGr0jo=; b=kasborzM+RHiNPBrowfyA8KLwMOF06LaiMg/mTrvAzesQq/lSMtMR72s03QCFqhGGX UEZWWb0SsquDzynLwXZlp977TxRqtWF1WJqSKq3mh2KEOynISpLesIlzJZOqxcVdwPqw ObjU8plklRordPXkZsGKLQ7DrWocDFwZkNDDpabJIm9ilmikRprJ21sujCKPDNH/wFd0 XwxdRbExDiNVKtTMiZZP1JT4W/jwC/YHgNgCdWAy3awEIuIqzjV88SD+FmqBZvmETNbb 1ejtzgNAZp5PXTKGhmLodxyZu4ZN30m2vF8pQ1HYRd3bGezZ2+wdknNlbsqw26HSHvUS 1TpQ== X-Gm-Message-State: ALoCoQlEmH/jcA2c6QijuVpnnwn1yykHSvaUD7RYl/LWPTig7UtMREqUFkx01SJ+xNWWeQLV8rMj MIME-Version: 1.0 X-Received: by 10.68.193.233 with SMTP id hr9mr46841460pbc.26.1388090620835; Thu, 26 Dec 2013 12:43:40 -0800 (PST) Received: by 10.66.162.3 with HTTP; Thu, 26 Dec 2013 12:43:40 -0800 (PST) In-Reply-To: <20131226200144.GP59496@kib.kiev.ua> References: <52BC1B41.2060900@FreeBSD.org> <20131226200144.GP59496@kib.kiev.ua> Date: Thu, 26 Dec 2013 12:43:40 -0800 Message-ID: Subject: Re: latest openjdk7 triggers kernel panic From: Peter Wemm To: Konstantin Belousov Content-Type: text/plain; charset=ISO-8859-1 Cc: Antoine Brodin , Marcel Moolenaar , Alan Cox , Andriy Gapon , FreeBSD Current , freebsd-java@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Thu, 26 Dec 2013 20:43:41 -0000 On Thu, Dec 26, 2013 at 12:01 PM, Konstantin Belousov wrote: > On Thu, Dec 26, 2013 at 07:51:45PM +0100, Antoine Brodin wrote: >> On Thu, Dec 26, 2013 at 7:33 PM, Peter Wemm wrote: >> > On Thu, Dec 26, 2013 at 7:39 AM, Antoine Brodin wrote: >> >> On Thu, Dec 26, 2013 at 1:04 PM, Andriy Gapon wrote: >> > ... >> >> Hello, >> >> >> >> FWIW, I had a similar panic today on 9.2-RELEASE with a GENERIC kernel: >> >> panic: Bad entry start/end for new stack entry >> >> cpuid = 1 >> >> KDB: stack backtrace: >> >> #0 0xffffffff80947986 at kdb_backtrace+0x66 >> >> #1 0xffffffff8090d9ae at panic+0x1ce >> >> #2 0xffffffff80b81314 at vm_map_stack+0x274 >> >> #3 0xffffffff80b83584 at vm_mmap+0x674 >> >> #4 0xffffffff80b83d2f at sys_mmap+0x1cf >> >> #5 0xffffffff80cf187a at amd64_syscall+0x5ea >> >> #6 0xffffffff80cdbff7 at Xfast_syscall+0xf7 >> >> >> >> It looks like the box was compiling java related ports (java/jaxen and >> >> devel/antlr) when it panic'ed. >> > >> > This is troubling. I'm wondering what's changed and why we haven't >> > seen this before. > Well, if MAP_STACK was started used only with update, or the condition > for coalescing only holds due to changes in the update, this is not > much strange. openjdk7 doesn't appear to use MAP_STACK itself. The mmap(.. MAP_STACK..) caller looks like it is libthr. The only odd thing that stood with a quick browse of the code was that openjdk tinkers with mprotect() for "stack guard pages". These will presumably be right on the boundaries of the stacks. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV