Firefox hangs on sleep
I noticed for the past week or so that firefox hangs on return from a sleep on my Thinkpad X1 Carbon version 4. This is true on both 7.3 and 7.4 stable. Other processes eg chrome, epiphany, don't. Not sure what additional info to provide. David J. Raymond david.raym...@nmt.edu http://kestrel.nmt.edu/~raymond
Lenovo Thinkpad T14 Gen3 very slow on MP kernel, faster on GENERIC
Hello, I'm experiencing big slowdowns on a LENOVO Thinkpad T14 Gen3 when using MP kernel (on 7.3 and 7.4) but strangely not on GENERIC. For example, starting LibreOffice on GENERIC takes 7 seconds but 35 seconds on MP kernel. It's even lagging when typing some text in an editor or a mail. Switching to GENERIC and all is working as expected... Thanks for your help ! Morgan This is my dmesg on both kernels: OpenBSD 7.4 (GENERIC) #1336: Tue Oct 10 08:52:22 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 34026549248 (32450MB) avail mem = 32975671296 (31448MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.4 @ 0x8f8a3000 (81 entries) bios0: vendor LENOVO version "N3MET16W (1.15 )" date 06/25/2023 bios0: LENOVO 21AHCTO1WW efi0 at bios0: UEFI 2.7 efi0: Lenovo rev 0x1150 acpi0 at bios0: ACPI 6.3 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT TPM2 HPET APIC MCFG ECDT SSDT SSDT SSDT SSDT SSDT SSDT LPIT WSMT SSDT DBGP DBG2 NHLT MSDM SSDT BATB DMAR SSDT SSDT SSDT BGRT PHAT UEFI FPDT acpi0: wakeup devices PEG0(S4) PEGP(S4) PEGP(S4) PEG2(S4) PEGP(S4) GLAN(S4) XHCI(S3) XDCI(S4) HDAS(S4) CNVW(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: 12th Gen Intel(R) Core(TM) i7-1260P, 2151.34 MHz, 06-9a-03, patch 042c cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE, SE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCI ,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,A M,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,C WB,PT,SHA,UMIP,PKU,WAITPKG,PKS,MD_CLEAR,IBT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DF ,MDS_NO,IF_PSCHANGE,TAA_NO,MISC_PKG_CT,ENERGY_FILT,DOITM,SBDR_SSDP_N,FBSDP_NO,PSDP_NO,RRSBA,OVERCLOC ,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 10-way L2 cache, 18MB 64b/line 12-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 38MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.0.1.0.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xc000, bus 0-255 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PC00) acpiprt1 at acpi0: bus 2 (PEG0) acpiprt2 at acpi0: bus -1 (PEG2) acpiprt3 at acpi0: bus -1 (RP01) acpiprt4 at acpi0: bus -1 (RP02) acpiprt5 at acpi0: bus -1 (RP03) acpiprt6 at acpi0: bus -1 (RP04) acpiprt7 at acpi0: bus -1 (RP05) acpiprt8 at acpi0: bus -1 (RP06) acpiprt9 at acpi0: bus -1 (RP07) acpiprt10 at acpi0: bus -1 (RP08) acpiprt11 at acpi0: bus -1 (RP09) acpiprt12 at acpi0: bus -1 (RP10) acpiprt13 at acpi0: bus -1 (RP11) acpiprt14 at acpi0: bus -1 (RP12) acpiprt15 at acpi0: bus -1 (RP13) acpiprt16 at acpi0: bus -1 (RP14) acpiprt17 at acpi0: bus -1 (RP15) acpiprt18 at acpi0: bus -1 (RP16) acpiprt19 at acpi0: bus -1 (RP17) acpiprt20 at acpi0: bus -1 (RP18) acpiprt21 at acpi0: bus -1 (RP19) acpiprt22 at acpi0: bus -1 (RP20) acpiprt23 at acpi0: bus -1 (RP21) acpiprt24 at acpi0: bus -1 (RP22) acpiprt25 at acpi0: bus -1 (RP23) acpiprt26 at acpi0: bus -1 (RP24) acpiprt27 at acpi0: bus -1 (RP25) acpiprt28 at acpi0: bus -1 (RP26) acpiprt29 at acpi0: bus -1 (RP27) acpiprt30 at acpi0: bus -1 (RP28) acpiprt31 at acpi0: bus 32 (TRP0) acpiprt32 at acpi0: bus 80 (TRP2) acpipci0 at acpi0 PC00: 0x 0x0011 0x0001 acpithinkpad0 at acpi0: version 2.0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "5B10W51867" serial 18480 type LiP oem "Sunwoda" "LEN0111" at acpi0 not configured "LEN0100" at acpi0 not configured "INTC1046" at acpi0 not configured "INTC1046" at acpi0 not configured "INTC1046" at acpi0 not configured "INTC1046" at acpi0 not configured "LEN0130" at acpi0 not configured "ELAN0676" at acpi0 not configured "ACPI000E" at acpi0 not configured pchgpio0 at acpi0 GPI0 addr 0xfd6e/0x1 0xfd6d/0x1 0xfd6a/0x1 0xfd69/0x1 irq 14, 360 pins acpibtn0 at acpi0: SLPB(wakeup) acpicpu0 at acpi0: C3(200@1048 mwait.1@0x60), C2(350@127 mwait.1@0x21)
mail.openbsd.org behaviour
Hi misc, Recently am receiving this lines from mail.openbsd.org: 2023-10-16 16:34:06 no MAIL in SMTP connection from (mail.openbsd.org) [199.185.178.25] D=11s X=TLS1.3:TLS_AES_256_GCM_SHA384:256 CV=no C=EHLO,STARTTLS,EHLO,QUIT Is that normal? Any misconfiguration from my side? Regards, Fabio
SSL issues after upgrading from 7.3 to 7.4
Hi. First of all, thank you very much for all your great efforts on 7.4! I upgraded my VPS from 7.3 to 7.4, and It's weird that, after upgrade, Qualys SSL Labs test for HTTPS/SSL websites gives: "HTTP request to this server failed, see below for details." However, my website works fine with browsers, and my nginx configuration has nothing weird at all, checked with "nginx -t", I had no such message as I checked just before I upgraded. And also, one more tool; immuniweb.com/ssl/ reports: "SERVER DOES NOT SUPPORT OCSP STAPLING" after the upgrade. However, again, OCSP stapling is implemented correctly in my nginx.conf file, working since a year. And just before upgrade, I had no such messages from none of those SSL checkers. and I haven't changed anything at all regarding my nginx configuration. My VPS is rented from Hetzner, and I had created a snapshot of it just before the upgrade process. So, now one-click revert to older snapshot, back to OpenBSD 7.3, both tests' reports are fine now. No more "HTTP request to this server failed" from Qualys SSL Labs, and no more "SERVER DOES NOT SUPPORT OCSP STAPLING" from Immuniweb SSL test. Obviously, something is not good with 7.4? My SSL certificates are from Let's Encrypt, and I have "ssl_protocols TLSv1.3 TLSv1.2;" in my nginx.conf, if that would help? Best Wishes&Regards, Mark.
Re: [EXTERNAL] Re: l2vpn pseudowire and bridge type interface
As noted by another this really is a misc@ list question. Take a look at https://www.openbsd.org/mail.html and you will see the following. misc@openbsd.org (Archive) User questions and answers, general questions. This is the most active list. Please read the FAQ and the installation documents, and see how to report a problem before posting. t...@openbsd.org (Archive) Discussion of technical topics for OpenBSD developers and advanced users. This is not a "tech support" forum — do not use it as such. OpenBSD developers will often make patches to implement new features and other important changes available for public testing through this list. -Original Message- From: owner-t...@openbsd.org On Behalf Of Wouter Prins Sent: Sunday, October 15, 2023 2:00 AM To: David Gwynne Cc: Claudio Jeker ; t...@openbsd.org Subject: [EXTERNAL] Re: l2vpn pseudowire and bridge type interface [You don't often get email from w...@null0.nl. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] Thanks for the replies! On Sun, Oct 15, 2023 at 9:26 AM David Gwynne wrote: > > > > > On 14 Oct 2023, at 23:18, Claudio Jeker wrote: > > > > On Sat, Oct 14, 2023 at 11:07:11AM +0200, Wouter Prins wrote: > >> hello list, > >> > >> Was wondering if the veb interface is supported as a bridge for > >> pseudowires? > >> The manpage doesn't mention anything about the type of bridge > >> interface required (bridge/veb)? > > > > I have not tried it but I think mpw(4) should work with veb(4) just fine. > > Agreed. Does it work? I will try it soon and post the feedback here, considered using tpmr(4) but in this case i want to use MPLS as transport and terminate the pseudowire on a Cisco. -- Wouter Prins w...@null0.nl
Re: OpenBSD 7.4 released -- Oct 16, 2023
Wow. 55 releases. I remember starting out with OpenBSD 2.2 or 2.3 and still have the CDs in a box downstairs somewhere :) Congratulations on another fine release. I'll have to go stock up on some tshirts in a bit.
Re: l2vpn pseudowire and bridge type interface
Switching from tech@ to misc@ > > > On Sat, Oct 14, 2023 at 11:07:11AM +0200, Wouter Prins wrote: > > >> hello list, > > >> > > >> Was wondering if the veb interface is supported as a bridge for > > >> pseudowires? > > >> The manpage doesn't mention anything about the type of > > >> bridge interface required (bridge/veb)? > > > > > > I have not tried it but I think mpw(4) should work with veb(4) just fine. > > > > Agreed. Does it work? I just tested the l2vpn setup between openbsd and cisco, with the veb(4) bridge the mac addresses are not learned from the mpw(4) interface. When replacing the veb(4) with a bridge(4) the mac addresses are learned from the mpw(4) interface and the pseudowire is working correctly. If you want the configuration, please let me know but it should be easy to replicate (if it needs to be fixed :)) /Wouter
Re: OpenBSD 7.4 released -- Oct 16, 2023
Congratulations to Theo and everyone involved in making OpenBSD 7.4 a reality and for this awesome project altogether! I also love the artwork (big thanks also to the artist that created it). so I'll be getting some 7.4 merch soon! Claudio Miranda On Mon, Oct 16, 2023 at 9:37 AM pela0 wrote: > > Upgrading... > > ;) > > > > > --- Original Message --- > On Monday, October 16th, 2023 at 09:53, Theo de Raadt > wrote: > > > > > > > > > > > > - OpenBSD 7.4 RELEASED - > > > > October 16, 2023. > > > > We are pleased to announce the official release of OpenBSD 7.4. > > This is our 55th release. We remain proud of OpenBSD's record of more > > than twenty years with only two remote holes in the default install. > > > > As in our previous releases, 7.4 provides significant improvements, > > including new features, in nearly all areas of the system: > > > > - Various kernel improvements: > > o On arm64, show BTI and SBSS features in dmesg(8). > > o New kqueue1(2) system call supporting the O_CLOEXEC flag. > > o Map device tree read/write to unbreak root on softraid(4). > > o Correctly recognize umass(4) floppy disk devices as floppy disks. > > o In wscons(4), catch up with box drawing characters which have been > > standardized in unicode after the original wscons code was written > > and chose placeholder values. > > o In wscons(4), make sure we do not increase the escape sequence > > argument count beyond usable bounds. > > o Implement dt(4) utrace(2) support on amd64 and i386. > > o Correct undefined behavior when using MS-DOS filesystems, fixes > > imported from FreeBSD. > > o Make the softdep mount(8) option a no-op. Softdep was a > > significant impediment to improving the vfs layer. > > o Allow unveil(2)ed programs to dump core(5) into the current > > working directory. > > o Address incomplete validation of ELF program headers in execve(2). > > o On arm64, use the deep idle state available on Apple M1/M2 cores > > in the idle loop and for suspend, resulting in power savings. > > o Update AMD CPU microcode if a newer patch is available. > > o Enable a workaround for the 'Zenbleed' AMD CPU bug. > > o Report speculation control bits in dmesg(8) CPU lines. > > o To give the primary CPU an opportunity to perform clock interrupt > > preparation in a machine-independent manner we need to separate > > the "initialization" parts of cpu_initclocks() from the "start the > > clock interrupt" parts. Separate cpu_initclocks() from > > cpu_startclock(). > > o Fix a problem where CPU time accounting and RLIMIT_CPU was > > unreliable on idle systems. > > o Improve the output of the "show proc" command of the kernel > > debugger ddb(4) and show both the PID and TID of the proc. > > > > - SMP Improvements > > o Rewrite pfsync(4), in particular to improve locking and to help > > with unlocking more of pf(4) and with parallelisation of the > > network stack in the future. The protocol remains compatible with > > the older version. > > o Remove kernel locks from the ARP input path. > > o Pull MP-safe arprequest() out of kernel lock. > > o Remove the kernel lock from IPv6 neighbor discovery. > > o Unlock more parts of ioctl(2) and the routing code in the network > > stack. > > > > - Direct Rendering Manager and graphics drivers > > o Update drm(4) to Linux 6.1.55. > > o Don't change end marker in sg_set_page(). Caused bad memory > > accesses when using page flipping on Alder Lake and Raptor Lake. > > > > - VMM/VMD improvements > > o Allowed vmm(4) guests to enable and use supervisor IBT. > > o Suppressed AMD hardware p-state visibility to vmm(4) guests. > > o Avoid use of uninitialised memory in vmd(8). > > o Migrate vmd_vm.vm_ttyname to char array allowing a vmd_vm object > > to be transmitted over an ipc channel. > > o Cleaned up file descriptor closing in vmd(8) vmm process. > > o Fixed vm send/receive, restoring device virtqueue addresses on > > receive. > > o Introduced execvp(3) after fork for child vm processes. > > o No longer generate an error in vmd(8) if vm.conf(5) is absent. > > o Split vmm(4) into MI/MD parts. > > o Introduced multi-process model for vmd(8) virtio block and network > > devices. > > o Allowed vm owners to override boot kernel when using vmctl(8) to > > start a vm. > > o Changed staggered start of vms to number of online CPUs. > > o Fixed a segfault on vm creation. > > o Switched to anonymous shared memory mappings for vmd(8) vm > > processes, introducing a new vmm(4) ioctl(2). > > o Relaxed absolute path requirements for vmd(8) configtest mode > > (-n). > > o Adjusted shutdown logic by vm id to function similarly as by name. > > o Moved validation of local network prefixes for the internal vmd(8) > > DHCP service into the config parser. > > o Fixed QCOW2 base images when used with the vmd(8) multi-process > > device model. > > o Fixed setting verbose logging in child proce
Re: OpenBSD 7.4 released -- Oct 16, 2023
Upgrading... ;) --- Original Message --- On Monday, October 16th, 2023 at 09:53, Theo de Raadt wrote: > > > > > - OpenBSD 7.4 RELEASED - > > October 16, 2023. > > We are pleased to announce the official release of OpenBSD 7.4. > This is our 55th release. We remain proud of OpenBSD's record of more > than twenty years with only two remote holes in the default install. > > As in our previous releases, 7.4 provides significant improvements, > including new features, in nearly all areas of the system: > > - Various kernel improvements: > o On arm64, show BTI and SBSS features in dmesg(8). > o New kqueue1(2) system call supporting the O_CLOEXEC flag. > o Map device tree read/write to unbreak root on softraid(4). > o Correctly recognize umass(4) floppy disk devices as floppy disks. > o In wscons(4), catch up with box drawing characters which have been > standardized in unicode after the original wscons code was written > and chose placeholder values. > o In wscons(4), make sure we do not increase the escape sequence > argument count beyond usable bounds. > o Implement dt(4) utrace(2) support on amd64 and i386. > o Correct undefined behavior when using MS-DOS filesystems, fixes > imported from FreeBSD. > o Make the softdep mount(8) option a no-op. Softdep was a > significant impediment to improving the vfs layer. > o Allow unveil(2)ed programs to dump core(5) into the current > working directory. > o Address incomplete validation of ELF program headers in execve(2). > o On arm64, use the deep idle state available on Apple M1/M2 cores > in the idle loop and for suspend, resulting in power savings. > o Update AMD CPU microcode if a newer patch is available. > o Enable a workaround for the 'Zenbleed' AMD CPU bug. > o Report speculation control bits in dmesg(8) CPU lines. > o To give the primary CPU an opportunity to perform clock interrupt > preparation in a machine-independent manner we need to separate > the "initialization" parts of cpu_initclocks() from the "start the > clock interrupt" parts. Separate cpu_initclocks() from > cpu_startclock(). > o Fix a problem where CPU time accounting and RLIMIT_CPU was > unreliable on idle systems. > o Improve the output of the "show proc" command of the kernel > debugger ddb(4) and show both the PID and TID of the proc. > > - SMP Improvements > o Rewrite pfsync(4), in particular to improve locking and to help > with unlocking more of pf(4) and with parallelisation of the > network stack in the future. The protocol remains compatible with > the older version. > o Remove kernel locks from the ARP input path. > o Pull MP-safe arprequest() out of kernel lock. > o Remove the kernel lock from IPv6 neighbor discovery. > o Unlock more parts of ioctl(2) and the routing code in the network > stack. > > - Direct Rendering Manager and graphics drivers > o Update drm(4) to Linux 6.1.55. > o Don't change end marker in sg_set_page(). Caused bad memory > accesses when using page flipping on Alder Lake and Raptor Lake. > > - VMM/VMD improvements > o Allowed vmm(4) guests to enable and use supervisor IBT. > o Suppressed AMD hardware p-state visibility to vmm(4) guests. > o Avoid use of uninitialised memory in vmd(8). > o Migrate vmd_vm.vm_ttyname to char array allowing a vmd_vm object > to be transmitted over an ipc channel. > o Cleaned up file descriptor closing in vmd(8) vmm process. > o Fixed vm send/receive, restoring device virtqueue addresses on > receive. > o Introduced execvp(3) after fork for child vm processes. > o No longer generate an error in vmd(8) if vm.conf(5) is absent. > o Split vmm(4) into MI/MD parts. > o Introduced multi-process model for vmd(8) virtio block and network > devices. > o Allowed vm owners to override boot kernel when using vmctl(8) to > start a vm. > o Changed staggered start of vms to number of online CPUs. > o Fixed a segfault on vm creation. > o Switched to anonymous shared memory mappings for vmd(8) vm > processes, introducing a new vmm(4) ioctl(2). > o Relaxed absolute path requirements for vmd(8) configtest mode > (-n). > o Adjusted shutdown logic by vm id to function similarly as by name. > o Moved validation of local network prefixes for the internal vmd(8) > DHCP service into the config parser. > o Fixed QCOW2 base images when used with the vmd(8) multi-process > device model. > o Fixed setting verbose logging in child processes. > o Fixed a race condition related to the emulated i8259 interrupt > controller by ignoring interrupt masks on assert. > o Inlined pending interrupts in the vmm(4) ioctl(2) for running the > vcpu, reducing vm latency. > o Added zero-copy, vectored io to the vmd(8) virtio block device. > o Changed to logging vmd(8) vm ids in the vcpu run loop on error and > not the ids used by vmm(4). > o Fixed a vm pause deadlock. > o Changed vmd(8) logging format to disambiguate vm and device
OpenBSD 7.4 released -- Oct 16, 2023
- OpenBSD 7.4 RELEASED - October 16, 2023. We are pleased to announce the official release of OpenBSD 7.4. This is our 55th release. We remain proud of OpenBSD's record of more than twenty years with only two remote holes in the default install. As in our previous releases, 7.4 provides significant improvements, including new features, in nearly all areas of the system: - Various kernel improvements: o On arm64, show BTI and SBSS features in dmesg(8). o New kqueue1(2) system call supporting the O_CLOEXEC flag. o Map device tree read/write to unbreak root on softraid(4). o Correctly recognize umass(4) floppy disk devices as floppy disks. o In wscons(4), catch up with box drawing characters which have been standardized in unicode after the original wscons code was written and chose placeholder values. o In wscons(4), make sure we do not increase the escape sequence argument count beyond usable bounds. o Implement dt(4) utrace(2) support on amd64 and i386. o Correct undefined behavior when using MS-DOS filesystems, fixes imported from FreeBSD. o Make the softdep mount(8) option a no-op. Softdep was a significant impediment to improving the vfs layer. o Allow unveil(2)ed programs to dump core(5) into the current working directory. o Address incomplete validation of ELF program headers in execve(2). o On arm64, use the deep idle state available on Apple M1/M2 cores in the idle loop and for suspend, resulting in power savings. o Update AMD CPU microcode if a newer patch is available. o Enable a workaround for the 'Zenbleed' AMD CPU bug. o Report speculation control bits in dmesg(8) CPU lines. o To give the primary CPU an opportunity to perform clock interrupt preparation in a machine-independent manner we need to separate the "initialization" parts of cpu_initclocks() from the "start the clock interrupt" parts. Separate cpu_initclocks() from cpu_startclock(). o Fix a problem where CPU time accounting and RLIMIT_CPU was unreliable on idle systems. o Improve the output of the "show proc" command of the kernel debugger ddb(4) and show both the PID and TID of the proc. - SMP Improvements o Rewrite pfsync(4), in particular to improve locking and to help with unlocking more of pf(4) and with parallelisation of the network stack in the future. The protocol remains compatible with the older version. o Remove kernel locks from the ARP input path. o Pull MP-safe arprequest() out of kernel lock. o Remove the kernel lock from IPv6 neighbor discovery. o Unlock more parts of ioctl(2) and the routing code in the network stack. - Direct Rendering Manager and graphics drivers o Update drm(4) to Linux 6.1.55. o Don't change end marker in sg_set_page(). Caused bad memory accesses when using page flipping on Alder Lake and Raptor Lake. - VMM/VMD improvements o Allowed vmm(4) guests to enable and use supervisor IBT. o Suppressed AMD hardware p-state visibility to vmm(4) guests. o Avoid use of uninitialised memory in vmd(8). o Migrate vmd_vm.vm_ttyname to char array allowing a vmd_vm object to be transmitted over an ipc channel. o Cleaned up file descriptor closing in vmd(8) vmm process. o Fixed vm send/receive, restoring device virtqueue addresses on receive. o Introduced execvp(3) after fork for child vm processes. o No longer generate an error in vmd(8) if vm.conf(5) is absent. o Split vmm(4) into MI/MD parts. o Introduced multi-process model for vmd(8) virtio block and network devices. o Allowed vm owners to override boot kernel when using vmctl(8) to start a vm. o Changed staggered start of vms to number of online CPUs. o Fixed a segfault on vm creation. o Switched to anonymous shared memory mappings for vmd(8) vm processes, introducing a new vmm(4) ioctl(2). o Relaxed absolute path requirements for vmd(8) configtest mode (-n). o Adjusted shutdown logic by vm id to function similarly as by name. o Moved validation of local network prefixes for the internal vmd(8) DHCP service into the config parser. o Fixed QCOW2 base images when used with the vmd(8) multi-process device model. o Fixed setting verbose logging in child processes. o Fixed a race condition related to the emulated i8259 interrupt controller by ignoring interrupt masks on assert. o Inlined pending interrupts in the vmm(4) ioctl(2) for running the vcpu, reducing vm latency. o Added zero-copy, vectored io to the vmd(8) virtio block device. o Changed to logging vmd(8) vm ids in the vcpu run loop on error and not the ids used by vmm(4). o Fixed a vm pause deadlock. o Chan
Re: Starting Homebridge / nodejs daemon at boot
Am Sonntag 15 Oktober 2023 um 16:47:37 -, schrieb Stuart Henderson 0,2K: > On 2023-10-14, Manuel Kuklinski wrote: > > Thank you again - can you possibly direct me in the correct way to "dump > > the environment"? I guess you don't mean `env`? > > Yes, env - e.g. "(date; env) >> /tmp/env.log Hi! O.K., so my first guess wasn't that wrong - I thought there was a more complex step involved, dumping the environment; maybe a nodejs switch - sorry for the extra typing... Nevertheless, that's the result: # cat /tmp/env.log Mon Oct 16 14:07:50 CEST 2023 _=/usr/bin/env INRC=1 HOME=/ PWD=/ PATH=/sbin:/bin:/usr/sbin:/usr/bin Mon Oct 16 14:12:23 CEST 2023 _=/usr/bin/env LOGNAME=root TERM=xterm-256color USER=root HOME=/root SHELL=/bin/ksh PWD=/root PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/sbin:/usr/local/bin I have no clue what to make of this, since the daemon receives a SIGTERM, as visible in the debug log of homebridge (can be attached, if needed). My wild guess would be the missing SHELL?! Help is appreciated :-/ Kind regards.
Re: Greedy match of traffic in iked between site and hub
On 2023-10-16, rea...@catastrophe.net wrote: > On Sun, Oct 15, 2023 at 04:56:17PM -, Stuart Henderson wrote: >>On 2023-10-15, rea...@catastrophe.net wrote: >>> What is a better way to configure iked on site-obsd so that it does not >>> encapsulate local traffic on the 10.89.2.0/24 network? Obviously my >>> understanding is incorrect, so any help is appreciated. >> >>You should be able to add a bypass flow in ipsec.conf, and set ipsec=YES >>but *not* isakmpd_flags in rc.conf.local. >> >>To load manually without rebooting, ipsecctl -f /etc/ipsec.conf > > Ah, well...I'm using iked. I'll see if there is something similar. While ipsecctl is normally used to signal isakmpd it can also be used to install flows manually and that is what you want to do in this case.
