It seems ${MAKEOBJDIR} was not created for usr.bin/clang/llvm-objcopy.
--- all_subdir_usr.bin ---
--- objwarn ---
Warning: Object directory not changed from original
/usr/src/usr.bin/clang/llvm-objcopy
--- COFF/COFFObjcopy.o ---
c++ -target aarch64-unknown-freebsd14.0
--sysroot=/usr/obj/usr/src/
--- Original Message ---
On Monday, January 23rd, 2023 at 10:02 AM, Dimitry Andric
wrote:
> On 23 Jan 2023, at 04:05, qroxana qrox...@protonmail.com wrote:
>
> > It seems ${MAKEOBJDIR} was not created for usr.bin/clang/llvm-objcopy.
> >
> > --- all_subdir_usr
--- Original Message ---
On Monday, January 23rd, 2023 at 1:44 PM, qroxana
wrote:
> --- Original Message ---
> On Monday, January 23rd, 2023 at 10:02 AM, Dimitry Andric d...@freebsd.org
> wrote:
>
>
>
> > On 23 Jan 2023, at 04:05, qroxana qrox
/etc/rc failed to run "mount -uw /" when booting from NFS root,
this happened after the commit 906c312bbf7493ccbcce883936d67e5c66a9c3c2,
the previous commit works fine.
+ mount -uw /
af 1 sotype 1 not supported
+ echo 'Mounting root filesystem rw failed, startup aborted'
Mounting root filesystem r
- Original Message ---
On Sunday, January 29th, 2023 at 3:06 PM, qroxana
wrote:
> It appears buildworld doesn't create the obj directory for
> usr.bin/clang/llvm-objcopy in stage 2.2 after this commit.
>
> commit adc3c128c6603054586a993d117e5dd808deac17
> Au
--- Original Message ---
On Monday, January 30th, 2023 at 3:08 PM, Rick Macklem
wrote:
> I think this was fixed by a commit yesterday.
>
> rick
>
Thanks Rick. Yes, it has been fixed.
commit ad055467bec35885dc3eff2f4dd765f5b2f53259
Author: Kirk McKusick
AuthorDate: Sun Jan 29 15:1
Hi,
I have an old i386 machine running r364479. After upgrading to
r367045, running kldload zfs.ko freezes the whole system.
I also tried to replace the 4GB memory with another 2GB one
and kldload zfs.ko works without freezing the machine.
Thanks.
__
I have exec.fib = 2 in /etc/jail.conf, but it seems the address of
the jail is not inserted into this fib. What's the best practice
for using jail with fib when net.add_addr_allfibs=0?
Thanks.
___
freebsd-current@freebsd.org mailing list
https://lists.
On Mon, 11 Jan 2021 13:25:51 +, Alexander V. Chernikov
wrote:
> Could you please consider clarifying the end result you want to achieve?
> If you could include some more details of how it was configured earlier, it
> would help as well.
Thank you for the quick reply.
Let's say there are tw
‐‐‐ Original Message ‐‐‐
On Monday, January 11, 2021 7:37 PM, Alexander V. Chernikov
wrote:
> 11.01.2021, 14:59, "qroxana" qrox...@protonmail.com:
>
> > On Mon, 11 Jan 2021 13:25:51 +, Alexander V. Chernikov melif...@ipfw.ru
> > wrote:
> >
> >
I know running make install for /usr/src/tools/build/test-includes can fix this,
but this still fails on a newly installed 14.0-CURRENT.
--- test-includes ---
cd /usr/src/tools/build/test-includes; MACHINE_ARCH=aarch64 MACHINE=arm64
CPUTYPE= CC="cc -target aarch64-unknown-freebsd14.0
--sysroot=/
It's running 14.0-CURRENT armv7 main-n252983-d21e71efce39
Kernel page fault with the following non-sleepable locks held:
exclusive sleep mutex epairidx (epairidx) r = 0 (0xe2fe9160) locked @
/usr/src/sys/net/if_epair.c:165
stack backtrace:
#0 0xc03558f8 at witness_debugger+0x7c
#1 0xc0356b3c at w
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
On Sun, 01 May 2022 03:13:43 +, qroxana wrote:
> After git bisecting the panic started since this commit.
>
> commit 78bc3d5e1712bc1649aa5574d2b8d153f9665113
> Author: Kristof Provost
> Date: Mon Feb 14 20:09:54 2022 +0100
>
> vlan: allow net.link.vlan.mtag_p
On Monday, May 2nd, 2022 at 9:02 AM, Kristof Provost wrote:
> On 1 May 2022, at 5:13, qroxana wrote:
>
> > After git bisecting the panic started since this commit.
> >
> > commit 78bc3d5e1712bc1649aa5574d2b8d153f9665113
> >
> > Author: Kristof Provost <
Hi all,
What's the best practice for setting up bridge0 on a NFS root system?
Let's say the system is boot from TFTP via em0 and mount the NFS root
filesystem, is there any way to create bridge0 and addm em0 after the system is
up? or is it possible to create and use bridge0 before mounting the
16 matches
Mail list logo
