Date: Fri, 26 Jul 2024 17:14:31 -0700 From: Mark Millard <marklmi@yahoo.com> To: Warner Losh <imp@bsdimp.com> Cc: Philip Paeps <philip@freebsd.org>, FreeBSD ARM List <freebsd-arm@freebsd.org>, FreeBSD Mailing List <freebsd-ports@freebsd.org>, Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: [main has a fix for] armv7-on-aarch64 stuck at urdlck: I got a replication of the "ampere2" bulk build hangup problem on a Windows DevKit 2023 Message-ID: <68C09CB4-92AF-4369-A1E0-A6EADF092449@yahoo.com> In-Reply-To: <CANCZdfqBTdyYgFCMkkW=FRnvbHw6zfoz%2B37t4SJsJwiJ=C4oQQ@mail.gmail.com> References: <A3BBDBA3-FF7E-47B8-8B45-C3351918FC08@yahoo.com> <8214703E-AB28-4FB3-A3DD-03C87363D8C6@yahoo.com> <E40B106D-30B7-49DC-8540-911A56E53FCA@yahoo.com> <BFCA474F-78D4-4E98-8A9B-B92C2DB6B0DE@yahoo.com> <E40627DC-35A2-4D5E-A85C-73D7FFD426DF@yahoo.com> <A208F7C8-0D9E-402C-BB85-A5022B37E3EC@yahoo.com> <561E4947-6D56-4431-AE08-C843FF232066@yahoo.com> <E91E066B-D9D3-4218-BA03-589408051763@yahoo.com> <E8192BA4-6A6F-4EB5-A8DE-069CE3B29F2D@freebsd.org> <F5173B0C-5A91-43E3-9DDC-E4294CE8DD3D@yahoo.com> <CANCZdfqBTdyYgFCMkkW=FRnvbHw6zfoz%2B37t4SJsJwiJ=C4oQQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Jul 26, 2024, at 16:44, Warner Losh <imp@bsdimp.com> wrote: > On Fri, Jul 26, 2024, 5:37 PM Mark Millard <marklmi@yahoo.com> wrote: >> On Jul 26, 2024, at 07:56, Philip Paeps <philip@freebsd.org> wrote: >> >> > On 2024-07-26 22:46:57 (+0800), Mark Millard wrote: >> >> So, it looks like updating the kernel and world on ampere2 and >> >> enabling builds of main-armv7-default should no longer have >> >> main-armv7-default hang-up during graphviz installation (or >> >> analogous contexts). Hopefully, that means that >> >> main-armv7-default builds will then complete and be distributed. >> > >> > I've set the stop-builds flag on the ampere machines. I'll kick off a cluster build and upgrade them when they finish their current builds (or get stuck). >> > >> > Thanks for chasing this down. >> >> FYI: As stands, only main has the update. The MFC will not happen >> for about a week. ampere1 and ampere3 should probably wait to >> upate until after the MFC since they do not build main-armv7-* . >> >> Note: The fix is a world change, not a kernel change. So it is >> the jail's world that matters. >> >> I'm not sure if any existing releng/13.*/ or releng/14.*/ will >> get an update for this. stable/13/ and stable/14/ are likely to. > > I wonder if a rebuilt system will make it through an armv7 bsd-user poudriere bulk.... I assume that this wording is about having amd64 with qemu attempting bulk -a for building amv7 packages, not about having aarch64 (without qemu) bulk -a with armv7 jails do so (which are now being done). Have I got that right? (It appears that main used to have some prior use of the __aeabi_* in question before the failure point, thereby historically avoiding the recursive lock use deadlock. 13 and 14 are still operational for bulk -a on aarch64 for armv7 jails --but are subject to breakage, just like main was.) If spreading the package-building load around more to amd64 contexts was a goal, and if amd64 with qemu worked well for aarch64, one could imagine having some of the aarch64 package builds on amd64 but all the armv7 ones on the ampere*'s. This may be more likely to work better overall than amd64 with qemu ever handling a 32-bit context well (armv7 here). === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?68C09CB4-92AF-4369-A1E0-A6EADF092449>