Re: armv7-on-aarch64 stuck at urdlck: I got a replication of the "ampere2" bulk build hangup problem on a Windows DevKit 2023
John F Carr <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
> On Jul 22, 2024, at 12:51, Mark Millard <[email protected]> wrote: > > Another systematic difference in my personal builds vs. > official pkgbase builds, snapshots, releases, etc. is > that my armv7 builds are built on aarch64-as-armv7, not > on amd64. Not that I have any specific evidence that > such matters here. > > But Michal Meloun's report indicated not using builds > done on amd64 as well. ("Tegra" models and examples of > ARMv7-A and of ARMv8-A.) > > For John Carr, I do not know if amd64 based builds of > the world were systematically in use, never in use, > or some mix in his tests. > > === > Mark Millard > marklmi at yahoo.com > I reproduced the hang with code built on aarch64. I have not been cross-compiling from amd64. For poudriere I use armv7 jails running on aarch64. One of them just hit the hang with 14.1-STABLE kernel and 15.0-CURRENT userspace. # ps -d -J 1021 PID TT STAT TIME COMMAND 77550 1 IJ 0:00.27 /usr/bin/make -C /usr/ports/graphics/librsvg2-rust stage 77574 1 IJ 0:00.00 - /bin/sh -e /wrkdirs/usr/ports/graphics/librsvg2-rust/work/makeiFVIOP 77575 1 IJ 0:00.06 `-- gmake -f Makefile DESTDIR=/wrkdirs/usr/ports/graphics/librsvg2-rust/wo 77576 1 IJ 0:00.06 `-- gmake INSTALL_PROGRAM=/bin/sh /wrkdirs/usr/ports/graphics/librsvg2-r 77577 1 IJ 0:00.06 `-- gmake install-recursive 77578 1 IJ 0:00.00 `-- /bin/sh -c fail=; \\\nif (target_option=k; case ${target_option- 77709 1 IJ 0:00.01 `-- gmake install 77710 1 IJ 0:00.00 `-- /bin/sh -c ( /usr/local/bin/gdk-pixbuf-query-loaders ./libpi 77711 1 IJ 0:00.01 `-- /usr/local/bin/gdk-pixbuf-query-loaders ./libpixbufloader- # ps -l -p 77711 UID PID PPID C PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 65534 77711 77710 27 20 0 27520 16660 urdlck IJ 1 0:00.01 /usr/local/bin/gdk-pixbuf-query-l Poudriere told me I shouldn't run a newer userspace than kernel. It usually works despite the warning.