From: Alyssa Ross <hi@alyssa.is>
To: devel@spectrum-os.org
Subject: [PATCH] host: use a bigger kernel buffer for mdevd
Date: Sat, 23 Apr 2022 12:46:30 +0000 [thread overview]
Message-ID: <20220423124630.749434-1-hi@alyssa.is> (raw)
This should fix a boot error on a Thinkpad P51s:
> mdevd: fatal: unable to receive netlink message: No buffer space available
>From the mdevd documentation:
> • -b kbufsz : try and reserve a kernel buffer of kbufsz bytes for
> the netlink queue. Too large a buffer wastes kernel memory; too
> small a buffer risks losing events. The default is 500 kB, which
> should be enough for most systems; if you're getting "No buffer
> space available" errors from mdevd at coldplug time, try
> increasing this number.
The new value of 128MiB is used by default by both udev and Busybox's mdev.
---
I'm hoping this will fix the problem reported by terwiz in #spectrum.
host/initramfs/etc/init | 2 +-
host/rootfs/etc/s6-rc/mdevd/run | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/host/initramfs/etc/init b/host/initramfs/etc/init
index bb58c84..e6236bc 100755
--- a/host/initramfs/etc/init
+++ b/host/initramfs/etc/init
@@ -19,7 +19,7 @@ if { mkfifo /dev/rootfs.poll }
background {
fdclose 3
- mdevd -C
+ mdevd -C -b134217728
}
importas -iu mdevd_pid !
diff --git a/host/rootfs/etc/s6-rc/mdevd/run b/host/rootfs/etc/s6-rc/mdevd/run
index 03ad5e3..22f0127 100644
--- a/host/rootfs/etc/s6-rc/mdevd/run
+++ b/host/rootfs/etc/s6-rc/mdevd/run
@@ -2,4 +2,4 @@
# SPDX-License-Identifier: EUPL-1.2
# SPDX-FileCopyrightText: 2020-2021 Alyssa Ross <hi@alyssa.is>
-mdevd -D3
+mdevd -D3 -b134217728
base-commit: 92e918a477dc7a16460a73d466fc2d42f7e7c421
--
2.35.1
next reply other threads:[~2022-04-23 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 12:46 Alyssa Ross [this message]
2022-04-23 14:39 ` Alyssa Ross
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=20220423124630.749434-1-hi@alyssa.is \
--to=hi@alyssa.is \
--cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).