From owner-freebsd-current@freebsd.org Mon Sep 17 18:32:19 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 2A83210A4033 for ; Mon, 17 Sep 2018 18:32:19 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BF41B86A06; Mon, 17 Sep 2018 18:32:18 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1537209129; bh=rFv77Kv3 5zNIzxsmqUEewjKoQI/Fg83Y3EtqpkktYH4=; b=daHJ4i6w6jUeY/bK7WLCwN6u 7ZT75UGfW1TyCUNFBR/x1EASmrRiZ4ErDZI+ynEQEcBDTYta5M37jzs8z66h5Zbu dkX6Z5lATdpMaQo/4iRNyC87HDMBCpCRb219uH4sD4IsBLsyeNmclIE0+9OzR99A cZyeRcuXJnpCmoIcxVc= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 475CD1CA7E; Mon, 17 Sep 2018 14:32:09 -0400 (EDT) Subject: Re: intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted' To: John Baldwin , Konstantin Belousov Cc: Ian FREISLICH , freebsd-current 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> From: Michael Butler Openpgp: preference=signencrypt Message-ID: Date: Mon, 17 Sep 2018 14:32:09 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <1918dda4-e9e5-a7bd-09e3-b3a70fcccd01@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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:32:19 -0000 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! :-) imb