IPv6 inconsistent local routing

Hello all, with IPv4 the handling of local traffic was simple: all

Re: IPv6 inconsistent local routing

On Wed, Oct 20, 2021 at 10:06:00PM +, Bjoern A. Zeeb wrote: ! > You might say, it does not usually make sense to route traffic local-to- ! > local over an IPadress of an outbound interface. But actually this ! > is common practice in e.g. failover scenarios, where you don't know ! > in the app

Re: IPv6 inconsistent local routing

Friends, thanks to the good vibrations, this is going easier than I thought. The problem is already well known, and is actually intended behaviour (while probably not "works as designed"). The BPF didn't work with these circumstances either, but that one was fixed: https://reviews.freebsd.org/

IPv6 checksum errors with divert

I'm getting these errors when e.g. querying the root nameservers: 05:58:50.916825 IP6 (flowlabel 0x08c7c, hlim 64, next-header UDP (17) payload length: 62) 2003:e7:17ff:192c:41d:92ff:fe01:301.42518 > 2600:1401:2::a.53: [bad udp cksum 0x24ca -> 0x48

Re: IPv6 checksum errors with divert

Hi Andrey, On Fri, Oct 29, 2021 at 08:45:38PM +0300, Andrey V. Elsukov wrote: ! 27.10.2021 16:28, Peter пишет: ! > I see these checksum error when the packet goes into the divert ! > socket, I see it when the packet comes back from divert, and I ! > see it when the packet goes out

Re: IPv6 checksum errors with divert

Hi Andrey, hi all, there is at least one further issue with divert (and dummynet) and IPv6: If I put EITHER a divert OR a dummynet pipe/queue into the OUTgoing (layer3) ruleset to the uplink interface, then Youtube is not able to insert their advertisments into playback, and may hang entirly o

IPv6 inflight fragmentation

>From what I understood, inflight fragmentation (on an intermediate router) is not practical with IPv6. But it happens: This router has inbound ethernet and outbound PPPoE: vtnet0: flags=8943 metric 0 mtu 1500 tun0: flags=8151 metric 0 mtu 1492 And that's what is transported - Incoming on vt

Re: IPv6 inflight fragmentation

Hi Andrey! On Mon, Nov 01, 2021 at 02:44:50PM +0300, Andrey V. Elsukov wrote: ! 31.10.2021 05:24, Peter пишет: ! > From what I understood, inflight fragmentation (on an intermediate router) ! > is not practical with IPv6. But it happens: ! > And it doesn't seem like these pa

12.3-RC1 fails to install pkg

Not sure if this is intended or not - it certainly wasn't the case with 12.2, and it likely will break a few automated deploys: # ls -la pkg* -rw-r--r-- 1 root wheel 4011616 Nov 17 17:52 pkg-1.17.2.pkg # pkg add /tmp/vb/pkg-1.17.2.pkg < /dev/null The package management tool is not yet instal

Re: 12.3-RC1 fails to install pkg

> Can you try this? > # pkg add -y file:///tmp/vb/pkg-1.17.2.pkg Hi Glen, tried, doesn't help. I found the cause in the meantime, it's #370420 It states: * Chop off the final "-" (version delimiter) and check the name that * precedes it. If we didn't have a version delim

12.3-RC1 fails to compile perl, tcl86 (dtrace error)

Hija, I get a strange error when trying to build perl or tcl from ports: dtrace: failed to establish error handler: "/usr/lib/dtrace/ipfw.d", line 106: failed to copy type of 'inp': Conflicting type is already defined That file ipfw.d appears to be new in 12.3, but I'm clueless what the error

12.3-RC1 errors on boot and shutdown

Hija, when we're already at it: there are errors reported during startup and shutdown. In startup: > xargs: not found This one comes from /etc/rc.d/rctl. Consequentially, rctl rules will not be loaded. The flaw was always there, but (for whatever reason) /etc/rc.d/rctl is now run very early

Re: 12.3-RC1 fails to compile perl,tcl86 (ipfw dtrace issue)

## this seems not have arrived on the list at first send ## > dtrace: failed to establish error handler: "/usr/lib/dtrace/ipfw.d", > line 106: failed to copy type of 'inp': Conflicting type is already defined > That file ipfw.d appears to be new in 12.3, but I'm clueless what > the error means (a

Re: 12.3-RC1 errors on boot and shutdown

Eirik Øverby wrote; > > > waitwhat? > > > This means we *can not* upgrade our 100+ systems upon release, because > > > we cannot at the same time roll out local changes to basic stuff in > > > /etc/rc.d .. > > > > With approval of re_at_, the change's merged to stable/12 and will be > > incl

Re: 12.3-RC1 fails to compile perl,tcl86 (ipfw dtrace issue)

On Mon, Nov 22, 2021 at 10:45:09AM -0500, Mark Johnston wrote: ! On Sun, Nov 21, 2021 at 10:46:30PM +0100, Peter wrote: ! > ## this seems not have arrived on the list at first send ## ! > ! > > dtrace: failed to establish error handler: "/usr/lib/dtrace/ipfw.d", ! > &

Re: 12.3-RC1 fails to compile perl,tcl86 (ipfw dtrace issue)

On Mon, Nov 22, 2021 at 04:09:43PM -0500, Mark Johnston wrote: ! On Mon, Nov 22, 2021 at 09:52:38PM +0100, Peter wrote: ! > On Mon, Nov 22, 2021 at 10:45:09AM -0500, Mark Johnston wrote: ! > ! On Sun, Nov 21, 2021 at 10:46:30PM +0100, Peter wrote: ! > ! > ## this seems not have arrived

12.3: igb driver does not receive vlan-tagged packets

Hija, after swapping network interface card (re0) to igb0, my networking failed. I found that igb does send out vlan tagged packets, but not receive any answers, unless a vlan* device was previousely attached with the required vlan number (observed with tcpdump). My current workaround is this

12.3: vt driver does not provide virtual console terminals

Hija, the (current default) vt console driver does not provide multiple virtual terminals on VGA console (no KMS). Only one console terminal is accessible. The others are present, they can be switched to with Alt-Fn, but they provide no I/O and are just black. When reverting to the sc console d

12.3: kernel crash when stopping disks

Hija, that one doesn' seem to like me. Dec 5 01:08:14 edge gstopd[8837]: da0:0@Sun Dec 5 01:08:14 2021 Dec 5 01:08:25 edge gstopd[64139]: Error received from stop unit command Dec 5 01:08:25 edge kernel: ahd0: Recovery Initiated - Card was not paused Dec 5 01:08:25 edge kern

12.3: "swapon -a" crashes the system

Hija, if you run out of swapspace and you think you might just create some extra devices and add them to /etc/fstab and then run "swapon -a" to enable them, don't do that. The result might look like this: kernel: pid 12296 (daemon), jid 5, uid 5100: exited on signal 10 (core dumped) kernel: pid

Re: 12.3: "swapon -a" crashes the system

On Thu, Dec 09, 2021 at 02:35:55PM +0700, Eugene Grosbein wrote: ! 09.12.2021 13:11, Peter wrote: ! ! > if you run out of swapspace and you think you might just create ! > some extra devices and add them to /etc/fstab and then run "swapon -a" ! > to enable them, don'

[ahd driver] 12.3: kernel crash when stopping disks

> Dec 5 01:08:25 edge gstopd[64139]: Error received from stop > unit command > Dec 5 01:08:25 edge kernel: ahd0: Recovery Initiated - Card was > not paused > Dec 5 01:08:25 edge kernel: >> Dump Card State > Begins < > Dec 5 01:08:25 edge kernel: ahd0: Dump

Re: 12.3: vt driver does not provide virtual console terminals

On Thu, Dec 09, 2021 at 01:29:19PM -0500, Ed Maste wrote: ! On Sat, 4 Dec 2021 at 13:27, Peter wrote: ! > ! > There is also this error reported: ! > > module_register_init: MOD_LOAD (vesa, 0x80e22c00, 0) error 19 ! ! Are you trying to load vesa.ko via /boot/loader.conf

Re: 12.3: igb driver does not receive vlan-tagged packets

er" capability. With the same ! differential, it will work for you also. ! ! regards ! Ozkan ! ! On Sat, Dec 4, 2021 at 1:54 PM Peter wrote: ! > ! > Hija, ! > ! > after swapping network interface card (re0) to igb0, my networking ! > failed. ! > ! > I found that igb do

12.3:[ZFS pointer corruption] kernel crash exporting FreeBSD src repo

Hija, I have a filesystem with the FreeBSD src repo clone. When I do > git checkout-index -a --prefix=/new-filesystem/ in 5 of 6 cases I get a kernel crash. The repo otherwise looks sane: # git status On branch local.generic Your branch is ahead of 'origin/releng/12.3' by 51 commits. (

Re: 12.3:[ZFS pointer corruption] kernel crash exporting FreeBSD src repo

On Mon, Dec 13, 2021 at 08:34:13PM +0100, Peter wrote: ! I have a filesystem with the FreeBSD src repo clone. ! ! When I do ! > git checkout-index -a --prefix=/new-filesystem/ ! in 5 of 6 cases I get a kernel crash. ! ! Fatal trap 12: page fault while in kernel mode ! cpuid = 19; a

Re: dtrace bitfields failure (was: 12.3-RC1 fails ...)

Hija, sadly, I was too early in agreeing that the two patches 22082f15f9 68396709e7 together do solve the issue. They only do on a certain assumption, which does not hold true in all cases. Let's look at https://reviews.freebsd.org/D27213 This is the code in question that will tri

Re: dtrace bitfields failure (was: 12.3-RC1 fails ...)

On Tue, Jan 04, 2022 at 01:01:55PM -0500, Mark Johnston wrote: ! On Tue, Jan 04, 2022 at 04:05:53PM +0100, Peter wrote: ! > ! > Hija, ! > ! > sadly, I was too early in agreeing that the two patches ! > 22082f15f9 ! > 68396709e7 ! > together do solve the iss

Re: dtrace bitfields failure (was: 12.3-RC1 fails ...)

On Tue, Jan 04, 2022 at 05:58:13PM -0500, Mark Johnston wrote: ! On Tue, Jan 04, 2022 at 10:58:13PM +0100, Peter wrote: ! > On Tue, Jan 04, 2022 at 01:01:55PM -0500, Mark Johnston wrote: ! > ! On Tue, Jan 04, 2022 at 04:05:53PM +0100, Peter wrote: ! > ! > ! > ! > Hija, ! > !

stable/13: undefined symbol: dtrace_instr_size

Hija, when adding "device dtrace" to kernel conf, I get this: linking kernel.full ld: error: undefined symbol: dtrace_instr_size >>> referenced by dtrace_subr.c:0 (/usr/src/sys/cddl/dev/dtrace/amd64/dtrace_sub r.c:0) >>> dtrace_subr.o:(dtrace_trap) *** [kernel.full] Error code 1

Program crashes on stable/13 (but not on 12.3)

Hija, this program crashes SEGV on stable/13 after 135962 iterations, but continues to run on 12.3. My stable/13 is still at 22ba2970766 - if You happen to be on a newer level, then please just try this out. -- #include #include #include

Re: Program crashes on stable/13 (but not on 12.3)

On Sun, Mar 06, 2022 at 04:26:10AM +0700, Eugene Grosbein wrote: ! 06.03.2022 2:26, Peter wrote: ! ! Adding kib@ to CC: in case this is connected to recent commit by him. It is. ! > Hija, ! > ! > this program crashes SEGV on stable/13 after 135962 iterations, ! > but continues to

Different PATHs in /etc/rc and /etc/rc.shutdown

Quoting Andre Albsmeier: > Today I was bitten by the fact that /etc/rc.shutdown and /etc/rc set different > PATHs at least on 12.3-STABLE (I used a command sitting in /usr/local/sbin w/o > specifying its path and it worked in stop_cmd() but not in start_cmd()): > > /etc/rc.shutdown: PATH=/sbin:/

13.1: "ipfw forward" no longer works (after upgrade from 12.3)

Hija, I just upgraded from 12.3 to 13.1-STABLE, and now "ipfw forward" gets ignored. I checked with: $ ipfw add 1 fwd 10.1.0.120 all from any to any out I get an incrementing count there: # ipfw show 1 1 4101782871 fwd 10.1.0.120 ip from any to any out # ipfw show 1

13.1: "ipfw forward" TESTCASE for crosscheck

I did now a testcase, as follows: === root@zwlf:~ # cat /boot/loader.conf net.fibs="3" net.inet.ip.fw.default_to_accept=1 root@zwlf:~ # uname -a FreeBSD zwlf 12.3-RELEASE FreeBSD 12.3-RELEASE r371126 GENERIC amd64 root@zwlf:~ # k

Re: 13.1: "ipfw forward" no longer works (after upgrade from 12.3)

Ah, wow, that's cute. So I'm apparently not the only one. Thank You very much. Now there are two questions: 1. Why does this happen only on SOME systems? (I don't see an obvious reason yet.) The second question then is, what do we do to get it fixed. (This quite ruined my day.)

CORRECTION 13.1: "ipfw forward" TESTCASE for crosscheck

Message before was missing the most essential line (cut+paste error), correction as below. And I think I have found why some of my systems are not concerned by the bug: apparently the problem appears only with packets that are locally created. Packets that are traversed (with net.inet.ip.forward

Slow startup from D19488 (rtsol: sendmsg: Permission denied)

Hija, after upgrading 12.3 to stable/13, I am seeing these errors in all my jails: > Additional TCP/IP options: log_in_vain=1. > ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/c cmpat/pkg /usr/local/lib/compat/pkg > 32-bit compatibility ldconfig path: > rtso

Re: Slow startup from D19488 (rtsol: sendmsg: Permission denied)

Hello Bjoern, thanks much for the quick reply! On Tue, Mar 29, 2022 at 10:04:11PM +, Bjoern A. Zeeb wrote: ! On Tue, 29 Mar 2022, Peter wrote: ! ! Hi, ! ! I am a bit puzzled as after two years you are the first one to report ! that problem to my knowledge for either base system or

stable/13: ARC no longer self-tuning?

Hi, while up to Rel 12 the ZFS ARC adjusted it's size to the demand, in Rel. 13 it appears to be locked to a fixed minimum of 100M compressed. Consequentially I just got a machine stall/freeze under moderate load: no cmdline reaction (except in the guests), no login possible, all processes i

Re: Slow startup from D19488 (rtsol: sendmsg: Permission denied)

On Wed, Mar 30, 2022 at 08:59:24PM -0700, Kevin Oberman wrote: ! > ! I am a bit puzzled as after two years you are the first one to report ! > ! that problem to my knowledge for either base system or jails. ! > ! > This is what greatly wonders me, too. So I was stronly thinking ! > that I am doing

Re: Slow startup from D19488 (rtsol: sendmsg: Permission denied)

On Sun, Apr 03, 2022 at 10:27:59PM -0700, Kevin Oberman wrote: ! > Hi Kevin, ! > ! > (You are Kevin Oberman the network guru ?!?) ! > ! > Maybe a decade or so ago. After over a decade of retirement, I'm not sure ! how BGP is spelled. And why would the network fib? Ah, I see. So thats what happ

nfs stalls client: nfsrv_cache_session: no session

Hija, I have a problem with NFSv4: The configuration: Server Rel. 13.1-RC2 nfs_server_enable="YES" nfs_server_flags="-u -t --minthreads 2 --maxthreads 20 -h ..." mountd_enable="YES" mountd_flags="-S -p 803 -h ..." rpc_lockd_enable="YES" rpc_lockd_flags="-h ..." rpc_

Re: nfs stalls client: nfsrv_cache_session: no session

On Sat, Jul 16, 2022 at 01:43:11PM +, Rick Macklem wrote: ! Peter wrote: ! > Hija, ! > I have a problem with NFSv4: ! > ! > The configuration: ! > Server Rel. 13.1-RC2 ! > nfs_server_enable="YES" ! > nfs_server_flags="-u -t --minthreads 2 --maxth

close() taking minutes

Does this look familiar with anybody? ("truss -dD ls -l something") 0.047760369 0.17548 open("/etc/nsswitch.conf",O_RDONLY|O_CLOEXEC,0666) = 4 (0x4) 0.047845099 0.11290 fstat(4,{ mode=-rw-r--r-- ,inode=13886,size=272,blksize=4096 }) = 0 (0x0) 0.047932166 0.34182 read(4,"#\n# nsswit

Re: close() taking minutes (ZFS related)

On Fri, Jan 20, 2023 at 12:05:20PM +0100, Mateusz Guzik wrote: ! On 1/20/23, Peter wrote: ! > ! > Does this look familiar with anybody? ("truss -dD ls -l something") ! > ! > 0.047760369 0.17548 open("/etc/nsswitch.conf",O_RDONLY|O_CLOEXEC,0666) = ! > 4 (0x4

Re: close() taking minutes (ZFS related)

On Fri, Jan 20, 2023 at 03:55:43PM +0100, Mateusz Guzik wrote: ! offcpu.d: ! ! #pragma D option dynvarsize=32m ! ! /* ! * The p_flag & 0x4 test filters out kernel threads. ! */ ! ! sched:::sleep ! /(curthread->td_proc->p_flag & 0x4) == 0/ ! { ! self->ts = timestamp; ! self->m

Re: close() taking minutes (ZFS related)

It seems I have found the reason for the strange behaviour: it is dedup. The pool is configured to use dedup, because it carries all my jail OS installation, which are very similar. But dedup makes no sense on database filesets, and apparently it has very bad effects on real workload: it creates i

Re: Slow WAN traffic to FreeBSD hosts but not to Linux hosts---

> TL;DR: When working from home, I can max out my residential 200 Mbit > network connection when downloading from remote Linux hosts at but > only manage about 20% of my max residential connection speed when > downloading from remote FreeBSD I had a similar effect once, when downloading from my

Re: Kernel is using a lot of CPU

> 12.4 autoloaded acpi_wmi with dubious results: > > Autoloading module: acpi_wmi > acpi_wmi0: on acpi0 > acpi_wmi0: cannot find EC device > device_attach: acpi_wmi0 attach returned 6 > acpi_wmi0: on acpi0 > acpi_wmi0: cannot find EC device > device_attach: acpi_wmi0 attach returned 6 > > 12.2 di

13.2 BETA2: how do debug META_MODE?

Hi folks, on /some/ of my nodes, META_MODE seems not being honored anymore: I had to build them another time, and the lengthy lib/clang gets built all over again (tried two times). This is so since 13.2 (BETA2). It did work in 13.1 (RELENG), at least according to the timing from the logfiles.

Re: 13.2 BETA2: how do debug META_MODE?

On Mon, Feb 20, 2023 at 08:44:59PM -0800, Mark Millard wrote: ! Peter wrote on ! Date: Tue, 21 Feb 2023 03:45:12 UTC : ! ! > on /some/ of my nodes, META_MODE seems not being honored anymore: ! > I had to build them another time, and the lengthy lib/clang gets ! > built all over aga

eval: startmsg: not found

https://www.mail-archive.com/stable@freebsd.org/msg00974.html me too.

13.2-BETA2: xz: illegal instruction

# ./xz < /dev/zero > /dev/null Illegal instruction (core dumped) CPU: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz (3059.08-MHz K8-class CPU) Origin="GenuineIntel" Id=0x20655 Family=0x6 Model=0x25 Stepping=5 CPUTYPE?=westmere ... investigating...

Re: 13.2-BETA2: xz: illegal instruction

> # ./xz < /dev/zero > /dev/null > Illegal instruction (core dumped) > CPU: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz (3059.08-MHz K8-class > CPU) > Origin="GenuineIntel" Id=0x20655 Family=0x6 Model=0x25 Ste

Re: 13.2-BETA2: xz: illegal instruction

>> CPU: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz (3059.08-MHz K8-class >> CPU) >> Origin="GenuineIntel" Id=0x20655 Family=0x6 Model=0x25 Stepping=5 >>

Re: 13.2 BETA2: how do debug META_MODE?

On Tue, Feb 21, 2023 at 11:56:13AM -0800, Mark Millard wrote: ! On Feb 21, 2023, at 04:55, Peter wrote: ! ! > ! # cd /usr/src/ ! > ! # env WITH_META_MODE=yes make buildworld ! > ! # env WITH_META_MODE=yes make installworld ! > ! # env WITH_META_MODE=yes make buildworld (again #0)

[analysis] Re: 13.2 BETA2: how do debug META_MODE?

It appears as my issue goes away by itself at the fourth subsequent build. ># cd /usr/src/ ># env WITH_META_MODE=yes make buildworld ># env WITH_META_MODE=yes make installworld ># env WITH_META_MODE=yes make buildworld (again #0) >## no more rebuilds below? ># env WITH_META_MODE=yes make buildwo

Re: 13.2 BETA2: how do debug META_MODE?

On Tue, Feb 21, 2023 at 06:44:09PM -0800, Mark Millard wrote: ! On Feb 21, 2023, at 18:10, Peter wrote: ! ! > On Tue, Feb 21, 2023 at 11:56:13AM -0800, Mark Millard wrote: ! > ! On Feb 21, 2023, at 04:55, Peter wrote: ! > ! ! > ! > ! # cd /usr/src/ ! > ! > ! # env WI

Re: 13.2-BETA2: xz: illegal instruction

On Thu, Feb 23, 2023 at 02:22:01PM +, Jamie Landeg-Jones wrote: ! Peter wrote: ! ! > > # ./xz < /dev/zero > /dev/null ! > > Illegal instruction (core dumped) ! > ! > > CPU: Intel(R)

Re: 13.2-BETA2: xz: illegal instruction

On Thu, Feb 23, 2023 at 10:14:13PM +, Jamie Landeg-Jones wrote: ! Peter wrote: ! ! > -target-cpu westmere ! > ! > But when building with CPTYPE?=native, the code works! ! ! That's weird! Ah. Hm... ! I notice the only difference between those 2 is that the "native"

13.2-STABLE: vlc does not work (SEGV_MAPERR)

Problem: Some 1 or 2 minutes into the flight, vlc does continue to play A+V, but the GUI does not react and does not get refreshed anymore. At the same time, coredumps are generated (quite a lot of them). The coredumps don't say much: (lldb) thread info all thread #1: tid = 101730, 0x3eda3bff

Re: 13.2-STABLE: vlc does not work (SEGV_MAPERR)

On Tue, Mar 07, 2023 at 03:43:15PM -0500, Ed Maste wrote: ! On Mon, 6 Mar 2023 at 09:18, Peter wrote: ! > ! > Problem: ! > Some 1 or 2 minutes into the flight, vlc does continue to play A+V, ! > but the GUI does not react and does not get refreshed anymore. At ! > the same time

Re: 13.2-STABLE: vlc does not work (SEGV_MAPERR)

On Tue, Mar 07, 2023 at 07:03:01PM -0500, Ed Maste wrote: ! > I'm going to do the same now for java + node + libreoffice, and then ! > engage the allow_wx=0 again. ! ! Setting allow_wx=0 is likely to have significant fallout, so be ! prepared for that. Yepp, I got these: www/node16

ports-mgmt/portconfig surprize

Folks, somebody got the idea to replace the dialog4ports options configuring interface by something named 'ports-mgmt/portconfig'. (And they did not even find it worth mentioning this in the UPGRADING file.) Now this one looks terrible, the screen is garbled, and it is quite unintellegible whic

Re: ports-mgmt/portconfig surprize

On Fri, Jan 05, 2024 at 07:56:16AM -0800, Cy Schubert wrote: ! ! This should have been posted to freebsd-ports@. Next time use the correct ! ML. Hi, I was thinking -ports is for malfunctioning individual ports. Whereas the matter at hand is about general infrastructure (every server needs som

Re: ports-mgmt/portconfig surprize

On Sat, Jan 06, 2024 at 12:00:13AM +0100, Alfonso Sabato Siciliano wrote: ! Thank you for the report ! ! I am in a rural place far from my laptop. ! I'll investigate the problem on Monday. Hi, thank You very much for reporting back! Take Your time, relax, enjoy the country; this is not an issu

Re: 13-STABLE high idprio load gives poor responsiveness and excessive CPU time per task

On Thu, Feb 29, 2024 at 08:02:42AM -0800, Mark Millard wrote: ! Peter 'PMc' Much wrote on ! Date: Thu, 29 Feb 2024 13:40:05 UTC : ! ! > There is an updated patch in the PR 275594 (5 pieces), that works for ! > 13.3; I have it installed, and only with that I am able to build gcc12

Re: 13-STABLE high idprio load gives poor responsiveness and excessive CPU time per task

First off: the honorable Sir Edward, III. had the decency to have me ntified that they prefer to censor my messages (reasons were not given), I for my part consider it rather pointless to publicly ask questions, only to then inform those who bother to answer that one declines to receive their a

Re: Change to FreeBSD release scheduling etc.

Folks, there was recently a message from Colin Percival, concerning the release schedule. And now I see on the main webpage a new release 13.4 announced to appear soon, while the upgrade to 13.3 was only recently. I read statements concerning the rationale behind this. These statements circle a

Re: Change to FreeBSD release scheduling etc.

Folks, thank You all for the feedback. As it seems. I'm not the only one concerned. On Mon, Jul 15, 2024 at 11:58:16AM -0700, Colin Percival wrote: > While I see your point, we're hoping that having roughly 2x as many minor > releases will result in at least a 2x reduction in the number of surp

13.4 compiles firefox functionally different

Hi, after upgrading to 13.4-RC2-p1, I recompiled all ports. Today I found my firefox can no longer render a certain webpage; the output is garbled as if the CSS were missing/defective. Here is details and picture: https://forums.freebsd.org/threads/firefox-displays-unintellegible-garbage-only-on

Re: 13.4 compiles firefox functionally different

On Tue, Sep 17, 2024 at 08:35:59AM -0500, Dan Mack wrote: ! On Tue, 17 Sep 2024, Peter wrote: ! ! > Hi, ! > ! > after upgrading to 13.4-RC2-p1, I recompiled all ports. ! > ! > Today I found my firefox can no longer render a certain webpage; ! > the output is garbled as if th

Consistent panic with "zfs send --raw"

And --large-block as on option doesn't actually make sense with --raw because the send stream must match what's on local disk by definition). At this point, I'm not sure what the correct fix is. -- Peter Jeremy signature.asc Description: PGP signature

Re: Deprecating ISA sound cards

ple of systems with ISA mainboards that I'm happy to donate. -- Peter Jeremy signature.asc Description: PGP signature

Re: No DHCP server found (stable/12 & stable/13)

ied to hardware or implementation by > whatever company Marriott is using. > Maybe related - maybe ot. I am running a public and not encrypted WLAN "freifunk.net". An ancient linux router box will not automatically ask for a new lease. I have to reconnect manually. Slackware 15.0 will not connect at all. I remember Slackware 14.2 (6 years old) did connect I have no problem connecting to two "normal" encrypted WLAN routers and the router box does automatically renew its lease and get a new local ipaddress. I cannot test with FreeBSD because my WLAN adapter is not supported. My guess something in WLAN changed and not only FreeBSD sees this problem. Cheers Peter

ZFS does not activate a pool after upgrade 12-stable to 13-stable

carefully. Any ideas why this happens, how to fix this? Peter

Re: ZFS does not activate a pool after upgrade 12-stable to 13-stable - SOLVED

I did multiple systems and I probably forgot to do the etcupdate -B on this system. /etc/rc.d/zpool was missing and other scripts were not update. Thx a lot > On 20 Jun 2022, at 13:05, Tomoaki AOKI wrote: > > On Mon, 20 Jun 2022 12:39:53 +0200 > Peter Blok wrote: > >&

Re: Upgrade to 13, zfs issues

I have the same issue on a couple of servers. I haven’t found a way to correct this, but it wasn’t any problem upgrading and after the upgrade everything worked ok. Peter > On 3 Jul 2022, at 13:26, Éric Masson wrote: > > Hi, > > I'm planning to upgrade my kitchen

Re: Upgrade to 13, zfs issues

contains COMPAT_FREEBSD12. Best is to use GENERIC Peter > On 4 Jul 2022, at 13:15, Éric Masson wrote: > > Peter Blok writes: > > Hi Peter, > >> I have the same issue on a couple of servers. I haven’t found a way to >> correct this, but it wasn’t any problem upgr

Re: boot environment and /var/db/etcupdate ?

or versions, it probably does make sense to include /usr/local in the BE - but then you need to extricate all the application data that needs to not be rolled back. -- Peter Jeremy signature.asc Description: PGP signature

Re: close() taking minutes

On Fri, 20 Jan 2023 05:11:38 +0100 Peter wrote: > Does this look familiar with anybody? ("truss -dD ls -l something") > > 0.047760369 0.17548 > open("/etc/nsswitch.conf",O_RDONLY|O_CLOEXEC,0666) = 4 (0x4) > 0.047845099 0.11290 > fstat(4,{ mode=-r

Re: FreeBSD Errata Notice FreeBSD-EN-23:09.freebsd-update [REVISED]

Me too! My sshd_config is also customized and everytime there is a new patch I need to run freebsd-update manually and get rid of the attempt to trash the sshd config that could make my server unreachable over the network. Why does the freebsd-update need a vanilla sshd_config? Why not give a me

Re: FreeBSD Errata Notice FreeBSD-EN-23:09.freebsd-update [REVISED]

> 4 okt. 2023 kl. 11:05 skrev Ruben : > > Hi, > > On 10/4/23 09:31, Karl Levik wrote: >> Agreed, this is an annoyance. >> If /etc/sshd_config would read/include e.g. /etc/sshd_config.d/* then >> customisations could be put into those files instead and the problem would >> go away. > > Pendi

Re: Error building py-setuptools-scm in STABLE.10

I removed py39-setuptools_scm , did a pkg autoremove, followed by a fresh build of py-setuptools-scm and it completed ok > On 11 Mar 2024, at 07:30, Daniel Braniss wrote: > > same in stable 13.3 > >> On 9 Mar 2024, at 17:05, Filippo Moretti > > wrote: >> >> The f

Re: FreeBSD 14.1-BETA2 Now Available

In the release notes https://www.freebsd.org/releases/14.1R/relnotes/ , Section "Userland Configuration Changes” talks about periodic(8) and mentions rc.conf(5). Should it mention ”periodic.conf(5)” instead? /Peter

Re: APU1 bricked on stable/14 - solved

BIOS version v4.8.0.2 2032 MB DRAM SeaBIOS (version rel-1.11.0.5-0-gd34c797) (I admit that I haven't updated the firmware on it since I got it). Let me know if you want more information. -- Peter Jeremy signature.asc Description: PGP signature

Re: FreeBSD 13.2-RELEASE started failing to load i915kms.ko after upgrade from RC5

On 2023-04-09, Yoshihiro Ota wrote: > Hi, > > I've been following releng/13.2 since it was branched. > I use amd64 arch for this. > > I had built kernel modules during BETA/RC period. > The above i915kms had worked until RC5. > I had not built RC6 locally and picked up RELEASE on releng/13.2. [...

Re: Camcontrol question related to Seagate disks

On 2023-06-06, Karl Denninger wrote: > Certain "newer" Seagate drives have an EPC profile that doesn't interact > as expected with the camcontrol "standard" way to tell spinning disks to > go into an idle state. > > Specifically those that support this: > https://www.seagate.com/files/docs/pdf/

Re: EARLY_AP_STARTUP now (effectively) mandatory?

On 2023-08-07, Garrett Wollman wrote: > This option was apparently added in 2016 by jhb@, and in his > PHabricator description, he wrote: > > As a transition aid, the new behavior is moved under a new > kernel option (EARLY_AP_STARTUP). This will allow the option > to be turned

Re: Interesting (Open)ZFS issue

On 2023-08-13, Garrett Wollman wrote: > This seems to me like a bug: `zpool scrub` correctly identified the > damaged parts of the disk, so ZFS knows that those regions of the pool > are bad in some way -- they should cause an error rather than a panic! Yes, but it does. On seriousely inconsiste

Re: vfs.zfs.compressed_arc_enabled=0 is INCOMPATIBLE with L2ARC at least in FreeBSD 13 (Was: Crash on adding L2ARC to raidz1 pool)

On 2024-01-13, Alexander Burke wrote: > Hello, > > It looks like the issue is fixed in OpenZFS 2.2 (and thus in FreeBSD > 14-RELEASE): > > https://github.com/openzfs/zfs/issues/15764#issuecomment-1890491789 > > Cheers, > Alex > > > Jan 13, 2024 12:26:50 Le

Re: git log - how to find out latest stable/14 breakage

On 2024-01-20, Harry Schmalzbauer wrote: > How can you all manage your daily jobs with git?!?!  For me as a daily jobs? Hm, maybe that's the mistake. This is FreeBSD, this ought to be fun! (I don't have a job, I don't get a job, I'm just normal unemployed trash :/ ). But to answer your question

Re: gpart device permissions security hole (/dev/geom.ctl)

On 2024-02-24, Miroslav Lachman <000.f...@quip.cz> wrote: > On 24/02/2024 21:00, Vincent Stemen wrote: >> On Sat, Feb 24, 2024 at 04:40:00PM +0100, Miroslav Lachman wrote: >>> I agree with this security problem. Just a small note - there are >>> backups of partitions (/var/backups/gpart.*) created

Re: 13-STABLE high idprio load gives poor responsiveness and excessive CPU time per task

On 2024-02-27, Edward Sanford Sutton, III wrote: >More recently looked and see top showing threads+system processes > shows I have one core getting 100% cpu for kernel{arc_prune} which has > 21.2 hours over a 2 hour 23 minute uptime. Ack. > I started looking to see if > https://www.freebs