The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2022.07.02.04.37.15 skrll
src/sys/external/bsd/drm2/include/drm/drm_gem_cma_helper.h,v 1.4
Logs can be found at:
Updating src tree:
P src/sbin/shutdown/shutdown.8
P src/sbin/shutdown/shutdown.c
P src/sys/external/bsd/drm2/drm/drm_gem_cma_helper.c
P src/sys/external/bsd/drm2/include/drm/drm_gem_cma_helper.h
P src/sys/kern/kern_fork.c
P src/sys/kern/kern_time.c
P src/sys/kern/uipc_syscalls.c
P
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2022.07.02.00.26.07.
An extract from the build.sh output follows:
# compile LEGACY/drm_damage_helper.o
Hi Matthias !
See PR 55707
http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=55707 , which
I do not considere fixed due to the pgdaemon issue. reverting arc.cto
1.20 will give you many xcalls, but the system stays more usable.
Frank
On 07/01/22 07:55, Matthias Petermann wrote:
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2022.07.01.09.54.36 prlw1 src/sys/kern/kern_fork.c,v 1.229
Logs can be found at:
"J. Hannken-Illjes" writes:
>> On 1. Jul 2022, at 07:55, Matthias Petermann wrote:
>>
>> Good day,
>>
>> since some time I noticed that on several of my systems with NetBSD/amd64
>> 9.99.97/98 after longer usage the kernel process pgdaemon completely claims
>> a CPU core for itself, i.e.
> On 1. Jul 2022, at 07:55, Matthias Petermann wrote:
>
> Good day,
>
> since some time I noticed that on several of my systems with NetBSD/amd64
> 9.99.97/98 after longer usage the kernel process pgdaemon completely claims a
> CPU core for itself, i.e. constantly consumes 100%.
> The
m...@petermann-it.de (Matthias Petermann) writes:
>since some time I noticed that on several of my systems with=20
>NetBSD/amd64 9.99.97/98 after longer usage the kernel process pgdaemon=20
>completely claims a CPU core for itself, i.e. constantly consumes 100%.
>The affected systems do not have
