From owner-freebsd-current@FreeBSD.ORG Thu Dec 26 18:51:48 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 7BF737CE; Thu, 26 Dec 2013 18:51:48 +0000 (UTC) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7958318D3; Thu, 26 Dec 2013 18:51:47 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id y10so11606873wgg.4 for ; Thu, 26 Dec 2013 10:51:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Zre8wczz7Cjo2z/gHZ/nYWASQUjShbmGolkLvJmfxYc=; b=qLV6jFq+rOQM2+lcQqXSopQCGScEbByIxE5Y8ynhAPWjwLr5hghDmF+VWZkJ87+gvQ dNPusmbZI5mVEqBebfjIzj0/Dk6wzJmmSicwIZ4Bk3j63A3nYN5/Dqw67FB9NvsOgCHc n5cmYQltjBC6h7EP7atphJYQBNo7VDQf3irDax3MT6nNh5OeX4p47MSA3qgIOvvZLAJJ hyeKa+pacsj7wJERl4KUp7DJ+pUos9fjvA2PtL8nTWyyX/X8ZEqmVjeZeCKLKZuAXSfs sXcT17sYhLIYVyGSrkm3/FltPPcnhlx9rUpybBXt4GNScyCLzkA86BGiTO6uO+8ZY94B bJnA== MIME-Version: 1.0 X-Received: by 10.180.205.138 with SMTP id lg10mr29572567wic.30.1388083906010; Thu, 26 Dec 2013 10:51:46 -0800 (PST) Sender: antoine.brodin.freebsd@gmail.com Received: by 10.194.33.37 with HTTP; Thu, 26 Dec 2013 10:51:45 -0800 (PST) In-Reply-To: References: <52BC1B41.2060900@FreeBSD.org> Date: Thu, 26 Dec 2013 19:51:45 +0100 X-Google-Sender-Auth: IK8IS3hZxbtIF2GuvzJxT7fUTWk Message-ID: Subject: Re: latest openjdk7 triggers kernel panic From: Antoine Brodin To: Peter Wemm Content-Type: text/plain; charset=ISO-8859-1 Cc: Alan Cox , Marcel Moolenaar , FreeBSD Current , Andriy Gapon , 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 18:51:48 -0000 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. > > Just so I'm clear, you're building 9.2 ports on a 9.2-REL kernel, > right? and not something like building 9.2-REL ports inside a jail on > a 10.x or 11.x host? 10.x / 11.x are not involved and you're seeing > this? This is 9.2-REL host and kernel. The only thing "new" is the ports tree, ports tree from 20 december didn't make the box panic while ports tree from 26 december does. (and there was an openjdk update between) Cheers, Antoine