Re: aarch64 main-n263493-4e8d558c9d1c-dirty (so: 2023-Jun-10) Kyuafile run: "Fatal data abort" crash during vnet_register_sysinit

> On Jun 24, 2023, at 13:00, Mark Millard wrote: > > The running system build is a non-debug build (but > with symbols not stripped). > > The HoneyComb's console log shows: > > . . . > GEOM_STRIPE: Device stripe.IMfBZr destroyed. > GEOM_NOP: Device md0.nop created. > g_vfs_done():md0.nop[READ

Re: aarch64 main-n263493-4e8d558c9d1c-dirty (so: 2023-Jun-10) Kyuafile run: "Fatal data abort" crash during vnet_register_sysinit

> On Jun 26, 2023, at 04:32, Mark Millard wrote: > > On Jun 24, 2023, at 17:25, Mark Millard wrote: > >> On Jun 24, 2023, at 14:26, John F Carr wrote: >> >>> >>>> On Jun 24, 2023, at 13:00, Mark Millard wrote: >>>> >>

Re: For snapshot builds: armv7 chroot on aarch64 has kyua test -k /usr/tests/Kyuafile sys/kern/kern_copyin hung up [in getpid?], unkillable, prevents reboot

> On Jun 25, 2023, at 20:16, Mark Millard wrote: > > Using the likes of: > > FreeBSD-14.0-CURRENT-arm64-aarch64-ROCK64-20230622-b95d2237af40-263748.img > and: > FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20230622-b95d2237af40-263748.img > > I have shown the following behavior after setting up

Re: For snapshot builds: armv7 chroot on aarch64 has kyua test -k /usr/tests/Kyuafile sys/kern/kern_copyin hung up [in getpid?], unkillable, prevents reboot

On Jul 6, 2023, at 20:42, Mike Karels wrote: > > > Thanks for isolating this. Let me know when you have the bug number. > I just tested a fix (the compat code drops the reference on the current > address space an extra time, probably freeing it). > > Mike The bug was introduced in January, 20

shell hung in fork system call

Kernel and system at a146207d66f320ed239c1059de9df854b66b55b7 plus some irrelevant local changes, four 64 bit ARM processors, make.conf sets CPUTYPE?=cortex-a57. I typed ^C while /bin/sh was starting a pipeline and my shell got hung in the middle of fork(). >From the terminal: # git log --one

Re: shell hung in fork system call

> On Jul 9, 2023, at 19:25, Konstantin Belousov wrote: > > On Sun, Jul 09, 2023 at 10:41:27PM +0000, John F Carr wrote: >> Kernel and system at a146207d66f320ed239c1059de9df854b66b55b7 plus some >> irrelevant local changes, four 64 bit ARM processors, make.conf sets &

Re: shell hung in fork system call

> On Jul 9, 2023, at 19:59, Konstantin Belousov wrote: > > On Sun, Jul 09, 2023 at 11:36:03PM +0000, John F Carr wrote: >> >> >>> On Jul 9, 2023, at 19:25, Konstantin Belousov wrote: >>> >>> On Sun, Jul 09, 2023 at 10:41:27PM +00

sscanf change prevents build of CURRENT

I had a problem yesterday and today rebuilding a -CURRENT system from source: --- magic.mgc --- ./mkmagic magic magic, 4979: Warning: Current entry does not yet have a description for adding a MIME type mkmagic: could not find any valid magic files! The cause was an sscanf call unexpecte

make installworld fails because /usr/include/c++/v1/__tuple is a file

On arm64 running CURRENT from two weeks ago I updated to c711af772782 Bump __FreeBSD_version for llvm 17.0.6 merge and built and installed from source. make installworld failed: install: target directory `/usr/include/c++/v1/__tuple/' does not exist That pathname is a file: -r--r--r--

Re: How to upgrade an EOL FreeBSD release or how to make it working again

Judging by a commit message BSD on the ARM Chromebook didn't work when support was removed in 2019. >RK* Exynos* and Meson*/Odroid* don't even work with current >source code, if someone wants to make them work again they >better use the Linux DTS. https://cgit.freebsd.org/src/commit?id=9dfa2a54684

Re: armv7-on-aarch64 stuck at urdlck: I got a replication of the "ampere2" bulk build hangup problem on a Windows DevKit 2023

> On Jul 22, 2024, at 12:51, Mark Millard 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 h

Re: armv7-on-aarch64 stuck at urdlck

On Jul 23, 2024, at 13:46, Michal Meloun wrote: > > On 23.07.2024 11:36, Konstantin Belousov wrote: >> On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote: >>> The good news is that I'm finally able to generate a working/locking >>> test case. The culprit (at least for me) is if "-mcpu

Re: armv7-on-aarch64 stuck at urdlck

> On Jul 24, 2024, at 06:50, Konstantin Belousov wrote: > > On Wed, Jul 24, 2024 at 12:34:57PM +0200, m...@freebsd.org wrote: >> >> >> On 24.07.2024 12:24, Konstantin Belousov wrote: >>> On Tue, Jul 23, 2024 at 08:11:13PM +, John F Carr wrote: &g

Emacs tramp mode doesn't work with CURRENT

I use emacs tramp mode, which opens an ssh connection to a remote machine for file access. It works to Linux and FreeBSD 12.1, but not to CURRENT. There has been a change in the way characters are echoed by the shell, with 12.1 treating a consecutive run of backspace as an atomic unit and CURR

Can't build with INVARIANTS but not WITNESS

My -CURRENT kernel has INVARIANTS (inherited from GENERIC) but not WITNESS: include GENERIC ident STRIATUS nooptions WITNESS nooptions WITNESS_SKIPSPIN My kernel build fails: /usr/home/jfc/freebsd/src/sys/kern/vfs_lookup.c:102:13: error: variable 'line' set but not used [-Werror,-

panic: Memory modified after free

My ARM server crashed while running "make installworld installkernel". The message is panic: Memory modified after free 0xa6305e60 (16, malloc-16, devbuf) + 0 = deadc0dedeadc006 The stack trace goes through tmpfs, which could be an innocent victim. The other filesystems are ZFS. There a