Re: support update

2022-10-31 Thread Martin Hein 
On Mon, 31 Oct 2022 02:07:00 +0100 (CET)
i...@tutanota.com wrote:
> The entry under Denmark listed with a company name "Zen System"
> doesn't exist. There no longer is such a company, and the URL
> redirects to a completely different company that doesn't provide
> any kind of OpenBSD service.

I am the one listed as the contact person in the support entry.

Zen Systems was sold to Nianet, an Danish ISP 7 years ago. Two year
later Globalconnect, another Danish ISP, acquired Nianet.

It was finally closed in July 2021.

Somewhere in time the old support entry was forgotten and no one
asked for it to be deleted.

I am pretty sure you can remove that entry.

Best regards Martin

Re: support update

2022-10-31 Thread Martin Hein 
On Mon, 31 Oct 2022 02:07:00 +0100 (CET)
i...@tutanota.com wrote:
> The entry under Denmark listed with a company name "Zen System"
> doesn't exist. There no longer is such a company, and the URL
> redirects to a completely different company that doesn't provide
> any kind of OpenBSD service.

This is correct. It is me that is listed as the contact person.

Zen Systems was sold to Nianet, an Danish ISP 7 years ago. Two year
later Globalconnect, another Danish ISP, acquired Nianet.

I am pretty sure you can remove that entry.

Best regards Martin

Re: VMware Tools driver to advertise OS as 'FreeBSD 64-bit' OS, not 32-bit version

2022-10-31 Thread Patrick Wildt 
On Fri, Oct 28, 2022 at 12:26:07PM -0700, Mike Larkin wrote:
> On Fri, Oct 28, 2022 at 12:30:11PM -0600, Theo de Raadt wrote:
> > Kalabic S,  wrote:
> >
> > > To be more precise, I wanted to say sticking with FreeBSD means
> > > sticking with whatever behavior VMware will keep consistent and
> > > support in the future. For "Others" option I don't think they care and
> > > is more probable to vary.
> >
> > I cannot tell the difference.  I think you are completely unqualified
> > to know what "they will not change" fakery vmware is doing with the MSR's
> > and clock related registers... it is actually possible that when they
> > *know* it is one particular operating system they do something sophisticated
> > to fool that one specific operating system, whereas when they don't know
> > what the operating system is, they reduce the amount of trickery.
> >
> > You don't know.  I don't know.  None of us know.
> >
> > But can you please stop making claims you can't back.
> >
> 
> I think it's reasonable to try and claim that whatever we are, we are the
> closest to "that thing". Meaning, the OP said we should claim we are FreeBSD
> 64 bit or 32 bit or whatever. Fine, but let's spend some time to actually
> figure out *what* we should say we are before we just pick something randomly
> because "it fixed my machine". Maybe we should say we're Windows? Maybe we
> should say we're Linux? My point, and I think Theo's as well, is we don't
> know and just randomly taking a diff because it fixes one scenario on one
> version of ESXi is shortsighted.
> 
> So I would ask the OP to:
> 
>  - try different OS choices
>  - on different versions of ESX
>  - on different versions of VMware fusion
>  - on different versions of VMware workstation
>  - on different versions of OpenBSD VMs
>  - on different archs (i386/amd64) of OpenBSD VMs
> 
> ... and then report back what the findings are.
> 
> -ml

Hi,

>From what I've been told from someone in the know:

* What we report in vmt(4) doesn't influence what machine is modeled,
  that's just for what's shown in vCenter.  We should probably show
  something useful.  I kinda liked that OpenBSD 7.2 GENEIRC.MP#31 string
  that jmatthew@ showed, but that's another discussion.

* The guest type configured in the .vmx influences the VM model.  Just
  assume the ESXi version has a workaround for FreeBSD to run fine on
  that ESXi, it could be possible that it actually degrades OpenBSD
  performance/stability.  In general it makes more sense to opt for the
  Other 64-Bit guest type (for amd64).

I personally sometimes use Windows 11 guest types on things like VMware
Fusion or Parallels, but that's mostly because they sometimes have some
funky devices and I'm doing that for testing w/ graphics.  For ESXi I'd
opt for Other 64-Bit.

Cheers,
Patrick

cpu frequency sensors

2022-10-31 Thread Jan Stary 
> > > o Added CPU frequency sensors for each core on CPUs that have
> > >   MPERF/APERF support.

This is current/amd64 on an APU2 (dmesg below).
The cpu line says PERF - does that imply MPERF/APEEF support?
The sensors seem enabled:
 
   hw.sensors.cpu0.frequency0=95000.00 Hz
   hw.sensors.cpu1.frequency0=95000.00 Hz
   hw.sensors.cpu2.frequency0=95000.00 Hz
   hw.sensors.cpu3.frequency0=95000.00 Hz
 
while apm says
 
   Performance adjustment mode: auto (1000 MHz)
 
In fact, dmesg says
 
   cpu0: 998 MHz: speeds: 1000 800 600 MHz
 
Is the 950 expected, and in fact more true than dmesg's 1000?
Or is that a bug in the sensors code? How can I debug this?
 
Jan


OpenBSD 7.2-current (GENERIC.MP) #822: Fri Oct 28 21:59:48 MDT 2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2112425984 (2014MB)
avail mem = 2031046656 (1936MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7ee92040 (13 entries)
bios0: vendor coreboot version "v4.17.0.2" date 07/28/2022
bios0: PC Engines apu2
acpi0 at bios0: ACPI 6.0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP SSDT MCFG TPM2 APIC HEST IVRS SSDT SSDT DRTM HPET
acpi0: wakeup devices PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PBR8(S4) UOH1(S3) 
UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) UOH6(S3) XHC0(S4)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD GX-412TC SOC, 998.19 MHz, 16-30-01
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache, 2MB 64b/line 
16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD GX-412TC SOC, 998.24 MHz, 16-30-01
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache, 2MB 64b/line 
16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD GX-412TC SOC, 998.14 MHz, 16-30-01
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT
cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache, 2MB 64b/line 
16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: AMD GX-412TC SOC, 998.14 MHz, 16-30-01
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT
cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache, 2MB 64b/line 
16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 21, 24 pins
ioapic1 at mainbus0: apid 5 pa 0xfec2, version 21, 32 pins
acpihpet0 at acpi0: 14318180 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PBR4)
acpiprt2 at acpi0: bus 1 (PBR5)
acpiprt3 at acpi0: bus -1 (PBR6)
acpiprt4 at acpi0: bus 2 (PBR7)
acpiprt5 at acpi0: bus -1 (PBR8)
acpicpu0 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu1 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu2 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu3 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu4 at acpi0: no cpu matching ACPI ID 4
acpicpu5 at acpi0: no cpu matching ACPI ID 5
acpicpu6 at acpi0: no cpu matching ACPI ID 6
acpicpu7 at acpi0: no cpu matching ACPI ID 7
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
com0 at acpi0 COM1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at acpi0 COM2 addr 0x2f8/0x8 irq 3: ns16550a, 16 byte fifo
amdgpio0 at acpi0 GPIO uid 0 addr 0xfed81500/0x300 irq 7, 184 pins
"PRP0001" at acpi0 not configured
"PRP0001" at acpi0 not configured
"PRP0