Date: Thu, 8 Jan 2015 17:57:08 -0800 From: Mark Johnston <markj@freebsd.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: Ed Maste <emaste@freebsd.org>, Mark Johnston <markj@freebsd.org>, Dimitry Andric <dim@freebsd.org>, FreeBSD CURRENT <current@freebsd.org> Subject: Re: "*** [kernel.debug] Error code 139"? Message-ID: <CAMw1wOwLZco-fXV26VPtia-vOhNZo3wPvDaz-=8P_cWPAxmE5Q@mail.gmail.com> In-Reply-To: <A1CCD0A3-2E5E-413D-921E-CB583528A954@lists.zabbadoz.net> References: <20150107135756.GC14822@albert.catwhisker.org> <CAPyFy2CHDc%2BskpJzrVgborDYgUK3CcPVcGeJiKOfo9UqnDfrfw@mail.gmail.com> <A27C6742-BCD7-43E5-9ED1-D34A6BF0C8E4@lists.zabbadoz.net> <3C59182B-D747-4F33-9AED-6DED638596E7@lists.zabbadoz.net> <A01756B6-1B4E-48D2-BFF9-B7B29F4AA337@FreeBSD.org> <20150108133756.GA32884@raichu> <EE2CBAF1-5C3D-43CE-9926-8E416AAAA490@lists.zabbadoz.net> <20150108152439.GC32884@raichu> <E56A4767-9A2B-4A0D-9565-4AE2A29B33A5@FreeBSD.org> <20150108184616.GD32884@raichu> <A1CCD0A3-2E5E-413D-921E-CB583528A954@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 8, 2015 at 5:42 PM, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote: > >> On 08 Jan 2015, at 18:46 , Mark Johnston <markj@freebsd.org> wrote: >> >> On Thu, Jan 08, 2015 at 07:27:10PM +0100, Dimitry Andric wrote: >>> On 08 Jan 2015, at 16:24, Mark Johnston <markj@freebsd.org> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMw1wOwLZco-fXV26VPtia-vOhNZo3wPvDaz-=8P_cWPAxmE5Q>