Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld
void <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <aRI2y_cxmh_4Q6QE@int21h> |
On Mon, Nov 10, 2025 at 07:39:51AM -0800, bob prohaska wrote: >Did the machine hang entirely? If so, how did you recover control? locked solid. rebooted. The machine responded ok interactively until that point. I don't know what would cause a stack overflow, a programming error maybe? After rebooting, resuming the buildkernel with -j2 allowed it to complete. The reasoning behind using nfs for /usr/src /usr/obj and /var/cache/ccache from another machine is that it's so much faster and responsive than usb2 on rpi2b+ which seems to get bogged down with reads/writes on usb2 (same effect seen when using git to update). When using nfs this way the machine is always responsive for interactive work. But, I had to abandon testing in the end due to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 which wasn't triggered with a buildkernel/installkernel, but was with a buildworld. The patch in comment #3 didn't fix the problem for me (16:current) --