Pull up following revision(s) (requested by yamt in ticket #299):
sys/arch/x86/x86/identcpu_subr.c: revision 1.16
x86: use 0x40000010 cpuid leaf only on vmware and kvm
specifically, do not use it on nvmm.
these hypervisor cpuid leafs are basically hypervisor-specific.
(there was a proposal on commonizing these hypervisor leafs. [1]
but it doesn't seem agreed on.)
this cpuid leaf 0x40000010 was originally from vmware. although it
seems more common to use the GETHZ (45) hypercall instead these days.
kvm seems to implement it as well. (via qemu vmware-cpuid-freq)
i personally haven't tested this on either vmware or kvm.
for nvmm (netbsd), the leaf has been implemented in 2025. [2]
and then the lapic bit has been disabled in 2026. [3] that is,
[8 lines not shown]
Pull up the following, requested by kim in ticket #303:
external/bsd/tmux/dist/CHANGES up to 1.1.1.13
external/bsd/tmux/dist/configure up to 1.1.1.13
external/bsd/tmux/dist/configure.ac up to 1.1.1.13
external/bsd/tmux/dist/image.c up to 1.2
external/bsd/tmux/dist/screen.c up to 1.18
external/bsd/tmux/dist/tmux.h up to 1.25
external/bsd/tmux/usr.bin/tmux/Makefile up to 1.46
Import tmux 3.6b.
CHANGES FROM 3.6a TO 3.6b
* Remove images from the correct list when they are removed while in the
alternate screen (reported by xlabai at tencent dot com).
Pull up following revision(s) (requested by jnemeth in ticket #302):
usr.bin/calendar/calendars/calendar.christian: revision 1.16
usr.bin/calendar/calendars/calendar.holiday: revision 1.37
usr.bin/calendar/calendars/calendar.usholiday: revision 1.14
usr.bin/calendar/calendars/calendar.judaic: revision 1.14
Update calendar entries for items happening in the first half of
the year in the hopes that NetBSD 11.0 gets released around mid-year.
Pull up following revision(s) (requested by christos in ticket #301):
sys/nfs/nfsmount.h: revision 1.55
sbin/mount_nfs/mount_nfs.c: revision 1.77
sys/nfs/nfs_clntsubs.c: revision 1.8
sbin/mount_nfs/mount_nfs.8: revision 1.53
PR/59452: Marcin Gondek: Add a new mount flag "nowccmsg" to suppress printing
wcc-related messages. Apparently some synology server is causing them. This
just suppresses the messages, but does not change the behavior of the client.
Pull up following revision(s) (requested by ozaki-r in ticket #1269):
sys/net/if_llatbl.h: revision 1.20
sys/netinet/if_arp.c: revision 1.319
sys/net/nd.c: revision 1.10
tests/net/arp/t_arp.sh: revision 1.50
tests/net/arp/t_arp.sh: revision 1.51
sys/netinet6/nd6.c: revision 1.286
commit 27c3de6c8063a7850ef0efbea0d83f314e541ce8
Author: Ryota Ozaki <ozaki-r at iij.ad.jp>
Date: Thu Mar 12 12:42:03 2026 +0900
nd: reset ln_asked on state reset
Even if a userland program such as ping continuously sends packets
to a (temporarily) unreachable host, the ND resolver only sends
request packets up to nd_mmaxtries times. This change allows ND
request packets to continue being sent while the userland process
[21 lines not shown]
Pull up following revision(s) (requested by ozaki-r in ticket #300):
sys/net/if_llatbl.h: revision 1.20
sys/netinet/if_arp.c: revision 1.319
sys/net/nd.c: revision 1.10
tests/net/arp/t_arp.sh: revision 1.50
tests/net/arp/t_arp.sh: revision 1.51
sys/netinet6/nd6.c: revision 1.286
commit 27c3de6c8063a7850ef0efbea0d83f314e541ce8
Author: Ryota Ozaki <ozaki-r at iij.ad.jp>
Date: Thu Mar 12 12:42:03 2026 +0900
nd: reset ln_asked on state reset
Even if a userland program such as ping continuously sends packets
to a (temporarily) unreachable host, the ND resolver only sends
request packets up to nd_mmaxtries times. This change allows ND
request packets to continue being sent while the userland process
[21 lines not shown]
Pull up following revision(s) (requested by yamt in ticket #298):
sys/dev/nvmm/x86/nvmm_x86_svm.c: revision 1.95
sys/dev/nvmm/x86/nvmm_x86_vmx.c: revision 1.95
nvmm: remove cpuid leaf 0x40000010
* given the lapic bit disabled, (PR/59424) [1]
this leaf doesn't seem to have much benefit anymore.
as nvmm is used in other platforms, (dragonfly bsd)
it's better to avoid guest ABI changes without clear benefits.
* I couldn't find any documenation about what RBX=0 means.
(vmware or kvm)
we can revisit this when/if someone comes up with a better
implementation. (probably userland-assisted one)
discussed on source-changes-d. [2]
reviewed by Taylor R Campbell.
[2 lines not shown]
Pull up following revision(s) (requested by nia in ticket #296):
external/mit/xorg/lib/libepoxy/Makefile: revision 1.10
external/mit/xorg/lib/libepoxy/Makefile: revision 1.11
libepoxy: Make EGL libs depend on EGL support rather than GLAMOR.
Build tested on sparc64, which has EGL but no GLAMOR x server.
PR pkg/60295 x11/gtk3 does not build on NetBSD/macppc
libepoxy: Update the pkg-config file for new reality.
Pull up following revision(s) (requested by bouyer in ticket #295):
sys/external/bsd/ipf/netinet/ip_fil_netbsd.c: revision 1.40
Explicitely check a pointer against NULL before computing a member address,
to avoid undefined behavior. Avoids the same NULL pointer check being
"optimised" later, leading to NULL pointer dereference.
It is expected that -fno-delete-null-pointer-checks would avoid this but
it does not.
For details see
https://mail-index.netbsd.org/tech-toolchain/2026/05/23/msg004818.html
and PR toolchain/60289
Pull up following revision(s) (requested by kre in ticket #294):
bin/sh/trap.c: revision 1.60
bin/sh/trap.c: revision 1.61
bin/sh/trap.c: revision 1.62
bin/sh/jobs.h: revision 1.28
bin/sh/eval.h: revision 1.25
bin/sh/eval.c: revision 1.198
bin/sh/eval.c: revision 1.199
bin/sh/jobs.c: revision 1.126
bin/sh/trap.c: revision 1.59
PR bin/60275 discard less arriving signals
If the signal state is returned to the default state (SIG_DFL)
while sh has a pending signal for the process, that it is not
yet ready to process, then forget the pending signal, and instead
send it to ourself, so the kernel can take whatever is the default
action for that signal (if it is just ignored, then we just keep
[95 lines not shown]
genfs_do_io: fix a pagedaemon deadlock
this should fix the following panic i observed on my machine.
```
panic: out of memory before the pagedaemon thread exists
cpu0: Begin traceback...
vpanic() at netbsd:vpanic+0x189
panic() at netbsd:panic+0x3c
uvm_wait() at netbsd:uvm_wait+0xa5
uvm_km_kmem_alloc() at netbsd:uvm_km_kmem_alloc+0x21b
pool_page_alloc() at netbsd:pool_page_alloc+0x2c
pool_grow() at netbsd:pool_grow+0x367
pool_get() at netbsd:pool_get+0x9f
pool_cache_get_slow() at netbsd:pool_cache_get_slow+0x136
pool_cache_get_paddr() at netbsd:pool_cache_get_paddr+0x256
getiobuf() at netbsd:getiobuf+0x23
genfs_do_io() at netbsd:genfs_do_io+0xde
genfs_gop_write() at netbsd:genfs_gop_write+0x52
[5 lines not shown]
sw_reg_strategy: fix a pagedaemon deadlock
this should fix the following panic i observed on my machine.
```
panic: out of memory before the pagedaemon thread exists
cpu0: Begin traceback...
vpanic() at netbsd:vpanic+0x189
panic() at netbsd:panic+0x3c
uvm_wait() at netbsd:uvm_wait+0xa5
uvm_km_kmem_alloc() at netbsd:uvm_km_kmem_alloc+0x21b
pool_page_alloc() at netbsd:pool_page_alloc+0x2c
pool_grow() at netbsd:pool_grow+0x367
pool_get() at netbsd:pool_get+0x9f
pool_cache_get_slow() at netbsd:pool_cache_get_slow+0x136
pool_cache_get_paddr() at netbsd:pool_cache_get_paddr+0x256
getiobuf() at netbsd:getiobuf+0x23
swstrategy() at netbsd:swstrategy+0x25a
bdev_strategy() at netbsd:bdev_strategy+0x83
[6 lines not shown]
Add a driver for the NXP LM75A temperature sensor.
The chip is used in the Sun Ultra 45.
Note, that this is not the same as the TI LM75A temperature sensor (lmtemp).
