freebsd-arm@FreeBSD.org

Porting FreeBSD to ARM processors

Go to: [ monthly archives ] [ by author ] [ by date ]

November 2025 Archives by thread

Re: FYI: main-arm64 port-packages built per Hr. on ampere2, some history and comparisons/contrasts: Mark Millard (Sat, 01 Nov 2025 02:18:19 UTC)
Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: bob prohaska (Sat, 01 Nov 2025 15:18:29 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: Adrian Chadd (Sat, 01 Nov 2025 15:57:13 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: Mark Millard (Sat, 01 Nov 2025 16:36:41 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: Adrian Chadd (Sat, 01 Nov 2025 17:22:37 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: Mark Millard (Sat, 01 Nov 2025 17:45:18 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: Mark Millard (Sat, 01 Nov 2025 18:26:37 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: Mark Millard (Sat, 01 Nov 2025 18:59:10 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: Konstantin Belousov (Sat, 01 Nov 2025 17:50:42 UTC)
Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: bob prohaska (Sat, 01 Nov 2025 19:07:44 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: bob prohaska (Sun, 02 Nov 2025 23:47:04 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: Mark Millard (Sat, 01 Nov 2025 16:05:09 UTC)

Re: Buildkernel fails in /usr/obj/usr/src/arm.armv7/sys/GENERIC/vchiq_shim.o: Adrian Chadd (Sat, 01 Nov 2025 16:36:30 UTC)

rk356x sound: titus (Sun, 02 Nov 2025 13:19:25 UTC)
I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Mario Marietto (Sun, 02 Nov 2025 16:13:05 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Adrian Chadd (Tue, 04 Nov 2025 19:05:48 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Warner Losh (Tue, 04 Nov 2025 19:11:11 UTC)
Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Mark Millard (Tue, 04 Nov 2025 19:16:45 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Warner Losh (Tue, 04 Nov 2025 19:25:08 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Mark Millard (Tue, 04 Nov 2025 21:37:35 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Adrian Chadd (Wed, 05 Nov 2025 07:28:52 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Warner Losh (Wed, 05 Nov 2025 08:21:08 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Mario Marietto (Wed, 05 Nov 2025 10:48:37 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Adrian Chadd (Wed, 05 Nov 2025 15:02:37 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Andrew Turner (Tue, 11 Nov 2025 16:49:12 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Mario Marietto (Thu, 13 Nov 2025 07:44:06 UTC)

Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Mark Millard (Thu, 13 Nov 2025 15:46:15 UTC)

Problem reports for freebsd-arm@FreeBSD.org that need special attention: bugzilla-noreply_at_FreeBSD.org (Sun, 02 Nov 2025 21:00:39 UTC)
[Bug 245160] allow selection of am335x rtc external / internal clock source: bugzilla-noreply_at_freebsd.org (Mon, 03 Nov 2025 13:07:14 UTC)
acpica-tools-20250807 fails to build for armv7: error: format specifies type 'unsigned long' but the argument has type 'UINT64' (aka 'unsigned long long'): Mark Millard (Wed, 05 Nov 2025 15:10:36 UTC)

Re: acpica-tools-20250807 fails to build for armv7: error: format specifies type 'unsigned long' but the argument has type 'UINT64' (aka 'unsigned long long'): Robert Clausecker (Wed, 05 Nov 2025 15:29:13 UTC)

Re: acpica-tools-20250807 fails to build for armv7: error: format specifies type 'unsigned long' but the argument has type 'UINT64' (aka 'unsigned long long'): Mark Millard (Wed, 05 Nov 2025 15:41:37 UTC)

libunwind-20250904 fails to build for armv7: error: implement UNW_ARM_FRAME_SIGRETURN on FreeBSD: Mark Millard (Wed, 05 Nov 2025 15:35:45 UTC)

Re: libunwind-20250904 fails to build for armv7: error: implement UNW_ARM_FRAME_SIGRETURN on FreeBSD: Mark Millard (Wed, 05 Nov 2025 15:48:24 UTC)

fuz@ : do you want bugzilla-submitals for armv7 port-package build problems generally?: Mark Millard (Wed, 05 Nov 2025 16:10:45 UTC)
Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Mark Millard (Wed, 05 Nov 2025 21:19:58 UTC)
Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Thu, 06 Nov 2025 14:04:52 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Ronald Klop (Thu, 06 Nov 2025 14:45:01 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Thu, 06 Nov 2025 16:38:28 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Mark Millard (Thu, 06 Nov 2025 18:00:19 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Fri, 07 Nov 2025 02:22:37 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Mark Millard (Fri, 07 Nov 2025 04:15:49 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Fri, 07 Nov 2025 16:16:47 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Mark Millard (Fri, 07 Nov 2025 17:02:43 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Paul Mather (Fri, 07 Nov 2025 15:42:24 UTC)

mongodb - Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Ronald Klop (Fri, 07 Nov 2025 15:55:59 UTC)

Re: mongodb - Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Paul Mather (Fri, 07 Nov 2025 16:26:07 UTC)

Re: mongodb - Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: John Kennedy (Fri, 07 Nov 2025 17:06:45 UTC)
Re: mongodb - Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Mark Millard (Fri, 07 Nov 2025 18:14:20 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Mark Millard (Fri, 07 Nov 2025 16:41:13 UTC)
Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Fri, 07 Nov 2025 16:49:05 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: void (Sun, 09 Nov 2025 04:07:20 UTC)
Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: void (Mon, 10 Nov 2025 00:44:27 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Mon, 10 Nov 2025 15:39:51 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: void (Mon, 10 Nov 2025 19:02:35 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Tue, 11 Nov 2025 01:46:54 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Mark Millard (Fri, 14 Nov 2025 21:57:44 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Mark Millard (Fri, 14 Nov 2025 22:04:44 UTC)

RETITLED: On aarch64 in a armv7 chroot, I've reproduced the armv7: jemalloc/internal/ehooks.h:170: Failed assertion: "p[i] == 0": Mark Millard (Fri, 14 Nov 2025 23:49:07 UTC)

Re: RETITLED: On aarch64 in a armv7 chroot, I've reproduced the armv7: jemalloc/internal/ehooks.h:170: Failed assertion: "p[i] == 0" [adding: small memory aarch64 behavior]: Mark Millard (Sat, 15 Nov 2025 22:02:56 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Tue, 25 Nov 2025 02:07:26 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Mark Millard (Tue, 25 Nov 2025 03:40:21 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Tue, 25 Nov 2025 15:48:01 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: bob prohaska (Tue, 25 Nov 2025 03:56:56 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: void (Tue, 18 Nov 2025 13:47:49 UTC)

Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld: Ronald Klop (Fri, 07 Nov 2025 17:19:02 UTC)
Problem reports for freebsd-arm@FreeBSD.org that need special attention: bugzilla-noreply_at_FreeBSD.org (Sun, 09 Nov 2025 21:00:40 UTC)
Re: I ported the panfrost driver on FreeBSD 15.0 for my radxa zero 3W board,BUT....: Mark Millard (Sun, 09 Nov 2025 22:30:21 UTC)
[Bug 290411] lib32: __syscall() not supported: bugzilla-noreply_at_freebsd.org (Mon, 10 Nov 2025 11:01:57 UTC)
official ruby33's rdoc build failed for main-arm64-default: ld-elf.so.1: /usr/local/lib/libunwind.so.8: Undefined symbol "__aarch64_ldadd4_acq_rel": Mark Millard (Mon, 10 Nov 2025 15:14:14 UTC)

Re: official ruby33's rdoc build failed for main-arm64-default: ld-elf.so.1: /usr/local/lib/libunwind.so.8: Undefined symbol "__aarch64_ldadd4_acq_rel": Mark Millard (Mon, 10 Nov 2025 16:50:15 UTC)

kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: void (Mon, 10 Nov 2025 23:29:10 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: void (Mon, 10 Nov 2025 23:33:24 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: Mark Millard (Tue, 11 Nov 2025 00:27:05 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: bob prohaska (Tue, 11 Nov 2025 01:40:49 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: void (Tue, 11 Nov 2025 12:45:35 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: Ronald Klop (Tue, 11 Nov 2025 12:55:20 UTC)
Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: bob prohaska (Tue, 11 Nov 2025 16:30:54 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: void (Tue, 11 Nov 2025 17:09:46 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: bob prohaska (Tue, 11 Nov 2025 18:53:55 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: Mark Millard (Tue, 11 Nov 2025 22:30:35 UTC)
Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: void (Wed, 12 Nov 2025 01:10:31 UTC)

was: configured swap now: relative rpi2+ ufs2 nfs random rw speeds: void (Wed, 12 Nov 2025 12:39:46 UTC)

Re: was: configured swap now: relative rpi2+ ufs2 nfs random rw speeds: bob prohaska (Wed, 12 Nov 2025 21:58:26 UTC)
Re: was: configured swap now: relative rpi2+ ufs2 nfs random rw speeds: void (Wed, 12 Nov 2025 23:22:31 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: Dag-Erling_Smørgrav (Tue, 11 Nov 2025 15:34:43 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: bob prohaska (Tue, 11 Nov 2025 16:46:47 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: Dag-Erling_Smørgrav (Tue, 11 Nov 2025 16:58:45 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: Mark Millard (Tue, 11 Nov 2025 18:24:47 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: bob prohaska (Tue, 11 Nov 2025 19:03:31 UTC)

Re: kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount: Mark Millard (Tue, 11 Nov 2025 17:22:45 UTC)

[Bug 290951] on brand new armv7 image kernel: warning: total configured swap (493567 pages) exceeds maximum recommended amount (493248 pages).": bugzilla-noreply_at_freebsd.org (Tue, 11 Nov 2025 12:32:33 UTC)
main [so: 16] armv7 chroot and lib32 use: example fio command works on real armv7 system boots but fails on aarch64 chroot or lib32 use: Mark Millard (Tue, 11 Nov 2025 22:09:23 UTC)
[Bug 290962] armv7 chroot and lib32 use on aarch64: example fio command works on real armv7 system boots but fails for aarch64-to-armv7 chroot or lib32 use: bugzilla-noreply_at_freebsd.org (Tue, 11 Nov 2025 22:15:21 UTC)
FreeBSD on Zynq (Cortex-A9), new Phy for cgem0?: Shiro (Wed, 12 Nov 2025 19:18:08 UTC)

Re: FreeBSD on Zynq (Cortex-A9), new Phy for cgem0?: Milan Obuch (Wed, 12 Nov 2025 19:32:22 UTC)

Re: FreeBSD on Zynq (Cortex-A9), new Phy for cgem0?: Shiro (Thu, 13 Nov 2025 19:49:19 UTC)

Re: FreeBSD on Zynq (Cortex-A9), new Phy for cgem0?: Milan Obuch (Thu, 13 Nov 2025 20:23:14 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Wed, 12 Nov 2025 22:25:02 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Ronald Klop (Thu, 13 Nov 2025 08:11:51 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Warner Losh (Thu, 13 Nov 2025 08:17:52 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Fri, 14 Nov 2025 03:44:55 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Herbert J. Skuhra (Fri, 14 Nov 2025 07:31:26 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Fri, 14 Nov 2025 15:45:45 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Herbert J. Skuhra (Sat, 15 Nov 2025 10:04:08 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Sat, 15 Nov 2025 21:34:52 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Warner Losh (Sat, 15 Nov 2025 23:08:50 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Sun, 16 Nov 2025 15:43:54 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Warner Losh (Sun, 16 Nov 2025 17:51:01 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Michal Meloun (Sun, 16 Nov 2025 21:11:15 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Konstantin Belousov (Mon, 17 Nov 2025 02:03:50 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Mark Millard (Mon, 17 Nov 2025 03:04:12 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Mark Millard (Mon, 17 Nov 2025 08:24:16 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Mark Millard (Mon, 17 Nov 2025 09:15:13 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [only main 16 does the check]: Mark Millard (Mon, 17 Nov 2025 15:13:56 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Fri, 21 Nov 2025 03:34:28 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Mark Millard (Fri, 21 Nov 2025 04:16:55 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Fri, 21 Nov 2025 14:55:40 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [kib committed git: 72a447d0bc76 that should help]: Mark Millard (Mon, 24 Nov 2025 18:34:04 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Ronald Klop (Thu, 13 Nov 2025 09:52:10 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Michal Meloun (Thu, 13 Nov 2025 10:38:08 UTC)

openjdk11 compile fail on armv7 - (Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld): Ronald Klop (Fri, 14 Nov 2025 12:50:54 UTC)

Re: openjdk11 compile fail on armv7 - (Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld): Mark Millard (Fri, 14 Nov 2025 13:15:52 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Mark Millard (Thu, 13 Nov 2025 15:28:21 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Thu, 13 Nov 2025 14:41:49 UTC)
native armv7 for struct aiocb offsets and overall size vs. aarch64 for struct aiocb32 offsets and overall size: most fields do not match: Mark Millard (Thu, 13 Nov 2025 22:01:37 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Fri, 14 Nov 2025 15:25:27 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Mark Millard (Fri, 14 Nov 2025 17:16:57 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Fri, 14 Nov 2025 19:25:54 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Mark Millard (Fri, 14 Nov 2025 20:14:57 UTC)

Re: D43399 FreeBSD Review, enable VCHIQ HDMI Audio subsystem for BCM2711 Raspberry Pi 4B, 400 adding 3 patch files.: Adrian Chadd (Sat, 15 Nov 2025 15:47:21 UTC)

Re: D43399 FreeBSD Review, enable VCHIQ HDMI Audio subsystem for BCM2711 Raspberry Pi 4B, 400 adding 3 patch files.: Nuno Teixeira (Sun, 16 Nov 2025 11:39:07 UTC)

WITHOUT_CLEAN confusion in -current: void (Mon, 17 Nov 2025 01:14:17 UTC)

Re: WITHOUT_CLEAN confusion in -current: Herbert J. Skuhra (Mon, 17 Nov 2025 05:57:18 UTC)
Re: WITHOUT_CLEAN confusion in -current: Warner Losh (Mon, 17 Nov 2025 06:29:07 UTC)

Re: WITHOUT_CLEAN confusion in -current: void (Mon, 17 Nov 2025 09:31:54 UTC)

RE: WITHOUT_CLEAN confusion in -current: Mark Millard (Mon, 17 Nov 2025 05:57:42 UTC)
[Bug 246865] c++: error: unable to execute command: Killed: bugzilla-noreply_at_freebsd.org (Mon, 17 Nov 2025 10:14:05 UTC)
FYI: linux 6.18 arm64 update: Use load LSE atomics for the non-return per-CPU atomic operations: Mark Millard (Mon, 17 Nov 2025 14:43:55 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: bob prohaska (Mon, 17 Nov 2025 15:38:09 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Adrian Chadd (Tue, 18 Nov 2025 03:53:15 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld: Mark Millard (Tue, 18 Nov 2025 05:08:29 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [gdb backtrace!]: Mark Millard (Tue, 18 Nov 2025 18:18:04 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [gdb backtrace! End of area has 0x5a5a5a5a sequence]: Mark Millard (Tue, 18 Nov 2025 18:39:06 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [gdb backtrace! End of area has 0x5a5a5a5a sequence]: Mark Millard (Tue, 18 Nov 2025 21:44:59 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #1]: Mark Millard (Wed, 19 Nov 2025 00:29:08 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #1]: Mark Millard (Wed, 19 Nov 2025 01:05:51 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #1]: Mark Millard (Wed, 19 Nov 2025 01:14:46 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #2]: Mark Millard (Wed, 19 Nov 2025 01:24:12 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #3]: Mark Millard (Wed, 19 Nov 2025 01:57:21 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #4] [New common range #0..#10 __je_pa_alloc]: Mark Millard (Wed, 19 Nov 2025 03:03:16 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #5] [Common range #0..#10 __je_pa_alloc]: Mark Millard (Wed, 19 Nov 2025 06:10:19 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #5] [Common range #0..#10 __je_pa_alloc]: Mark Millard (Wed, 19 Nov 2025 17:53:13 UTC)
Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #5] [Common range #0..#10 __je_pa_alloc]: Mark Millard (Wed, 19 Nov 2025 21:04:25 UTC)

FYI: RPi5 power consumption reply [Not on topic for original "Future of armv7" message]: Mark Millard (Mon, 17 Nov 2025 16:59:54 UTC)

Re: FYI: RPi5 power consumption reply [Not on topic for original "Future of armv7" message]: Tomek CEDRO (Mon, 17 Nov 2025 18:05:35 UTC)

[Bug 269726] kern.msgbufsize=4587520 in loader.conf, kernel never boots: bugzilla-noreply_at_freebsd.org (Tue, 18 Nov 2025 22:05:55 UTC)
eqos on Panther X2 RK3566: qroxana (Thu, 20 Nov 2025 07:01:26 UTC)

Re: eqos on Panther X2 RK3566: Milan Obuch (Thu, 20 Nov 2025 07:13:56 UTC)

Re: eqos on Panther X2 RK3566: qroxana (Thu, 20 Nov 2025 08:15:24 UTC)

Re: eqos on Panther X2 RK3566: Milan Obuch (Thu, 20 Nov 2025 11:48:12 UTC)

Re: eqos on Panther X2 RK3566: Søren_Schmidt (Thu, 20 Nov 2025 17:40:06 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ]: Mark Millard (Thu, 20 Nov 2025 23:38:16 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ]: Mark Millard (Fri, 21 Nov 2025 00:03:17 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ]: Mark Millard (Fri, 21 Nov 2025 16:30:54 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] [failed without new kernel check detection]: Mark Millard (Fri, 21 Nov 2025 18:29:36 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] [failed without new kernel check detection]: Mark Millard (Fri, 21 Nov 2025 19:34:21 UTC)

Re: Still seeing Failed assertion: "p[i] == 0" [ junk:true vs. junk:alloc,zero:true ]: Mark Millard (Sat, 22 Nov 2025 15:01:39 UTC)

bug in sys/dev/[extres]/nvmem/nvmem.c: titus (Sat, 22 Nov 2025 08:58:56 UTC)

Re: bug in sys/dev/[extres]/nvmem/nvmem.c: Adrian Chadd (Sat, 22 Nov 2025 22:30:34 UTC)

Re: bug in sys/dev/[extres]/nvmem/nvmem.c: Emmanuel Vadot (Sun, 23 Nov 2025 07:37:48 UTC)

Re: bug in sys/dev/[extres]/nvmem/nvmem.c: titus (Sun, 23 Nov 2025 07:57:34 UTC)
Re: bug in sys/dev/[extres]/nvmem/nvmem.c: titus (Sun, 23 Nov 2025 10:59:34 UTC)

wlan0 goes down but system doesn't notice: bob prohaska (Sun, 23 Nov 2025 02:18:43 UTC)

Re: wlan0 goes down but system doesn't notice: Adrian Chadd (Sun, 23 Nov 2025 04:14:49 UTC)

Re: wlan0 goes down but system doesn't notice: bob prohaska (Sun, 23 Nov 2025 15:15:24 UTC)

Re: wlan0 goes down but system doesn't notice: Adrian Chadd (Sun, 23 Nov 2025 15:44:51 UTC)

Re: wlan0 goes down but system doesn't notice: bob prohaska (Mon, 24 Nov 2025 15:19:28 UTC)

allwinner gpio bank offset: Titus Manea (Tue, 25 Nov 2025 12:12:06 UTC)

Go to: [ monthly archives ] [ by author ] [ by date ]