[Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU

2024-01-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Zhenlei Huang changed: What|Removed |Added CC||z...@freebsd.org --- Comment #3 fr

Re: route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64

2024-01-09 Thread void
On Mon, Jan 08, 2024 at 01:07:30PM -0800, Enji Cooper wrote: Was the kernel/utility built with IPv6? If not, that’s a general bug which should be filed (which can be easily checked/avoided using the FEATURES(9) subsystem)… Cheers! -Enji world/kernel was built with WITHOUT_INET6= in /etc/src

Re: noatime on ufs2

2024-01-09 Thread void
On Mon, Jan 08, 2024 at 12:41:02PM -0800, Xin LI wrote: On Sun, Jan 7, 2024 at 5:27 AM void wrote: Hi, Does /var/mail still need atime? I've installed a ufs2-based -current main-n267425-aa1223ac3afc on rpi4/8BG which installs into one / . If it's mounted with noatime, will it have consequenc

Re: noatime on ufs2

2024-01-09 Thread void
On Tue, Jan 09, 2024 at 09:47:59AM +0100, Olivier Certner wrote:i So, to me, at this point, it still sounds more than a gimmick than something really useful. If someone has a precise use case for it and motivation, than of course please go ahead. The only use-cases I [1] can think of are eit

Re: noatime on ufs2

2024-01-09 Thread robert
On Tue, Jan 9, 2024, at 05:13, void wrote: > On Tue, Jan 09, 2024 at 09:47:59AM +0100, Olivier Certner wrote:i > >> So, to me, at this point, it still sounds more than a gimmick >> than something really useful. If someone has a precise use case >> for it and motivation, than of course please go

Re: noatime on ufs2

2024-01-09 Thread robert
On Tue, Jan 9, 2024, at 04:47, void wrote: > On Mon, Jan 08, 2024 at 12:41:02PM -0800, Xin LI wrote: >>On Sun, Jan 7, 2024 at 5:27 AM void wrote: >> >>> Hi, >>> >>> Does /var/mail still need atime? >>> >>> I've installed a ufs2-based -current main-n267425-aa1223ac3afc on >>> rpi4/8BG which install

Re: route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64

2024-01-09 Thread void
On Tue, Jan 09, 2024 at 10:24:53AM +, void wrote: On Mon, Jan 08, 2024 at 01:07:30PM -0800, Enji Cooper wrote: Was the kernel/utility built with IPv6? If not, that’s a general bug which should be filed (which can be easily checked/avoided using the FEATURES(9) subsystem)… Cheers! -Enji

Re: route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64

2024-01-09 Thread void
On Tue, Jan 09, 2024 at 12:24:40PM +, void wrote: On Tue, Jan 09, 2024 at 10:24:53AM +, void wrote: On Mon, Jan 08, 2024 at 01:07:30PM -0800, Enji Cooper wrote: Was the kernel/utility built with IPv6? If not, that’s a general bug which should be filed (which can be easily checked/avoi

Re: noatime on ufs2

2024-01-09 Thread Xin LI
On Tue, Jan 9, 2024 at 2:47 AM void wrote: > I was concerned that email might not work right without atime. > So far, it seems to be working OK. > Depending on how you define "correct". Deliveries won't be affected by atime setting in any way; telling if you have new mail _may_ be affected, but

kernel: fatal trap 12 on CURRENT, when using WireGuard

2024-01-09 Thread Rainer Hurling
I tried to update my 15.0-CURRENT box from n267335-499e84e16f56 to a very recent commit. The build and install went fine. After booting with new base, I got a page fault with the following error: Kernel page fault with the following non-sleepable locks held: shared rm netlink lock (netlink loc

Re: kernel: fatal trap 12 on CURRENT, when using WireGuard

2024-01-09 Thread Gleb Smirnoff
Rainer, On Tue, Jan 09, 2024 at 09:23:54PM +0100, Rainer Hurling wrote: R> I tried to update my 15.0-CURRENT box from n267335-499e84e16f56 to a very R> recent commit. The build and install went fine. After booting with new R> base, I got a page fault with the following error: Sorry for that, my

Re: noatime on ufs2

2024-01-09 Thread Warner Losh
On Tue, Jan 9, 2024, 11:11 AM Steffen Nurpmeso wrote: > rob...@rrbrussell.com wrote in > <5f370bce-bcdb-47ea-aaa7-551ee092a...@app.fastmail.com>: > |On Tue, Jan 9, 2024, at 05:13, void wrote: > |> On Tue, Jan 09, 2024 at 09:47:59AM +0100, Olivier Certner wrote:i > |>> So, to me, at this point

Re: e179d973 insta-panics in nl_send_one()

2024-01-09 Thread Gleb Smirnoff
On Mon, Jan 08, 2024 at 10:40:52AM +0100, Jakob Alvermark wrote: J> > > --- trap 0xc, rip = 0x...f80d97b78, rsp = 0x... J> > > nl_send_one() at nl_send_one+0x18/frame 0xf J> > > nl_send_group() at nl_send_group+0x1bc/frame 0xf... J> > > _nlmsg_flush() at _nlmsg_flush+0x37/frame 0xf... J

Re: kernel: fatal trap 12 on CURRENT, when using WireGuard

2024-01-09 Thread Rainer Hurling
Am 09.01.24 um 21:40 schrieb Gleb Smirnoff: Rainer, On Tue, Jan 09, 2024 at 09:23:54PM +0100, Rainer Hurling wrote: R> I tried to update my 15.0-CURRENT box from n267335-499e84e16f56 to a very R> recent commit. The build and install went fine. After booting with new R> base, I got a page faul