From owner-freebsd-current@freebsd.org Mon Sep 17 18:43:46 2018 Return-Path: Delivered-To: freebsd-current@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 E38CF10A44F4 for ; Mon, 17 Sep 2018 18:43:45 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::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 7FA9F871C7 for ; Mon, 17 Sep 2018 18:43:45 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id E815610A87D; Mon, 17 Sep 2018 14:43:43 -0400 (EDT) Subject: Re: intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted' To: Michael Butler , Konstantin Belousov References: <524214ac-e3ca-53cd-aee3-dac9212e9800@capeaugusta.com> <0aa35f96-9f62-bfca-c04a-f6ddcb1ce738@FreeBSD.org> <8ed7961e-e12a-9267-2bd0-a9bcbe383c7f@protected-networks.net> <20180831052805.GP2340@kib.kiev.ua> <04526140-c561-ae1c-cc0a-52bc8b4edb3c@protected-networks.net> <20180908194316.GI3161@kib.kiev.ua> <1918dda4-e9e5-a7bd-09e3-b3a70fcccd01@FreeBSD.org> Cc: Ian FREISLICH , freebsd-current From: John Baldwin Message-ID: <04dda74e-3b62-c4a1-0fed-9d2ceb7d5a7b@FreeBSD.org> Date: Mon, 17 Sep 2018 11:43:41 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 17 Sep 2018 14:43:44 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 17 Sep 2018 18:43:46 -0000 On 9/17/18 11:32 AM, Michael Butler wrote: > On 9/10/18 1:20 PM, John Baldwin wrote: >> On 9/8/18 1:44 PM, Michael Butler wrote: >>> On 9/8/18 3:43 PM, Konstantin Belousov wrote: >>>> On Sat, Sep 08, 2018 at 02:07:41PM -0400, Michael Butler wrote: >>>>> On 8/31/18 1:28 AM, Konstantin Belousov wrote: >>>>>> On Fri, Aug 31, 2018 at 12:21:02AM -0400, Michael Butler wrote: >>>>> >>>>> [ .. snip .. ] >>>>> >>>>>>> I see another problem after using Ian's workaround of moving the #ifdef >>>>>>> SMP; it seems I now run out of kernel stack on an i386 (Pentium-III) >>>>>>> machine with only 512MB of RAM: >>>>>>> >>>>>>> Aug 29 23:29:19 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:26 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:30 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:38 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:38 sarah kernel: vm_thread_new: kstack allocation failed >>>>>>> Aug 29 23:29:40 sarah kernel: vm_thread_new: kstack allocation failed >>>>>> >>>>>> What is the kernel revision for "now". What was the previous revision >>>>>> where the kstack allocation failures did not happen. >>>>>> >>>>>> Also, what is the workload ? >>>>> >>>>> Sorry for the delay. Any version at or after SVN r338360 would either a) >>>>> not boot at all or b) crash shortly after boot with a swarm of messages >>>>> as above. It was stable before that. >>>>> >>>>> Unfortunately, this machine is remote and, being as old as it is, has no >>>>> remote console facility. 'nextboot' has been my savior ;-) >>>>> >>>>> It is a 700MHz Pentium-III with 512MB of RAM and has 3 used interfaces, >>>>> local ethernet (FXP), GIF for an IPv6 tunnel to HE and TAP for an >>>>> OpenVPN endpoint. It has IPFW compiled into the kernel and acts as a >>>>> router/firewall with few actual applications running. >>>>> >>>>> As another data point, I manually reversed both SVN r338360 and r338415 >>>>> (a related change) and it is now stable running at SVN r338520, >>>> >>>> It is very unprobable. I do not see how could r338360 affect KVA allocation. >>>> Double-check that you booted right kernels. >>>> >>> >>> FreeBSD sarah.protected-networks.net 12.0-ALPHA5 FreeBSD 12.0-ALPHA5 #14 >>> r338520M: Thu Sep 6 21:35:31 EDT 2018 >>> >>> 'svn diff' reports the only changes being the two reversals I noted above, >> >> Can you get the output of 'x num_io_irqs' at the DDB prompt after the >> panic? >> > > SVN r338725 fixed this - thanks! :-) Hmm, I'm not sure how that fixed this, but glad it is ok now. -- John Baldwin