Date: Sun, 16 Jul 2023 17:14:42 +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-6Oog4sMmm0@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 --- Comment #4 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Yuri Victorovich from comment #2) Being in a VirtualBox VM the /dev/ada0p2 may not indicate much about the actual media involved. Microsd card and spinning rust media are more likely than some other types of media to end up with larger than desirable delays. The environment running the VM (outside the VM) could be relevant as well. I was mostly after if the media was more vs. less likely to contribute to such a problem when the swap space is under heavy use. Other relevant things to know would include the actual RAM available to the FreeBSD instance, the number of hardware threads actually present for FreeBSD to run on, and probably more that I'm not managing to think of at the moment. Another would be if the system that was running the VM was also busy with other activities vs. being basically dedicated to running the one VM instance that was running the FreeBSD instance. But . . . It may be that, unless you end up showing repeatability, trying to make notes for such a range of issues is not worth the time and effort. --=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-6Oog4sMmm0>