From owner-freebsd-stable@freebsd.org Fri Aug 9 20:06:09 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 ED2D5A8697 for ; Fri, 9 Aug 2019 20:06:09 +0000 (UTC) (envelope-from kob6558@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 464x814gn7z3ygy for ; Fri, 9 Aug 2019 20:06:09 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id A0244A8696; Fri, 9 Aug 2019 20:06:09 +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 9FE82A8695 for ; Fri, 9 Aug 2019 20:06:09 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 464x813l8rz3ygx; Fri, 9 Aug 2019 20:06:09 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x330.google.com with SMTP id b7so86957418otl.11; Fri, 09 Aug 2019 13:06:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/gZUS+GyfuiKEaLF8cDMw1KCvKUJFdodETmGoh8hp0s=; b=F55lM3NjRNWH5L/leD9WgfYm/ZtZLj+iJ/Z6nJ8dD7BLIVZ24GntSUsL9bHEm8quuE a2MgEgcT4vm+wy/ESobzvr1RWraYRO7t67bQRAGpP2OefFdgMJDYpfj5M2e9QhpWITAq jWSRC6z7yEOAGeiqCzSve55IQXz/1p1bjgY7FC5NwUgkihUjYuJpBg2ImIpwRyymuVAB SBRzL8QQz+Xy1tfA/IZOc/5+yeAU+QUGAIB7KZmV/2ybIdYwNCkCB3W66OMegC4NvMsi zGCXO4b3ZMZ3OrpzFkXFqQkUumPIQOwJBtJwbpr7ZkgBZCq6lVpTKP6AIjVnYkaVrbwh H0EA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/gZUS+GyfuiKEaLF8cDMw1KCvKUJFdodETmGoh8hp0s=; b=rHtVn5Cg9z4Tod4hd3gOaD3hGaeWNtx7t+DTLDl/h4sBVgCp/iBbyOLnBwFuj2wg/V gm4FQNKIA7bckx71YBs99V1MjJPBblpxYXWHxG2teNa9b5KZba4QFQ9jgmj2GntF0ety nXOhxPzEjDY8AOv1lA3qIHGIoOuNlH6sGMViIkqlSyzyF+pORTOmy24MKznJ4XtAKb/u dwcOY7UK0wroG/Wdtx03IHZ0xjQHHusRk0s77AayNEJDHvlqG47IJpE7NGUmNazVTTr1 IE5+ZlK7LDTLw/zJfrUhCvwWlkdFP6GZxudbeHhV4CKOV17PcrJMPTdV+pSoR+pJXwpn FYnA== X-Gm-Message-State: APjAAAWPUKl6Wh86FJNrh5IX0wt1MWRCvGrl3ZR/0BP2jAytNxC+MfZH iheoKkLYoPFIxA0Kk1qY2Kl23geiaGb2tzrKUNSDtwYZYJQ= X-Google-Smtp-Source: APXvYqzGYUhx9XavtRn6/hwUn1AdfReZ/VTiYAJRsIn7jnYjgkHVM7aUqYwrKagxZB6u2bRI0H4pFaKIbfDGBwxYY/0= X-Received: by 2002:aca:1c02:: with SMTP id c2mr7634215oic.166.1565381167718; Fri, 09 Aug 2019 13:06:07 -0700 (PDT) MIME-Version: 1.0 References: <20190809183547.GE86532@raichu> In-Reply-To: <20190809183547.GE86532@raichu> From: Kevin Oberman Date: Fri, 9 Aug 2019 13:05:50 -0700 Message-ID: Subject: Re: Memory management changes after kernel update on 6-Aug To: Mark Johnston Cc: FreeBSD Stable ML X-Rspamd-Queue-Id: 464x813l8rz3ygx X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.982,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 20:06:10 -0000 On Fri, Aug 9, 2019 at 11:35 AM Mark Johnston wrote: > 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? > I am monitoring memory usage with gkrellm. It appears to define "Free" as the sum of "Inactive" and "Free". If you are referring to size of the VM, was supposed to be the memory specified when I created the VM, but my fingers got ahead of my brain and it should have been 4G, not 4M. Hey! What's a few orders of magnitude? Oddly, when I watch memory space closely I note that, as the VM loads, I started seeing swap utilization increase as free space was exhausted at about 80% loaded. Loading continued to 98%. at that point loading stopped and swap use continued to grow for a bit. Then free space started to increase from about 300M to about 700M before the error window popped up. > > 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? > Failed to open a session for the virtual machine Win7. Failed to load unit 'pgm' (VERR_EM_NO_MEMORY). Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} > > > 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. > This started after the 6-Aug build (r350664). My prior build was r350292, so just before these two commits. Can I try just reverting these two? Once I do, it will need to run for a while or do something to tie up a lot of memory before the error will recur. In normal use it is a matter of firefox increasing resident memory until there is not enough free memory to load the VM without swapping. (These days I often see the sum of all firefox process resident memory exceeding 3G after it's been up for a day or two. Still, not worse than chromium.) Thanks, Mark, for the quick response. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683