Date: Mon, 26 Jun 2017 14:44:10 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: "O. Hartmann" <o.hartmann@walstatt.org> Cc: current@freebsd.org, David Wolfskill <david@catwhisker.org>, Boris Samorodov <bsam@passap.ru> Subject: Re: r319971 -> r320351: Fatal error 'Cannot allocate red zone for initial thread' Message-ID: <20170626114410.GN3437@kib.kiev.ua> In-Reply-To: <20170626102942.274b42e6@freyja.zeit4.iv.bundesimmobilien.de> References: <20170625120731.GE1241@albert.catwhisker.org> <20170626102942.274b42e6@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 26, 2017 at 10:29:47AM +0200, O. Hartmann wrote: > Over the past week we did not update several 12-CURRENT running development > hosts, so today is the first day of performing this task. > > First I hit the very same problem David Wolfskill reported earlier, a fatal > trap 12, but fowllowing the thread, I did as advised: removing /usr/obj > completely (we use filemon/WITH_META_MODE=YES all over the place) and > recompiling world and kernel. > > Since tag 20170617 in /usr/src/UPDATING referred to the INO64 update and the > INO64 update hasn't performed so far starting from r319971, I installed the > kernel, rebooted the box in single user mode (this time smoothly), did a > mergemaster and tried to do "make installworld" - but the box instantanously > bails out: > > [...] > Fatal error 'Cannot allocate red zone for initial thread' at line 392 in > file /usr/src/lib/libthread/thr_init.c > pid 60 (cc) uid0: exited on signal 6 ... It is strange that cc is executed during installworld. Anyway, show ktrace of the failure.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170626114410.GN3437>