From nobody Sat May 14 13:20:39 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A21C21AE04B3 for ; Sat, 14 May 2022 13:20:47 +0000 (UTC) (envelope-from wayne@post.wayne47.com) Received: from post.wayne47.com (post.wayne47.com [198.11.56.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "post.wayne47.com", Issuer "post.wayne47.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4L0mNZ4SKZz4dRG for ; Sat, 14 May 2022 13:20:46 +0000 (UTC) (envelope-from wayne@post.wayne47.com) Received: from post.wayne47.com (post.wayne47.com [198.11.56.11]) by post.wayne47.com (8.15.2/8.15.2) with ESMTPS id 24EDKdf0071729 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 14 May 2022 09:20:39 -0400 (EDT) (envelope-from wayne@post.wayne47.com) Received: (from wayne@localhost) by post.wayne47.com (8.15.2/8.15.2/Submit) id 24EDKdEP071728 for freebsd-hackers@freebsd.org; Sat, 14 May 2022 09:20:39 -0400 (EDT) (envelope-from wayne) Date: Sat, 14 May 2022 09:20:39 -0400 From: Michael Wayne To: freebsd-hackers@freebsd.org Subject: Re: Can not build kernel on 1GB VM Message-ID: <20220514132039.GX72471@post.wayne47.com> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20220415174953.GE13678@post.wayne47.com> <5db061cf-1e23-7cfb-fea-4573f379ae5d@puchar.net> <20220509170925.GQ72471@post.wayne47.com> <70185630-ccea-d92b-a691-bc9cd784cbf5@puchar.net> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <70185630-ccea-d92b-a691-bc9cd784cbf5@puchar.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 4L0mNZ4SKZz4dRG X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of wayne@post.wayne47.com designates 198.11.56.11 as permitted sender) smtp.mailfrom=wayne@post.wayne47.com X-Spamd-Result: default: False [-2.63 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.75)[-0.749]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:198.11.56.11]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.983]; DMARC_NA(0.00)[wayne47.com]; MLMMJ_DEST(0.00)[freebsd-hackers]; RCVD_COUNT_ONE(0.00)[1]; FORGED_SENDER(0.30)[freebsd07@wayne47.com,wayne@post.wayne47.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2015, ipnet:198.11.56.0/24, country:US]; FROM_NEQ_ENVFROM(0.00)[freebsd07@wayne47.com,wayne@post.wayne47.com]; RCVD_TLS_ALL(0.00)[]; ONCE_RECEIVED(0.10)[] X-ThisMailContainsUnwantedMimeParts: N On Fri, May 13, 2022 at 01:25:11PM +0200, Wojciech Puchar wrote: > >>> sudo make buildkernel KERNCONF=ROUTING > >>> the machine ran out of swap. with a bunch of messages like: > >>> Apr 15 12:11:26 g1 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 240593, size: 4096 > >>> Apr 15 12:11:35 g1 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 236224, size: 16384 > >>> Apr 15 12:11:37 g1 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 245, size: 12288 > >>> Apr 15 12:11:46 g1 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 240593, size: 4096 > >>> Apr 15 12:11:55 g1 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 236224, size: 16384 > >>> Apr 15 12:11:57 g1 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 245, size: 12288 > > i was getting such message when i used crappy SSD that stalled for very > long after receiving bunch of TRIM command from UFS filesystem and in the > same time OS did some swapping. I had the provider check the SSD and got this back: We see no issues present on the host at this time. I suspect you may be experiencing the effects of a noisy neighbor or swap is coming into play. > If you get out of swap, some processes (usually the largest) are killed. > And different messages are in log. Those messsages are on the screen. The machine >thinks< it's running out of swap: May 9 13:05:57 g1 kernel: pid 9507 (ctfmerge), jid 0, uid 0, was killed: out of swap space May 9 13:05:58 g1 kernel: pid 4969 (make), jid 0, uid 0, was killed: out of swap space May 9 13:06:00 g1 kernel: pid 828 (openvpn), jid 0, uid 301, was killed: out of swap space May 9 13:06:00 g1 kernel: tun0: link state changed to DOWN May 9 13:06:01 g1 kernel: pid 889 (sendmail), jid 0, uid 0, was killed: out of swap space May 9 13:06:03 g1 kernel: pid 909 (tcsh), jid 0, uid 5147, was killed: out of swap space May 9 13:06:05 g1 kernel: pid 1091 (tcsh), jid 0, uid 5147, was killed: out of swap space May 9 13:06:06 g1 kernel: pid 892 (sendmail), jid 0, uid 25, was killed: out of swap space May 9 13:06:08 g1 kernel: pid 814 (ntpd), jid 0, uid 0, was killed: out of swap space May 9 13:06:09 g1 kernel: pid 881 (bird), jid 0, uid 0, was killed: out of swap space May 9 13:06:10 g1 kernel: pid 532 (devd), jid 0, uid 0, was killed: out of swap space May 9 13:06:11 g1 kernel: pid 526 (dhclient), jid 0, uid 65, was killed: out of swap space May 9 13:06:12 g1 kernel: pid 474 (dhclient), jid 0, uid 0, was killed: out of swap space May 9 13:06:14 g1 kernel: pid 903 (getty), jid 0, uid 0, was killed: out of swap space