Re: Modern CPUs AES-NI enabling system wide

2019-02-03 Thread Christian Weisgerber
On 2019-02-03, Stuart Henderson  wrote:

>> If your CPU supports AES-NI, the kernel and base software will use it by
>> default.
>
> You do need to pick suitable ciphers though. And it is only supported
> on OpenBSD/amd64 not OpenBSD/i386.

Only the kernel support (IPsec, softraid crypto) is limited to
amd64.  The userland can still use AES-NI on i386; specifically,
LibreSSL does.  Of course all CPUs that support AES-NI can also run
amd64.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de



Re: amd64 cc error unknown argument '-msave-args'

2019-02-03 Thread John Rigg
On Sun, Feb 03, 2019 at 02:51:08PM -0700, Theo de Raadt wrote:
> John Rigg  wrote:
> 
> > I'm trying to compile a GENERIC.MP kernel on amd64
> > 6.4 -stable.
> 
> No way, you are not.  Only -current has that, as of a few days ago.

I used the wrong cvs command and didn't spot it. Stupid mistake.
Sorry for the noise.

John



Re: amd64 cc error unknown argument '-msave-args'

2019-02-03 Thread Theo de Raadt
And since you are doing this with -current *ALL OVER THE PLACE*
there are instructions that if you have trouble you should upgrade
to a snapshot.

Those instructions to exist the noise on the list everytime we
make a change and people don't notice or understand it and suddenly
they are in over their heads

*even our own developers* have to do that, from time to time



> John Rigg  wrote:
> 
> > I'm trying to compile a GENERIC.MP kernel on amd64
> > 6.4 -stable.
> 
> No way, you are not.  Only -current has that, as of a few days ago.
> 
>  I've followed the instructions in the
> > FAQ for building a custom kernel, but the 'make'
> > step fails with an unknown argument: '-msave-args'
> > error. I've copied the compiler messages and dmesg
> > below. Suggestions for a cure or workaround would
> > be appreciated.=20
> > 
> > John
> > 
> > 
> > cat /usr/src/sys/arch/amd64/amd64/genassym.cf /usr/src/sys/arch/amd64/amd64=
> > /genassym.cf |  sh /usr/src/sys/kern/genassym.sh cc -no-integrated-as -g -W=
> > error -Wall -Wimplicit-function-declaration  -Wno-uninitialized -Wno-pointe=
> > r-sign  -Wframe-larger-than=3D2047 -Wno-address-of-packed-member -Wno-const=
> > ant-conversion -mcmodel=3Dkernel -mno-red-zone -mno-sse2 -mno-sse -mno-3dno=
> > w  -mno-mmx -msoft-float -fno-omit-frame-pointer -ffreestanding -fno-pie -m=
> > save-args -O2 -pipe -nostdinc -I/usr/src/sys -I/sys/arch/amd64/compile/GENE=
> > RIC.MP/obj -I/usr/src/sys/arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DK=
> > MEMSTATS -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUVM=
> > _SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA -DEXT2FS=
> >  -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO -DFUSE -DSOC=
> > KET_SPLICE -DTCP_ECN -DTCP_SIGNATURE -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DE=
> > FLATE -DPIPEX -DMROUTING -DMPLS -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DM=
> > TRR -DNTFS -DHIBERNATE -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DW=
> > SDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS=3D"6" -DX86EMU -DONEWIREV=
> > ERBOSE -DMULTIPROCESSOR -DMAXUSERS=3D80 -D_KERNEL -MD -MP -MF assym.P > ass=
> > ym.h.tmp
> > cc: error: unknown argument: '-msave-args'
> > *** Error 1 in /sys/arch/amd64/compile/GENERIC.MP (Makefile:1010 'assym.h')
> > 
> > 
> > dmesg
> > _
> > 
> > OpenBSD 6.4 (GENERIC.MP) #6: Sat Jan 26 20:37:44 CET 2019
> > r...@syspatch-64-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENE=
> > RIC.MP
> > real mem =3D 4007526400 (3821MB)
> > avail mem =3D 3876790272 (3697MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (57 entries)
> > bios0: vendor Award Software International, Inc. version "F5" date 06/18/20=
> > 08
> > bios0: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H
> > acpi0 at bios0: rev 0
> > acpi0: sleep states S0 S1 S4 S5
> > acpi0: tables DSDT FACP SSDT HPET MCFG APIC
> > acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3)=
> >  USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PC=
> > E7(S4) PCE9(S4) [...]
> > acpitimer0 at acpi0: 3579545 Hz, 32 bits
> > acpihpet0 at acpi0: 14318180 Hz
> > acpimcfg0 at acpi0
> > acpimcfg0: addr 0xe000, bus 0-255
> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: AMD Athlon(tm) Dual Core Processor 4850e, 2505.72 MHz, 0f-6b-02
> > cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
> > 36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
> > ,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
> > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
> > ine 16-way L2 cache
> > cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
> > cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
> > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> > cpu0: apic clock running at 200MHz
> > cpu1 at mainbus0: apid 1 (application processor)
> > cpu1: AMD Athlon(tm) Dual Core Processor 4850e, 2505.33 MHz, 0f-6b-02
> > cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
> > 36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
> > ,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
> > cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
> > ine 16-way L2 cache
> > cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
> > cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
> > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins, remapped
> > acpiprt0 at acpi0: bus 0 (PCI0)
> > acpiprt1 at acpi0: bus 3 (P2P_)
> > acpiprt2 at acpi0: bus -1 (PCE2)
> > acpiprt3 at acpi0: bus -1 (PCE3)
> > acpiprt4 at acpi0: bus -1 (PCE4)
> > acpiprt5 at acpi0: bus -1 (PCE5)
> > acpiprt6 at acpi0: bus -1 (PCE6)
> > acpiprt7 at acpi0: bus -1 

Re: amd64 cc error unknown argument '-msave-args'

2019-02-03 Thread Theo de Raadt
John Rigg  wrote:

> I'm trying to compile a GENERIC.MP kernel on amd64
> 6.4 -stable.

No way, you are not.  Only -current has that, as of a few days ago.

 I've followed the instructions in the
> FAQ for building a custom kernel, but the 'make'
> step fails with an unknown argument: '-msave-args'
> error. I've copied the compiler messages and dmesg
> below. Suggestions for a cure or workaround would
> be appreciated.=20
> 
> John
> 
> 
> cat /usr/src/sys/arch/amd64/amd64/genassym.cf /usr/src/sys/arch/amd64/amd64=
> /genassym.cf |  sh /usr/src/sys/kern/genassym.sh cc -no-integrated-as -g -W=
> error -Wall -Wimplicit-function-declaration  -Wno-uninitialized -Wno-pointe=
> r-sign  -Wframe-larger-than=3D2047 -Wno-address-of-packed-member -Wno-const=
> ant-conversion -mcmodel=3Dkernel -mno-red-zone -mno-sse2 -mno-sse -mno-3dno=
> w  -mno-mmx -msoft-float -fno-omit-frame-pointer -ffreestanding -fno-pie -m=
> save-args -O2 -pipe -nostdinc -I/usr/src/sys -I/sys/arch/amd64/compile/GENE=
> RIC.MP/obj -I/usr/src/sys/arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DK=
> MEMSTATS -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUVM=
> _SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA -DEXT2FS=
>  -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO -DFUSE -DSOC=
> KET_SPLICE -DTCP_ECN -DTCP_SIGNATURE -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DE=
> FLATE -DPIPEX -DMROUTING -DMPLS -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DM=
> TRR -DNTFS -DHIBERNATE -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DW=
> SDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS=3D"6" -DX86EMU -DONEWIREV=
> ERBOSE -DMULTIPROCESSOR -DMAXUSERS=3D80 -D_KERNEL -MD -MP -MF assym.P > ass=
> ym.h.tmp
> cc: error: unknown argument: '-msave-args'
> *** Error 1 in /sys/arch/amd64/compile/GENERIC.MP (Makefile:1010 'assym.h')
> 
> 
> dmesg
> _
> 
> OpenBSD 6.4 (GENERIC.MP) #6: Sat Jan 26 20:37:44 CET 2019
> r...@syspatch-64-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENE=
> RIC.MP
> real mem =3D 4007526400 (3821MB)
> avail mem =3D 3876790272 (3697MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (57 entries)
> bios0: vendor Award Software International, Inc. version "F5" date 06/18/20=
> 08
> bios0: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S1 S4 S5
> acpi0: tables DSDT FACP SSDT HPET MCFG APIC
> acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3)=
>  USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PC=
> E7(S4) PCE9(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 32 bits
> acpihpet0 at acpi0: 14318180 Hz
> acpimcfg0 at acpi0
> acpimcfg0: addr 0xe000, bus 0-255
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: AMD Athlon(tm) Dual Core Processor 4850e, 2505.72 MHz, 0f-6b-02
> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
> 36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
> ,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
> cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
> ine 16-way L2 cache
> cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
> cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 200MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: AMD Athlon(tm) Dual Core Processor 4850e, 2505.33 MHz, 0f-6b-02
> cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
> 36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
> ,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
> cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
> ine 16-way L2 cache
> cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
> cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins, remapped
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 3 (P2P_)
> acpiprt2 at acpi0: bus -1 (PCE2)
> acpiprt3 at acpi0: bus -1 (PCE3)
> acpiprt4 at acpi0: bus -1 (PCE4)
> acpiprt5 at acpi0: bus -1 (PCE5)
> acpiprt6 at acpi0: bus -1 (PCE6)
> acpiprt7 at acpi0: bus -1 (PCE7)
> acpiprt8 at acpi0: bus -1 (PCE9)
> acpiprt9 at acpi0: bus 2 (PCEA)
> acpiprt10 at acpi0: bus -1 (PCEB)
> acpiprt11 at acpi0: bus -1 (PCEC)
> acpiprt12 at acpi0: bus 1 (AGP_)
> acpicpu0 at acpi0: C1(@1 halt!), PSS
> acpicpu1 at acpi0: C1(@1 halt!), PSS
> acpibtn0 at acpi0: PWRB
> acpicmos0 at acpi0
> "PNP0C14" at acpi0 not configured
> cpu0: PowerNow! K8 2505 MHz: speeds: 2500 2400 2200 2000 1800 1000 MHz
> pci0 at mainbus0 bus 0
> 0:0:0: mem address conflict 0xe000/0x2000
> pchb0 at pci0 dev 0 function 0 "AMD RS780 Host" rev 0x00
> ppb0 

amd64 cc error unknown argument '-msave-args'

2019-02-03 Thread John Rigg
I'm trying to compile a GENERIC.MP kernel on amd64
6.4 -stable. I've followed the instructions in the
FAQ for building a custom kernel, but the 'make'
step fails with an unknown argument: '-msave-args'
error. I've copied the compiler messages and dmesg
below. Suggestions for a cure or workaround would
be appreciated.=20

John


cat /usr/src/sys/arch/amd64/amd64/genassym.cf /usr/src/sys/arch/amd64/amd64=
/genassym.cf |  sh /usr/src/sys/kern/genassym.sh cc -no-integrated-as -g -W=
error -Wall -Wimplicit-function-declaration  -Wno-uninitialized -Wno-pointe=
r-sign  -Wframe-larger-than=3D2047 -Wno-address-of-packed-member -Wno-const=
ant-conversion -mcmodel=3Dkernel -mno-red-zone -mno-sse2 -mno-sse -mno-3dno=
w  -mno-mmx -msoft-float -fno-omit-frame-pointer -ffreestanding -fno-pie -m=
save-args -O2 -pipe -nostdinc -I/usr/src/sys -I/sys/arch/amd64/compile/GENE=
RIC.MP/obj -I/usr/src/sys/arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DK=
MEMSTATS -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUVM=
_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA -DEXT2FS=
 -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO -DFUSE -DSOC=
KET_SPLICE -DTCP_ECN -DTCP_SIGNATURE -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DE=
FLATE -DPIPEX -DMROUTING -DMPLS -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DM=
TRR -DNTFS -DHIBERNATE -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DW=
SDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS=3D"6" -DX86EMU -DONEWIREV=
ERBOSE -DMULTIPROCESSOR -DMAXUSERS=3D80 -D_KERNEL -MD -MP -MF assym.P > ass=
ym.h.tmp
cc: error: unknown argument: '-msave-args'
*** Error 1 in /sys/arch/amd64/compile/GENERIC.MP (Makefile:1010 'assym.h')


dmesg
_

OpenBSD 6.4 (GENERIC.MP) #6: Sat Jan 26 20:37:44 CET 2019
r...@syspatch-64-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENE=
RIC.MP
real mem =3D 4007526400 (3821MB)
avail mem =3D 3876790272 (3697MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (57 entries)
bios0: vendor Award Software International, Inc. version "F5" date 06/18/20=
08
bios0: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP SSDT HPET MCFG APIC
acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3)=
 USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PC=
E7(S4) PCE9(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) Dual Core Processor 4850e, 2505.72 MHz, 0f-6b-02
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
ine 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Athlon(tm) Dual Core Processor 4850e, 2505.33 MHz, 0f-6b-02
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
ine 16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins, remapped
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (P2P_)
acpiprt2 at acpi0: bus -1 (PCE2)
acpiprt3 at acpi0: bus -1 (PCE3)
acpiprt4 at acpi0: bus -1 (PCE4)
acpiprt5 at acpi0: bus -1 (PCE5)
acpiprt6 at acpi0: bus -1 (PCE6)
acpiprt7 at acpi0: bus -1 (PCE7)
acpiprt8 at acpi0: bus -1 (PCE9)
acpiprt9 at acpi0: bus 2 (PCEA)
acpiprt10 at acpi0: bus -1 (PCEB)
acpiprt11 at acpi0: bus -1 (PCEC)
acpiprt12 at acpi0: bus 1 (AGP_)
acpicpu0 at acpi0: C1(@1 halt!), PSS
acpicpu1 at acpi0: C1(@1 halt!), PSS
acpibtn0 at acpi0: PWRB
acpicmos0 at acpi0
"PNP0C14" at acpi0 not configured
cpu0: PowerNow! K8 2505 MHz: speeds: 2500 2400 2200 2000 1800 1000 MHz
pci0 at mainbus0 bus 0
0:0:0: mem address conflict 0xe000/0x2000
pchb0 at pci0 dev 0 function 0 "AMD RS780 Host" rev 0x00
ppb0 at pci0 dev 1 function 0 "AMD RS780 PCIE" rev 0x00
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 5 function 0 "ATI Radeon HD 3200" rev 0x00
drm0 at radeondrm0
radeondrm0: apic 2 int 18
azalia0 at pci1 dev 5 function 1 "ATI RS780 HD Audio" rev 0x00: msi
azalia0: no supported codecs
ppb1 at pci0 dev 

Re: Modern CPUs AES-NI enabling system wide

2019-02-03 Thread Stuart Henderson
On 2019-02-03, Juan Francisco Cantero Hurtado  wrote:
> On Sun, Feb 03, 2019 at 11:35:52AM +0300, Denis wrote:
>> How to enable AES-NI AES system wide hardware acceleration support for
>> crypto disciplines like LibreSSL, softraid0 crypto etc?
>
> If your CPU supports AES-NI, the kernel and base software will use it by
> default.

You do need to pick suitable ciphers though. And it is only supported
on OpenBSD/amd64 not OpenBSD/i386.




40G ixl nics

2019-02-03 Thread Tony Sarendal
Good evening,

We inserted a 2x40G NIC into one of our old franken-pc's, and got this:

ixl0 at pci2 dev 0 function 0 "Intel XL710 QSFP+" rev 0x02: port 0, FW
5.0.40043 API 1.5, msi, address 0c:c4:7a:5e:f9:c8
ixl0: unable to query phy types
ixl1 at pci2 dev 0 function 1 "Intel XL710 QSFP+" rev 0x02: port 1, FW
5.0.40043 API 1.5, msi, address 0c:c4:7a:5e:f9:c9
ixl1: unable to query phy types

NIC:
https://www.supermicro.com/manuals/other/datasheet-AOC-S40G-i1Q_i2Q.pdf

Any ideas ?

Regards Tony

OpenBSD 6.4-current (GENERIC.MP) #658: Fri Feb  1 02:25:34 MST 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 34300891136 (32711MB)
avail mem = 33251758080 (31711MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec170 (34 entries)
bios0: vendor American Megatrends Inc. version "3.0" date 04/24/2015
bios0: Supermicro X10SLD
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT MCFG PRAD HPET SSDT SSDT
SPMI DMAR EINJ ERST HEST BERT
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4)
PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4)
PXSX(S4) RP05(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz, 3500.69 MHz, 06-3c-03
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LO
NG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz, 3500.01 MHz, 06-3c-03
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LO
NG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz, 3500.01 MHz, 06-3c-03
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LO
NG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz, 3500.01 MHz, 06-3c-03
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LO
NG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEG0)
acpiprt2 at acpi0: bus 2 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus 3 (RP01)
acpiprt5 at acpi0: bus -1 (RP02)
acpiprt6 at acpi0: bus -1 (RP03)
acpiprt7 at acpi0: bus -1 (RP04)
acpiprt8 at acpi0: bus -1 (RP05)
acpiprt9 at acpi0: bus -1 (RP06)
acpiprt10 at acpi0: bus -1 (RP07)
acpiprt11 at acpi0: bus -1 (RP08)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
acpicpu2 at acpi0: C1(@1 halt!)
acpicpu3 at acpi0: C1(@1 halt!)
acpipwrres0 at acpi0: PG00, resource for PEG0
acpipwrres1 at acpi0: PG01, resource for PEG1
acpipwrres2 at acpi0: PG02, resource for PEG2
acpipwrres3 at acpi0: FN00, resource for FAN0
acpipwrres4 at acpi0: FN01, resource for FAN1
acpipwrres5 at acpi0: FN02, resource for FAN2
acpipwrres6 at acpi0: FN03, resource for FAN3
acpipwrres7 at acpi0: FN04, resource for FAN4
acpitz0 at 

Re: httpd option max body size is ignored for subdomain

2019-02-03 Thread Robert Paschedag
Am 3. Februar 2019 16:43:20 MEZ schrieb Chris Narkiewicz :
>Hi,
>
>I'm trying to configure Nextcloud on a subdomain. My config has 2
>vhosts and connection max request body is not respected for my
>subdomain.
>
>default vhost:
>
>server "default" {
>listen on * port 80
>
>location "/.well-known/acme-challenge/*" {
>root "/acme"
>request strip 2
>}
>
>location * {
>block return 404
>}
>}
>
>server "default_tls" {
>listen on * tls port 443
>tls certificate ...
>tls key ...
>
># I must place max request body here, but why?
># connection max request body 536870912
>
>location * {
>block return 403
>}
>}
>
>
>nextcloud vhost:
>
>server "nextcloud.mydomain.com" {
>listen on * tls port 443
>...
># this is ignored! It takes setting from "default_tls"!
>connection max request body 536870912
>}
>
>server "nextcloud.mydomain.com" {
>listen on * port 80;
>location "/.well-known/acme-challenge/*" {
>root "/acme"
>request strip 2
>}
>
>block return 301 "https://nextcloud.mydomain.com$REQUEST_URI;
>}
>
>
>When I try PUT a file to nextcloud.mydomain.com, my access.log tells me
>that this request is handled by default_tls:
>
>default_tls xx.xx.xx.xx - - [03/Feb/2019:14:38:35 +] "PUT
>/remote.php/webdav/bigger-file.png HTTP/1.1" 413 0
>
>For smaller files with body <1024k (default body limit) it works ok:
>
>nextcloud.mydomain.com xx.xx.xx.xx - - [03/Feb/2019:14:39:51 +]
>"PUT
>/remote.php/webdav/smaller-file.png HTTP/1.1" 201 0
>
>Why is httpd not specting subdomain config?

I think it's because all your servers are listening on all ip addresses for tls 
and httpd cannot determine the "hostname" of the server you're requesting
So it takes the *first*... The default. Define a IP to listen for nextcloud 
and it should work.

Robert

-- 
sent from my mobile device



Re: httpd option max body size is ignored for subdomain

2019-02-03 Thread Florian Obser
On Sun, Feb 03, 2019 at 03:43:20PM +, Chris Narkiewicz wrote:
> Hi,
> 
> I'm trying to configure Nextcloud on a subdomain. My config has 2
> vhosts and connection max request body is not respected for my subdomain.

this has been fixed in current. Wild guess, you are on 6.4?

This diff should apply cleanly to stable sources:

Index: server_http.c
===
RCS file: /cvs/src/usr.sbin/httpd/server_http.c,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -p -r1.127 -r1.128
--- server_http.c   4 Nov 2018 05:56:45 -   1.127
+++ server_http.c   4 Dec 2018 18:12:08 -   1.128
@@ -198,7 +198,6 @@ void
 server_read_http(struct bufferevent *bev, void *arg)
 {
struct client   *clt = arg;
-   struct server_config*srv_conf = clt->clt_srv_conf;
struct http_descriptor  *desc = clt->clt_descreq;
struct evbuffer *src = EVBUFFER_INPUT(bev);
char*line = NULL, *key, *value;
@@ -357,11 +356,6 @@ server_read_http(struct bufferevent *bev
server_abort_http(clt, 500, errstr);
goto abort;
}
-   if ((size_t)clt->clt_toread >
-   srv_conf->maxrequestbody) {
-   server_abort_http(clt, 413, NULL);
-   goto abort;
-   }
}
 
if (strcasecmp("Transfer-Encoding", key) == 0 &&
@@ -1332,6 +1326,12 @@ server_response(struct httpd *httpd, str
 
/* Now search for the updated location */
srv_conf = server_getlocation(clt, desc->http_path);
+   }
+
+   if (clt->clt_toread > 0 && (size_t)clt->clt_toread >
+   srv_conf->maxrequestbody) {
+   server_abort_http(clt, 413, NULL);
+   return (-1);
}
 
if (srv_conf->flags & SRVFLAG_BLOCK) {


-- 
I'm not entirely sure you are real.



httpd option max body size is ignored for subdomain

2019-02-03 Thread Chris Narkiewicz
Hi,

I'm trying to configure Nextcloud on a subdomain. My config has 2
vhosts and connection max request body is not respected for my subdomain.

default vhost:

server "default" {
listen on * port 80

location "/.well-known/acme-challenge/*" {
root "/acme"
request strip 2
}

location * {
block return 404
}
}

server "default_tls" {
listen on * tls port 443
tls certificate ...
tls key ...

# I must place max request body here, but why?
# connection max request body 536870912

location * {
block return 403
}
}


nextcloud vhost:

server "nextcloud.mydomain.com" {
listen on * tls port 443
...
# this is ignored! It takes setting from "default_tls"!
connection max request body 536870912
}

server "nextcloud.mydomain.com" {
listen on * port 80;
location "/.well-known/acme-challenge/*" {
root "/acme"
request strip 2
}

block return 301 "https://nextcloud.mydomain.com$REQUEST_URI;
}


When I try PUT a file to nextcloud.mydomain.com, my access.log tells me
that this request is handled by default_tls:

default_tls xx.xx.xx.xx - - [03/Feb/2019:14:38:35 +] "PUT
/remote.php/webdav/bigger-file.png HTTP/1.1" 413 0

For smaller files with body <1024k (default body limit) it works ok:

nextcloud.mydomain.com xx.xx.xx.xx - - [03/Feb/2019:14:39:51 +] "PUT
/remote.php/webdav/smaller-file.png HTTP/1.1" 201 0

Why is httpd not specting subdomain config?



signature.asc
Description: OpenPGP digital signature


Re: Modern CPUs AES-NI enabling system wide

2019-02-03 Thread Juan Francisco Cantero Hurtado
On Sun, Feb 03, 2019 at 11:35:52AM +0300, Denis wrote:
> How to enable AES-NI AES system wide hardware acceleration support for
> crypto disciplines like LibreSSL, softraid0 crypto etc?

If your CPU supports AES-NI, the kernel and base software will use it by
default.


-- 
Juan Francisco Cantero Hurtado http://juanfra.info



Re: Modern CPUs AES-NI enabling system wide

2019-02-03 Thread Solene Rapenne
Denis  wrote:
> How to enable AES-NI AES system wide hardware acceleration support for
> crypto disciplines like LibreSSL, softraid0 crypto etc?

Hi, just enable it in bios.



Re: Any experiences with recent single-socket Dell machines (i.e. R230/R330/R340)

2019-02-03 Thread Stuart Henderson
On 2019-02-02, Rachel Roch  wrote:
> Hi,
>
> Subject line says it all really, I'm looking to hear of people's experiences 
> with recent models of Dell single-socket machines (i.e. R230/R330/R340 - 
> especially the newest R340, obviously!).
>
> I'm looking for a decent machine with enterprisey features (i.e. hotswap PSU 
> + drives, high-efficiency power,and high quality ipmi/ilo). I'm not chained 
> to Dell if anyone better ideas, but have had good experience with Dell.
>
> I've contemplated Supermicro machines, but quite frankly what I've read 
> online about the quality of their iLO leaves a lot to be desired (combined 
> with the fact my 'friendly local reseller' tells me their iLO still requires 
> Java).

iLO is HP's name for their range of BMCs, as DRAC/iDRAC are Dell terms.

None of these from any company are things I would put anywhere other
than a separate restricted-access management network. I usually ssh
through a jump host to reach them and don't give them direct internet
access in either direction.

Your 'friendly local reseller' is wrong, current supermicro BMCs have
HTML5 web console, though I usually just configure IPMI serial-over-lan
and access them that way (normally front-ended by conserver running on
the jump host).




Modern CPUs AES-NI enabling system wide

2019-02-03 Thread Denis
How to enable AES-NI AES system wide hardware acceleration support for
crypto disciplines like LibreSSL, softraid0 crypto etc?