Re: base packages orphaned

On 05/06/2025 19:15, Graham Perrin wrote: … grahamperrin@mowa219-gjp4-zbook-freebsd ~> pkg orphans | grep orphaned\:\ base | wc -l 518 grahamperrin@mowa219-gjp4-zbook-freebsd ~> … Re: the boot environments listed at the foot of this email Upgrade from 1500044-003-base to 15000

Re: Installer, before exit: /bin/tcsh for pkg

On 09/05/2025 17:39, Dag-Erling Smørgrav wrote: Ed Maste writes: It looks like nano's post-install/-deinstall requires print/indexinfo and it's not available. This doesn't appear to be directly related to /bin/sh, /bin/tcsh, or pkgbase. If you have concise reproduction steps, please submit a P

Installer, before exit: /bin/tcsh for pkg (was: CFT: pkgbase support in 15.0)

Re: has two screenshots that compare the 14.2-RELEASE experience (good) with the 15.0-CURRENT experience. It seems that /bin/tcsh no longer works aro

Re: pkg: invalid option --, and pkg: illegal option --

Also (with /usr/sbin/pkg in CURRENT), fish completions are sometimes broken. The most recent example: grahamperrin@mowa219-gjp4-zbook-freebsd ~> pkg iinfo Fpkg: invalid option -- l pkg: invalid option -- q rames/    reeBSD

Preferring /usr/local/sbin/pkg (was: pkg: invalid option --, and pkg: illegal option --)

On 02/05/2025 08:15, Florian Smeets wrote: … I suspect be61deae0aa2 … Thanks! I remembered "breaking change" somewhere, couldn't find it before I sent my previous email. So, I can work around by specify

/var/crash/vmcore.* not present (was: Kernel panic on HEAD …)

On 29/03/2025 20:46, Steven Harms (High-Security Mail) wrote: … two questions: 1. Why am I not getting any panic dump artifacts? 2. … geli list or (with the port) lsblk /dev/ada0

Re: pkgbase major version upgrades

On 28/12/2024 10:17, Graham Perrin wrote: Someone might like to update <https://wiki.freebsd.org/PkgBase#major>, where the current example is 11 to 12. :x86:64 was recently a cause of confusion for someone (not me); and so on. Ideally, verify the validity of the updated section with

iwlwifi kernel panics, Wireless 7260, main-n275833-136c5e17b61a (2025-03-07)

136c5e17b61a from pkgbase base_latest. First panic today, Saturday 2025-03-08 02:18, in response to service netif restart wlan1 at home with ssid 'piano5'. Photographed five minutes after the command (whilst the computer was visibly fr

iwm(4) occasionally troublesome since before main-n274579-50c1e179b584

Subject line changed; _before_ main-n274579-50c1e179b584. I first encountered trouble with 50c1e179b584 (<50c1e179b584f43ba82e9afc91b25ec4831b58ef>, 2025-01-05) with eduroam, on my first day back at work after the Christmas break. Boot environment named 1500030-005-base. Today, with a clone

Re: iwm(4) occasionally troublesome since main-n274579-50c1e179b584 (2025-01-05)

On 10/01/2025 04:19, Adrian Chadd wrote: … Can you provide a "this is good" and "this is broken" pair of commit hashes from all of your build environments? … No recent build environment, I use pkgbase. So, realistically, the closest that I can get is this pair of lines from my previous

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On 09/10/2024 07:35, Paul Floyd wrote: … ld-elf.so.1: Shared object "libmd.so.6" not found, … pkgbase context: |

1500024, libmd.so.6 and libmd.so.7 (was: FYI: make's "max_jobs" needs to be separated from -j (now?))

On 02/10/2024 14:19, dsdq...@hotmail.com wrote: … (now) missing libmd.so.6. … sys: Chase libmd version bump with a __FreeBSD_version bump · freebsd/freebsd-src@e3953c0

Re: Wake (resume) regression?

On 01/10/2024 03:21, Graham Perrin wrote: Has anything changed in the past two months that might cause wake to become unreliable? … IIRC the unreliability became noticeable not long after the bump to 1500023. That was around the end of August (with pkgbase). … Correction: that was

Wake (resume) regression?

Has anything changed in the past two months that might cause wake to become unreliable? nvidia-driver-470, if that's relevant. Built from source. HP ZBook 17 G2. IIRC the unreliability became noticeable not long after the bump to 1500023. That was around the end of August (with pkgbase). Pr

Kernel panics with Widevine and htop: VNPASS in sys/kern/vfs_cache.c

On 16/09/2024 04:48, Mark Millard wrote: Graham Perrin wrote on Date: Wed, 22 May 2024 20:32:42 UTC : Reproducible at <https://bitmovin.com/demos/drm>. <https://codeberg.org/grahamperrin/freebsd-src/issues/10> This is a list message that is directly explicit about various t

Re: CURRENT kernel crash beyond git: 02d15215cef2

On 26/05/2024 13:45, Herbert J. Skuhra wrote: … No, idea why the fix hasn't been committed yet: … A few hours earlier: uma: Fix improper uses of UMA_MD_SMALL_ALLOC · freebsd/freebsd-src@d25ed65 HTH

Chromium with Widevine: kernel panic: condition vp->v_type == VDIR || VN_IS_DOOMED(vp) not met ⋯vfs_cache.c:3452 (vn_fullpath_dir)

Reproducible at .

CURRENT 220ee18f1964 memstick kernel panic, MacBookPro8,3

Originally posted to Photograph:

Boot failure, amd64 (HP EliteBook 650 G10)

amd64. AFAICT the EliteBook 650 G10 was introduced around May 2023. Does anything in the three photographs tally with a report in Bugzilla? Any overlap with fo

99132daf6f70 rc.d/ldconfig: Prepend rtld stdlib paths to ldconfig(32)_paths

On Mon, 20 Nov 2023 at 08:48, Dima Panov wrote: > On 20.11.2023 06:48, Graham Perrin wrote: > >> … >> ldconfig: warning: /lib32: No such file or directory >> > > It is related to > https://cgit.freebsd.org/src/commit/?id=99132daf6f70cb0cc969c555d3612547fa3c

FreeBSD user environment repeatedly inferior to kernel (was: uname -KU 1500001 1500000)

On Sun, 1 Oct 2023 at 20:28, Graham Perrin wrote: > User environment (150) inferior to kernel (151). > > … I discovered a comparable mismatch from build and installation on 9th November. Any ideas? I use devel/ccache4 4.8, if that's relevant. Copied from : % uname -KU 1

Re: uname -KU 1500001 1500000

On Mon, 2 Oct 2023 at 08:33, Mark Millard wrote: > Or file and ls results for the amd64.amd64/usr.bin/uname/uname.o ? > (Just checking for if there are surprises.) Please, where would I find that file? I'm lost

Re: kernel 100% CPU

On 03/09/2023 20:25, Mateusz Guzik wrote: … Sorry mate, neglected to specify: collect sysctl -a once you run into the problem. Once I look at that I'm probably going to ship some debug patches to narrow it down. I had what might be the same issue this afternoon, for the first time in w

vfs.zfs.arc.min (was: how to set vfs.zfs.arc.max in 15-current ?)

On 13/10/2023 07:46, Toomas Soome wrote: On 13. Oct 2023, at 09:35, void wrote: On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote: Set also vfs.zfs.arc.min to some value higher than zero. aha! that worked!!! :D root@beer:/root# sysctl vfs.zfs.arc.min=1073741824 vfs.zfs.arc.min:

Occasional suspend/sleep failures: race? USB, HP dock, ZFS, three L2ARC devices.

On 31/08/2023 19:42, Graham Perrin wrote (to freebsd-current alone, <https://lists.freebsd.org/archives/freebsd-current/2023-August/004509.html>): I have a suspend.sh script that aims to take three cache devices offline before sleep of the computer: % grep -v -e '# ' /etc/r

Occasional supend/sleep failures: race? USB, HP dock, ZFS, three L2ARC devices.

On 31/08/2023 19:42, Graham Perrin wrote (to freebsd-current alone, <https://lists.freebsd.org/archives/freebsd-current/2023-August/004509.html>): I have a suspend.sh script that aims to take three cache devices offline before sleep of the computer: % grep -v -e '# ' /etc/r

Re: uname -KU 1500001 1500000

On 01/10/2023 23:41, Mark Millard wrote: That indicates that __FreeBSD_version was 150 when the uname that was run was built but the running kernel was built when __FreeBSD_version was 151 . (Presumes a lack of use of OSVERSION to override the getosreldate result for the kernel case.)

uname -KU 1500001 1500000

User environment (150) inferior to kernel (151). Is this type of discrepancy ever normal/acceptable? Below, builds and installations were orderly. % grep -C 2 completed\ on /var/log/buildworld.log  267.66 real   176.81 user    81.72 sys -

buildkernel: Cleaning for nvidia-driver-470-470.161.03: [all] Stopped -- signal 22

The tail of a log: … Building /usr/obj/usr/src/amd64.amd64/sys/GENERIC/kernel.full --- kernel.full --- linking kernel.full ctfmerge -L VERSION -g -o kernel.full ...   text  data    bss    dec hex   filename   20670038   1677321   19288064   41635423   0x27b4e5f kernel.full

vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available)

On 16/09/2023 01:28, Glen Barber wrote: o A fix for the ZFS block_cloning feature has been implemented. Thanks I see , with

Re: Continually count the number of open files

On 12/09/2023 17:19, Bakul Shah wrote: On Sep 11, 2023, at 11:38 PM, Graham Perrin wrote: Can anything like systat(1) present a count, continually? How about while sleep 0.1; do sysctl -n kern.openfiles; done That's ideal, thanks. I knew about the sysctl, but not how to f

Continually count the number of open files

Can anything like systat(1) present a count, continually? I'd like to monitor, after log in to Plasma (X11), in connection with .

Re: ZFS Panics Still

On 12/09/2023 00:17, Cy Schubert wrote: … poudriere … panic: vm_page_dequeue_deferred: page 0xfe000b7e9748 has unexpected queue state … is for arm64. Should we broaden the hardware field, there?

/var/db/etcupdate/ in hier(7) (was: user problems when upgrading to v15)

On 09/09/2023 17:02, John Baldwin wrote: On 9/2/23 7:11 AM, Dimitry Andric wrote: … … /var/db/etcupdate/conflicts, … Shall I make a simple (non-contentious) pull request for hier(7) to include /var/db/etcupdate/ and the conflicts/ subdirectory? /var/db/etcupdate/ is present by default wi

Re: kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time

On 03/09/2023 10:26, Michael Gmelin wrote: On Sat, 2 Sep 2023 09:53:38 +0100 Graham Perrin wrote: Some inspections are extraordinarily time-consuming. Others complete very quickly, as they should. One recent inspection took more than half an hour. Anyone else? Does `git clone https

sysutils/panicmail and boot environments

For the penultimate panic: panicmail was received (in my Gmail Inbox). For the most recent panic: no panicmail in the same Inbox. Might this be, because the kernel panicked in a different boot environment? If so: will a temporary boot of the env

Re: kernel 100% CPU

On 03/09/2023 17:55, Mateusz Guzik wrote: On 9/3/23, Graham Perrin wrote: On 02/09/2023 18:31, Mateusz Guzik wrote: On 9/2/23, Graham Perrin wrote: … I began the trace /after/ the issue became observable. Will it be more meaningful to begin a trace and then reproduce the issue (before the

Re: kernel 100% CPU

On 02/09/2023 18:31, Mateusz Guzik wrote: On 9/2/23, Graham Perrin wrote: … I began the trace /after/ the issue became observable. Will it be more meaningful to begin a trace and then reproduce the issue (before the trace ends)? … Looks like you have a lot of unrelated traffic in there

Re: kernel 100% CPU

On 03/09/2023 15:02, Mateusz Guzik wrote: On 9/3/23, Graham Perrin wrote: … The script is intended to run when you have git executing for a long time. Ah, sorry for my poor understanding. Re: <https://lists.freebsd.org/archives/freebsd-current/2023-September/004539.html>, I ran i

Re: kernel 100% CPU

On 03/09/2023 09:01, Juraj Lutter wrote: … The script mjg@ provided is not a shell script. The script filename is “script.d” where you should put the above-mentioned DTrace script (without the "dtrace -s script.d -o out” line). Thanks, I guess that I'm still doing something wrong: root@mowa

Re: kernel 100% CPU

On 02/09/2023 18:31, Mateusz Guzik wrote: Looks like you have a lot of unrelated traffic in there. Run this script: #pragma D option dynvarsize=32m profile:::profile-997 /execname == "find"/ { @oncpu[stack(), "oncpu"] = count(); } /* * The p_flag & 0x4 test filters out kernel threa

Re: kernel 100% CPU …

On 02/09/2023 18:31, Mateusz Guzik wrote: … upload it to freefall … Sorry, that's no longer possible. Do people have a preferred FreeBSD-oriented location/service for FreeBSD-specific files? TIA In the meantime: I find the symptom reproducible, quite frequently, without using poudriere.

Re: kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time

On 02/09/2023 10:17, Mateusz Guzik wrote: On 9/2/23, Graham Perrin wrote: Some inspections are extraordinarily time-consuming. Others complete very quickly, as they should. One recent inspection took more than half an hour. Anyone else? A screenshot: <https://i.imgur.com/SK9qvfw.png>

kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time

Some inspections are extraordinarily time-consuming. Others complete very quickly, as they should. One recent inspection took more than half an hour. Anyone else? A screenshot: % pkg iinfo poudriere-devel poudriere-devel-3.3.99.20220831 % uname -aKU FreeBSD m

Unicode input regression

Following my first pkg upgrade with 15.0-CURRENT, I no longer get the required character after input. In applications such as Dolphin, Konsole, Firefox, and Thunderbird: the visible input (e.g. code 2013 for an en dash) is followed by disappearance. In Code - OSS (editors/vscode): input is fo

Occasional supend/sleep failure

I have a suspend.sh script that aims to take three cache devices offline before sleep of the computer: % grep -v -e '# ' /etc/rc.suspend | uniq | grep -B 3 -A 2 suspend.sh #!/bin/sh # /usr/local/sbin/suspend.sh     echo "Usage: $0 [apm|acpi] [standby,suspend|1-4]" % grep -v -e '# ' /usr/lo

Re: user problems when upgrading to v15

d reset passwords and am retrying this. BW Thanks. For clarity: did the routine /not/ prompt you to edit the file (in which, you would have seen conflict markers etc.)? On 8/30/2023 7:21 PM, Graham Perrin wrote: On 31/08/2023 03:00, brian whalen wrote: … I ran etcupdate resolve accepting

Re: user problems when upgrading to v15

On 31/08/2023 03:00, brian whalen wrote: … I ran etcupdate resolve accepting the remote option and saw 2 issues. The root user's password was deleted. The non root user no longer existed. Logically, remote does not include things such as your root user's password.

Re: pkg problems with v15

On 31/08/2023 02:59, brian whalen wrote: … pkg: http://pkgmir.geo.freebsd.org/FreeBSD:15:amd64/quarterly/meta.txz: Not Found … For 15.0-CURRENT you should use latest; don't expect quarterly. Also, it's probably too soon for latest. 1.

(264305, 268393, 272878) 14-ALPHA2 panic on cold boot

On 29/08/2023 09:09, cglogic wrote: … I found two related bug reports: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264305 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 My backtrace is the same as in reported issues. So I did not write it from a screen to a paper. As I underst

etcupdate -p, and other uses of etcupdate(8)

On 28/08/2023 09:53, Tomoaki AOKI wrote: On Sun, 27 Aug 2023 18:16:35 +0100 Graham Perrin wrote: On 07/08/2023 16:51, Kevin Oberman wrote: … …  "etcupdate -p". … <https://mastodon.bsd.cafe/@fbfortune/110960171470986602> … Is this fortune-provided tip outdated? … for sr

etcupdate -p, and other uses of etcupdate(8) (was: Has the update procedure changed?)

On 07/08/2023 16:51, Kevin Oberman wrote: UPDATING seems to match the Makefile except that Makefile is far less detailed. The Makefile even says "See src/UPDATING `COMMON ITEMS' for more complete information." …  "etcupdate -p". … pro

273297 – BOOT time panic after preloading TSLOG data (was: 7addfafe73e0 early boot kernel panics)

Thanks, people. I couldn't attach a photograph to the opening post (entire emails, not just attachments, disappear in the ether). Instead, a photo here:

7addfafe73e0 early boot kernel panics

I could not get 7addfafe73e0 to boot. (2023-08-21, 21 hours ago). I reverted to a edacf4b4824a boot environment, which is fine. Should I simply update to ? Assuming a known issue with 7addfafe73e0

Re: ports-mgmt/portconf – not src.conf(5) – to specify multiple flavours of a port for buildkernel purposes

On 22/08/2023 06:42, Graham Perrin wrote: … % cat /usr/local/etc/ports.conf graphics/gpu-firmware-radeon-kmod: FLAVORS=btc sumo turks % Still, there's guesswork. I have /no/ idea whether the FLAVORS part of that last line is valid :-) Time will tell. /me tails /var/log/buildkerne

ports-mgmt/portconf – not src.conf(5) – to specify multiple flavours of a port for buildkernel purposes

On 22/08/2023 05:34, Warner Losh wrote: How might I use /etc/src.conf to achieve much the same, with a different port? I thought stuff like this went in ports.conf... … Warner solves another mystery. Thanks! Honestly, I was oblivious to the possibility: % man -P cat 5 ports.conf

src.conf(5) to specify multiple flavours of a port

In a thread elsewhere, as an example that did /not/ involve src.conf, Mark Johnston wrote: $ cd /usr/ports/graphics/gpu-firmware-intel-kmod $ sudo make reinstall FLAVOR=kabylake How might I use /etc/src.conf to achieve much the same, with a different port? A recent edition of my file inclu

GPU firmware: could not load firmware image, error 2

On 20/08/2023 23:06, Graham Perrin wrote: Some relevant messages at<https://pastebin.com/raw/wxWi8YS7>. Should I be concerned by error 2 in these contexts? % pkg iinfo drm-510-kmod drm-510-kmod-5.10.163_7 % uname -aKU FreeBSD mowa219-gjp4-8570p-freebsd 14.0-ALPHA2 FreeBSD 14.0-ALPHA2

GPU firmware: could not load firmware image, error 2

Some relevant messages at. Should I be concerned by error 2 in these contexts? % pkg iinfo drm-510-kmod drm-510-kmod-5.10.163_7 % uname -aKU FreeBSD mowa219-gjp4-8570p-freebsd 14.0-ALPHA2 FreeBSD 14.0-ALPHA2 amd64 1400094 #4 main-n264868-edacf4b4824a-dirty: Fr

Boot failures with 14.0-ALPHA1 and 14.0-ALPHA2

On 18/08/2023 13:21, Graham Perrin wrote: I'll update to ALPHA2. Another failure. In this case, removal of a USB device was unnecessary; the next start succeeded. % bectl list -c creation | grep edacf4b4824a n264868-edacf4b4824a-a NR /  460G  2023-08-19 03:54 n2

ZFS deadlock in 14: with ZIL :-)

On 19/08/2023 11:31, Dimitry Andric wrote: On 19 Aug 2023, at 09:36, Graham Perrin wrote: … <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271945#c0> no ZIL; I never used the feature. The ZIL always exists, but it can be stored on a separate device for performance reason

ZFS deadlock in 14: without ZIL

On 19/08/2023 00:03, Mark Millard wrote: I believe the below quoted messages were reports of deadlocks based on after the following 2 MFV being in place in their environments: Thu, 10 Aug 2023 . . . • git: cd25b0f740f8 - main - zfs: cherry-pick fix from openzfs Martin Matuska • git: 2

Boot failures with 14.0-ALPHA1

I'll update to ALPHA2. In the meantime, briefly: – no visible progress beyond the four lines of EFI framebuffer information. In each case, I worked around by removing a USB flash drive that's used for L2ARC. The most recent incident was preceded

etcupdate -B, /.cshrc and /.profile

If I recall correctly, a few hours ago etcupdate -B resulted in removal of two files: /.cshrc /.profile Is this degree of checking/removal a novelty? (I can't recall the files' contents, or when I created them. I guess that I carelessly created them as dot files months ago without realising

Re: Fwd: Unreliability with DHCP

On 06/08/2023 17:05, Warner Losh wrote: On Sun, Aug 6, 2023 at 12:38 AM Kevin Oberman wrote: On Sat, Aug 5, 2023 at 3:16 PM Graham Perrin wrote: On 05/08/2023 12:39, Oleksandr Kryvulia wrote: > … > > As dirty workaround I have in my /etc/

Re: Speed improvements in ZFS

On 15/08/2023 13:05, Alexander Leidinger wrote: … periodic runs … Here, I get a sense that these benefit greatly from L2ARC. … So whatever was done inside ZFS or VFS or nullfs between 2023-06-19 and 2023-07-20 has given a huge speed improvement. …

Re: ZFS deadlock in 14

On 11/08/2023 04:32, Kevin Bowling wrote: Spoke too soon still seeing zfs lockups Kevin, do you have a log device? (ZIL) under heavy poudriere workload … Can you tell what was building when the problem occurred? For example, qutebrowser /usr/local/poudriere/data/logs/bulk/main-default/la

Re: 14.0 boot failure

On 09/08/2023 07:10, Kevin Oberman wrote: I closed the ticket. I wasn't aware of a ticket, thanks for the update. Yesterday's 09c20a293280 boots fine for me.

Re: 14.0 boot failure

On 05/08/2023 00:45, Kevin Oberman wrote: A new kernel built from sources pulled today (4-Aug) at 5:26 UTC fails to boot. … I refrained from updating after reading this. Any news? TIA OpenPGP_signature Description: OpenPGP digital signature

Re: ZFS deadlock in 14

maybe. OpenPGP_signature Description: OpenPGP digital signature

Re: Has the update procedure changed?

On 06/08/2023 09:20, Mark Millard wrote: … https://docs.freebsd.org/en/books/handbook/cutting-edge/#makeworld section 26.6.1 lists: # git pull /usr/src check /usr/src/UPDATING # cd /usr/src # make -j4 buildworld # make -j4 kernel # shutdown -r now # etcupdate -p # cd /usr/src # make installworl

Re: Has the update procedure changed?

On 08/08/2023 03:50, Robert Huff wrote: … 1) It would be really nice is someone would take a look and make sure these 100% non-contradictory. … Looks by people should, ideally, include: 209744 – Move installation instruction

service routing restart, service dhclient restart (was: Unreliability with DHCP)

Thanks, On 06/08/2023 08:36, Oleksandr Kryvulia wrote: … In my case default route is assigned by dhclient, so 'service routing restart' must be run quickly after 'service netif restart' - before we receive dhcp offer. Is this documented and explained somewhere, or did you learn through tria

service routing restart (was: Unreliability with DHCP)

On 05/08/2023 23:16, Graham Perrin wrote: On 05/08/2023 12:39, Oleksandr Kryvulia wrote: 04.08.23 19:07, Graham Perrin пише: … As dirty workaround I have in my /etc/rc.resume service netif restart service routing restart  … 'service routing restart' can be problematic. Please

Re: Fwd: Unreliability with DHCP

On 05/08/2023 12:39, Oleksandr Kryvulia wrote: 04.08.23 19:07, Graham Perrin пише: Can anyone from freebsd-net@ help? Forwarded Message Subject: Unreliability with DHCP Date: Sun, 30 Jul 2023 16:17:43 +0100 From: Graham Perrin Organisation: FreeBSD To

Fwd: Unreliability with DHCP

Can anyone from freebsd-net@ help? Forwarded Message Subject:Unreliability with DHCP Date: Sun, 30 Jul 2023 16:17:43 +0100 From: Graham Perrin Organisation: FreeBSD To: FreeBSD CURRENT 1. Sleep (suspend) whilst connected to one network 2. connect to a

Unreliability with DHCP

1. Sleep (suspend) whilst connected to one network 2. connect to a network elsewhere 3. wake (resume). Result: /etc/resolv.conf frequently contains outdated information. In some (maybe all) such cases, the IPv4 inet address is outdated; and so on. Which /etc/rc.d/ file(s) should I attempt t

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

On 21/06/2023 01:29, Graham Perrin wrote: … Thanks, people. A few hours ago I took a hint from one of the pages linked from <https://dan.langille.org/2020/01/01/listen-queue-overflow/>, added a line to my sysctl.conf(5). … % grep ipc /etc/sysctl.conf kern.ipc.soacceptqueue=256 % I

Re: Possible PEBKAC bug for fwget(8)?

On 07/07/2023 00:58, Kenneth Raplee wrote: … `fwget -vn pci`, it only prints out the following usage info: … I made what might have been the same mistake, . PCI pictured at , somehow I don't

Re: System lockups on 14-current with Plasma 5

Plasma here, packages upgraded a few hours ago. % uname -aKU FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n263900-cd9da8d072e4-dirty: Sat Jul  1 23:55:17 BST 2023 grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1400092 1400

Re: f81be7a8318b installworld failed

On 29/06/2023 19:12, Kyle Evans wrote: … This error indicates that for some reason we're trying to build during the install phase; either tree was updated since last build, messed up timestamps on build artifacts, messed up clock, etc. Whatever the case may be, make(1) sees the build output o

651d1efd96a6 buildworld failed, cd9da8d072e4 succeeded

On 29/06/2023 19:16, Graham Perrin wrote: % uname -KU 1400092 1400090 % uname -a FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n263799-f81be7a8318b-dirty: Mon Jun 26 22:09:58 BST 2023 grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys

Re: dhclient unable to negotiate on WPA2-Enterprise network (eduroam)

On 29/06/2023 09:07, Graham Perrin wrote: … I just realised my discrepancy above, 1400092 1400090. … I'll installworld then review. Sorry, review is delayed. (I remembered and repeated the cause of the discrepancy, an installworld failure <https://lists.freebsd.org/archives

651d1efd96a6 buildworld failed

% uname -KU 1400092 1400090 % uname -a FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n263799-f81be7a8318b-dirty: Mon Jun 26 22:09:58 BST 2023 grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 % bectl list -c creation | tail -n

f81be7a8318b installworld failed

… ===> stand/efi/loader_4th (install) installing DIRS BINDIR install  -d -m 0755 -o root  -g wheel  /boot /usr/local/bin/ccache cc -target x86_64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin  -O2 -pipe -O3 -pipe -march=native -mtune=n

Re: dhclient unable to negotiate on WPA2-Enterprise network (eduroam)

On 28/06/2023 17:54, Naman Sood wrote: After doing a system update to the newest CURRENT, dhclient is not able to obtain an IP address for itself over an eduroam WPA2-Enterprise PEAP network. … No problem with eduroam here, % uname -aKU FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD

Re: f190c36b5d45 buildworld failure: ld: error: undefined symbol: SSL_get_peer_certificate

On 26/06/2023 05:31, Graham Perrin wrote: On 25/06/2023 20:57, Graham Perrin wrote: From <https://reviews.freebsd.org/P590$177>: clang: error: linker command failed with exit code 1 (use -v to see invocation) *** [dma.full] Error code 1 make[5]: stopped in /usr/src/libexec/dma/d

f190c36b5d45 buildworld failure: ld: error: undefined symbol: SSL_get_peer_certificate

On 25/06/2023 20:57, Graham Perrin wrote: From <https://reviews.freebsd.org/P590$177>: clang: error: linker command failed with exit code 1 (use -v to see invocation) *** [dma.full] Error code 1 make[5]: stopped in /usr/src/libexec/dma/dmagent .ERROR_TARGET='dma.full' .ERROR

debug.verbose_sysinit=1 and kern.msgbufsize=196608

On 25/06/2023 21:32, David Wolfskill wrote: On Sun, Jun 25, 2023 at 09:20:40PM +0100, Graham Perrin wrote: When debug.verbose_sysinit=1 is set in loader.conf(5), is normal to _not_ have BOOT and copyright messages? It's normal (in that situation) to require a higher value in kern.msgbufsi

debug.verbose_sysinit=1

When debug.verbose_sysinit=1 is set in loader.conf(5), is normal to _not_ have BOOT and copyright messages? Boot began with: Jun 25 06:49:31 mowa219-gjp4-8570p-freebsd syslogd: kernel boot file is /boot/kernel/kernel – then (timestamps etc. trimmed): DEP)... done.    malloc_init(&M_JADDREF)

Freeze with mount of a UFS volume, main-n263630-ab3e6234ab6e-dirty

Froze at 06:40, when I used Plasma to mount and open the volume. Photographs: . The freeze occurred a split-second after a click; the option to mount and open was replaced by the option to safely remove. Probed not long aft

f190c36b5d45 buildworld failure

From : clang: error: linker command failed with exit code 1 (use -v to see invocation) *** [dma.full] Error code 1 make[5]: stopped in /usr/src/libexec/dma/dmagent .ERROR_TARGET='dma.full' .ERROR_META_FILE='/usr/obj/usr/src/amd64.amd64/libexec/dma/dmagent/

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

On 20/06/2023 15:41, Gary Jennejohn wrote: On Tue, 20 Jun 2023 12:04:13 +0200 Alexander Leidinger wrote: Quoting Gary Jennejohn (from Tue, 20 Jun 2023 07:41:08 +): … In other words the software listening on it didn't process the request fast enough and a backlog piled up (e.g apache Li

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

Please, what's the meaning of the sonewconn lines? % tail -f -n 0 /var/log/messages Jun 20 04:08:41 mowa219-gjp4-8570p-freebsd su[4159]: grahamperrin to root on /dev/pts/6 Jun 20 04:12:20 mowa219-gjp4-8570p-freebsd apps.plugin[3178]: Cannot fetch process 4501 command line (command 'sysctl') J

Re: Following a panic (271945): zpool status reports 1 data error but identifies no file

On 11/06/2023 19:06, Graham Perrin wrote: … I think it likely that the reportedly permanent error will simply disappear when the scrub completes. True; % date ; zpool status -x Mon 12 Jun 2023 02:00:49 BST all pools are healthy % zdb … might be looking for a needle in a haystack, when

Directory 1002/ missing from /var/run/user/

What normally takes care of creation of the numbered directories? A few hours ago, it was unexpectedly missing: % whoami grahamperrin % ls -dhln ~ drwxr-xr-x  143 1002  1002   240B 11 Jun 13:38 /home/grahamperrin % ls -hl /var/run/user total 1 drwx--  2 root    wheel  2B 19 May 0

Re: Following a panic (271945): zpool status reports 1 data error but identifies no file

On 11/06/2023 18:51, Cy Schubert wrote: Zpool export/import or reboot may fix this. Thanks, it's my boot pool, and there have been two boots since my first email: % grep BOOT /var/log/messages Jun 11 13:29:13 mowa219-gjp4-8570p-freebsd kernel: ---<>--- Jun 11 13:50:04 mowa219-gjp4-8570p-fre

Re: Following a panic (271945): zpool status reports 1 data error but identifies no file

On 11/06/2023 14:48, Alexander Motin wrote: On 11.06.2023 08:02, Graham Perrin wrote: See below, should I begin scrubbing? Or (before I begin) might zdb reveal something useful? The only case when I would not recommend to run scrub is if there is a suspicion of memory corruptions on the

Following a panic (271945): zpool status reports 1 data error but identifies no file

See below, should I begin scrubbing? Or (before I begin) might zdb reveal something useful? The supposed error was observable after /271945 – panic: deadlres_td_sleep_q: possible deadlock detected for 0xfe0133324ac0 (stat), block

Re: ZFS: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed

On 27/05/2023 16:30, Graham Perrin wrote: Three panics with c2c9ac88c2bb (2023-05-26, 1400089): … Martin, if you'd like to take <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271772>, please go ahead. Thanks OpenPGP_signature Description: OpenPGP digital signature

  1   2   3   4   5   >