From owner-freebsd-current@FreeBSD.ORG Fri Jan 9 01:57:10 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 B7E72220; Fri, 9 Jan 2015 01:57:10 +0000 (UTC) Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (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 55BF2B6E; Fri, 9 Jan 2015 01:57:10 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id q59so5579672wes.10; Thu, 08 Jan 2015 17:57:08 -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:content-transfer-encoding; bh=v8F7cT3gFz/B725DVgQN7ByuZSvQNR54+f9MFaYI42M=; b=Lf1rE/hUE7pLKTJFKs8rBkhIqDY7Uauhl3fhsAfWcWblFSOEJgfNDKU+Fsy0aKLhzc tp17lpRXwdhV/Ou8y7w+wv0ziNDjVA36HosBBbPYmleFJobt1Ngkm8RwS/+elqx8WmFn 1o/vqwHJtR0ezC7EfoZRoNZrfgjF/y7vM+j3PiJqg0b8Ijg/DhrPrxmfo+VMDSH3wJbo F8cVLZfWKkqgbz8/2RaEDSkd+6lxR7v1mNQ3X+qg3fgDc0wSg7S2k+t5gRbd5dEuWIYi JkyaBbm0Hcb+zS8TnXFFqCvNPG5XBNuFOkNRbXi65ygkt6ILrHELU+RaVQh9Xyhv6RI5 oStQ== MIME-Version: 1.0 X-Received: by 10.195.13.104 with SMTP id ex8mr27480184wjd.12.1420768628821; Thu, 08 Jan 2015 17:57:08 -0800 (PST) Sender: markjdb@gmail.com Received: by 10.194.81.106 with HTTP; Thu, 8 Jan 2015 17:57:08 -0800 (PST) In-Reply-To: References: <20150107135756.GC14822@albert.catwhisker.org> <3C59182B-D747-4F33-9AED-6DED638596E7@lists.zabbadoz.net> <20150108133756.GA32884@raichu> <20150108152439.GC32884@raichu> <20150108184616.GD32884@raichu> Date: Thu, 8 Jan 2015 17:57:08 -0800 X-Google-Sender-Auth: DLSpPsemduwNXqn_b8w9w0-oo98 Message-ID: Subject: Re: "*** [kernel.debug] Error code 139"? From: Mark Johnston To: "Bjoern A. Zeeb" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Ed Maste , Mark Johnston , Dimitry Andric , FreeBSD CURRENT 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: Fri, 09 Jan 2015 01:57:10 -0000 On Thu, Jan 8, 2015 at 5:42 PM, Bjoern A. Zeeb wrote: > >> On 08 Jan 2015, at 18:46 , Mark Johnston wrote: >> >> On Thu, Jan 08, 2015 at 07:27:10PM +0100, Dimitry Andric wrote: >>> On 08 Jan 2015, at 16:24, Mark Johnston wrote: >>>> >>>> On Thu, Jan 08, 2015 at 02:06:16PM +0000, Bjoern A. Zeeb wrote: >>> ... >>>>> It only started 2 nights ago and we are both doing daily builds. Unl= ikely that stuff from November would do it oh so suddenly. >>>>> >>>>> It=E2=80=99s hard to exactly narrow it down as there was a lot of oth= er breakage in the tree but I know that r276729 finished a full universe an= d I hadn=E2=80=99t noticed the problem before. So I would almost assume it= was something after that (but obviously it could be a combination of thing= s). >>>> >>>> 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. >>> >>> Same here, reverting r274569 makes it work again. >> >> I've reverted it in r276848. > > So I may revert this reverted changed locally again and see, as the unive= rse before your =E2=80=9Cbackout=E2=80=9D went through smoothly; I=E2=80= =99d rather understand the root-cause that triggers this then having someth= ing I don=E2=80=99t quite understand why it started to happen 8 weeks after= a change=E2=80=A6 Me too. Apparently my change was interacting badly with the type graph of recent i386 GENERIC kernels. I don't think that r274569 is fundamentally incorrect, but I clearly missed something, and didn't have the cycles to investigate right away (ctfmerge can be quite time-consuming to debug in my experience). Given that the change was breaking the build, I opted to revert it quickly. This weekend, I'll try to figure out what actually happened.