r319971 -> r320351: Fatal error 'Cannot allocate red zone for initial thread'

David Wolfskill david at catwhisker.org
Mon Jun 26 11:28:49 UTC 2017


On Mon, Jun 26, 2017 at 10:29:47AM +0200, O. Hartmann wrote:
> ...
> 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 ...

My head update this morning was from r320324 to r320353; I did not
encounter the above.  (I did, however, encounter an inability to load
tmpfs.ko; I will describe that issue in a separate thread.)

> ...

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
Trump (et al.): Hiding information doesn't prove its falsity.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20170626/00db6c25/attachment.sig>


More information about the freebsd-current mailing list