Re: The lib{c,sys} split in main: will man pages be updated for 15.0-RELEASE?

On Mar 21, 2025, at 17:43, Konstantin Belousov wrote: > On Fri, Mar 21, 2025 at 02:30:40PM -0700, Mark Millard wrote: >> Under: >> >> # uname -apKU >> FreeBSD 7950X3D-ZFS 15.0-CURRENT FreeBSD 15.0-CURRENT #4 >> main-n275926-a54a240c1b57-dirty: Thu Mar 13 00:44:25 PDT 2025 >> root@7950X3D-

Re: The lib{c,sys} split in main: will man pages be updated for 15.0-RELEASE?

On Fri, Mar 21, 2025 at 02:30:40PM -0700, Mark Millard wrote: > Under: > > # uname -apKU > FreeBSD 7950X3D-ZFS 15.0-CURRENT FreeBSD 15.0-CURRENT #4 > main-n275926-a54a240c1b57-dirty: Thu Mar 13 00:44:25 PDT 2025 > root@7950X3D-ZFS:/usr/obj/BUILDs/main-ZNV4-nodbg-clang/usr/main-src/amd64.amd

Re: Possible video driver issue after main-n275966-d2a55e6a9348 -> main-n275975-5963423232e8

On Fri, 21 Mar 2025, Gleb Smirnoff wrote: On Thu, Mar 20, 2025 at 07:52:19PM +, Bjoern A. Zeeb wrote: B> He's hitting a ... somewhere in i915kms.ko (here's the two instances I B> have): B> REDZONE: Buffer underflow detected. 16 bytes corrupted before 0xfe089bc65000 (262148 bytes allocat

Confused by boot_mute documentation, terminal systems, and goals

Folks, I am attempting to figure out what boot_mute wants me to do. I'm trying to make a "laptop guide" and I'm confused. I'm not a C programmer at this scale of sophistication so there's a decent chance I'm foolishly making an error, but current is not doing what I expect. - boot_mute doesn't

The lib{c,sys} split in main: will man pages be updated for 15.0-RELEASE?

Under: # uname -apKU FreeBSD 7950X3D-ZFS 15.0-CURRENT FreeBSD 15.0-CURRENT #4 main-n275926-a54a240c1b57-dirty: Thu Mar 13 00:44:25 PDT 2025 root@7950X3D-ZFS:/usr/obj/BUILDs/main-ZNV4-nodbg-clang/usr/main-src/amd64.amd64/sys/GENERIC-NODBG amd64 amd64 1500034 1500034 Looking, I see: # man

Re: Possible video driver issue after main-n275966-d2a55e6a9348 -> main-n275975-5963423232e8

On Fri, Mar 21, 2025 at 05:34:16AM -0400, Mark Johnston wrote: > ... > Can we not just add redzone padding to contigmalloc() allocations? > Compile-tested patch below: > > diff --git a/sys/kern/kern_malloc.c b/sys/kern/kern_malloc.c > index b1347b15e651..0b76e633b04a 100644 > --- a/sys/kern/kern_m

Re: Possible video driver issue after main-n275966-d2a55e6a9348 -> main-n275975-5963423232e8

On Fri, 21 Mar 2025, Mark Johnston wrote: On Fri, Mar 21, 2025 at 02:50:58AM -0700, Gleb Smirnoff wrote: On Fri, Mar 21, 2025 at 05:34:16AM -0400, Mark Johnston wrote: M> On Fri, Mar 21, 2025 at 01:56:01AM -0700, Gleb Smirnoff wrote: M> > On Thu, Mar 20, 2025 at 07:52:19PM +, Bjoern A. Zeeb

Re: Possible video driver issue after main-n275966-d2a55e6a9348 -> main-n275975-5963423232e8

On Fri, Mar 21, 2025 at 09:55:10AM -0400, Mark Johnston wrote: M> > I was about to suggest that, but was afraid it is too naive :) But M> > if that works, why not? We probably should document that for M> > contigmalloc() the redzone would provide protection of the virtual M> > space, but not the p

Re: Possible video driver issue after main-n275966-d2a55e6a9348 -> main-n275975-5963423232e8

On Fri, Mar 21, 2025 at 05:34:16AM -0400, Mark Johnston wrote: M> On Fri, Mar 21, 2025 at 01:56:01AM -0700, Gleb Smirnoff wrote: M> > On Thu, Mar 20, 2025 at 07:52:19PM +, Bjoern A. Zeeb wrote: M> > B> He's hitting a ... somewhere in i915kms.ko (here's the two instances I M> > B> have): M> > B>

Re: Possible video driver issue after main-n275966-d2a55e6a9348 -> main-n275975-5963423232e8

On Thu, Mar 20, 2025 at 07:52:19PM +, Bjoern A. Zeeb wrote: B> He's hitting a ... somewhere in i915kms.ko (here's the two instances I B> have): B> REDZONE: Buffer underflow detected. 16 bytes corrupted before 0xfe089bc65000 (262148 bytes allocated). B> REDZONE: Buffer underflow detected. 1