Re: kernel 100% CPU

On 10/14/23, Graham Perrin <grahamperrin@gmail.com> wrote:
> On 03/09/2023 20:25, Mateusz Guzik wrote:
>
>> …
>>
>> Sorry mate, neglected to specify: collect sysctl -a once you run into
>> the problem.
>>
>> Once I look at that I'm probably going to ship some debug patches to
>> narrow it down.
>
>
> I had what might be the same issue this afternoon, for the first time in
> weeks. With the slowdown, it took a few minutes for me to find your
> email, unfortunately the symptoms subsided moments before finding it.
>
> So, I collected the information, but it's probably another missed
> opportunity (the information collected too late).
>
> The busy period lasted for around six minutes:
>
> root@mowa219-gjp4-8570p-freebsd:~ # poudriere bulk -j main -J 3 -Ctv
> devel/pkgconf
> [00:00:00] Creating the reference jail... done
> [00:00:01] Mounting system devices for main-default
> [00:00:02] Warning: Using packages from previously failed, or
> uncommitted, build:
> /usr/local/poudriere/data/packages/main-default/.building
> [00:00:02] Mounting ccache from: /usr/.ccache
> [00:00:02] Mounting ports from: /usr/local/poudriere/ports/default
> [00:00:02] Mounting packages from:
> /usr/local/poudriere/data/packages/main-default
> [00:00:02] Mounting distfiles from: /usr/ports/distfiles
> [00:00:02] Copying /var/db/ports from:
> /usr/local/etc/poudriere.d/main-options
> [00:00:02] Appending to make.conf: /usr/local/etc/poudriere.d/make.conf
> /etc/resolv.conf ->
> /usr/local/poudriere/data/.m/main-default/ref/etc/resolv.conf
> [00:00:02] Starting jail main-default
> [00:00:02] Will build as nobody:nobody (65534:65534)
> [00:00:05] Logs:
> /usr/local/poudriere/data/logs/bulk/main-default/2023-10-14_16h16m30s
> [00:00:05] Loading MOVED for
> /usr/local/poudriere/data/.m/main-default/ref/usr/ports
> [00:00:06] Ports supports: FLAVORS SELECTED_OPTIONS
> [00:00:06] Inspecting ports tree for modifications to git checkout... yes
> [00:06:39] Ports top-level git hash: e843b8293c (dirty)
> …
>

sysctl output you pasted privately shows you are running a kernel form
October 9th, fee14577d590. This predates a slew of fixes to vnlru I
committed the day after.

They fix some of the problems (not all of them!), but it should be good enough.

tl;dr just update to newest main and it should be fine.

-- 
Mateusz Guzik <mjguzik gmail.com>