Re: FreeBSD 13.0-BETA2 Now Available

2021-02-16 Thread Jason Tubnor
On Sat, 13 Feb 2021 at 09:52, Glen Barber wrote: > The second BETA build of the 13.0-RELEASE release cycle is now available. > > > === Upgrading === > > The freebsd-update(8) utility supports binary upgrades of amd64, i386 > and aarch64 systems running earlier FreeBSD releases. Systems running >

Re: loader/boot fonts are painfully small (again)

2021-02-16 Thread Walter von Entferndt
Why not add the option to in/decrease the font size with the +/- keys to the boot menu? And/or PgUP/Down or Up/Down arrow. Last resort: 9 & 0 are the last unused numbers in the boot menu. -- =|o) "Stell' Dir vor es geht und keiner kriegt's hin." (Wolfgang Neuss)

Re: pkg vs uname troubles after upgrade to 14 (lld not rebuilt issue? (X_)LINKER_FREEBSD_VERSION still 13 based?)

2021-02-16 Thread Mark Millard via freebsd-current
On 2021-Feb-16, at 15:37, Mark Millard wrote: > On 2021-Feb-16, at 11:49, Brandon Bergren wrote: > >> It looks like there were recently some fixes to release.sh, that just got >> backported to 13. I wonder if the problem is the packages themselves being >> misbuilt. >> >> https://cgit.fre

Re: "grep -rI ... /" vs. processing of /dev/ : should "--exclude-dir /dev" be required in order to avoid /dev/?

2021-02-16 Thread Kyle Evans
On Tue, Feb 16, 2021 at 7:23 PM Mark Millard via freebsd-current wrote: > > I historically on occasion have done something like: > > # grep -rI ... / > > in order to find all instances of a text, including > in build trees and such. I now find that I need to > do something more like (using a more

"grep -rI ... /" vs. processing of /dev/ : should "--exclude-dir /dev" be required in order to avoid /dev/?

2021-02-16 Thread Mark Millard via freebsd-current
I historically on occasion have done something like: # grep -rI ... / in order to find all instances of a text, including in build trees and such. I now find that I need to do something more like (using a more specific example): # grep -rI --exclude-dir /dev '#define.*__FreeBSD_version' otherwi

Is stand/kshim/bsd_kernel.h 's __FreeBSD_version supposed to track main's 13->14 change?

2021-02-16 Thread Mark Millard via freebsd-current
stand/kshim/bsd_kernel.h has its own define of __FreeBSD_version and seems to have last had it changed in the main branch as shown below. Is it as it should be for main 14? It does seem to have skipped being updated for HEAD 12. Last change . . . author Hans Petter Selasky 2020-11-18 13:22

Re: pkg vs uname troubles after upgrade to 14

2021-02-16 Thread Mark Millard via freebsd-current
On 2021-Feb-16, at 11:49, Brandon Bergren wrote: > It looks like there were recently some fixes to release.sh, that just got > backported to 13. I wonder if the problem is the packages themselves being > misbuilt. > > https://cgit.freebsd.org/src/commit/release?h=releng/13.0&id=4689ab1eab624d1

Re: panic: condition seqc_in_modify(_vp->v_seqc) not met at zfs_acl.c:1147 (zfs_acl_chown_setattr)

2021-02-16 Thread Mateusz Guzik
I think for future proofing it would be best if all vnodes going there had seqc marked, thus I think this should do the trick: diff --git a/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c b/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c index d5f0da9ecd4b..8172916c4329 100644 --

Re: panic: condition seqc_in_modify(_vp->v_seqc) not met at zfs_acl.c:1147 (zfs_acl_chown_setattr)

2021-02-16 Thread Andriy Gapon
On 15/02/2021 11:45, Andriy Gapon wrote: > On 15/02/2021 10:22, Andriy Gapon wrote: >> >> I've got this panic once when copying a couple of files. >> The system is stable/13 as of 1996360d7338d, a custom kernel configuration, >> but >> no local source code modifications. >> >> Unread portion of th

Re: pkg vs uname troubles after upgrade to 14

2021-02-16 Thread Brandon Bergren
It looks like there were recently some fixes to release.sh, that just got backported to 13. I wonder if the problem is the packages themselves being misbuilt. https://cgit.freebsd.org/src/commit/release?h=releng/13.0&id=4689ab1eab624d1a551a5a8f109383ea18eeba20 On Tue, Feb 16, 2021, at 12:20 PM

Re: pkg vs uname troubles after upgrade to 14

2021-02-16 Thread Mark Millard via freebsd-current
Brandon Bergren bdragon at FreeBSD.org wrote on Tue Feb 16 17:29:45 UTC 2021 : > On Tue, Feb 16, 2021, at 10:38 AM, Ronald Klop wrote: > > I normally compile WITHOUT_CLEAN. What is the shortcut to recompile > > uname with the proper version nr and not having to recompiling clang? > > Cleaning an

Re: pkg vs uname troubles after upgrade to 14

2021-02-16 Thread Brandon Bergren
On Tue, Feb 16, 2021, at 10:38 AM, Ronald Klop wrote: > I normally compile WITHOUT_CLEAN. What is the shortcut to recompile > uname with the proper version nr and not having to recompiling clang? > Cleaning and rebuilding only uname does not help. Uh, I would drop into a buildenv with "make buil

Re: pkg vs uname troubles after upgrade to 14

2021-02-16 Thread Ronald Klop
libpkg/pkg_elf.c:const char *abi_files[] = { libpkg/pkg_elf.c-getenv("ABI_FILE"), libpkg/pkg_elf.c-_PATH_UNAME, libpkg/pkg_elf.c-_PATH_BSHELL, libpkg/pkg_elf.c-}; The detection first checks "/usr/bin/uname" if it exists and ABI_FILE is not set. Yes the base is upg

Re: pkg vs uname troubles after upgrade to 14

2021-02-16 Thread Brandon Bergren
IIRC, the detection works by probing /bin/sh, make sure you upgraded your base properly. On Tue, Feb 16, 2021, at 9:55 AM, Ronald Klop wrote: > Hi, > > Upgraded from 13 to 14. > > # uname -UK > 143 143 > > But elfdump on uname gives: > note (.note.tag): > FreeBSD 1300133 (NT_FR

pkg vs uname troubles after upgrade to 14

2021-02-16 Thread Ronald Klop
Hi, Upgraded from 13 to 14. # uname -UK 143 143 But elfdump on uname gives: note (.note.tag): FreeBSD 1300133 (NT_FREEBSD_ABI_TAG) # pkg -o OSVERSION=143 upgrade pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended Updating FreeBSD repos

Re: Interface counter inaccurate

2021-02-16 Thread Daniel Ponte
On Tue, Feb 16, 2021 at 10:39:28AM +0100, Kristof Provost wrote: [...] > Even stranger, in that you appear to only have the issue on one of your igb0 > interfaces. > My initial guess was that there was a driver bug causing it to double count > the packets. > > That machine has 4 ethernet ports, do

Re: New Optane AIC does not show up in FreeBSD until . . . ?

2021-02-16 Thread Mark Millard via freebsd-current
On 2021-Feb-16, at 02:22, Harry Schmalzbauer wrote: > Am 16.02.2021 um 11:08 schrieb Mark Millard: >> On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote: >>> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: On 2021-Feb-13, at 16:40, Warner Losh wrote: > Are you aw

Re: New Optane AIC does not show up in FreeBSD until . . . ?

2021-02-16 Thread Harry Schmalzbauer
Am 16.02.2021 um 11:08 schrieb Mark Millard: On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote: Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: On 2021-Feb-13, at 16:40, Warner Losh wrote: Are you aware of gpart create? Warner From which I derive that I had an implicit

make installworld crashes the system in g_slice_access geom_slice.c:127

2021-02-16 Thread Ali Abdallah via freebsd-current
Hello, While upgrading from source my 13-CURRENT box from ALPHA1 to BETA1, I got the following crash on make installworld. Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x30 fault code = supervisor read data, page not present instruc

Re: New Optane AIC does not show up in FreeBSD until . . . ?

2021-02-16 Thread Mark Millard via freebsd-current
On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote: > Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: >> On 2021-Feb-13, at 16:40, Warner Losh wrote: >> >>> Are you aware of gpart create? >>> >>> Warner >> From which I derive that I had an implicit, incorrect >> assumption tha

Re: Interface counter inaccurate

2021-02-16 Thread Kristof Provost
On 16 Feb 2021, at 0:58, Daniel Ponte wrote: On Mon, Feb 15, 2021 at 10:25:47PM +0100, Kristof Provost wrote: On 15 Feb 2021, at 22:09, Daniel Ponte wrote: I've noticed that since upgrading to stable/13-n244514-18097ee2fb7c from 12.2-STABLE, throughput on my WAN interface (the box runs pf) is

freebsd-update(8) without an echo of "You must be root to run this."

2021-02-16 Thread Graham Perrin
        echo "You must be root to run this." Below: is this my PEBKAM, or (with a system that is preconfigured to deny login as root) _should_ there be an echo of the r

Re: New Optane AIC does not show up in FreeBSD until . . . ?

2021-02-16 Thread Harry Schmalzbauer
Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: On 2021-Feb-13, at 16:40, Warner Losh wrote: Are you aware of gpart create? Warner From which I derive that I had an implicit, incorrect assumption that gpart show would in some way list everything available that gpart could m

Re: loader/boot fonts are painfully small (again)

2021-02-16 Thread Harry Schmalzbauer
Am 15.02.2021 um 16:55 schrieb Daniel Nebdal: On Fri, 12 Feb 2021 at 15:33, Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: On 11. Feb 2021, at 23:21, Yuri Pankov wrote: Lenovo P51 laptop, 15'' 4k (3840x2160) display. Booting from the latest available current snapshot (20210107),