Radius challenges in FreeBSD 14.0 Re: FreeBSD 14.0-RC4 Now Available
On Mon, Nov 06, 2023 at 08:43:05AM +0100, Baptiste Daroussin wrote: > On Sun, Nov 05, 2023 at 12:11:06PM -0700, The Doctor wrote: > > On Sun, Nov 05, 2023 at 10:32:44AM -0700, The Doctor wrote: > > > On Fri, Nov 03, 2023 at 11:42:32PM +, Glen Barber wrote: > > > > The fourth RC build of the 14.0-RELEASE release cycle is now available. > > > > > > > > Installation images are available for: > > > > > > > > o 14.0-RC4 amd64 GENERIC > > > > > > > > > > > > > > I am having a problem witb Freeradius and GNU radius. > > > > > > Anyone else? > > > > > > > > > > I found the problem. Replace /usr/lib/libncursesw.so as a symbolic > > link to /lib/libncursesw.so.9 > > can you provide more inputs here, please where do you get your freeradious or > gnu radius implementation from, what is failing an so on? > > Best regards, > Bapt freeradius looks like a TLS issue with openssl 3 . gnu Radius was biuld by me and not a port. Trying to recode is a challenge. What is happening is that the so file is not being recognised so I have to symlink in order to get GNU radius 1.6.X to work . It will work with /lib/libncursesw.so.9 if the so file is found in /usr/lib . -- Member - Liberal International This is doc...@nk.ca Ici doc...@nk.ca Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen Suffering will continue until we stop believing lies. -unknown Beware https://mindspring.com
Re: FreeBSD 14.0-RC4 Now Available
On Sun, Nov 05, 2023 at 12:11:06PM -0700, The Doctor wrote: > On Sun, Nov 05, 2023 at 10:32:44AM -0700, The Doctor wrote: > > On Fri, Nov 03, 2023 at 11:42:32PM +, Glen Barber wrote: > > > The fourth RC build of the 14.0-RELEASE release cycle is now available. > > > > > > Installation images are available for: > > > > > > o 14.0-RC4 amd64 GENERIC > > > o 14.0-RC4 i386 GENERIC > > > o 14.0-RC4 powerpc GENERIC > > > o 14.0-RC4 powerpc64 GENERIC64 > > > o 14.0-RC4 powerpc64le GENERIC64LE > > > o 14.0-RC4 powerpcspe MPC85XXSPE > > > o 14.0-RC4 armv7 GENERICSD > > > o 14.0-RC4 aarch64 GENERIC > > > o 14.0-RC4 aarch64 RPI > > > o 14.0-RC4 aarch64 PINE64 > > > o 14.0-RC4 aarch64 PINE64-LTS > > > o 14.0-RC4 aarch64 PINEBOOK > > > o 14.0-RC4 aarch64 ROCK64 > > > o 14.0-RC4 aarch64 ROCKPRO64 > > > o 14.0-RC4 riscv64 GENERIC > > > o 14.0-RC4 riscv64 GENERICSD > > > > > > Note regarding arm SD card images: For convenience for those without > > > console access to the system, a freebsd user with a password of > > > freebsd is available by default for ssh(1) access. Additionally, > > > the root user password is set to root. It is strongly recommended > > > to change the password for both users after gaining access to the > > > system. > > > > > > Installer images and memory stick images are available here: > > > > > > https://download.freebsd.org/releases/ISO-IMAGES/14.0/ > > > > > > The image checksums follow at the end of this e-mail. > > > > > > If you notice problems you can report them through the Bugzilla PR > > > system or on the -stable mailing list. > > > > > > If you would like to use Git to do a source based update of an existing > > > system, use the "releng/14.0" branch. > > > > > > A summary of changes since 14.0-RC3 includes: > > > > > > o ISA and GIANT-locked driver removal has been delayed to FreeBSD 15, > > > and system messages have been updated to reflect such. > > > > > > o An update to OpenZFS correcting block cloning between encrypted and > > > unencrypted datasets has been included. > > > > > > o A fix for Hyper-V emulation within QEMU resulting in system crashes > > > has been addressed. > > > > > > A list of changes since 13.2-RELEASE is available in the releng/14.0 > > > release notes: > > > > > > https://www.freebsd.org/releases/14.0R/relnotes/ > > > > > > Please note, the release notes page is not yet complete, and will be > > > updated on an ongoing basis as the 14.0-RELEASE cycle progresses. > > > > > > === Virtual Machine Disk Images === > > > > > > VM disk images are available for the amd64, i386, and aarch64 > > > architectures. Disk images may be downloaded from the following URL > > > (or any of the FreeBSD download mirrors): > > > > > > https://download.freebsd.org/releases/VM-IMAGES/14.0-RC4/ > > > > > > BASIC-CI images can be found at: > > > > > > https://download.freebsd.org/releases/CI-IMAGES/14.0-RC4/ > > > > > > The partition layout is: > > > > > > ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) > > > ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) > > > ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) > > > > > > The disk images are available in QCOW2, VHD, VMDK, and raw disk image > > > formats. The image download size is approximately 135 MB and 165 MB > > > respectively (amd64/i386), decompressing to a 21 GB sparse image. > > > > > > Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI > > > loader file is needed for qemu-system-aarch64 to be able to boot the > > > virtual machine images. See this page for more information: > > > > > > https://wiki.freebsd.org/arm64/QEMU > > > > > > To boot the VM image, run: > > > > > > % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ > > > -bios QEMU_EFI.fd -serial telnet::,server -nographic \ > > > -drive if=none,file=VMDISK,id=hd0 \ > > > -device virtio-blk-device,drive=hd0 \ > > > -device virtio-net-device,netdev=net0 \ > > > -netdev user,id=net0 > > > > > > Be sure to replace "VMDISK" with the path to the virtual machine image. > > > > > > === Amazon EC2 AMI Images === > > > > > > FreeBSD/amd64 EC2 AMI IDs can be retrieved from the Systems Manager > > > Parameter Store in each region using the keys: > > > > > > /aws/service/freebsd/amd64/base/ufs/14.0/RC4 > > > /aws/service/freebsd/amd64/base/zfs/14.0/RC4 > > > /aws/service/freebsd/amd64/cloud-init/ufs/14.0/RC4 > > > /aws/service/freebsd/amd64/cloud-init/zfs/14.0/RC4 > > > > > > FreeBSD/aarch64 EC2 AMI IDs can be retrieved from the Systems Manager > > > Parameter Store in each region using the keys: > > > > > > /aws/service/freebsd/aarch64/base/ufs/14.0/RC4 > > > /aws/service/freebsd/aarch64/base/zfs/14.0/RC4 > > > /aws/service/freebsd/aarch64/cloud-init/ufs/14.0/RC4 > > > /aws/service/freebsd/aarch64/cloud-init/zfs/14.0/RC4 > > > > > > === Vagrant Images === > > > > > > FreeBSD/amd64 images are available
Re: FreeBSD 14.0-RC4 Now Available
On Sun, Nov 05, 2023 at 10:32:44AM -0700, The Doctor wrote: > On Fri, Nov 03, 2023 at 11:42:32PM +, Glen Barber wrote: > > The fourth RC build of the 14.0-RELEASE release cycle is now available. > > > > Installation images are available for: > > > > o 14.0-RC4 amd64 GENERIC > > o 14.0-RC4 i386 GENERIC > > o 14.0-RC4 powerpc GENERIC > > o 14.0-RC4 powerpc64 GENERIC64 > > o 14.0-RC4 powerpc64le GENERIC64LE > > o 14.0-RC4 powerpcspe MPC85XXSPE > > o 14.0-RC4 armv7 GENERICSD > > o 14.0-RC4 aarch64 GENERIC > > o 14.0-RC4 aarch64 RPI > > o 14.0-RC4 aarch64 PINE64 > > o 14.0-RC4 aarch64 PINE64-LTS > > o 14.0-RC4 aarch64 PINEBOOK > > o 14.0-RC4 aarch64 ROCK64 > > o 14.0-RC4 aarch64 ROCKPRO64 > > o 14.0-RC4 riscv64 GENERIC > > o 14.0-RC4 riscv64 GENERICSD > > > > Note regarding arm SD card images: For convenience for those without > > console access to the system, a freebsd user with a password of > > freebsd is available by default for ssh(1) access. Additionally, > > the root user password is set to root. It is strongly recommended > > to change the password for both users after gaining access to the > > system. > > > > Installer images and memory stick images are available here: > > > > https://download.freebsd.org/releases/ISO-IMAGES/14.0/ > > > > The image checksums follow at the end of this e-mail. > > > > If you notice problems you can report them through the Bugzilla PR > > system or on the -stable mailing list. > > > > If you would like to use Git to do a source based update of an existing > > system, use the "releng/14.0" branch. > > > > A summary of changes since 14.0-RC3 includes: > > > > o ISA and GIANT-locked driver removal has been delayed to FreeBSD 15, > > and system messages have been updated to reflect such. > > > > o An update to OpenZFS correcting block cloning between encrypted and > > unencrypted datasets has been included. > > > > o A fix for Hyper-V emulation within QEMU resulting in system crashes > > has been addressed. > > > > A list of changes since 13.2-RELEASE is available in the releng/14.0 > > release notes: > > > > https://www.freebsd.org/releases/14.0R/relnotes/ > > > > Please note, the release notes page is not yet complete, and will be > > updated on an ongoing basis as the 14.0-RELEASE cycle progresses. > > > > === Virtual Machine Disk Images === > > > > VM disk images are available for the amd64, i386, and aarch64 > > architectures. Disk images may be downloaded from the following URL > > (or any of the FreeBSD download mirrors): > > > > https://download.freebsd.org/releases/VM-IMAGES/14.0-RC4/ > > > > BASIC-CI images can be found at: > > > > https://download.freebsd.org/releases/CI-IMAGES/14.0-RC4/ > > > > The partition layout is: > > > > ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) > > ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) > > ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) > > > > The disk images are available in QCOW2, VHD, VMDK, and raw disk image > > formats. The image download size is approximately 135 MB and 165 MB > > respectively (amd64/i386), decompressing to a 21 GB sparse image. > > > > Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI > > loader file is needed for qemu-system-aarch64 to be able to boot the > > virtual machine images. See this page for more information: > > > > https://wiki.freebsd.org/arm64/QEMU > > > > To boot the VM image, run: > > > > % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ > > -bios QEMU_EFI.fd -serial telnet::,server -nographic \ > > -drive if=none,file=VMDISK,id=hd0 \ > > -device virtio-blk-device,drive=hd0 \ > > -device virtio-net-device,netdev=net0 \ > > -netdev user,id=net0 > > > > Be sure to replace "VMDISK" with the path to the virtual machine image. > > > > === Amazon EC2 AMI Images === > > > > FreeBSD/amd64 EC2 AMI IDs can be retrieved from the Systems Manager > > Parameter Store in each region using the keys: > > > > /aws/service/freebsd/amd64/base/ufs/14.0/RC4 > > /aws/service/freebsd/amd64/base/zfs/14.0/RC4 > > /aws/service/freebsd/amd64/cloud-init/ufs/14.0/RC4 > > /aws/service/freebsd/amd64/cloud-init/zfs/14.0/RC4 > > > > FreeBSD/aarch64 EC2 AMI IDs can be retrieved from the Systems Manager > > Parameter Store in each region using the keys: > > > > /aws/service/freebsd/aarch64/base/ufs/14.0/RC4 > > /aws/service/freebsd/aarch64/base/zfs/14.0/RC4 > > /aws/service/freebsd/aarch64/cloud-init/ufs/14.0/RC4 > > /aws/service/freebsd/aarch64/cloud-init/zfs/14.0/RC4 > > > > === Vagrant Images === > > > > FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can > > be installed by running: > > > > % vagrant init freebsd/FreeBSD-14.0-RC4 > > % vagrant up > > > > === Upgrading === > > > > The freebsd-update(8) utility supports binary upgrades of amd64, i386, > > and aarch64 systems
Kernel with INVARIANTS panicing if drm is loaded
I am observing kernel panic when entering multiuser mode after sucessful
system boot. It happens when I load CURRENT kernel with INVARIANTS and drm
module loaded ( drm-515-kmod-5.15.118_1 in particular ) . drm module and kenel
are in sync
FreeBSD moonset.home 15.0-CURRENT FreeBSD 15.0-CURRENT #3 main-n266267-
e116e040f309: Sun Nov 5 10:00:51 EET 2023 r...@moonset.home:/usr/obj/usr/
src/amd64.amd64/sys/moonset amd64
panic: sleepq_add: td 0xf8000203c000 to sleep on wchan 0xf800021d8648
with sleeping prohibited
...
Reading symbols from /boot/kernel/kernel...
Reading symbols from /usr/lib/debug//boot/kernel/kernel.debug...
Unread portion of the kernel message buffer:
panic: malloc(M_WAITOK) with sleeping prohibited
cpuid = 0
time = 1699171621
.
__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
57 __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct
pcpu,
(kgdb) #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
#1 doadump (textdump=)
at /usr/src/sys/kern/kern_shutdown.c:405
#2 0x81e2ec53 in vt_kms_postswitch () from /boot/modules/drm.ko
#3 0x8043ad6e in vt_window_switch (vw=0xf800021d8640)
at /usr/src/sys/dev/vt/vt_core.c:595
#4 0x804ec583 in kern_reboot (howto=4)
at /usr/src/sys/kern/kern_shutdown.c:501
#5 0x804eccfa in vpanic (
fmt=0x808263fb "malloc(M_WAITOK) with sleeping prohibited",
ap=ap@entry=0xfe00ce259850) at /usr/src/sys/kern/kern_shutdown.c:970
#6 0x804ecb03 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:894
#7 0x804c8a04 in malloc_dbg (vap=,
sizep=, mtp=, flags=)
at /usr/src/sys/kern/kern_malloc.c:540
#8 0x804c885c in malloc (size=,
mtp=0x81e931c0 , flags=)
at /usr/src/sys/kern/kern_malloc.c:641
#9 0x81c5a750 in intel_atomic_state_alloc ()
from /boot/modules/i915kms.ko
#10 0x81dfe404 in drm_client_modeset_commit_atomic ()
from /boot/modules/drm.ko
#11 0x81dfe614 in drm_client_modeset_commit_locked ()
from /boot/modules/drm.ko
#12 0x81dfe7a1 in drm_client_modeset_commit ()
from /boot/modules/drm.ko
#13 0x81e41ab3 in drm_fb_helper_restore_fbdev_mode_unlocked ()
from /boot/modules/drm.ko
#14 0x81e2ed91 in vt_kms_postswitch () from /boot/modules/drm.ko
#15 0x8043ac31 in vt_window_switch (vw=0xf80001d3a600,
vw@entry=0x80a47178 )
at /usr/src/sys/dev/vt/vt_core.c:612
#16 0x8043be0f in vtterm_cngrab (tm=,
tm@entry=)
at /usr/src/sys/dev/vt/vt_core.c:1863
#17 0x804893f6 in cngrab () at /usr/src/sys/kern/kern_cons.c:385
#18 0x804ecc79 in vpanic (
fmt=0x808799a9 "%s: td %p to sleep on wchan %p with sleeping
prohibited", ap=ap@entry=0xfe00ce259c20)
at /usr/src/sys/kern/kern_shutdown.c:942
#19 0x804ecb03 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:894
#20 0x805465b3 in sleepq_add (wchan=wchan@entry=0xf800021d8648,
lock=lock@entry=0xf80001823340,
wmesg=wmesg@entry=0x808b194e "tq_drain", flags=0,
flags@entry=, queue=queue@entry=0)
at /usr/src/sys/kern/subr_sleepqueue.c:326
#21 0x804f8efe in _sleep (ident=ident@entry=0xf800021d8648,
lock=lock@entry=0xf80001823340, priority=priority@entry=0,
wmesg=0x808b194e "tq_drain", sbt=sbt@entry=0, pr=pr@entry=0,
flags=256) at /usr/src/sys/kern/kern_synch.c:207
#22 0x8054cffb in TQ_SLEEP (tq=0xf80001823300,
p=0xf800021d8648, wm=)
at /usr/src/sys/kern/subr_taskqueue.c:124
#23 taskqueue_drain (queue=0xf80001823300, task=0xf800021d8648)
at /usr/src/sys/kern/subr_taskqueue.c:614
#24 0x81e2ed35 in vt_kms_postswitch () from /boot/modules/drm.ko
#25 0x8043ac31 in vt_window_switch (vw=0xf800021d8648,
vw@entry=0xf800038fb180) at /usr/src/sys/dev/vt/vt_core.c:612
#26 0x8043b3b2 in vt_late_window_switch (vw=0xf800038fb180)
at /usr/src/sys/dev/vt/vt_core.c:468
#27 vt_proc_window_switch (vw=0xf800038fb180)
at /usr/src/sys/dev/vt/vt_core.c:553
#28 0x8043e318 in vt_processkey (
kbd=0x80cef898 , vd=0x80a472c8 ,
c=) at /usr/src/sys/dev/vt/vt_core.c:903
#29 vt_kbdevent (kbd=0x80cef898 , event=,
arg=0x80a472c8 ) at /usr/src/sys/dev/vt/vt_core.c:1018
#30 0x8078ffcf in atkbd_intr (kbd=0x80cef898 ,
arg=) at /usr/src/sys/dev/atkbdc/atkbd.c:565
#31 0x804b1376 in intr_event_execute_handlers (ie=0xf800010ece00,
p=) at /usr/src/sys/kern/kern_intr.c:1205
#32 ithread_execute_handlers (ie=0xf800010ece00, p=)
at /usr/src/sys/kern/kern_intr.c:1218
#33 ithread_loop (arg=arg@entry=0xf80001c5aea0)
at /usr/src/sys/kern/kern_intr.c:1306
#34 0x804adae2 in fork_exit (
callout=0x804b1120 , arg=0xf80001c5aea0,
frame=0xfe00ce259f40) at
Re: FreeBSD 14.0-RC4 Now Available
On Fri, Nov 03, 2023 at 11:42:32PM +, Glen Barber wrote: > The fourth RC build of the 14.0-RELEASE release cycle is now available. > > Installation images are available for: > > o 14.0-RC4 amd64 GENERIC > o 14.0-RC4 i386 GENERIC > o 14.0-RC4 powerpc GENERIC > o 14.0-RC4 powerpc64 GENERIC64 > o 14.0-RC4 powerpc64le GENERIC64LE > o 14.0-RC4 powerpcspe MPC85XXSPE > o 14.0-RC4 armv7 GENERICSD > o 14.0-RC4 aarch64 GENERIC > o 14.0-RC4 aarch64 RPI > o 14.0-RC4 aarch64 PINE64 > o 14.0-RC4 aarch64 PINE64-LTS > o 14.0-RC4 aarch64 PINEBOOK > o 14.0-RC4 aarch64 ROCK64 > o 14.0-RC4 aarch64 ROCKPRO64 > o 14.0-RC4 riscv64 GENERIC > o 14.0-RC4 riscv64 GENERICSD > > Note regarding arm SD card images: For convenience for those without > console access to the system, a freebsd user with a password of > freebsd is available by default for ssh(1) access. Additionally, > the root user password is set to root. It is strongly recommended > to change the password for both users after gaining access to the > system. > > Installer images and memory stick images are available here: > > https://download.freebsd.org/releases/ISO-IMAGES/14.0/ > > The image checksums follow at the end of this e-mail. > > If you notice problems you can report them through the Bugzilla PR > system or on the -stable mailing list. > > If you would like to use Git to do a source based update of an existing > system, use the "releng/14.0" branch. > > A summary of changes since 14.0-RC3 includes: > > o ISA and GIANT-locked driver removal has been delayed to FreeBSD 15, > and system messages have been updated to reflect such. > > o An update to OpenZFS correcting block cloning between encrypted and > unencrypted datasets has been included. > > o A fix for Hyper-V emulation within QEMU resulting in system crashes > has been addressed. > > A list of changes since 13.2-RELEASE is available in the releng/14.0 > release notes: > > https://www.freebsd.org/releases/14.0R/relnotes/ > > Please note, the release notes page is not yet complete, and will be > updated on an ongoing basis as the 14.0-RELEASE cycle progresses. > > === Virtual Machine Disk Images === > > VM disk images are available for the amd64, i386, and aarch64 > architectures. Disk images may be downloaded from the following URL > (or any of the FreeBSD download mirrors): > > https://download.freebsd.org/releases/VM-IMAGES/14.0-RC4/ > > BASIC-CI images can be found at: > > https://download.freebsd.org/releases/CI-IMAGES/14.0-RC4/ > > The partition layout is: > > ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) > ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) > ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) > > The disk images are available in QCOW2, VHD, VMDK, and raw disk image > formats. The image download size is approximately 135 MB and 165 MB > respectively (amd64/i386), decompressing to a 21 GB sparse image. > > Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI > loader file is needed for qemu-system-aarch64 to be able to boot the > virtual machine images. See this page for more information: > > https://wiki.freebsd.org/arm64/QEMU > > To boot the VM image, run: > > % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ > -bios QEMU_EFI.fd -serial telnet::,server -nographic \ > -drive if=none,file=VMDISK,id=hd0 \ > -device virtio-blk-device,drive=hd0 \ > -device virtio-net-device,netdev=net0 \ > -netdev user,id=net0 > > Be sure to replace "VMDISK" with the path to the virtual machine image. > > === Amazon EC2 AMI Images === > > FreeBSD/amd64 EC2 AMI IDs can be retrieved from the Systems Manager > Parameter Store in each region using the keys: > > /aws/service/freebsd/amd64/base/ufs/14.0/RC4 > /aws/service/freebsd/amd64/base/zfs/14.0/RC4 > /aws/service/freebsd/amd64/cloud-init/ufs/14.0/RC4 > /aws/service/freebsd/amd64/cloud-init/zfs/14.0/RC4 > > FreeBSD/aarch64 EC2 AMI IDs can be retrieved from the Systems Manager > Parameter Store in each region using the keys: > > /aws/service/freebsd/aarch64/base/ufs/14.0/RC4 > /aws/service/freebsd/aarch64/base/zfs/14.0/RC4 > /aws/service/freebsd/aarch64/cloud-init/ufs/14.0/RC4 > /aws/service/freebsd/aarch64/cloud-init/zfs/14.0/RC4 > > === Vagrant Images === > > FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can > be installed by running: > > % vagrant init freebsd/FreeBSD-14.0-RC4 > % vagrant up > > === Upgrading === > > The freebsd-update(8) utility supports binary upgrades of amd64, i386, > and aarch64 systems running earlier FreeBSD releases. Systems running > earlier FreeBSD releases can upgrade as follows: > > # freebsd-update upgrade -r 14.0-RC4 > > During this process, freebsd-update(8) may ask the user to help by > merging some configuration files or by confirming that the automatically
