Re: Profiled libraries on freebsd-current
On Fri, 29 Apr 2022 at 01:58, Steve Kargl wrote: > > If one looks at src.conf(5), one finds > >WITH_PROFILE > Build profiled libraries for use with gprof(8). This option is > deprecated and is not present in FreeBSD 14. > > I assume that the *_p.a libraries will no longer be built and > installed on FreeBSD 14 and later. Is this correct? FreeBSD 14 is not yet released, of course, but that is indeed the intent. PR256874 reports that a GCC patch (to stop linking against _p.a) is in the works but unfortunately has not had an update for some time.
Re: Profiled libraries on freebsd-current
On Sat, Apr 30, 2022 at 09:39:32AM -0400, Ed Maste wrote: > On Fri, 29 Apr 2022 at 01:58, Steve Kargl > wrote: > > > > If one looks at src.conf(5), one finds > > > >WITH_PROFILE > > Build profiled libraries for use with gprof(8). This option is > > deprecated and is not present in FreeBSD 14. > > > > I assume that the *_p.a libraries will no longer be built and > > installed on FreeBSD 14 and later. Is this correct? > > FreeBSD 14 is not yet released, of course, but that is indeed the > intent. PR256874 reports that a GCC patch (to stop linking against > _p.a) is in the works but unfortunately has not had an update for some > time. I see. It only took me 2+ years to get https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89125 committed to the GCC repository. Good luck with getting your patch upstream. -- Steve
Re: "pkg upgrade" failing with "Fail to create temporary file: ... Not a directory"
On Thu, Apr 28, 2022 at 10:43 AM Christoph Moench-Tegeder wrote: > > ## Michael Schuster (michaelspriv...@gmail.com): > > > $subject happened to me just now on current. I researched it on the > > internet, > > Don't look that far, the answer is in UPDATING: > 20220426: > AFFECTS: users of deskutils/grantleetheme thx all - that was the relevant hint here. regards Michael > > Regards, > Christoph > > -- > Spare Space -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion'
Re: ext2fs: WARNING: mount of XXXX denied due to unsupported optional features: needs_recovery
On Thu, 28 Apr 2022 13:36:21 -0600 Alan Somers wrote: > On Thu, Apr 28, 2022 at 1:29 PM Marek Zarychta > wrote: > > > > W dniu 28.04.2022 o 21:21, FreeBSD User pisze: > > > Running XigmaNAS 12.3.0.4.9009 on amd64 hardware, we try to mount HDD to > > > rescue > > > them and store the data on ZFS volumes. Mounting of the HDD doesn't work, > > > FreeBSD > > > 12.3 obviously lack in some etx2 features, namely "needs_recovery". The > > > kernel > > > reports: > > > > > > WARNING: mount of da4p3 denied due to unsupported optional features: > > > needs_recovery > > > > > > How can this problem be solved? > > > > > > Thanks in advance, > > > > > > oh > > > > > Probably as the name of the mailing list suggest you should upgrade to > > 14.0-CURRENT and maybe run fsck.ext2(8) on this partition to fix it. > > > > -- > > Marek Zarychta > > > > You might also try sysutils/fusefs-ext2 from ports. > Hi all, thanks for the response. First of all, I'm bound to FreeBSD 12.3, which is the base for XigmaNAS (used for the ease of use for those colleagues without FreeBSD experience). No clue, when this project will jump over to 13.0 or 13.1. Last time I installed ports on Xigmanas itself and tried to remove those ports, some of the base system essential also got removed - so the system was wrecked. Therefore, I'm planning to try jails and grant access to the jail and try to bind/mount the HDDs in question into the jail for backup - if this task is not an impossible mission on FBSD. Last, but the most problematic issue is: I do not know what the HDDs filesystem in reality really is! There is an EFI partition (FAT32), there is a second one, fstyp report unknown and here is the large partition identified as ext2fs by fstyp. But I think he former administration in the department used LVM on the more recent Linux boxes, so I might have to deal with that also. Kind regards, O. Hartmann Another issue on several of those HDDs in question seems to be
Re: Profiled libraries on freebsd-current
On Sat, 30 Apr 2022 at 11:34, Steve Kargl wrote: > > On Sat, Apr 30, 2022 at 09:39:32AM -0400, Ed Maste wrote: > > On Fri, 29 Apr 2022 at 01:58, Steve Kargl > > wrote: > > > > > > If one looks at src.conf(5), one finds > > > > > >WITH_PROFILE > > > Build profiled libraries for use with gprof(8). This option is > > > deprecated and is not present in FreeBSD 14. > > > > > > I assume that the *_p.a libraries will no longer be built and > > > installed on FreeBSD 14 and later. Is this correct? > > > > FreeBSD 14 is not yet released, of course, but that is indeed the > > intent. PR256874 reports that a GCC patch (to stop linking against > > _p.a) is in the works but unfortunately has not had an update for some > > time. > > I see. It only took me 2+ years to get > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89125 > > committed to the GCC repository. Good luck with > getting your patch upstream. Heh, thanks. I have just now changed the WITH_PROFILE description to state "a future version of FreeBSD" since it may well not happen for FreeBSD 14. We could also just install libc_p.a as a symlink to libc.a (and same for the other _p.a archives).
Kernel panic on armv7 when PF is enabled
After git bisecting the panic started since this commit. commit 78bc3d5e1712bc1649aa5574d2b8d153f9665113 Author: Kristof Provost < k...@freebsd.org > Date: Mon Feb 14 20:09:54 2022 +0100 vlan: allow net.link.vlan.mtag_pcp to be set per vnet The primary reason for this change is to facilitate testing. MFC after: 1 week sys/net/if_ethersubr.c | 9 + sys/net/if_vlan.c | 5 +++-- 2 files changed, 8 insertions(+), 6 deletions(-) The armv7 board boots from a NFS root, it can boot without any problem if PF is disabled. Any helps? add host ::1: gateway lo0 fib 0: route already in table add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net :::0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Enabling pf. Kernel page fault with the following non-sleepable locks held: shared rm pf rulesets (pf rulesets) r = 0 (0xe3099430) locked @ /usr/src/sys/netpfil/pf/pf.c:6493 exclusive rw tcpinp (tcpinp) r = 0 (0xdb748d88) locked @ /usr/src/sys/netinet/tcp_usrreq.c:1008 stack backtrace: #0 0xc0355cac at witness_debugger+0x7c #1 0xc0356ef0 at witness_warn+0x3fc #2 0xc05ec048 at abort_handler+0x1d8 #3 0xc05cb5ac at exception_exit+0 #4 0xe3083c10 at pf_syncookie_validate+0x60 #5 0xe30496a8 at pf_test+0x518 #6 0xe306d768 at pf_check_out+0x30 #7 0xc0415b44 at pfil_run_hooks+0xbc #8 0xc0445cfc at ip_output+0xce8 #9 0xc045bc9c at tcp_default_output+0x20ac #10 0xc0471eb4 at tcp_usr_send+0x1ac #11 0xc0389464 at sosend_generic+0x490 #12 0xc0389790 at sosend+0x64 #13 0xc0502888 at clnt_vc_call+0x560 #14 0xc05009d8 at clnt_reconnect_call+0x170 #15 0xc01e7b14 at newnfs_request+0xb20 #16 0xc0230218 at nfscl_request+0x60 #17 0xc020d9bc at nfsrpc_getattr+0xb0 Fatal kernel mode data abort: 'Alignment Fault' on read trapframe: 0xdf1f1c90 FSR=0001, FAR=d7840264, spsr=4013 r0 =6a228eda, r1 =dac0d785, r2 =d7840264, r3 =db5527c0 r4 =df1f1e00, r5 =dac0d75f, r6 =0018, r7 =d9422c00 r8 =c093e5e4, r9 =0001, r10=df1f1f5c, r11=df1f1d38 r12=e3098dd0, ssp=df1f1d20, slr=e3083bdc, pc =e3083c10 panic: Fatal abort cpuid = 1 time = 1651366089 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc05c8c00 lr = 0xc007ac8c (db_trace_self_wrapper+0x30) sp = 0xdf1f1a68 fp = 0xdf1f1b80 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc007ac8c lr = 0xc02e289c (vpanic+0x170) sp = 0xdf1f1b88 fp = 0xdf1f1ba8 r4 = 0x0100 r5 = 0x r6 = 0xc0780529 r7 = 0xc090ea10 vpanic() at vpanic+0x170 pc = 0xc02e289c lr = 0xc02e264c (doadump) sp = 0xdf1f1bb0 fp = 0xdf1f1bb4 r4 = 0xdf1f1c90 r5 = 0x0013 r6 = 0xd7840264 r7 = 0x0001 r8 = 0x0001 r9 = 0xdb5527c0 r10 = 0xd7840264 doadump() at doadump pc = 0xc02e264c lr = 0xc05ec698 (abort_align) sp = 0xdf1f1bbc fp = 0xdf1f1be8 r4 = 0xd7840264 r5 = 0xdf1f1bb4 r6 = 0xc02e264c r10 = 0xdf1f1bbc abort_align() at abort_align pc = 0xc05ec698 lr = 0xc05ec198 (abort_handler+0x328) sp = 0xdf1f1bf0 fp = 0xdf1f1c88 r4 = 0x0013 r5 = 0xd7840264 abort_handler() at abort_handler+0x328 pc = 0xc05ec198 lr = 0xc05cb5ac (exception_exit) sp = 0xdf1f1c90 fp = 0xdf1f1d38 r4 = 0xdf1f1e00 r5 = 0xdac0d75f r6 = 0x0018 r7 = 0xd9422c00 r8 = 0xc093e5e4 r9 = 0x0001 r10 = 0xdf1f1f5c exception_exit() at exception_exit pc = 0xc05cb5ac lr = 0xe3083bdc (pf_syncookie_validate+0x2c) sp = 0xdf1f1d20 fp = 0xdf1f1d38 r0 = 0x6a228eda r1 = 0xdac0d785 r2 = 0xd7840264 r3 = 0xdb5527c0 r4 = 0xdf1f1e00 r5 = 0xdac0d75f r6 = 0x0018 r7 = 0xd9422c00 r8 = 0xc093e5e4 r9 = 0x0001 r10 = 0xdf1f1f5c r12 = 0xe3098dd0 pf_syncookie_validate() at pf_syncookie_validate+0x60 pc = 0xe3083c10 lr = 0xe30496a8 (pf_test+0x518) sp = 0xdf1f1d40 fp = 0xdf1f1ea8 r4 = 0x0002 r5 = 0xdb4a6100 r6 = 0x0018 r7 = 0xd9422c00 r8 = 0x0002 r9 = 0x0001 pf_test() at pf_test+0x518 pc = 0xe30496a8 lr = 0xe306d768 (pf_check_out+0x30) sp = 0xdf1f1eb0 fp = 0xdf1f1ec0 r4 = 0xdf1f1f5c r5 = 0xe306d738 r6 = 0xdb6ba660 r7 = 0x r8 = 0xd9422c00 r9 = 0xdb748d80 r10 = 0xfff7 pf_check_out() at pf_check_out+0x30 pc = 0xe306d768 lr = 0xc0415b44 (pfil_run_hooks+0xbc) sp = 0xdf1f1ec8 fp = 0xdf1f1ef0 r4 = 0x0002 r5 = 0xe306d738 pfil_run_hooks() at pfil_run_hooks+0xbc pc = 0xc0415b44 lr = 0xc0445cfc (ip_output+0xce8) sp = 0xdf1f1ef8 fp = 0xdf1f1fa8 r4 = 0x010a r5 = 0x0a0a r6 = 0xdb4a6158 r7 = 0xc0946908 r8 = 0xdb5bec00 r9 = 0xd9422c00 r10 = 0x05dc ip_output() at ip_output+0xce8 pc = 0xc0445cfc lr = 0xc045bc9c (tcp_default_output+0x20ac) sp = 0xdf1f1fb0 f
