From owner-freebsd-current@freebsd.org Mon Jun 26 12:49:02 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81B17DA9F9B for ; Mon, 26 Jun 2017 12:49:02 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5A04F77BDC for ; Mon, 26 Jun 2017 12:49:02 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 56177DA9F9A; Mon, 26 Jun 2017 12:49:02 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 558C0DA9F99 for ; Mon, 26 Jun 2017 12:49:02 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D8DA177BDB for ; Mon, 26 Jun 2017 12:49:01 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr0-x243.google.com with SMTP id 77so29214744wrb.3 for ; Mon, 26 Jun 2017 05:49:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=RVw2P5FCiKrWrVqL6IfGTGERBYroNQOji7q3gR1Cvbo=; b=l+MxZY59sg8UmaXdzQZvris8KfgzMN9xnBO+z064Oi52UhxrHlWyOKE+/HbVgWsnEa 4cSgz4kS2aSbDWZB+2OjUpYf3oBbu7thP3UQynqRrrc3AQHoQecEf2/sFc1D7M6usTIq fQPCnrMatrm9LAdjYrPi5S240zjaqRVmqyL5KBwIHeritrdsq3jRRcxGWi/wcUkquFwj 7HNZF4iIGf56TgMiDMFZx0HeZjE+F/mIMXEnjvq2bJ6UZ46H7IFDLKbSlNwhwiuWIAsA bn3oyCRqtYUrckpuCgWfb5A0f0d0xfrth80cpsmwGIaRxQ9Uc3q9Svj3hnHSOVfNGTVF awyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=RVw2P5FCiKrWrVqL6IfGTGERBYroNQOji7q3gR1Cvbo=; b=sF6hlyjY4kr0MnoiBqd1jxZHLAEk+vS4dsznhGkjJ+tcW7yMf6MT6k7CxReEwHGO7s qUZLaE3T4sgMq9rH2GE9Po1YOwN9PilXQvdB+XO+zIwr5LsnEwii55lfB97xbpEMg1wA AFuIj0O5zqxJhh19y9WYQOCWsQPEAXyFxBMq2eU3h5zO+qL/PCf/X1iRKp7jDPxFZs7j Y6UkbnnLSZvqnd0WnQi+82RGkaPhafVqhlfLmfNAeO+EnyymTP3yq3O68WoV4EOq25yO 33YZZLT4xFB7+WCKYsBjQg7Tc/kboU1kFk048rRk1GiMKbO4xC8pFFQ8PpvI4S68RkWv YcXw== X-Gm-Message-State: AKS2vOz2zJOPLlVXkYArRUDpSxVqZj++IcaQxpqaUXbPtFwAMmvH4619 Bnpm3Lla5+tZpg== X-Received: by 10.223.172.183 with SMTP id o52mr9432111wrc.1.1498481340164; Mon, 26 Jun 2017 05:49:00 -0700 (PDT) Received: from ernst.home (p4FCA6CDA.dip0.t-ipconnect.de. [79.202.108.218]) by smtp.gmail.com with ESMTPSA id t70sm32298wmd.1.2017.06.26.05.48.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 26 Jun 2017 05:48:59 -0700 (PDT) Date: Mon, 26 Jun 2017 14:48:58 +0200 From: Gary Jennejohn To: "O. Hartmann" Cc: current@freebsd.org, David Wolfskill , Boris Samorodov , Konstantin Belousov Subject: Re: r319971 -> r320351: Fatal error 'Cannot allocate red zone for initial thread' Message-ID: <20170626144858.1b799130@ernst.home> In-Reply-To: <20170626140048.6d033c7e@freyja.zeit4.iv.bundesimmobilien.de> References: <20170625120731.GE1241@albert.catwhisker.org> <20170626102942.274b42e6@freyja.zeit4.iv.bundesimmobilien.de> <20170626132608.03eab0cf@ernst.home> <20170626140048.6d033c7e@freyja.zeit4.iv.bundesimmobilien.de> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 12:49:02 -0000 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 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 ... > > > > > > [...] > > > > > > That way, I obviously can not install a world :-( > > > > > > What is wrong here? Is the problem resovable? > > > > > > > How recent was your last update? Some changes were made just a few > > hours ago to fix a stack growth problem in threads. > > Well, what do you mean by "... source is not up to date ..."? > Performing an svn update of /usr/src should suffice, shouldn't > it? If not, then ... please correct me. I think the sources > are up to date as of the moment the bug occured. > > I consider the sources up to date, it is on the latest updated > box r320355. > You did not explicitly state in the orignal post at which SVN revison your code was. Seems to me that my question was reasonable. Now it's clear that your source should have been up to date. Just for the record, I just booted a kernel from SVN r320357 which immediately resulted in a kernel panic. I had to delete everything under /usr/obj/usr/src/sys to get a working kernel. -- Gary Jennejohn