From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 15:24:43 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D4BABC5; Thu, 8 Jan 2015 15:24:43 +0000 (UTC) Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8FCADFF; Thu, 8 Jan 2015 15:24:42 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id v10so11773235pde.1; Thu, 08 Jan 2015 07:24:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=ZeY1jLxxJkWyCzCOYs75HOauHu7IuP9wVLZrd9XmT5M=; b=a7vxtX4wnWPATRuJgNHAvYhe2sz7zkaLwaYTT6FG93oy2MBFnk5sIsUtWG4nVfGz0Y gZjLle2BmYrptmvuTdeHNRoxbqM6/0IQzA1QSXBiSbYoaTVpEt3tUPSwGh1655hJIXXh NRmtRMK30J/tdSizslAX7GpNsPfmstNpcSsfxSQCCuQof6iKHymD1D5DGMN6RrIplQU2 +uI1TyxMCjmyWmllPEUCAKkuvE74tsTbEWfQJEHoN3xecBgBNSkW9USfoxCuPQp0DGJx 2hA5nR/7EEtNaP9hBILXceCPGDL5mIGF6gNZTcXN9lJFR4cOUPZlgle1jXqOfCAR03b0 9WiQ== X-Received: by 10.66.121.132 with SMTP id lk4mr15999559pab.33.1420730682422; Thu, 08 Jan 2015 07:24:42 -0800 (PST) Received: from raichu ([198.244.104.6]) by mx.google.com with ESMTPSA id gk2sm4756132pbc.14.2015.01.08.07.24.40 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jan 2015 07:24:41 -0800 (PST) Sender: Mark Johnston Date: Thu, 8 Jan 2015 07:24:39 -0800 From: Mark Johnston To: "Bjoern A. Zeeb" Subject: Re: "*** [kernel.debug] Error code 139"? Message-ID: <20150108152439.GC32884@raichu> References: <20150107135756.GC14822@albert.catwhisker.org> <3C59182B-D747-4F33-9AED-6DED638596E7@lists.zabbadoz.net> <20150108133756.GA32884@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Ed Maste , Dimitry Andric , "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Jan 2015 15:24:43 -0000 On Thu, Jan 08, 2015 at 02:06:16PM +0000, Bjoern A. Zeeb wrote: > > > On 08 Jan 2015, at 13:37 , markj@FreeBSD.org wrote: > > > > On Thu, Jan 08, 2015 at 01:40:11PM +0100, Dimitry Andric wrote: > >> On 08 Jan 2015, at 13:09, Bjoern A. Zeeb wrote: > >>> > >>>> On 07 Jan 2015, at 15:02 , Bjoern A. Zeeb wrote: > >>>>> On 07 Jan 2015, at 14:13 , Ed Maste wrote: > >>>>> On 7 January 2015 at 08:57, David Wolfskill wrote: > >>>>>> --- kernel.debug --- > >>>>>> linking kernel.debug > >>>>>> ctfmerge -L VERSION -g -o kernel.debug ... > >>>>>> Segmentation fault (core dumped) > >>>>>> *** [kernel.debug] Error code 139 > >>>>> ... > >>>>>> I'm mostly wondering what "Error code 139" is intended to mean.... :-} > >>>>> > >>>>> It's the way termination due to a signal is reported. The exit status > >>>>> is 128 + the signal number and SIGSEGV = 11. > >>>> > >>>> I did see it twice last night while doing HEAD builds, and i386.GENERIC only. For later builds it was just gone again. Not sure if anyone wants to figure out what was special about the two SVN revisions. For me it was a cross-build from amd64 as part of make universe. > >>> > >>> Ok, this continues; I have since seen it four more times. Still i386.GENERIC only; none of the LINT kernels or other architectures. > >>> > >>> Can someone please investigate what triggers this? > >> > >> Looks like a stack overflow, cause unknown as of yet: > > > > I'll try to reproduce this, but perhaps try reverting r274569? r274565 > > and r274564 could also potentially be the cause of this, but r274569 > > would be my first guess. > > It only started 2 nights ago and we are both doing daily builds. Unlikely that stuff from November would do it oh so suddenly. > > It’s hard to exactly narrow it down as there was a lot of other breakage in the tree but I know that r276729 finished a full universe and I hadn’t noticed the problem before. So I would almost assume it was something after that (but obviously it could be a combination of things). Ok, I was able to reproduce the crash by cross-compiling i386 on amd64. Reverting r274569 made it go away for me. I'm going to try a few more times to see if it's consistent. -Mark