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

On 06/29/17 13:16, Hans Petter Selasky wrote: On 06/26/17 15:03, O. Hartmann wrote: On Mon, 26 Jun 2017 14:48:58 +0200 Gary Jennejohn wrote: On Mon, 26 Jun 2017 14:00:48 +0200 "O. Hartmann" wrote: On Mon, 26 Jun 2017 13:26:08 +0200 Gary

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

On 06/26/17 15:03, O. Hartmann wrote: On Mon, 26 Jun 2017 14:48:58 +0200 Gary Jennejohn wrote: On Mon, 26 Jun 2017 14:00:48 +0200 "O. Hartmann" wrote: On Mon, 26 Jun 2017 13:26:08 +0200 Gary Jennejohn wrote: On Mon,

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

On Mon, 26 Jun 2017 12:22:50 +0100 Steven Hartland wrote: > Is this related to kib's additional fix over the weekend? > > https://svnweb.freebsd.org/changeset/base/320344 > > Regards > Steve > > On 26/06/2017 09:29, O. Hartmann wrote: > > Over the past week

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

On Mon, 26 Jun 2017 14:48:58 +0200 Gary Jennejohn wrote: > On Mon, 26 Jun 2017 14:00:48 +0200 > "O. Hartmann" wrote: > > > On Mon, 26 Jun 2017 13:26:08 +0200 > > Gary Jennejohn wrote: > > > > > On Mon, 26 Jun 2017 10:29:47

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

On Mon, 26 Jun 2017 14:00:48 +0200 "O. Hartmann" wrote: > On Mon, 26 Jun 2017 13:26:08 +0200 > Gary Jennejohn wrote: > > > On Mon, 26 Jun 2017 10:29:47 +0200 > > "O. Hartmann" wrote: > > > > > Over the past week we did

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

On Mon, 26 Jun 2017 13:26:08 +0200 Gary Jennejohn wrote: > On Mon, 26 Jun 2017 10:29:47 +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

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

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

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

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

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

On Mon, 26 Jun 2017 12:22+0100, Steven Hartland wrote: > Is this related to kib's additional fix over the weekend? > > https://svnweb.freebsd.org/changeset/base/320344 Attempting to run r320348 with no patches applied proved unfruitful earlier today. I had partial success the weekend building

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

On Mon, 26 Jun 2017 10:29:47 +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

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

Is this related to kib's additional fix over the weekend? https://svnweb.freebsd.org/changeset/base/320344 Regards Steve On 26/06/2017 09:29, 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