Re: Where did the nvd devices go?

2023-06-21 Thread Kevin Oberman
Just found another breakage due to nvd becoming a symlimk. I use gkrellm as my system monitor and, after the update, my SSD showed no activity. Easy fix to edit the configuration to disable nvd0 and enable nda0, but another case of a tool not following the symlink. If I get a little time tomorrow.

Re: Where did the nvd devices go?

2023-06-21 Thread Warner Losh
On Wed, Jun 21, 2023 at 8:47 PM Kevin Oberman wrote: > > Commands used were "gpart show nvd0" and "geli attach -d -k > /dev/nvd0p7". Also tried both with and without the "/dev" which fail for > nvd* and succeed with nda*. > Ah. I see the problem. libgeom doesn't parse the nodes, n

Re: Where did the nvd devices go?

2023-06-21 Thread Kevin Oberman
On Wed, Jun 21, 2023 at 5:52 PM Warner Losh wrote: > > > On Wed, Jun 21, 2023, 6:22 PM Kevin Oberman wrote: > >> Well, they are still around, but not functional. They are symlinks to nda >> devices, but the symlinks don't work well. >> > > They work for filesystem access. > Not too surprised, b

Re: Where did the nvd devices go?

2023-06-21 Thread Warner Losh
On Wed, Jun 21, 2023, 6:22 PM Kevin Oberman wrote: > Well, they are still around, but not functional. They are symlinks to nda > devices, but the symlinks don't work well. > They work for filesystem access. I have no idea when the symlink of nvd to nda happened, but after updating > my system

Where did the nvd devices go?

2023-06-21 Thread Kevin Oberman
Well, they are still around, but not functional. They are symlinks to nda devices, but the symlinks don't work well. I have no idea when the symlink of nvd to nda happened, but after updating my system to main-n263630-ab3e6234ab6e, at least geom related commands no longer function using nvd0p?. I

Re: RTM_NEWNEIGH message for static ARP entry

2023-06-21 Thread Alexander Chernikov
On Wed, 21 Jun 2023, at 5:19 PM, Hartmut Brandt wrote: > Hi, > > when I set a static ARP entry I see an RTM_NEWNEIGH message on a netlink > socket as expected, but the ndm_state is NUD_INCOMPLETE. Should'nt this be > NUD_NOARP? At least this is what Linux returns. Thanks for the report, I’ll t

Re: panic: ASan: Invalid access, 1-byte read at ...

2023-06-21 Thread Peter Holm
On Wed, Jun 21, 2023 at 10:06:28AM -0400, Mark Johnston wrote: > On Wed, Jun 21, 2023 at 11:53:44AM +0200, Peter Holm wrote: > > Just got this panic: > > > > 20230621 11:15:23 all (37/912): linux.sh > > panic: ASan: Invalid access, 1-byte read at 0xfe020bd7

RTM_NEWNEIGH message for static ARP entry

2023-06-21 Thread Hartmut Brandt
Hi, when I set a static ARP entry I see an RTM_NEWNEIGH message on a netlink socket as expected, but the ndm_state is NUD_INCOMPLETE. Should'nt this be NUD_NOARP? At least this is what Linux returns. Cheers, Harti

Re: panic: ASan: Invalid access, 1-byte read at ...

2023-06-21 Thread Mark Johnston
On Wed, Jun 21, 2023 at 11:53:44AM +0200, Peter Holm wrote: > Just got this panic: > > 20230621 11:15:23 all (37/912): linux.sh > panic: ASan: Invalid access, 1-byte read at 0xfe020bd78e9f, > RedZonePartial(2) > cpuid = 1 > time = 1687338930 > KDB: stack backtrace:

panic: ASan: Invalid access, 1-byte read at ...

2023-06-21 Thread Peter Holm
Just got this panic: 20230621 11:15:23 all (37/912): linux.sh panic: ASan: Invalid access, 1-byte read at 0xfe020bd78e9f, RedZonePartial(2) cpuid = 1 time = 1687338930 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0xa5/frame 0xfe01f16abc10 kdb_backtrace() at

Re: kernel: sonewconn: pcb 0xfffff8002b255a00 (local:/var/run/devd.seqpacket.pipe): Listen queue overflow: 1 already in queue awaiting acceptance (60 occurrences), ?

2023-06-21 Thread Alexander Leidinger
Quoting Gary Jennejohn (from Tue, 20 Jun 2023 14:41:41 +): On Tue, 20 Jun 2023 12:04:13 +0200 Alexander Leidinger wrote: "listen X backlog=y" and "sysctl kern.ipx.somaxconn=X" for FreeBSD On my FreeBSD14 system these things are all under kern.ipc. Typo on my side... it was supposed