From owner-freebsd-stable@freebsd.org Fri Aug 9 18:35:53 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CBA9DCEA17 for ; Fri, 9 Aug 2019 18:35:53 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 464v7s42yWz3N8Y for ; Fri, 9 Aug 2019 18:35:53 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 88E2ACEA16; Fri, 9 Aug 2019 18:35:53 +0000 (UTC) Delivered-To: stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 88A53CEA15 for ; Fri, 9 Aug 2019 18:35:53 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ot1-x344.google.com (mail-ot1-x344.google.com [IPv6:2607:f8b0:4864:20::344]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 464v7s0NPyz3N8W for ; Fri, 9 Aug 2019 18:35:52 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-ot1-x344.google.com with SMTP id k18so4137607otr.3 for ; Fri, 09 Aug 2019 11:35:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=xp5nEJogvrbQcdqb6MDFO37njnyDeN4hXhTZwIRo3xI=; b=JRkG3tNU7w/LlFCEWzgsy5PKcNDz5yttppxe/ngMwI8IjjKHO7pMiFYCxpbi3tqEJp 1r14wH2DkRr5itQNS8+h6QW8pXt3SWGbUNbfBhUfg12k8guPzx7LXMBtwRC2Vu5hr8mA AvMaWzEkt4HQ0y1rjm6dMsfY6+U5OsBLFU/CiQJzpboBIoFQ6pjY/hWSA7Dbk0stw7Ha olQl14zr3rm3Nm5D0GW3pnYE+ADho2+4zdpvcZ3U8Uc62ZVb21O+awiIH7aJxteRb1Hf xkQ4M21PkpG4503xV5twciYVoNLhzK5rk7gEbGI/3oKXG21GxXVpuhs6rNxwmiisNYDz UG+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=xp5nEJogvrbQcdqb6MDFO37njnyDeN4hXhTZwIRo3xI=; b=Iw5e8eLOkPe4U9sAkyleOU61YsJWBYxnRDNBvfDD0S1nZxwH26DoVhRW/Au18IAGYJ ap54WaunR7h3RC8LEJIpUS8PtwWfCrI1U8HL0EhG0CUElu9wkYaSSSBdXAcsy73rMppq 7Gq7TiFVR14DHwWp2Yh2itao+HZm+jCXztW9ORsc1Ci5qKqx91ce53g4fw09bWZAKCc5 lmhmK/27XsSDKXv4SR17xwmi5Oo4uiez+J47RlP8sh6PO86ZDtnUEDi1a3/ypPEDIUpW rD0sLv7ojErEIN7kovia6JitM1KYRghlt9UQhP9i6zYKBsURBSyA/Luk6CjLJeStUzfS ClCg== X-Gm-Message-State: APjAAAWzBT2KKg5hvEIAG8qjqc4VNdvO8CyUvw2mP/UJhyyr4B/YdDKE 3kQAorNixTOkZYh+zKHvoak= X-Google-Smtp-Source: APXvYqwDtHFEMPb97Liub/sL4Rk69x+vl9hNGI1+js5Rsw2EhSAyR8dE3ADZHSfnmMB7hw7rHyGR6w== X-Received: by 2002:a5d:80c1:: with SMTP id h1mr356452ior.268.1565375751788; Fri, 09 Aug 2019 11:35:51 -0700 (PDT) Received: from raichu (toroon0560w-lp130-04-184-145-252-124.dsl.bell.ca. [184.145.252.124]) by smtp.gmail.com with ESMTPSA id l2sm10494860ioq.83.2019.08.09.11.35.49 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 09 Aug 2019 11:35:50 -0700 (PDT) Sender: Mark Johnston Date: Fri, 9 Aug 2019 14:35:47 -0400 From: Mark Johnston To: Kevin Oberman Cc: FreeBSD Stable ML Subject: Re: Memory management changes after kernel update on 6-Aug Message-ID: <20190809183547.GE86532@raichu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) X-Rspamd-Queue-Id: 464v7s0NPyz3N8W X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=JRkG3tNU; dmarc=none; spf=pass (mx1.freebsd.org: domain of markjdb@gmail.com designates 2607:f8b0:4864:20::344 as permitted sender) smtp.mailfrom=markjdb@gmail.com X-Spamd-Result: default: False [-3.08 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.92)[-0.918,0]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[124.252.145.184.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.46)[ip: (3.12), ipnet: 2607:f8b0::/32(-2.98), asn: 15169(-2.40), country: US(-0.05)]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[stable@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 09 Aug 2019 18:35:53 -0000 On Fri, Aug 09, 2019 at 11:09:24AM -0700, Kevin Oberman wrote: > Since I updated my 12.0-STABLE system on 6-Aug I have been seeing issues > resuming my Win7 VM on VirtualBox. My prior kernel was built on 24-Jul. If > there is not sufficient memory available to reload the system (4 Meg.), the Where does this number come from? What memory usage stats do you see in top(1) when the error occurs? > resume fails with a message that memory was exhausted. Usually I can try > resuming again and it will work. Sometimes I get the error two or three > times before the system resumes. What exactly is the error message? > Since I have not touched VirtualBox other than to rebuild the kmod after > the kernel build, it looks like something in the OS triggered this. Since > the system frees up some memory each time so that the VM eventually > resumes, it looks like the memory request is made to the OS, but VB is not > waiting or not enough memory is freed to allow the VB to complete the > resume. > > Any clue what might have changed over those 13 days? I am running GENERIC > except that I run the 4BSD scheduler. Possible culprits are r350374 and r350375, but I can't really see how.