Re: FYI: amd64 system: "error: fileid changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR MIDDLEWARE)"?

On 2021-Nov-18, at 15:54, Mark Millard wrote: > The ThreadRipper 1950X FreeBSD system is reporting a message at > 03:01:10 or so for the last 3 days. The .148 is a aarch64 system > (HoneyComb). None of the other systems (aarch64 Small Board > Computers and a armv7 SBC) are reporting such. > > No

FYI: amd64 system: "error: fileid changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR MIDDLEWARE)"?

The ThreadRipper 1950X FreeBSD system is reporting a message at 03:01:10 or so for the last 3 days. The .148 is a aarch64 system (HoneyComb). None of the other systems (aarch64 Small Board Computers and a armv7 SBC) are reporting such. Nov 16 03:01:10 amd64_ZFS kernel: newnfs: server '192.168.1.14

Re: "Khelp module "ertt" can't unload until its refcount drops from 1 to 0." after "All buffers synced."?

> On 2021-Nov-18, at 12:31, tue...@freebsd.org wrote: > >> On 17. Nov 2021, at 21:13, Mark Millard via freebsd-current >> wrote: >> >> I've not noticed the ertt message before in: >> >> . . . >> Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done >> All buffers synce

Re: 14.0-CURRENT panic in early boot

It was 16 days ago, so just a tad over 2 weeks :). Indeed, I'll start a bisect here in a few and I'll update as soon as I know. I figured I'd ask ahead of time before I did the work :). Thanks! -Dustin On Thu, Nov 18, 2021 at 12:29 PM Juraj Lutter wrote: > > > > On 18 Nov 2021, at 18:46, Karel

Re: "Khelp module "ertt" can't unload until its refcount drops from 1 to 0." after "All buffers synced."?

> On 17. Nov 2021, at 21:13, Mark Millard via freebsd-current > wrote: > > I've not noticed the ertt message before in: > > . . . > Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done > All buffers synced. > Uptime: 1d9h57m18s > Khelp module "ertt" can't unload until i

Re: aarch64(?) poudiere-devel based builds seem to get fairly-rare corrupted files after recent system update(s?)

On 2021-Nov-17, at 11:17, Mark Millard wrote: > On 2021-Nov-15, at 15:43, Mark Millard wrote: > >> On 2021-Nov-15, at 13:13, Mark Millard wrote: >> >>> On 2021-Nov-15, at 12:51, Mark Millard wrote: >>> On 2021-Nov-15, at 11:31, Mark Millard wrote: > I updated from (shown a s

Re: HEADS-UP: ASLR for 64-bit executables enabled by default on main

Hi, czw., 18 lis 2021 o 19:07 Li-Wen Hsu napisał(a): > > On Wed, Nov 17, 2021 at 6:30 AM Marcin Wojtas wrote: > > > > As of b014e0f15bc7 the ASLR (Address Space Layout > > Randomization) feature becomes enabled for the all 64-bit > > binaries by default. > > > > Address Space Layout Randomizatio

Re: 14.0-CURRENT panic in early boot

> On 18 Nov 2021, at 18:46, Karel Gardas wrote: > > > Completely speculating, but since you don't see ioapic's are you sure this is > just ~2 weeks old build? If not, then it may be relevant to: Bisecting would be a better approach. otis > > commit 1b7a2680fba589daf6f700565214919cb941ab56

Re: HEADS-UP: ASLR for 64-bit executables enabled by default on main

On Wed, Nov 17, 2021 at 6:30 AM Marcin Wojtas wrote: > > As of b014e0f15bc7 the ASLR (Address Space Layout > Randomization) feature becomes enabled for the all 64-bit > binaries by default. > > Address Space Layout Randomization (ASLR) is an exploit mitigation > technique implemented in the majori

Re: 14.0-CURRENT panic in early boot

Completely speculating, but since you don't see ioapic's are you sure this is just ~2 weeks old build? If not, then it may be relevant to: commit 1b7a2680fba589daf6f700565214919cb941ab56 Author: Jung-uk Kim Date: Thu Sep 30 16:23:21 2021 -0400 Import ACPICA 20210930 (cherry picke