From owner-freebsd-stable@freebsd.org Fri Aug 28 10:35:28 2015 Return-Path: Delivered-To: freebsd-stable@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 4FEFE9C2153 for ; Fri, 28 Aug 2015 10:35:28 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC13C103A for ; Fri, 28 Aug 2015 10:35:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id t7SAZLYj044428 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 28 Aug 2015 13:35:22 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua t7SAZLYj044428 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id t7SAZLfL044426; Fri, 28 Aug 2015 13:35:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 28 Aug 2015 13:35:21 +0300 From: Konstantin Belousov To: Anton Shterenlikht Cc: freebsd-stable@freebsd.org Subject: Re: ia64 stable/10 r286316: hang at Entering /boot/kernel/kernel Message-ID: <20150828103521.GS2072@kib.kiev.ua> References: <20150827162356.GI2072@kib.kiev.ua> <201508281030.t7SAUITF085404@mech-as222.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201508281030.t7SAUITF085404@mech-as222.men.bris.ac.uk> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2015 10:35:28 -0000 On Fri, Aug 28, 2015 at 11:30:18AM +0100, Anton Shterenlikht wrote: > >From kostikbel@gmail.com Thu Aug 27 18:22:37 2015 > > > >On Thu, Aug 27, 2015 at 01:12:16PM +0100, Anton Shterenlikht wrote: > >> ia64 stable/10 r286315 boots, but > >> r286316 hangs at "Entering /boot/kernel/kernel". > >> > >> Please advise > > > >To state an obvious thing. The commit which you pointed to, changes > >the code which is not executed at that early kernel boot stage. The > >revision cannot cause the consequences you described. > > yes, I'm surprised too. > > >I think that you either have build-environment issue which randomly pops > >up, or there is some other boot-time issue which is sporadic. The only > >suggestion I have, try many boots with kernels which look either good > >or bad, I would be not surprised if statistic would be completely > >different from binary good/bad outcome. > > > >Otherwise, I do not have an idea. > > > > I doubt it's a random or a sporadic issue. > I did a bisection, as suggested, during which > I built world/kernel on 7 revisions, and when I > narrowed it down to <50, a further 4 kernels. > All kernels <=286315 boot, all kernels >= 286316 > do not. I think if it were something random, > it wouldn't be such a clear cut picture. > > What about my loader.conf: > > # cat /boot/loader.conf > zfs_load="YES" > # soft limits > kern.dfldsiz=536748032 # default soft limit for process data > kern.dflssiz=536748032 # default soft limit for stack > # hard limits > kern.maxdsiz=536748032 # hard limit for process data > kern.maxssiz=536748032 # hard limit for stack > kern.maxtsiz=536748032 # hard limit for text size > # processes may not exceed these limits. > # > > My memory: > > real memory = 8589934592 (8192 MB) > avail memory = 8387649536 (7999 MB) > > I'll try disabling all these settings in loader.conf > and see if makes a difference. > But these settings have been there for a few years > with no problems. In the initial range you mentioned, there were some changes related to the handling of the userspace stacks. But again, the problem occurs too early for a userspace-related modification to affect the outcome. Might be, try the latest stable/10 kernel with the problematic revision r286316 reversed ? This might add more points to the Marcel' note about some static relocation table processed early.