From owner-freebsd-mips@freebsd.org Tue Mar 6 10:41:02 2018 Return-Path: Delivered-To: freebsd-mips@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF492F48CE2 for ; Tue, 6 Mar 2018 10:41:01 +0000 (UTC) (envelope-from wolfgang@lyxys.ka.sub.org) Received: from saturn.lyxys.ka.sub.org (saturn.lyxys.ka.sub.org [217.29.35.151]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 552F76FAF8 for ; Tue, 6 Mar 2018 10:41:00 +0000 (UTC) (envelope-from wolfgang@lyxys.ka.sub.org) Received: from juno.lyxys.ka.sub.org (juno.lyx [IPv6:fd2a:89ca:7d54:0:240:caff:fe92:4f47]) by saturn.lyxys.ka.sub.org (8.15.2/8.15.2) with ESMTPS id w26AeiBS030990 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=FAIL) for ; Tue, 6 Mar 2018 11:40:45 +0100 (CET) (envelope-from wolfgang@lyxys.ka.sub.org) Received: from juno.lyxys.ka.sub.org (localhost [127.0.0.1]) by juno.lyxys.ka.sub.org (8.15.2/8.15.2) with ESMTPS id w26AehUe034396 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 6 Mar 2018 11:40:43 +0100 (CET) (envelope-from wolfgang@lyxys.ka.sub.org) Received: (from wolfgang@localhost) by juno.lyxys.ka.sub.org (8.15.2/8.15.2/Submit) id w26AehKk034395 for freebsd-mips@freebsd.org; Tue, 6 Mar 2018 11:40:43 +0100 (CET) (envelope-from wolfgang@lyxys.ka.sub.org) X-Authentication-Warning: juno.lyx: wolfgang set sender to wolfgang@lyxys.ka.sub.org using -f Date: Tue, 6 Mar 2018 11:40:43 +0100 From: Wolfgang Zenker To: freebsd-mips@freebsd.org Subject: Re: ERL (was: ELF - panic on installworld) Message-ID: <20180306104043.GA34241@lyxys.ka.sub.org> References: <20180305211635.GA21623@lyxys.ka.sub.org> <20180305214528.GB21623@lyxys.ka.sub.org> <20180305203042.22a76c0b@kan> <20180305211527.04ad1c16@kan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180305211527.04ad1c16@kan> Organization: private site User-Agent: Mutt/1.9.4 (2018-02-28) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (saturn.lyxys.ka.sub.org [IPv6:fd2a:89ca:7d54:1:200:24ff:feca:b4cc]); Tue, 06 Mar 2018 11:40:45 +0100 (CET) X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 10:41:02 -0000 * Alexander Kabaev [180306 03:15]: > On Mon, 5 Mar 2018 20:30:42 -0500 > Alexander Kabaev wrote: >> On Mon, 5 Mar 2018 22:45:28 +0100 >> Wolfgang Zenker wrote: >>> Sorry for the messup in the subject. >>> * Wolfgang Zenker [180305 22:16]: >>>> I'm trying to run installworld using 11-STABLE on an Ubiquity Edge >>>> Router Lite (mips64, 2 cores, 512 MB Ram). Unfortunately I haven't >>>> managed to finish the installworld yet, I always get a >>>> panic: kernel stack overflow - trapframe at 0xffffffff80917eb0 >>>> in slightly different places during the installworld. Of the 4 >>>> panics I have seen on the serial console, 3 had the trapframe at >>>> 0xffffffff80917eb0 and one at 0xffffffff80915eb0 >>>> /usr/src and /usr/obj are nfs-mounted, and I have configured >>>> almost 2 GB of swap. The build was done in a Qemu environment. >>>> Any hints how to proceed from here? >> NFS is is known kernel stack hog. Try increasing KSTACK_PAGES up from >> whatever defaults in your kernel config file. IIRC, mips defaults to 2 >> pages, which is not enough for your workload. > I got reminded privately that variable stack sizes do not work on MIPS > without extra patches: True; due to KSTACK_PAGES being set to 2 unconditionally in sys/mips/include/param.h, buildkernel fails when KSTACK_PAGES is added to the conf file. Adding an "#ifndef KSTACK_PAGES" to param.h allows buildkernel to work, but the resulting kernel panics at boot. > http://people.freebsd.org/~sson/mips/kstack/kstack_large_page.diff That looks like quite a bit more than just a simple increase of the kernel stack space. I think I will go with updating by building media images (and less frequent upgrades) instead. > Not sure if it can still be applied to -current. I will at least try it once on 11-STABLE, just to find out. Will take a while, currently down with flu and not really that good with concentrating on that task. Wolfgang