Date: Thu, 8 Jan 2015 06:43:37 -0800 From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Re: "*** [kernel.debug] Error code 139"? Message-ID: <20150108144337.GT14822@albert.catwhisker.org> In-Reply-To: <EE2CBAF1-5C3D-43CE-9926-8E416AAAA490@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>
next in thread | previous in thread | raw e-mail | index | archive | help
--iibEmBFpDzSsDyxm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 08, 2015 at 02:06:16PM +0000, Bjoern A. Zeeb wrote: > ... > >>> Ok, this continues; I have since seen it four more times. Still i38= 6.GENERIC only; none of the LINT kernels or other architectures. > >>>=20 > >>> Can someone please investigate what triggers this? > >>=20 > >> Looks like a stack overflow, cause unknown as of yet: > >=20 > > 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. >=20 > It only started 2 nights ago and we are both doing daily builds. Unlikel= y that stuff from November would do it oh so suddenly. >=20 > 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 n= oticed the problem before. So I would almost assume it was something after= that (but obviously it could be a combination of things). > ... I'm only building world & kernel (vs. universe), and doing it natively on head/i386. You may see my history of (eventually, in a few cases) succssful builds for the machine & environment in question at <http://www.catwhisker.org/~david/FreeBSD/history/freebeast_i386_11.txt>. =20 While I did see an issue (that prevented a successful build) on 06 Jan and 01 Jan, the other daily builds in the last couple of weeks were fairly uneventful -- save for yesterday (07 Jan), where I encountered the SIGSEGV in ctfmerge (though, as I noted at the time, a re-build didn't experience it). Peace, david --=20 David H. Wolfskill david@catwhisker.org Actions have consequences ... as do inactions. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --iibEmBFpDzSsDyxm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUrpeZXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4 QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk7QeMP/jk0j4FbOp6qphP0x3VmaeUc cE1UUc7xDHDfzKe+w4UEMqZFAiEj0YbslJUJvRexSl4rW5k5ObI+tFLdvqR2JzQ9 MyOEY/H+pPPYCrKIAHkQZ82WmH+cyAQjlRVqvhOTncUgxHm9Cw6vrNd9nxTfgSg9 U3s945UqQseddOE6nupxM44TTpGl3NYNNtUY9F9M27BemCqm/gXKrWrcoaq4YBZD 8u3Uy11RkxeDNYxYIxBc/uSb4+TABv2RMXPCZBIZ494/hiuCO1O03mMSFfD/bDyx NIvV2En/aL9ktXN5Va5fXtZkvnWLQP0QzHrqfk2pKHuQt9Knd9iSbExqUJAwU8xG KuqwbMSetlXrBT7IPMpU5XQtNRBapTgmVahCpT7k4T0gbprdh2L17OqUm25Zv7LP e5GDcHYiyPlUeJDXY5CzxFzn0HvikZclAqPcvubVn4iH1i+JWwihkfglpdc6GC2v kTufteQsAJUwtCGB4Y4JNpTbNZJydnfrFygZb4WXTph/MldgNuo1Z2vZUEfBGibb YxwwGOF5GghdF4l0zZqA3uOWeogSoNK3VUOI8/wMH05VLyTktWqcJgqXtxGPi/31 WsAG/wHdAvTh4GZtYPZyTggkLqSC5IQkIH03huyTg74EM7OpcxHVNSrnWhnJBC7L Jx9sfv5umUxtwBlOnTkJ =oKnv -----END PGP SIGNATURE----- --iibEmBFpDzSsDyxm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150108144337.GT14822>