Date: Wed, 8 Jan 2020 15:12:44 -0800 From: Mark Millard <marklmi@yahoo.com> To: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: head -356426 based 32-bit powerpc (2 sock PowerMac G4): kyua sys/vm/mlock_test:mlock__copy_on_write_vnode seems stuck Message-ID: <FB2E3099-C59B-47CE-9524-6A1C5D477E82@yahoo.com> References: <FB2E3099-C59B-47CE-9524-6A1C5D477E82.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I've attempted a head -356426 based kyua run on an old 2-socket PowerMac G4. The buildworld and buildkernel were non-debug. The context has personal patches, mostly for dealing with PowerMac issues. It has had over 180 CPU minutes running for: sys/vm/mlock_test:mlock__copy_on_write_vnode -> Normal seems to be way under 0.1 sec on the other platforms I've made runs on recently. Hopefully kyua will time out and continue the testing at some point. The 2 socket (2 cores each) G5 powerpc64 context did not have this problem. Nor did the armv7 or aarch64 examples (CortexA7, CortexA53, CortexA57, and CortexA72). === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FB2E3099-C59B-47CE-9524-6A1C5D477E82>