Date: Sun, 28 Mar 2021 12:53:45 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: "dmilith ." <dmilith@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Graham Perrin <grahamperrin@gmail.com> Subject: Re: 13.0 RC4 might be delayed Message-ID: <CAN6yY1uJv__RsPwE0x3HA-r5VH7=iVgkK1qB5KT%2BbDud09ZQ=Q@mail.gmail.com> In-Reply-To: <CAJQ5JniRcGYKe_7_uB1Gs1rMf6SZUofiWYJViE9SRk_hZFUNUQ@mail.gmail.com> References: <2766233C-3CC7-4B02-95AB-7555A60FFD81@samsco.org> <YF1Xt5wbO20GyO8j@doctor.nl2k.ab.ca> <9c49b2b1-6c49-410b-fbb2-a3b73618b01c@gmail.com> <CAN6yY1uh7Lj5%2B7A=zoxDXo4ZyCYCxwc-6eHo6rmQiZpRaAE%2B8w@mail.gmail.com> <20210327050411.GS15485@mailx.dglawrence.com> <CAJQ5JniRcGYKe_7_uB1Gs1rMf6SZUofiWYJViE9SRk_hZFUNUQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 27, 2021 at 5:07 AM dmilith . <dmilith@gmail.com> wrote: > It may not only be Virtualbox, but also happens under Vmware VMs. > > I use Vmware Fusion 7 pro as my software build-host on top of my Mac > Pro for years now, but I can't build much with 13.0 cause regular > build processes (like sed, awk, grep, zsh) turn into zombies randomly. > Example shot from my private CI from yesterday: > http://s.verknowsys.com/12f14b0350ee3baeb8f153cd48764bc8.png > > The issue doesn't happen on 12.2, 12.1, 12.0 or older releases. > > I reported this issue (I'm testing it since 13-alpha) here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253718 > > In RC3 it feels it got even worse and happens even more often=E2=80=A6 It= 's a > critical release blocker if you ask me=E2=80=A6 > > kind regards > Daniel > > On 27/03/2021, David G Lawrence via freebsd-current > <freebsd-current@freebsd.org> wrote: > >> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin <grahamperrin@gmail.com> > >> wrote: > >> > >> > On 26/03/2021 03:40, The Doctor via freebsd-current wrote: > >> > > ??? if people are having issues with ports like ??? > >> > > >> > If I'm not mistaken: > >> > > >> > * 13.0-RC3 seems to be troublesome, as a guest machine, with > >> > emulators/virtualbox-ose 6.1.18 as the host > >> > > >> > * no such trouble with 12.0-RELEASE-p5 as a guest. > >> > > >> > I hope to refine the bug report this weekend. > >> > > >> > >> Had nothing but frequent guest lockups on 6.1.18 with my Win7 system. > >> That > >> was right after 6.1.18 was put into ports. Fell back to legacy (v5) an= d > >> will try again shortly to see if it's any better. > > > > Kevin, > > > > Make sure you have these options in your /etc/sysctl.conf : > > > > vfs.aio.max_buf_aio=3D8192 > > vfs.aio.max_aio_queue_per_proc=3D65536 > > vfs.aio.max_aio_per_proc=3D8192 > > vfs.aio.max_aio_queue=3D65536 > > > > ...otherwise the guest I/O will random hang in VirtualBox. This issu= e > > was > > mitigated in a late 5.x VirtualBox by patching to not use AIO, but the > > issue > > came back in 6.x when that patch wasn't carried forward. > > > > -DG > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > > > -- > -- > Daniel Dettlaff > Versatile Knowledge Systems > verknowsys.com > My problem was resolved when I spent the time to read the pkg-message in the port. It is running just fine, now. Somehow I missed David's message, as well. Not good. Unfortunate that the patches to turn off AIO did not make it into V6. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uJv__RsPwE0x3HA-r5VH7=iVgkK1qB5KT%2BbDud09ZQ=Q>