Date: Sun, 16 Jul 2023 16:38:06 +0000 From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page Message-ID: <bug-272536-2597-2jViILuwoe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272536-2597@https.bugs.freebsd.org/bugzilla/> References: <bug-272536-2597@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272536 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #1 from Mark Millard <marklmi26-fbsd@yahoo.com> --- The actual message is from sys/vm/vm_pageout.c (looking in modern source): case VM_OOM_MEM_PF: reason =3D "a thread waited too long to allocate a = page"; break; ("waited" instead of "waiting"). Do you have anything specific for what controls getting VM_OOM_MEM_PF: # sysctl -d vm.pfault_oom_wait vm.pfault_oom_attempts vm.pfault_oom_wait: Number of seconds to wait for free pages before retrying the page fault handler vm.pfault_oom_attempts: Number of page allocation attempts in page fault handler before it triggers OOM handling The defaults are: # sysctl vm.pfault_oom_wait vm.pfault_oom_attempts vm.pfault_oom_wait: 10 vm.pfault_oom_attempts: 3 What sort of storage media was the swap space on? Spinning Rust? Sometimes VM environments have accuracy problems with various forms of time handling. So that might be another direction involved for this issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272536-2597-2jViILuwoe>