On 2022-10-17, navere...@xsec.at <navere...@xsec.at> wrote:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> --------------Ul4Ju1YTbRJ7mI3pDCjI9wxQ
> Content-Type: multipart/mixed;
> boundary="------------7bJ04sybIOvQeGF8TtkbbrkC";
> protected-headers="v1"
> From: navere...@xsec.at
> To: misc@openbsd.org
> Message-ID: <508a4699-4d17-e6cb-85c9-7a117f897...@xsec.at>
> Subject: Increase kernel memory
>
> --------------7bJ04sybIOvQeGF8TtkbbrkC
> Content-Type: multipart/mixed; boundary="------------aLZ0sMHaMBH5kQXYzt4fVxL0"
>
> --------------aLZ0sMHaMBH5kQXYzt4fVxL0
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Content-Transfer-Encoding: 8bit
ugh
> Hi,
>
> I'm running an OpenBSD instance which is handling quite a lot of vlan
> traffic. When trying to replace the currently running ruleset the kernel
> panics.
"quite a lot" -> how much?
> ddb{0}> show panic
>
> *cpu0: malloc: out of space in kmem_map
That's not really expected for just forwarding traffic.
> This issue is probably due to too little kernel memory.
>
> How may I increase the amount of available kernel memory?
Better to investigate why it's using so much kernel memory.
There might be something useful in some of these:
$ vmstat -m
$ netstat -m
$ systat -B mbuf
$ dmesg
$ ifconfig -A
(and a quick description of anything unusual that the machine might be
doing)
If you can capture the output from ddb after a panic, it might be
helpful to include "sh all pools" and "sh malloc". (If it's via
screenshots rather than a plaintext method then just post URLs to
them, don't attach them to a mailing list post).
