From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Sander Eikelenboom <linux@eikelenboom.it>,
Linus Torvalds <torvalds@linux-foundation.org>,
Juergen Gross <jgross@suse.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
kernel test robot <oliver.sang@intel.com>
Subject: Re: Linux 5.13-rc6 regression to 5.12.x: kernel OOM and panic during kernel boot in low memory Xen VM's (256MB assigned memory).
Date: Mon, 21 Jun 2021 18:54:00 +0200 [thread overview]
Message-ID: <bfdd1d6b-77a3-450b-71f4-63e9cc314ace@rasmusvillemoes.dk> (raw)
In-Reply-To: <e7f9c4f8-1669-75ce-b052-1030350a159e@eikelenboom.it>
On 18/06/2021 03.06, Sander Eikelenboom wrote:
> On 17/06/2021 21:39, Sander Eikelenboom wrote:
>
> OK, done some experimentation and it seems with 256M assigned to the VM
> it was almost at the edge of OOM with the 5.12 kernel as well in the
> config I am using it.
> With v5.12 when I assign 240M it boots, with 230M it doesn't. With 5.13
> the tipping point seems to be around 265M and 270M, so my config was
> already quite close to the edge.
>
> The "direct kernel boot" feature I'm using just seems somewhat memory
> hungry, but using another compression algorithm for the kernel and
> initramfs already helped in my case.
>
> So sorry for the noise, clearly user-error.
Hm, perhaps, but I'm still a bit nervous about that report from Oliver
Sang/kernel test robot, which was for a VM equipped with 16G of memory.
But despite quite a few attempts, I haven't been able to reproduce that
locally, so unfortunately I have no idea what's going on.
Rasmus
next prev parent reply other threads:[~2021-06-21 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:26 Linux 5.13-rc6 regression to 5.12.x: kernel OOM and panic during kernel boot in low memory Xen VM's (256MB assigned memory) Sander Eikelenboom
2021-06-17 10:30 ` Juergen Gross
2021-06-17 12:35 ` Sander Eikelenboom
2021-06-17 15:01 ` Linus Torvalds
2021-06-17 15:37 ` Rasmus Villemoes
2021-06-17 15:37 ` Rasmus Villemoes
2021-06-17 18:02 ` Sander Eikelenboom
2021-06-17 19:39 ` Sander Eikelenboom
2021-06-18 1:06 ` Sander Eikelenboom
2021-06-21 16:54 ` Rasmus Villemoes [this message]
2021-06-21 21:36 ` Sander Eikelenboom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bfdd1d6b-77a3-450b-71f4-63e9cc314ace@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=oliver.sang@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).