aarch64 lib32 vs. armv7 mdconfig behavior: "mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device"

Not via a chroot'd context, but using the files from a directory tree that allows an armv7 chroot: # /usr/obj/DESTDIRs/main-CA7-chroot/sbin/mdconfig -s40m mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device This sort of thing messes up the operation of the likes of the /usr/tests/sbin/gro

Re: aarch64 lib32 vs. armv7 mdconfig behavior: "mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device"

On Jul 31, 2023, at 23:22, Mark Millard wrote: > Not via a chroot'd context, but using the files from a > directory tree that allows an armv7 chroot: > > # /usr/obj/DESTDIRs/main-CA7-chroot/sbin/mdconfig -s40m > mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device > > This sort of thing

Some results from my crude technique of using (some of) Kyua to test aarch64's lib32 vs. kyua runs in a armv7 chroot on aarch64

[I first report how I tested before reporting on errors that look to be valid kyua reports of issues.] [This testing is with a line commented out in order to prevent sys/net/if_bridge_test:gif from being tested, because of its leading to a panic for lib32 style testing.] I have /usr/obj/DESTDIRs/

aarch64/armv7 via lib32 and via chroot: db_test:btree_byteswap_unaligned_access_skbd gets bus error

I do not know if the unaligned access activity in the likes of: db_test:btree_byteswap_unaligned_access_skbd is some form of FreeBSD requirement or not. But, for armv7 activity, it results in a bus error (and kyua test failure). Probaly also true native armv7 operation. ===> lib/libc/db/db_test:

Can't assign address to igc

Running a recent-ish version (n264266-8f8da1bcc799) on an Intel NUC (RNUC11PABi5), assigning an IPv4 address to igc0 doesn't work. There is no error message, and this has been working in the past. Looking through dmesg only shows: igc0: link state changed to UP igc0: link state changed to DOWN igc