New console output at boot?

Since an update to current a couple of weeks ago, I now see several lines (6 or 7) early in the boot. I'm not sure whether it is from one of the boots or the loader, but it comes out so quickly (and so briefly) but it vanishes on my display before I can read it. I'm guessing that some part of the b

new tls-cert-store and cert-bundle methods

Hello, Now that we have system tls-cert-store, if one needs to reference a tls-cert-bundle like provided by ca_root_nss, do we need to concatenate all of the certs listed in /usr/share/certs/trusted into, for example cert.pem then symlink /etc/ssl/cert.pem to that concatenated file? thanks in ad

New FreeBSD snapshots available: stable/14 (ALPHA4) (20230901 4c3f144478d4)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 New FreeBSD development branch installation ISOs and virtual machine disk images have been uploaded to the FreeBSD Project mirrors. As with any development branch, the installation snapshots are not intended for use on production systems. We do

Re: Question about KBI change / new feature

le/> says CURRENT/14 's KBI is > froze > and new features should be avoided. > > I'm working on https://reviews.freebsd.org/D39638 > <https://reviews.freebsd.org/D39638> (sysctl(9): Enable vnet sysctl variables > be loader tunable) > and I think it is ne

New FreeBSD snapshots available: stable/14 (ALPHA3) (20230825 2af9390e54ed)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 New FreeBSD development branch installation ISOs and virtual machine disk images have been uploaded to the FreeBSD Project mirrors. As with any development branch, the installation snapshots are not intended for use on production systems. We do

Re: poudriere bulk with ZFS and USE_TMPFS=no on main [14-ALPHA2 based]: extensive vlruwk for cpdup's on new builders after pkg builds in first builder

On Aug 24, 2023, at 00:22, Mark Millard wrote: > On Aug 23, 2023, at 22:54, Mateusz Guzik wrote: > >> On 8/24/23, Mark Millard wrote: >>> On Aug 23, 2023, at 15:10, Mateusz Guzik wrote: >>> On 8/23/23, Mark Millard wrote: > [Forked off the ZFS deadlock 14 discussion, per feedback.]

Re: poudriere bulk with ZFS and USE_TMPFS=no on main [14-ALPHA2 based]: extensive vlruwk for cpdup's on new builders after pkg builds in first builder

On Aug 23, 2023, at 22:54, Mateusz Guzik wrote: > On 8/24/23, Mark Millard wrote: >> On Aug 23, 2023, at 15:10, Mateusz Guzik wrote: >> >>> On 8/23/23, Mark Millard wrote: [Forked off the ZFS deadlock 14 discussion, per feedback.] . . . >>> >>> This is a known problem, but it is un

Re: poudriere bulk with ZFS and USE_TMPFS=no on main [14-ALPHA2 based]: extensive vlruwk for cpdup's on new builders after pkg builds in first builder

l updated: 2021-12-04 14:55:22 >>> Jail pkgbase: disabled >>> >>> >>> >>> So, setting up another test with some related information >>> shown before, during, and after. sysctl output is from >>> another ssh session than the bulk -

Re: poudriere bulk with ZFS and USE_TMPFS=no on main [14-ALPHA2 based]: extensive vlruwk for cpdup's on new builders after pkg builds in first builder

t;> >>> >>> >>> So, setting up another test with some related information >>> shown before, during, and after. sysctl output is from >>> another ssh session than the bulk -a run. >>> >>> # sysctl -a | grep vnode >>> kern.m

Re: poudriere bulk with ZFS and USE_TMPFS=no on main [14-ALPHA2 based]: extensive vlruwk for cpdup's on new builders after pkg builds in first builder

m.vnode_pbufs: 2048 >> vm.stats.vm.v_vnodepgsout: 0 >> vm.stats.vm.v_vnodepgsin: 272429 >> vm.stats.vm.v_vnodeout: 0 >> vm.stats.vm.v_vnodein: 12461 >> vfs.vnode_alloc_sleeps: 0 >> vfs.wantfreevnodes: 553452 >> vfs.freevnodes: 962766 >> vfs.vnodes_create

Re: poudriere bulk with ZFS and USE_TMPFS=no on main [14-ALPHA2 based]: extensive vlruwk for cpdup's on new builders after pkg builds in first builder

ebug.sizeof.vnode: 448 > debug.fail_point.status_fill_kinfo_vnode__random_path: off > debug.fail_point.fill_kinfo_vnode__random_path: off > > # poudriere bulk -jmain-amd64-bulk_a -a > . . . > [00:01:34] Building 34042 packages using up to 32 builders > [00:01:34] Hit CTRL+t

poudriere bulk with ZFS and USE_TMPFS=no on main [14-ALPHA2 based]: extensive vlruwk for cpdup's on new builders after pkg builds in first builder

:12] Finished ports-mgmt/pkg | pkg-1.20.4: Success [00:03:22] [01] [00:00:00] Building print/indexinfo | indexinfo-0.3.1 [00:03:22] [02] [00:00:00] Builder starting [00:03:22] [03] [00:00:00] Builder starting . . . [00:03:22] [31] [00:00:00] Builder starting [00:03:22] [32] [00:00:00] Builder sta

Re: Question about KBI change / new feature

On Mon, Aug 21, 2023 at 9:42 AM Zhenlei Huang wrote: > Hi, > > The https://www.freebsd.org/releases/14.0R/schedule/ says CURRENT/14 's > KBI is froze > and new features should be avoided. > > I'm working on https://reviews.freebsd.org/D39638 (sysctl(9): Enable vn

Question about KBI change / new feature

Hi, The https://www.freebsd.org/releases/14.0R/schedule/ says CURRENT/14 's KBI is froze and new features should be avoided. I'm working on https://reviews.freebsd.org/D39638 (sysctl(9): Enable vnet sysctl variables be loader tunable) and I think it is new feature, but not quite su

New FreeBSD snapshots available: main (ALPHA2) (20230819 77013f29d048)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 New FreeBSD development branch installation ISOs and virtual machine disk images have been uploaded to the FreeBSD Project mirrors. As with any development branch, the installation snapshots are not intended for use on production systems. We do

Re: Lacking "arminess" (was Re: New FreeBSD snapshots available) (OFF TOPIC)

Ship it! Glen Sent from my phone. Please excuse my brevity and/or typos. > On Aug 13, 2023, at 2:39 PM, George Mitchell wrote: > > On 8/11/23 23:15, Glen Barber wrote: >> [...] >> It was discovered that due to human error (my own) the arm64 are, as >> Colin put it very politely, are "lacking '

Re: New FreeBSD snapshots available: stable/14 (ALPHA1) (20230811 136fc495615f)

On Fri, Aug 11, 2023 at 08:53:12PM +, Glen Barber wrote: [...] > FreeBSD/aarch64 UFS EC2 AMIs are available in the following regions: > [...] > > FreeBSD/aarch64 ZFS EC2 AMIs are available in the following regions: > [...] It was discovered that due to human error (my own) the arm64 are,

New FreeBSD snapshots available: stable/14 (ALPHA1) (20230811 136fc495615f)

New FreeBSD development branch installation ISOs and virtual machine disk images have been uploaded to the FreeBSD Project mirrors. As with any development branch, the installation snapshots are not intended for use on production systems. We do, however, encourage testing on non-production

Re: problems on new -current install with pkg/ssl

thanks everyone it's working normally now after full buildworld kernel then forced rebuild of all ports from their updated sources --

Re: problems on new -current install with pkg/ssl

On 7/9/23 18:27, void wrote: On Sun, Jul 09, 2023 at 05:17:38PM +0100, void wrote: Hi, On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg for anything and this error happens: # pkg install doas The package management tool is not yet installed on your system. Do you want

Re: problems on new -current install with pkg/ssl

On Sun, 9 Jul 2023 17:17:38 +0100 void wrote: > Hi, > > On a fresh 14-current install (main-n263444-653738e895ba) > I try to use pkg for anything and this error > happens: > > # pkg install doas > The package management tool is not yet installed on your system. > Do you want to fetch and install

Re: problems on new -current install with pkg/ssl

void wrote: > Hi, > > On a fresh 14-current install (main-n263444-653738e895ba) I try to use > pkg for anything and this error > happens: > > # pkg install doas > The package management tool is not yet installed on your system. > Do you want to fetch and install it now? [y/N]: y > Bootstrapping p

Re: problems on new -current install with pkg/ssl

On Sun, Jul 09, 2023 at 05:17:38PM +0100, void wrote: > Hi, > > On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg > for anything and this error > happens: > > # pkg install doas > The package management tool is not yet installed on your system. > Do you want to fetch and

Re: problems on new -current install with pkg/ssl

On Sun, Jul 09, 2023 at 05:17:38PM +0100, void wrote: Hi, On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg for anything and this error happens: # pkg install doas The package management tool is not yet installed on your system. Do you want to fetch and install it now?

problems on new -current install with pkg/ssl

Hi, On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg for anything and this error happens: # pkg install doas The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: y Bootstrapping pkg from pkg+http://pkg.FreeBS

Re: No new FreeBSD images on Google Cloud since 13-April

On Mon, Jun 19, 2023 at 12:11 PM Alan Somers wrote: > > New builds of stable/13, stable/12, and current used to appear in > Google Cloud about once per week. But the latest builds all date from > 13-April-2023. Does some script need to be kicked? To see the > currently avail

new syctl to allow ignoring time from fs if no rtc found

unsure if anybody else needs that functionality. i was suggested to submit it into actual code review place, but i'm unsure. it's from 2014, it still cleanly applies. probably because noone needed to touch working code! anyway, i used it in in arm board development, in bbb, to default system time t

No new FreeBSD images on Google Cloud since 13-April

New builds of stable/13, stable/12, and current used to appear in Google Cloud about once per week. But the latest builds all date from 13-April-2023. Does some script need to be kicked? To see the currently available images, do: pkg install google-cloud-sdk gcloud compute images list

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

On 6/8/23 05:48, Warner Losh wrote: On Thu, Jun 8, 2023, 4:35 AM Rebecca Cran wrote: It's ZFS, using the default options when creating it via the FreeBSD installer so I presume TRIM is enabled. Without a reliable way to reproduce the error I'm not sure disabling TRIM will help at

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

On Thu, Jun 8, 2023, 4:35 AM Rebecca Cran wrote: > It's ZFS, using the default options when creating it via the FreeBSD > installer so I presume TRIM is enabled. Without a reliable way to > reproduce the error I'm not sure disabling TRIM will help at the moment. > > I don't think there's any newe

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

It's ZFS, using the default options when creating it via the FreeBSD installer so I presume TRIM is enabled. Without a reliable way to reproduce the error I'm not sure disabling TRIM will help at the moment. I don't think there's any newer firmware for it. -- Rebecca Cran On 6/8/23 04:25,

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

what filesystem? is TRIM enabled on that drive? have you tried disabling trim? i had similar ssd related problem on samsung's ssd long time ago that was related to trim. maybe drive firmware can be updated too? :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

On 6/8/23 00:24, Warner Losh wrote: PCIe 3 or PCIe 4? PCIe 4. nda0 at nvme0 bus 0 scbus0 target 0 lun 1 nda0: nda0: Serial Number S55KNC0TC00168 nda0: nvme version 1.3 x8 (max x8) lanes PCIe Gen4 (max Gen4) link nda0: 6104710MB (12502446768 512 byte sectors) -- Rebecca Cran

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

On Wed, Jun 7, 2023 at 11:12 PM Rebecca Cran wrote: > I got a seemingly random nvme data transfer error on my new arm64 Ampere > Altra machine, which has a Samsung PM1735 PCIe AIC NVMe drive. > > Since it's a new drive and smartctl doesn't show any errors I thought it >

Seemingly random nvme (nda) write error on new drive (retries exhausted)

I got a seemingly random nvme data transfer error on my new arm64 Ampere Altra machine, which has a Samsung PM1735 PCIe AIC NVMe drive. Since it's a new drive and smartctl doesn't show any errors I thought it might be worth mentioning here. I'm running 14.0-CURRENT FreeBSD

Re: photo/video on tty console with the new VT/framebuffer

Alastair Hogge writes: > On 2023-05-19 11:04, Ivan Quitschal wrote: > >> Hi all >> >> i have a question. searched everywhere and found nothing about. >> >> Is it possible to visualize photos on tty console like we used to on old >> SYSCONS by using zgv or something? See https://github.com/mpv

Re: photo/video on tty console with the new VT/framebuffer

Btw. freebsd-questions list is better place for this kind of questions. freebsd-current is specific for CURRENT branch development related discussions :-) that was precisely my question, if it is possible to do *on current* at all. because as i pointed out, i havent found almost anyone sa

Re: photo/video on tty console with the new VT/framebuffer

On Fri, 19 May 2023, Alastair Hogge wrote: On 2023-05-19 12:51, Ivan Quitschal wrote: hi Alastair Hey Ivan, could you please tell us how did you do to make mpv working ? when i try to run it, i get something like this: $ mpv --vo=drm video.mp4 (+) Video --vid=1 (*) (h264 424x240 30.00

Re: photo/video on tty console with the new VT/framebuffer

On 2023-05-19 12:51, Ivan Quitschal wrote: > hi Alastair Hey Ivan, > could you please tell us how did you do to make mpv working ? > > when i try to run it, i get something like this: > > $ mpv --vo=drm video.mp4 > (+) Video --vid=1 (*) (h264 424x240 30.000fps) > (+) Audio --aid=1 (*) (aac 2

Re: photo/video on tty console with the new VT/framebuffer

On Fri, May 19, 2023 at 2:51 PM Ivan Quitschal wrote: > could you please tell us how did you do to make mpv working ? > > when i try to run it, i get something like this: > $ mpv --vo=drm video.mp4 > (+) Video --vid=1 (*) (h264 424x240 30.000fps) > (+) Audio --aid=1 (*) (aac 2ch 44100Hz) > [vo/

Re: photo/video on tty console with the new VT/framebuffer

On Fri, 19 May 2023, Alastair Hogge wrote: On 2023-05-19 11:04, Ivan Quitschal wrote: Hi all i have a question. searched everywhere and found nothing about. Is it possible to visualize photos on tty console like we used to on old SYSCONS by using zgv or something? Or watching videos with

Re: photo/video on tty console with the new VT/framebuffer

On Fri, May 19, 2023 at 2:29 PM Yuri wrote: > Tomek CEDRO wrote: > > On Fri, May 19, 2023 at 1:44 PM Alastair Hogge wrote: > >> On 2023-05-19 11:30, Tomek CEDRO wrote: > >>> On Fri, May 19, 2023 at 1:28 PM Alastair Hogge wrote: > As long as those packages support DRMKMS and does your GPU, you

Re: photo/video on tty console with the new VT/framebuffer

Tomek CEDRO wrote: > On Fri, May 19, 2023 at 1:44 PM Alastair Hogge wrote: >> On 2023-05-19 11:30, Tomek CEDRO wrote: >>> On Fri, May 19, 2023 at 1:28 PM Alastair Hogge wrote: As long as those packages support DRMKMS and does your GPU, you can to a degree. I noticed video works for mpv an

Re: photo/video on tty console with the new VT/framebuffer

On Fri, May 19, 2023 at 1:44 PM Alastair Hogge wrote: > On 2023-05-19 11:30, Tomek CEDRO wrote: > > On Fri, May 19, 2023 at 1:28 PM Alastair Hogge wrote: > >> As long as those packages support DRMKMS and does your GPU, you can to a > >> degree. I noticed video works for mpv and games/sdl, tho, I ca

Re: photo/video on tty console with the new VT/framebuffer

On 2023-05-19 11:30, Tomek CEDRO wrote: > On Fri, May 19, 2023 at 1:28 PM Alastair Hogge wrote: >> As long as those packages support DRMKMS and does your GPU, you can to a >> degree. I noticed video works for mpv and games/sdl, tho, I cannot get >> input working. I tried the Doom 3 port, and watche

Re: photo/video on tty console with the new VT/framebuffer

On Fri, May 19, 2023 at 1:28 PM Alastair Hogge wrote: > As long as those packages support DRMKMS and does your GPU, you can to a > degree. I noticed video works for mpv and games/sdl, tho, I cannot get > input working. I tried the Doom 3 port, and watched movies with mpv all > from the vty just a c

Re: photo/video on tty console with the new VT/framebuffer

On 2023-05-19 11:04, Ivan Quitschal wrote: > Hi all > > i have a question. searched everywhere and found nothing about. > > Is it possible to visualize photos on tty console like we used to on old > SYSCONS by using zgv or something? > > Or watching videos with mpv/mplayer + sdl 2.0/openGL or s

photo/video on tty console with the new VT/framebuffer

Hi all i have a question. searched everywhere and found nothing about. Is it possible to visualize photos on tty console like we used to on old SYSCONS by using zgv or something? Or watching videos with mpv/mplayer + sdl 2.0/openGL or something? Or seeing pictures on w3m-img like unix does ?

Re: RFC: A new NFS mount option to encourage use of Kerberized mounts

On Tue, Mar 14, 2023 at 11:53 AM Pete Wright wrote: > > On Mon, Mar 13, 2023 at 07:25:07PM -0700, Rick Macklem wrote: > > Hi, > > > > I have implemented a new mount option for NFSv4.1/4.2 mounts > > that I hope will encourage use of Kerberos and TLS to help > &g

Re: RFC: A new NFS mount option to encourage use of Kerberized mounts

On Mon, Mar 13, 2023 at 07:25:07PM -0700, Rick Macklem wrote: > Hi, > > I have implemented a new mount option for NFSv4.1/4.2 mounts > that I hope will encourage use of Kerberos and TLS to help > secure NFS mounts. Although I do not know why users choose > to not use Kerber

RFC: A new NFS mount option to encourage use of Kerberized mounts

Hi, I have implemented a new mount option for NFSv4.1/4.2 mounts that I hope will encourage use of Kerberos and TLS to help secure NFS mounts. Although I do not know why users choose to not use Kerberized NFS mounts, I think that the administrative issues related to the "machine credential&

Re: Timekeeping problem in /usr/src on new RPI aarch64 snapshot

there is no /etc/wall_cmos_clock on the newly-installed filesystem >>> it appears the superblock timestamp is then interpreted as UTC when a Pi >>> boots, using whatever happens to be set in /etc/localtime. My confusion >>> is reduced somewhat. On first boot, what is th

Re: Timekeeping problem in /usr/src on new RPI aarch64 snapshot

is then interpreted as UTC when a Pi > > boots, using whatever happens to be set in /etc/localtime. My confusion > > is reduced somewhat. On first boot, what is the state of /etc/localtime? > > > > I've neglected to run tzsetup immediately on many previous installations

Re: Timekeeping problem in /usr/src on new RPI aarch64 snapshot

is the state of /etc/localtime? > > I've neglected to run tzsetup immediately on many previous installations > and not noticed any complaints about mis-set clocks in buildworld. Is this > new behavior? /etc/localtime is used in formatting dates (e.g. for ls), but is not involved in stor

Re: Timekeeping problem in /usr/src on new RPI aarch64 snapshot

bout mis-set clocks in buildworld. Is this new behavior? Thanks to both Mark and Ronald! bob prohaska

Re: Timekeeping problem in /usr/src on new RPI aarch64 snapshot

Van: bob prohaska Datum: 24 februari 2023 22:05 Aan: freebsd-current@freebsd.org CC: freebsd-...@freebsd.org Onderwerp: Timekeeping problem in /usr/src on new RPI aarch64 snapshot After installing FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20230223-fe5c211ba873-261074.img on a Pi3 and setting

Re: Timekeeping problem in /usr/src on new RPI aarch64 snapshot

On Feb 24, 2023, at 13:05, bob prohaska wrote: > After installing > FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20230223-fe5c211ba873-261074.img > on a Pi3 and setting up the hard disk to use separate swap and /usr partitions > an oddity came to light regarding dates. > > The image file was written

Timekeeping problem in /usr/src on new RPI aarch64 snapshot

After installing FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20230223-fe5c211ba873-261074.img on a Pi3 and setting up the hard disk to use separate swap and /usr partitions an oddity came to light regarding dates. The image file was written to disk the night of the 23rd, from a Pi3 with a correctly-se

Re: [RFC] Proposal adding new sorting algorithm, bsort() to libc

On 9/8/22 12:50, Hans Petter Selasky wrote: See: https://reviews.freebsd.org/D36493 Looking through base I see qsort() being used in places it shouldn't be used. For example in fts_open(). If for example you fill a directory with 64k simply numerical file names in the wrong order and ask fts

[RFC] Proposal adding new sorting algorithm, bsort() to libc

See: https://reviews.freebsd.org/D36493 Looking through base I see qsort() being used in places it shouldn't be used. For example in fts_open(). If for example you fill a directory with 64k simply numerical file names in the wrong order and ask fts_open() to sort these ascending for example,

Re: New panic in main-n253273-a52d8d4a6c6:

> --mikej >> >> >> >> >> >> *From:* Rob Wing [mailto:rob.fx...@gmail.com] >> *Sent:* Monday, February 21, 2022 9:30 PM >> *To:* Michael Jung >> *Cc:* Hans Petter Selasky ; freebsd-current < >> freebsd-current@freebsd.org> >&

Re: New panic in main-n253273-a52d8d4a6c6:

Monday, February 21, 2022 9:30 PM > *To:* Michael Jung > *Cc:* Hans Petter Selasky ; freebsd-current < > freebsd-current@freebsd.org> > *Subject:* Re: New panic in main-n253273-a52d8d4a6c6: > > > > The previous attached patch should work for testing purposes, but it&#x

RE: New panic in main-n253273-a52d8d4a6c6:

, February 21, 2022 9:30 PM To: Michael Jung Cc: Hans Petter Selasky ; freebsd-current Subject: Re: New panic in main-n253273-a52d8d4a6c6: The previous attached patch should work for testing purposes, but it's incorrect if an error occurs. The fhold() should be below FILEDESC_SUNLOCK(),

Re: New panic in main-n253273-a52d8d4a6c6:

have >> received this transmission in error, please notify us by >> telephone at (502) 212-4000 or notify us at: PAI, Dept. 99, >> 2101 High Wickham Place, Suite 101, Louisville, KY 40245 >> >> >> >> *From:* Michael Jung >> *Sent:* Monday, Februa

Re: New panic in main-n253273-a52d8d4a6c6:

please notify us by > telephone at (502) 212-4000 or notify us at: PAI, Dept. 99, > 2101 High Wickham Place, Suite 101, Louisville, KY 40245 > > > > *From:* Michael Jung > *Sent:* Monday, February 21, 2022 9:06 PM > *To:* 'Hans Petter Selasky' ; freebsd-current &l

RE: New panic in main-n253273-a52d8d4a6c6:

From: Michael Jung Sent: Monday, February 21, 2022 9:06 PM To: 'Hans Petter Selasky' ; freebsd-current Subject: RE: New panic in main-n253273-a52d8d4a6c6: From: Hans Petter Selasky [mailto:h...@selasky.org] Sent: Monday, February 21, 2022 8:34 PM To: Michael Jung

RE: New panic in main-n253273-a52d8d4a6c6:

From: Hans Petter Selasky [mailto:h...@selasky.org] Sent: Monday, February 21, 2022 8:34 PM To: Michael Jung ; freebsd-current Subject: Re: New panic in main-n253273-a52d8d4a6c6: On 2/22/22 00:42, Michael Jung wrote: > Hi: > > I was trying to remember what I did that was odd when t

Re: New panic in main-n253273-a52d8d4a6c6:

kinda thinking this might be related to commit f40dd6c8034b ("tty: switch ttyhook_register to use fget_cap_locked") fget_unlocked() must have grabbed an extra reference count on the file pointer that fget_cap_locked() doesn't get On Mon, Feb 21, 2022 at 4:35 PM Hans Petter Selasky wrote: > On 2

Re: New panic in main-n253273-a52d8d4a6c6:

On 2/22/22 00:42, Michael Jung wrote: Hi: I was trying to remember what I did that was odd when this crash occurred then it hit me. You can repeat this panic by doing: # watch -I -W pts/0 Here is another panic that happened write after issuing "watch" for comparison. http://mail.mikej.com/c

RE: New panic in main-n253273-a52d8d4a6c6:

com/info.1 http://mail.mikej.com/vmcore.1 --mikej -Original Message- From: Michael Jung Sent: Monday, February 21, 2022 6:22 PM To: 'Hans Petter Selasky' ; freebsd-current Subject: RE: New panic in main-n253273-a52d8d4a6c6: -Original Message- From: Hans Pett

RE: New panic in main-n253273-a52d8d4a6c6:

-Original Message- From: Hans Petter Selasky [mailto:h...@selasky.org] Sent: Monday, February 21, 2022 8:53 AM To: Michael Jung ; freebsd-current Subject: Re: New panic in main-n253273-a52d8d4a6c6: On 2/21/22 14:07, Michael Jung wrote: > (kgdb) fram 16 > #16 0x80bad

Re: New panic in main-n253273-a52d8d4a6c6:

On 2/21/22 14:07, Michael Jung wrote: (kgdb) fram 16 #16 0x80bad587 in closefp_impl (fdp=0xfe012b7c0430, fd=4, fp=0xf801cc119280, td=0xfe00df8d0560, audit=true) at /usr/src/sys/kern/kern_descrip.c:1300 1300error = closef(fp, td); (kgdb) print /x *fdp $1 = {fd_fi

RE: New panic in main-n253273-a52d8d4a6c6:

-Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Hans Petter Selasky Sent: Monday, February 21, 2022 2:48 AM To: Michael Jung ; freebsd-current Subject: Re: New panic in main-n253273-a52d8d4a6c6: On 2/20/22 21:53

Re: New panic in main-n253273-a52d8d4a6c6:

On 2/20/22 21:53, Michael Jung wrote: Hi! The box was quite busy at the time. The only odd thing I am aware of and which I do not think is related is I have not been able to expand one of my zpool's. ZFS sees my added draid2:2d:10c:0s vdev but I can't seem to force zpool's expansion - my be

New panic in main-n253273-a52d8d4a6c6:

Hi! The box was quite busy at the time. The only odd thing I am aware of and which I do not think is related is I have not been able to expand one of my zpool's. ZFS sees my added draid2:2d:10c:0s vdev but I can't seem to force zpool's expansion - my bet this is somehow related to the mirrore

new boot message: "/etc/rc: WARNING: $zfskeys_enable is not set properly - see rc.conf(5)."?

As of my update to (some line splitting applied): # uname -apKU FreeBSD CA72_UFS 14.0-CURRENT FreeBSD 14.0-CURRENT #25 main-n251456-22c4ab6cb015-dirty: Tue Dec 7 19:38:53 PST 2021 root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72 arm64 aar

Re: Bash Static broken with new ncurses update on current

On Tue, Oct 05, 2021 at 11:46:45AM -0700, Manfred Antar (KN6KBS) wrote: > After update to current world on 10/5/2021 bash static is broken: > > cc -L./builtins -L/usr/local/lib -L/usr/local/lib -L./lib/glob -L./lib/tilde > -L./lib/sh -L/usr/local/lib -fstack-protector-strong -fuse-ld=bfd -sta

Re: New loader_lua.efi causes kernels to hang at boot

BSD/SMP: Multiprocessor System Detected: 32 CPUs > > > > FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 hardware threads > > > > > > > > So I rebooted a selected kernel.old at the boot menu and.. same > thing. > > > > That's strange! > > >

Re: New loader_lua.efi causes kernels to hang at boot

old at the boot menu and.. same thing. > > > That's strange! > > > > > > So I booted off a USB stick, mounted the EFI partition and copied > > > BOOTX64.bak back to BOOTX64.efi and now the machine booted normally. > > > > > > So for some

Re: New loader_lua.efi causes kernels to hang at boot

; FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 hardware threads > > > > So I rebooted a selected kernel.old at the boot menu and.. same thing. > > That's strange! > > > > So I booted off a USB stick, mounted the EFI partition and copied > > BOOTX64.bak back to BOO

Re: copy_staging enable (was: New loader_lua.efi causes kernels to hang at boot)

On Mon, Aug 30, 2021 at 11:48:56AM +0100, Graham Perrin wrote: > On 30/08/2021 10:33, Konstantin Belousov wrote: > > Try to add > > exec="copy_staging enable" > > line to it, does it hide the problem? > > When I last tested (19th August), I got the impression that it was enabled > by default. It i

copy_staging enable (was: New loader_lua.efi causes kernels to hang at boot)

On 30/08/2021 10:33, Konstantin Belousov wrote: Try to add exec="copy_staging enable" line to it, does it hide the problem? When I last tested (19th August), I got the impression that it was enabled by default. Correct me, pleas

Re: New loader_lua.efi causes kernels to hang at boot

ange! > > So I booted off a USB stick, mounted the EFI partition and copied > BOOTX64.bak back to BOOTX64.efi and now the machine booted normally. > > So for some reason the newer loader_lua.efi is causing both the new kernel > AND the old kernel to hang, but the older

Re: New loader_lua.efi causes kernels to hang at boot

t; So I booted off a USB stick, mounted the EFI partition and copied > BOOTX64.bak back to BOOTX64.efi and now the machine booted normally. > > So for some reason the newer loader_lua.efi is causing both the new kernel > AND the old kernel to hang, but the older loader_lua.efi seems to wo

New loader_lua.efi causes kernels to hang at boot

er_lua.efi is causing both the new kernel AND the old kernel to hang, but the older loader_lua.efi seems to work with both no problem. Any ideas? Thanks! -Dustin

Re: etcupdate: Failed to build new tree

t; /tmp/etc.diff (etcupdate diff doesn't show any diffs.) Today I've just updated current and etcupdate -p gives: "Failed to build new tree" What might be wrong? You can look in /var/db/etcupdate/log to check for errors. -- John Baldwin

Re: etcupdate: Failed to build new tree

extract > etcupdate diff > /tmp/etc.diff > patch -R < /tmp/etc.diff > (etcupdate diff doesn't show any diffs.) > > Today I've just updated current and etcupdate -p gives: > > "Failed to build new tree" > > What might be wrong? > > Thanks > N

etcupdate: Failed to build new tree

ow any diffs.) Today I've just updated current and etcupdate -p gives: "Failed to build new tree" What might be wrong? Thanks Nuno Teixeira

Re: zpool upgrade can't enable new features

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 25 Feb 2021 18:28:06 +0100 Martin Matuska schrieb: > I have submitted a pull request to fix this in OpenZFS: > https://github.com/openzfs/zfs/pull/11653 > > On 25. 2. 2021 17:20, John Kennedy wrote: > > On Thu, Feb 25, 2021 at 11:09:17AM -

Re: zpool upgrade can't enable new features

I have submitted a pull request to fix this in OpenZFS: https://github.com/openzfs/zfs/pull/11653 On 25. 2. 2021 17:20, John Kennedy wrote: On Thu, Feb 25, 2021 at 11:09:17AM -0300, Renato Botelho wrote: I recently upgraded a CURRENT system to main-n244932-248a47a4c2f and zpool status shows:

Re: zpool upgrade can't enable new features

Looks like Ryan didn't think it all the way through in: https://github.com/openzfs/zfs/commit/35ec51796f0aa8d4fe322b48e7d1d5a65e38a4ce I am preparing a patch for OpenZFS. On 25. 2. 2021 17:20, John Kennedy wrote: On Thu, Feb 25, 2021 at 11:09:17AM -0300, Renato Botelho wrote: I recently upgrad

Re: zpool upgrade can't enable new features

On Thu, Feb 25, 2021 at 11:09:17AM -0300, Renato Botelho wrote: > I recently upgraded a CURRENT system to main-n244932-248a47a4c2f and > zpool status shows: > >pool: zroot > state: ONLINE > status: Some supported and requested features are not enabled on the pool. > The pool can st

zpool upgrade can't enable new features

I recently upgraded a CURRENT system to main-n244932-248a47a4c2f and zpool status shows: pool: zroot state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features usin

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

On Tue, Feb 16, 2021 at 1:48 AM 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 > > as

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

afaik. > > ... >> Thanks for the alternatives to sysctl kern.disks >> and to nvmecontrol devlist for making a list to >> compare to gpart show output in order to find >> what gpart show does not list (but can manipulate). > > gpart(8) doesn't enumerate di

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

e present. You can create new partition schemes with the help of gpart(8), but it's imho correct not to show them, because 'gpart show' is meant to give information about (existing) partition schemes - no scheme no info; thus your vanilla disk is "unknown" to gpart(8). I

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

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: New Optane AIC does not show up in FreeBSD until . . . ?

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: New Optane AIC does not show up in FreeBSD until . . . ?

1 da0 ada2 ada1 ada0 nvd5 nvd4 nvd3 nvd2 nvd1 nvd0 (I'd know it was one of the nvd*'s.) So for sysctl kern.disks use I'd need to look for a name (a nvd*) that gpart show had not listed and that would be the new one. So: use both commands. Good to know. nmvecontrol devlist d

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

kern.disks Mark > > > >> On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current < > freebsd-current@freebsd.org> wrote: > >> I plugged in a new Optane and booted FreeBSD on the > >> ThreadRipper 1950X system but FreeBSD did not show > >&g

  1   2   3   4   5   6   7   8   9   10   >