Must disable /usr/libexec/security on backup disks
Since /usr/libexec/security runs blindly on every attached storage media, it also runs on mounted tape and backup data volumes. This is stupid.
Re: ThinkPad T14 AMD
> Battery sucks on this laptop though. APM reported about 5.5hrs . Linux gives > me 5-7 and win10 A few more. "Fedora Workstation" on T14 amd draws ~450mW when idle (powertop). There is space for improvement, as disabled audio and wifi, and an unmounted ssd still consume power. Too bad obsd does not have powertop.
Re: ThinkPad T14 AMD
Bios settings may help. I disabled "secure boot" and see post. Immediately after, I see a 1001 error string. Nothing else. Original Message On Aug 24, 2020, 02:41, < s...@skolma.com> wrote: Hi all I have an amd T495 . If the T14 is the 10th gen , mine is the 9th gen. Other than the cpu the differences the remaining hw should be similar. V6.7 installed without issue on the T495 and the normal things worked out the box . Syspatch and firmware applied. Suspend on lid close, audio, and the function buttons. Bluetooth not supported. The finger print scanner was detected on the USB bus but not tested. Wifi was pegged at G speeds. Slow but ok. Perhaps Current would bring some goodies. Battery sucks on this laptop though. APM reported about 5.5hrs . Linux gives me 5-7 and win10 A few more. I think the S variants although slimmer have a slightly larger battery. This is my 1st personal think pad and other than poor inbuilt battery capacity the T series lives up to its famed build quality. Keyboard is nice too. I require Citrix and ms teams so unfortunately I’m running Linux on it . -sub On Mon, Aug 24, 2020 at 8:38 am, Tom Smyth wrote: IT is hard not to like the T Series Build quality ... I have a laptop on my desk here that is working away after multiple falls... the ethernet port is bent on the main board (main board is bent... still works 1G FDX... awesome... On Sun, 23 Aug 2020 at 23:38, Rupert Gallagher wrote: > T14 AMD turned out to be the very best ThinkPad ever produced, as far as > performance is concerned. The R5 cpu is faster than Intel's i7-10, and the > R7 is faster than the i9, both on single core and multi core benchmarks. > The T14 has a dual heat pipe, and its WAN slot can be used as a disk bay. > > The quality of the chassis is that of the T series. > > Original Message > On Aug 23, 2020, 21:24, flint pyrite < flintnpyr...@gmail.com> wrote: > I had an A485 everything worked except wifi, which I replaced with USB > wifi stick. The laptop, however, turned out ot be a lemon. It is in > repair depot as we speak. On of the cpu cores went bad, keys kept > popping off and the synaptics mouse pad would not click and drag. Just > so you know Lenov support is hideous. It has taken over a one (1) > year and still counting to resolve these issues . > WHat are the specs of the T14? Never heard of it. > On Sun, Aug 23, 2020 at 1:06 PM Rupert Gallagher > wrote: > > > > Anybody managed to boot obsd on the T14? I tried, and it does not even > start. By comparison, Debian chokes on a missing network driver, and Fedora > just works. > -- Kindest regards, Tom Smyth.
Re: ThinkPad T14 AMD
T14 AMD turned out to be the very best ThinkPad ever produced, as far as performance is concerned. The R5 cpu is faster than Intel's i7-10, and the R7 is faster than the i9, both on single core and multi core benchmarks. The T14 has a dual heat pipe, and its WAN slot can be used as a disk bay. The quality of the chassis is that of the T series. Original Message On Aug 23, 2020, 21:24, flint pyrite < flintnpyr...@gmail.com> wrote: I had an A485 everything worked except wifi, which I replaced with USB wifi stick. The laptop, however, turned out ot be a lemon. It is in repair depot as we speak. On of the cpu cores went bad, keys kept popping off and the synaptics mouse pad would not click and drag. Just so you know Lenov support is hideous. It has taken over a one (1) year and still counting to resolve these issues . WHat are the specs of the T14? Never heard of it. On Sun, Aug 23, 2020 at 1:06 PM Rupert Gallagher wrote: > > Anybody managed to boot obsd on the T14? I tried, and it does not even start. > By comparison, Debian chokes on a missing network driver, and Fedora just > works.
ThinkPad T14 AMD
Anybody managed to boot obsd on the T14? I tried, and it does not even start. By comparison, Debian chokes on a missing network driver, and Fedora just works.
Re: Tunefs(8)
Ha ha! Original Message On 10 Aug 2020, 23:39, Todd C. Miller < todd.mil...@sudo.ws> wrote: On Mon, 10 Aug 2020 16:05:12 -, Rupert Gallagher wrote: > Omit the last line of the manual, because there is no need for it. It's a play on the old joke: What's the difference between a piano and a fish? You can tune a piano, but you can't tuna fish! No one would dare remove the line in tunefs(8) due to the curse listed in the man page source: .\" Take this out and a Unix Demon will dog your steps from now until .\" the time_t's wrap around. You can tune a file system, but you can't tune a fish. - todd
Tunefs(8)
Omit the last line of the manual, because there is no need for it. Add the units used by the average file size, because of ambiguity. -g avgfilesize This specifies the expected average file size, expressed in bytes??? .
Re: Rsync is too slow
‐‐‐ Original Message ‐‐‐ On Thursday 30 July 2020 22:37, Chris Cappuccio wrote: > Rupert Gallagher [r...@protonmail.com] wrote: > > > No, I am not using USB. > > your dmesg didn't make it to the list because you are attaching a text file > and attachments are not allowed on misc. > > please put it inline with the message. OK OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17125511168 (16332MB) avail mem = 16593870848 (15825MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (34 entries) bios0: vendor American Megatrends Inc. version "1.2" date 11/05/2019 bios0: Supermicro A2SDi-4C-HLN4F acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP FPDT FIDT SPMI MCFG WDAT APIC BDAT HPET UEFI SSDT SSDT SSDT DMAR SPCR HEST BERT ERST EINJ WSMT acpi0: wakeup devices XHC1(S4) OBL1(S4) LAN1(S4) PEX0(S4) LAN2(S4) LAN3(S4) PEX1(S4) PEX6(S4) PEX7(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 1104.90 MHz, 06-5f-01 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 2MB 64b/line 16-way L2 cache cpu0: cannot disable silicon debug cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 25MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE cpu1 at mainbus0: apid 12 (application processor) cpu1: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 1100.10 MHz, 06-5f-01 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 2MB 64b/line 16-way L2 cache cpu1: cannot disable silicon debug cpu1: smt 0, core 6, package 0 cpu2 at mainbus0: apid 16 (application processor) cpu2: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 1100.10 MHz, 06-5f-01 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 2MB 64b/line 16-way L2 cache cpu2: cannot disable silicon debug cpu2: smt 0, core 8, package 0 cpu3 at mainbus0: apid 24 (application processor) cpu3: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 1100.10 MHz, 06-5f-01 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 2MB 64b/line 16-way L2 cache cpu3: cannot disable silicon debug cpu3: smt 0, core 12, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 6 (VRP0) acpiprt2 at acpi0: bus 2 (PEX0) acpiprt3 at acpi0: bus 1 (VRP2) acpiprt4 at acpi0: bus 7 (VRP1) acpiprt5 at acpi0: bus -1 (PEX1) acpiprt6 at acpi0: bus 3 (PEX6) acpiprt7 at acpi0: bus 4 (PEX7) acpiprt8 at acpi0: bus 5 (BR28) acpicpu0 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpicpu1 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpicpu2 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpicpu3 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x "PNP0003" at acpi0 not configured acpicmos0 at acpi0 "IPI0001" at acpi0 not configured "PNP0C33" at acpi0 not configured ipmi at mainbus0 not configured cpu0: Enhanced SpeedStep 1104 MHz: speeds: 2200, 2100, 2000, 1900, 180
Re: Rsync is too slow
‐‐‐ Original Message ‐‐‐ On Thursday 30 July 2020 22:36, Chris Cappuccio wrote: > Rupert Gallagher [r...@protonmail.com] wrote: > > > No, I am not using USB. > > rsync between disks should be very fast. Right. > you are going from the sata to the nvme ? No. It is SATA to SATA, using a M14TQC with a Mini-SAS HD to 4 SATA cable: https://www.supermicro.com/en/products/accessories/mobilerack/CSE-M14TQC.php > it might be interesting to try using cp between filesystems, or tar > > such as: cp -r /usr/bin /mnt/usr/bin > or: tar cf - -C /usr/bin . | tar xpf - -C /mnt/usr/bin > > also what speeds are you getting on the destination filesystem? > > dd count=1 bs=1G if=/dev/zero of=/mnt/test conv=fsync > > might give you some rough idea of what 1G write costs. > > here's 1G write on my Samsung 845DC Pro which is one of my all-time favorite > SATA SSDs for reliability > > dd count=1 bs=1G if=/dev/zero of=test conv=fsync > > = > > 1+0 records in > 1+0 records out > 1073741824 bytes transferred in 2.906 secs (369450372 bytes/sec) > > here's the same for a Crucial M500 > > dd count=1 bs=1G if=/dev/zero of=test conv=fsync > > = > > 1+0 records in > 1+0 records out > 1073741824 bytes transferred in 4.356 secs (246484472 bytes/sec) > > it's not clear to me how much the buffer cache affects this but i'm hoping > here that conv=fsync helps. in a wierd twist, tests like this with conv=fsync > run consistently faster than without, so my understanding isn't that great. Yours are NVMe. I have an SSD on a SATA bus. This is my result: >doas dd count=1 bs=1G if=/dev/zero of=/archive2/test conv=fsync 1+0 records in 1+0 records out 1073741824 bytes transferred in 8.118 secs (132261121 bytes/sec) >grep archive2 /etc/fstab [label].a /archive2 ffs rw,nodev,nosuid,softdep,noatime 1 2 However, 1G is not enough to go past the cache in ram. This is what I do: write test doas /bin/dd if=/dev/zero of=$testfile bs=$(( $bs * 1024 )) count=$count conv=sync read test doas /bin/dd if=$testfile of=/dev/null bs=$(( $bs * 1024 )) conv=sync where $testfile = /archive2/test for example $bs=$(( stat -f "%k" /dev/sd1a )) where sd1a is the device of /archive2 count=$(( $ram / ( $bs * 1024 ) )); # ram expressed in blocks count=$(( $count + 1 )); # exceed ram by 1 block This is the speed test on WDS400T1R0A (WD RED SSD 4TB) Free disk space: 3151013175296 bytes RAM: 17125511168 bytes fs block size : 8192 bytes Size of test file : 17129537536 bytes = 2042 block(s) of 8192K Test file : /archive2/disk-speed-test.raw Writing speed : 182 MB/s Reading speed : 109 MB/s The product brief of WD RED SSD says "560MB/s read" and "530MB/s write". By comparison, this is the speed test on the ST2000NX0403 (Seagate Exos 2TB) Writing speed : 117 MB/s Reading speed : 99 MB/s The product brief of the Exos says "136MB/s" max transfer. Both the exos and the wd red have hardware bytes/sector of 512. This is how I prepared both, with details for the wd red ssd only: > fdisk -iy -g sd1 >echo "/ 1G-* 100%" >/tmp/my_disk_label >disklabel -w -A -T /tmp/my_disk_label sd1 > disklabel -hn sd1 # /dev/rsd1c: type: SCSI disk: SCSI disk label: WDC WDS400T1R0A duid: b8d30be7c118b250 flags: bytes/sector: 512 sectors/track: 255 tracks/cylinder: 511 sectors/cylinder: 130305 cylinders: 59967 total sectors: 7814037168 # total bytes: 3.6T boundstart: 64 boundend: 7814037105 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 3.6T 64 4.2BSD 8192 65536 1 c: 3.6T0 unused > newfs -O2 sd1a /dev/rsd1a: 3815447.8MB in 7814036928 sectors of 512 bytes 1168 cylinder groups of 3266.88MB, 52270 blocks, 104704 inodes each super-block backups (for fsck -b #) at: [omissis] > dumpfs /dev/sd1a | head -19 magic 19540119 (FFS2) timeWed Jul 29 18:41:40 2020 superblock location 65536 id [ 5f21a6c4 bb9dec49 ] ncg 1168size488377308 blocks 484536905 bsize 65536 shift 16 mask0x fsize 8192shift 13 mask0xe000 frag8 shift 3 fsbtodb 4 minfree 5% optim timesymlinklen 120 maxbsize 0 maxbpg 8192maxcontig 1 contigsumsize 0 nbfree 60567111ndir1 nifree 122294269 nffree 16 bpg 52270 fpg 418160 ipg 104704 nindir 8192inopb 256 maxfilesize 36033195603132415 sbsize 8192cgsize 65536 csaddr 3304cssize 24576 sblkno 16 cblkno 24 iblkno 32 dblkno 3304 cgrotor 0 fmod0 ronly 0 c
Re: Rsync is too slow
Attached. OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17125511168 (16332MB) avail mem = 16593870848 (15825MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (34 entries) bios0: vendor American Megatrends Inc. version "1.2" date 11/05/2019 bios0: Supermicro A2SDi-4C-HLN4F acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP FPDT FIDT SPMI MCFG WDAT APIC BDAT HPET UEFI SSDT SSDT SSDT DMAR SPCR HEST BERT ERST EINJ WSMT acpi0: wakeup devices XHC1(S4) OBL1(S4) LAN1(S4) PEX0(S4) LAN2(S4) LAN3(S4) PEX1(S4) PEX6(S4) PEX7(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 1104.90 MHz, 06-5f-01 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 2MB 64b/line 16-way L2 cache cpu0: cannot disable silicon debug cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 25MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE cpu1 at mainbus0: apid 12 (application processor) cpu1: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 1100.10 MHz, 06-5f-01 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 2MB 64b/line 16-way L2 cache cpu1: cannot disable silicon debug cpu1: smt 0, core 6, package 0 cpu2 at mainbus0: apid 16 (application processor) cpu2: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 1100.10 MHz, 06-5f-01 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 2MB 64b/line 16-way L2 cache cpu2: cannot disable silicon debug cpu2: smt 0, core 8, package 0 cpu3 at mainbus0: apid 24 (application processor) cpu3: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 1100.10 MHz, 06-5f-01 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 2MB 64b/line 16-way L2 cache cpu3: cannot disable silicon debug cpu3: smt 0, core 12, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 6 (VRP0) acpiprt2 at acpi0: bus 2 (PEX0) acpiprt3 at acpi0: bus 1 (VRP2) acpiprt4 at acpi0: bus 7 (VRP1) acpiprt5 at acpi0: bus -1 (PEX1) acpiprt6 at acpi0: bus 3 (PEX6) acpiprt7 at acpi0: bus 4 (PEX7) acpiprt8 at acpi0: bus 5 (BR28) acpicpu0 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpicpu1 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpicpu2 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpicpu3 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x "PNP0003" at acpi0 not configured acpicmos0 at acpi0 "IPI0001" at acpi0 not configured "PNP0C33" at acpi0 not configured ipmi at mainbus0 not configured cpu0: Enhanced SpeedStep 1104 MHz: speeds: 2200, 2100, 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800 MHz pci0 at mainbus0 bus 0 0:31:5: mem address conflict 0xfe01/0x1000 pchb0 at pci0 dev 0 function 0 "Intel C3000 Host" rev 0x11 pchb1 at pci0 dev 4 function 0 "Intel C3000 GLREG" rev 0x11 "Intel C3000 RCEC" rev 0x11 at pci0 dev 5 function 0 not configured ppb0 at pci0 dev 6 function 0 "Intel C3000 PCIE" rev 0x11 pci1 at ppb0 bus 1 "Intel C300
Re: Rsync is too slow
No, I am not using USB.
Rsync is too slow
Latest obsd with new 4TB wd red ssd disk copying from 2TB seagate exos returns 80GB in 8 hours with zero activity by other tasks. The server has 12GB ecc ram cache. Copying 1.4 TB from a nas to the same exos took 2.5 hours shy. Is there a problem with how obsd handles internal storage? Or a problem with the default kernel sysconfig and staff defaults?
disklabel: autoalloc failed
Ref. disklabel(8) > The maximum disk and partition size is 64PB. Is that so? Let see... OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 $> doas dmesg | grep sd3 sd3 at scsibus2 targ 2 lun 0: naa.5000c500c3ad5c90 sd3: 4769307MB, 512 bytes/sector, 9767541168 sectors $> doas disklabel -p t sd3 # /dev/rsd3c: type: SCSI disk: SCSI disk label: ST5000LM000-2AN1 duid: [omitted] flags: bytes/sector: 512 sectors/track: 255 tracks/cylinder: 511 sectors/cylinder: 130305 cylinders: 74959 total sectors: 9767541168 # total bytes: 4.5T boundstart: 256 boundend: 4294852800 drivedata: 0 16 partitions: # size offset fstype [fsize bsize cpg] c: 4.5T 0 unused $> doas disklabel -E sd3 sd3> p t OpenBSD area: 256-4294852800; size: 2.0T; free: 2.0T ..^^ :( # size offset fstype [fsize bsize cpg] c: 4.5T 0 unused $> echo "/ 4T" >label $> doas disklabel -w -A -T label sd3 disklabel: autoalloc failed :( $> doas disklabel -E sd3 Label editor (enter '?' for help at any prompt) sd3> p t OpenBSD area: 256-4294852800; size: 2.0T; free: 2.0T #size offset fstype [fsize bsize cpg] c: 4.5T0 unused sd3> a partition: [a] offset: [256] size: [4294852544] FS type: [4.2BSD] sd3*> p t OpenBSD area: 256-4294852800; size: 2.0T; free: 0.0T #size offset fstype [fsize bsize cpg] a: 2.0T 256 4.2BSD 8192 65536 1 c: 4.5T0 unused sd3*> :(
Re: SuperMicro A2SDi-4C-HLN4F
Popescu, obsd does not always work. Hiding the bugs, instead of showing them on git issues or bugzilla, it does not make obsd any better. Sent from ProtonMail Mobile
Re: Atom CPU is clear of L1TF
https://marc.info/?l=openbsd-misc&m=153443566603373&w=2 Sent from ProtonMail Mobile On Sat, Aug 25, 2018 at 22:07, Rupert Gallagher wrote: > The fact that obsd works on your x7-Z8750 says nothing on the fact that it > does not work on my c3558. > > On Sat, Aug 25, 2018 at 15:48, Benjamin Baier wrote: > >> On Sat, 25 Aug 2018 07:10:14 + >> Rupert Gallagher wrote: >> >>> While Intel Core and Xeon are affected by L1TF, Atom CPUs (c3000) are clear >>> of it. Applying the patch to Cores and Xeons basically turns those CPUs >>> into Atoms. It is a shame that the self-appointed "most secure OS" does not >>> run on such processors. >> >> What? Atom X works well, why wouldn't it run on C3000? >> cpu0 at mainbus0: apid 0 (boot processor) >> cpu0: Intel(R) Atom(TM) x7-Z8750 CPU @ 1.60GHz, 1600.36 MHz >> >>> Your faithful troll. >> I see.
Re: SuperMicro A2SDi-4C-HLN4F
wrote: > This vendor addresses hardware & firmware faults like the other enterprise > vendors, they DON'T past year two. BIOS and BMC firmwares are not updated > after this even with the long term lifetime products, you are on your own! On bios and ipmi updates, you can download and apply them yourself. For advanced bios updates, there is a licence you can purchase, as you do with Dell and HP. On warranty, they are in line with the industry standards: https://www.supermicro.com/support/Warranty/ On open source, they work with the community, well enough to have a cetified list of compatible systems: https://www.supermicro.com/support/faqs/os.cfm When you are in business, you do not want to go back to the drawing board each time. You need a platform where to build your own services. If you have to develop disk and keyboard drivers, and you are told off from the support mailing list, then the OS is worth nothing to you. OpenBSD is not ready for enterprise. Your faithfull troll.
Atom CPU is clear of L1TF
While Intel Core and Xeon are affected by L1TF, Atom CPUs (c3000) are clear of it. Applying the patch to Cores and Xeons basically turns those CPUs into Atoms. It is a shame that the self-appointed "most secure OS" does not run on such processors. Your faithful troll.
Re: SuperMicro A2SDi-4C-HLN4F
Troll here... Step out of your nerdiness, and step into the real world with this scenario. A well-known vendor of server boards has an entite product line based on intel atom C3000 cpus. Each product has a list of certified operating systems, including windows, freebsd, red hat linux enterprise, esxi. The list does not include openbsd. You spend a few days testing the server with various oss. It turns out that the server *works* with everything linux, including debian, proxmox, centos. It also turns out that openbsd fails to recognise the devices, including the disks, and the keyboard. Then you post its dmesg, because obsd folks really like it, together with a positive dmesg from centos. Someone intervenes spreading FUD about the server and flaming you are a troll. You know what? Fuck you. Sent from ProtonMail Mobile On Sun, Aug 19, 2018 at 00:06, wrote: > Sat, 18 Aug 2018 12:28:17 +0000 Rupert Gallagher >> I am not complaining about obsd. >> >> I am complaining about your FUD on C3000 and your request for a >> post-installation dmesg. No installation is possible for lack of disk >> drivers. I do not develop/port drivers. The dmesgs I already posted >> are all I can share. >> >> The only way to run obsd at this time is via qemu/proxmox or >> vmware/esxi. > > Rupert, > > You would not have to complain if you hadn't spammed your puny pretences. > The boards and processors have issues to be known, accompanying warnings. > > The dmesg you posted does not help anything. It looks like a poorly done > commercial for other operating systems that "supposedly" work. Only, you > have not been running anything past boot up. Accept it, you are a troll. > > Looks like you point out there are "drivers to be written", for your use. > I call this helpless whining. I told you how you can help this process.. > > Get the boards in the hands of developers with OpenBSD who write drivers. > And first kindly ask about it whether it is possible to fit in busy work. > > Kind regards, > Anton Lazarov > >> On Sat, Aug 18, 2018 at 12:55, wrote: >> >> > Sat, 18 Aug 2018 08:29:33 + Rupert Gallagher >> >> Orher architectures are explicitly known for being bugged, but this >> >> did not stop the developers. >> > >> > Hi Rupert, >> > >> > Enough already, just post a full dmesg when you can. The hardware is not >> > perfect, watch out for unfixed CPU bugs as these are soldered down chips. >> > >> > They also include a lot more than the CPU where most of the problems are. >> > So keep an eye on these boards and be a bit more impartial and objective. >> > >> > It would be so nice if you could ship new boards like these to developers >> > or donate some of your excess hardware costs so that they get the boards. >> > >> > That might be much more helpful than complaints over the installer dmesg. >> > >> > Kind regards, >> > Anton Lazarov >> > >> >> On Fri, Aug 17, 2018 at 22:09, wrote: >> >> >> >> > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher >> >> >> This is a really nice board at a really nice price, and you should >> >> >> stop scaring people off. These Atoms are cleaner than both Cores and >> >> >> Xeons, and AMDs have have their fair share of problems. Citin g >> >> >> C2000 against the latest C3000 is FUD. You should come clean first, >> >> >> and cite a comparable server board at a comparable cost and clear of >> >> >> bugs. >> >> > >> >> > Rupert, >> >> > >> >> > The publication and processor specifications are about the C3000 CPU >> >> > bug. >> >> > Similar hardware flaws affect the new C3000 CPUs, same >> >> > microarchitecture. >> >> > These Atoms are also fully affected by Intel HW flaws Spectre & >> >> > Meltdown. >> >> > >> >> > With NONE real hardware understanding, you have to rely upon vendor >> >> > spec. >> >> > With NONE single dmesg after installation, you can NOT advise this >> >> > board. >> >> > With NONE real OpenBSD experience, you better ask the developers >> >> > instead. >> >> > >> >> > You are speculatively advertising yet unsupported boards as feature >> >> > sets. >> >> > Not interested reading anything that pops in your visibility on the >> >> > list. >> >> > It takes
Re: SuperMicro A2SDi-4C-HLN4F
I am not complaining about obsd. I am complaining about your FUD on C3000 and your request for a post-installation dmesg. No installation is possible for lack of disk drivers. I do not develop/port drivers. The dmesgs I already posted are all I can share. The only way to run obsd at this time is via qemu/proxmox or vmware/esxi. On Sat, Aug 18, 2018 at 12:55, wrote: > Sat, 18 Aug 2018 08:29:33 +0000 Rupert Gallagher >> Orher architectures are explicitly known for being bugged, but this >> did not stop the developers. > > Hi Rupert, > > Enough already, just post a full dmesg when you can. The hardware is not > perfect, watch out for unfixed CPU bugs as these are soldered down chips. > > They also include a lot more than the CPU where most of the problems are. > So keep an eye on these boards and be a bit more impartial and objective. > > It would be so nice if you could ship new boards like these to developers > or donate some of your excess hardware costs so that they get the boards. > > That might be much more helpful than complaints over the installer dmesg. > > Kind regards, > Anton Lazarov > >> On Fri, Aug 17, 2018 at 22:09, wrote: >> >> > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher >> >> This is a really nice board at a really nice price, and you should >> >> stop scaring people off. These Atoms are cleaner than both Cores and >> >> Xeons, and AMDs have have their fair share of problems. Citin g >> >> C2000 against the latest C3000 is FUD. You should come clean first, >> >> and cite a comparable server board at a comparable cost and clear of >> >> bugs. >> > >> > Rupert, >> > >> > The publication and processor specifications are about the C3000 CPU bug. >> > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. >> > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. >> > >> > With NONE real hardware understanding, you have to rely upon vendor spec. >> > With NONE single dmesg after installation, you can NOT advise this board. >> > With NONE real OpenBSD experience, you better ask the developers instead. >> > >> > You are speculatively advertising yet unsupported boards as feature sets. >> > Not interested reading anything that pops in your visibility on the list. >> > It takes very little effort to have some opinion and I do NOT want yours. >> > >> > Kind regards, >> > Anton Lazarov >> > >> >> On Fri, Aug 17, 2018 at 17:38, wrote: >> >> >> >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher >> >> > >> >> >> FUD >> >> >> >> >> >> Sent from total and utter ignorance. >> >> > >> >> > Rupert, >> >> > >> >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD >> >> > kernel. You Should complete an actual OpenBSD installation to get >> >> > the full dmesg. >> >> >> On Fri, Aug 17, 2018 at 12:24, wrote: >> >> >> >> >> >> > Fri, 17 Aug 2018 06:23:23 +0000 Rupert Gallagher >> >> >> > >> >> >> >> Using the serial over lan console, the keyboard keeps working, >> >> >> >> and it is possible to enter the shell. Using the standard >> >> >> >> console, the keyboard does not work. There is plenty of drivers >> >> >> >> that need to be written. No, I do not write/port drivers. >> >> >> >> >> >> >> >> By comparison, both freebsd and centos linux just work out of >> >> >> >> the box. Both dmesgs are attached as reference. >> >> >> >> >> >> >> >> The board is really nice. >> >> >> >> >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher >> >> >> >> wrote: >> >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm >> >> >> > >> >> >> > Hi misc@, >> >> >> > >> >> >> > This one is much quieter, the vendors have reacted to the >> >> >> > previous flaw. As nice as it can get.. before trusting >> >> >> > non-technical reviews, be aware: >> >> >> > >> >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum >> >> >> > https://www.serv
Re: SuperMicro A2SDi-4C-HLN4F
I can pay you with your same currency. You have no experience installing openbsd on a new architecture: > Available disks are: none Your references are not specific to the C3000 architecture. Orher architectures are explicitly known for being bugged, but this did not stop the developers. On Fri, Aug 17, 2018 at 22:09, wrote: > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher >> This is a really nice board at a really nice price, and you should >> stop scaring people off. These Atoms are cleaner than both Cores and >> Xeons, and AMDs have have their fair share of problems. Citin g >> C2000 against the latest C3000 is FUD. You should come clean first, >> and cite a comparable server board at a comparable cost and clear of >> bugs. > > Rupert, > > The publication and processor specifications are about the C3000 CPU bug. > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. > > With NONE real hardware understanding, you have to rely upon vendor spec. > With NONE single dmesg after installation, you can NOT advise this board. > With NONE real OpenBSD experience, you better ask the developers instead. > > You are speculatively advertising yet unsupported boards as feature sets. > Not interested reading anything that pops in your visibility on the list. > It takes very little effort to have some opinion and I do NOT want yours. > > Kind regards, > Anton Lazarov > >> On Fri, Aug 17, 2018 at 17:38, wrote: >> >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher >> > >> >> FUD >> >> >> >> Sent from total and utter ignorance. >> > >> > Rupert, >> > >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD >> > kernel. You Should complete an actual OpenBSD installation to get >> > the full dmesg. >> >> On Fri, Aug 17, 2018 at 12:24, wrote: >> >> >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher >> >> > >> >> >> Using the serial over lan console, the keyboard keeps working, >> >> >> and it is possible to enter the shell. Using the standard >> >> >> console, the keyboard does not work. There is plenty of drivers >> >> >> that need to be written. No, I do not write/port drivers. >> >> >> >> >> >> By comparison, both freebsd and centos linux just work out of >> >> >> the box. Both dmesgs are attached as reference. >> >> >> >> >> >> The board is really nice. >> >> >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher >> >> >> wrote: >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm >> >> > >> >> > Hi misc@, >> >> > >> >> > This one is much quieter, the vendors have reacted to the >> >> > previous flaw. As nice as it can get.. before trusting >> >> > non-technical reviews, be aware: >> >> > >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum >> >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ >> >> > https://www.google.com/search?q=intel+c3000+bug >> >> > >> >> > Recurring issue - similar problems were discussed noisily >> >> > industry wide: >> >> > >> >> > https://en.wikipedia.org/wiki/Silvermont#Erratum >> >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ >> >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ >> >> > https://www.google.com/search?q=intel+c2000+bug >> >> > >> >> > As with the previous generation processors and main boards, >> >> > Intel FAILS. Wait for updated CPU revision boards, consult techs >> >> > and prepare for RMA. >> >> > >> >> > Kind regards, >> >> > Anton Lazarov >> > >> > "Similar to previous Silvermont generation design flaws were found >> > in processor circuitry resulting in cease of operation when >> > processors are actively used for several years. Errata named >> > >> > APL47 System May Experience Inability to Boot or May Cease Operation >> > >> > and >> > >> > APL48 System May Experience Non-functioning GPIO Weak Pull-up >> > Circuitry >> > &
Re: SuperMicro A2SDi-4C-HLN4F
This is a really nice board at a really nice price, and you should stop scaring people off. These Atoms are cleaner than both Cores and Xeons, and AMDs have have their fair share of problems. Citin g C2000 against the latest C3000 is FUD. You should come clean first, and cite a comparable server board at a comparable cost and clear of bugs. On Fri, Aug 17, 2018 at 17:38, wrote: > Fri, 17 Aug 2018 11:15:32 +0000 Rupert Gallagher >> FUD >> >> Sent from total and utter ignorance. > > Rupert, > > Plus the dmesg you posted is by the RAM disk installation OpenBSD kernel. > You Should complete an actual OpenBSD installation to get the full dmesg. > >> On Fri, Aug 17, 2018 at 12:24, wrote: >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher >> >> Using the serial over lan console, the keyboard keeps working, and it is >> >> possible to enter the shell. Using the standard console, the keyboard >> >> does not work. There is plenty of drivers that need to be written. No, I >> >> do not write/port drivers. >> >> >> >> By comparison, both freebsd and centos linux just work out of the box. >> >> Both dmesgs are attached as reference. >> >> >> >> The board is really nice. >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher >> >> wrote: >> >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm >> > >> > Hi misc@, >> > >> > This one is much quieter, the vendors have reacted to the previous flaw. >> > As nice as it can get.. before trusting non-technical reviews, be aware: >> > >> > https://en.wikipedia.org/wiki/Goldmont#Erratum >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ >> > https://www.google.com/search?q=intel+c3000+bug >> > >> > Recurring issue - similar problems were discussed noisily industry wide: >> > >> > https://en.wikipedia.org/wiki/Silvermont#Erratum >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ >> > https://www.google.com/search?q=intel+c2000+bug >> > >> > As with the previous generation processors and main boards, Intel FAILS. >> > Wait for updated CPU revision boards, consult techs and prepare for RMA. >> > >> > Kind regards, >> > Anton Lazarov > > "Similar to previous Silvermont generation design flaws were found in > processor circuitry resulting in cease of operation when processors are > actively used for several years. Errata named > > APL47 System May Experience Inability to Boot or May Cease Operation > > and > > APL48 System May Experience Non-functioning GPIO Weak Pull-up Circuitry > > were added to documentation in June 2017 stating: > > The Low Pin Count (LPC), Real-Time Clock (RTC), Secure Digital (SD) card > and General-Purpose Input/Output (GPIO) interfaces may stop functioning. > > The documents cited in the Wikipedia article, see for current versions.. > that apply to the later CPU stepping models, if any, as time progresses: > > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/atom-c3000-family-spec-update.pdf > > APL47 Problem: Under certain conditions LPC, SD card and RTC circuitry > may stop functioning in the outer years of use. > > APL48 Problem: When platform drives the GPIO pin low, GPIOs programmed > with weak pull-up circuitry may not maintain a value above VIH when not > actively driven in outer years of service." > > Some other "interesting" errata: > > APL23 HD Audio Recording May Experience a Glitch While Opening or > Closing Audio Streams > > APL25 USB Device Controller Incorrectly Interprets U3 Wakeup For Warm > Reset > > APL27 USB 2.0 Timing Responsiveness Degradation > > APL50 System May Unexpectedly Shut Down When Software Requests a Reset > > APL53 Warm Reset May Result in System Hang or Unexpected System > Behaviour > > Keep your eyes open and.. expect some more technical Atom CPU findings.
Re: SuperMicro A2SDi-4C-HLN4F
FUD Sent from ProtonMail Mobile On Fri, Aug 17, 2018 at 12:24, wrote: > Fri, 17 Aug 2018 06:23:23 +0000 Rupert Gallagher >> Using the serial over lan console, the keyboard keeps working, and it is >> possible to enter the shell. Using the standard console, the keyboard does >> not work. There is plenty of drivers that need to be written. No, I do not >> write/port drivers. >> >> By comparison, both freebsd and centos linux just work out of the box. Both >> dmesgs are attached as reference. >> >> The board is really nice. >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher wrote: >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm > > Hi misc@, > > This one is much quieter, the vendors have reacted to the previous flaw. > As nice as it can get.. before trusting non-technical reviews, be aware: > > https://en.wikipedia.org/wiki/Goldmont#Erratum > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ > https://www.google.com/search?q=intel+c3000+bug > > Recurring issue - similar problems were discussed noisily industry wide: > > https://en.wikipedia.org/wiki/Silvermont#Erratum > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ > https://www.google.com/search?q=intel+c2000+bug > > As with the previous generation processors and main boards, Intel FAILS. > Wait for updated CPU revision boards, consult techs and prepare for RMA. > > Kind regards, > Anton Lazarov
Re: SuperMicro A2SDi-4C-HLN4F
Using the serial over lan console, the keyboard keeps working, and it is possible to enter the shell. Using the standard console, the keyboard does not work. There is plenty of drivers that need to be written. No, I do not write/port drivers. By comparison, both freebsd and centos linux just work out of the box. Both dmesgs are attached as reference. The board is really nice. On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher wrote: > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm
SuperMicro A2SDi-4C-HLN4F
https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm # OpenBSD 6.3 on SuperMicro SYS-E200-9A /usr/bin/ssh ADMIN@192.168.1.2 ATEN SMASH-CLP System Management Shell, version 1.05 Copyright (c) 2008-2009 by ATEN International CO., Ltd. All Rights Reserved -> cd /system1/sol1 /system1/sol1 -> start /system1/sol1 press , , and then to terminate session (press the keys in sequence, one after the other) [...] probing: pc0 com0 com1 mem[252K 384K 1894M 120M 136K 5M 14336M] disk: hd0 hd1* hd2* >> OpenBSD/amd64 BOOTX64 3.38 boot> stty com1 115200 boot> set tty com1 switching console to com1 >> OpenBSD/amd64 BOOTX64 3.38 boot> boot /bsd booting hd0a:/bsd: 3418091+1467392+3891704+0+598016=0x8f3280 entry point at 0xf000158 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2018 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.3 (RAMDISK_CD) #98: Sat Mar 24 14:26:39 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 17136254976 (16342MB) avail mem = 16613122048 (15843MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c7000 (34 entries) bios0: vendor American Megatrends Inc. version "1.0b" date 12/12/2017 bios0: Supermicro A2SDi-4C-HLN4F acpi0 at bios0: rev 2, can't enable ACPI cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.40 MHz 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,IBRS,IBPB,STIBP,SENSOR,ARAT cpu0: 2MB 64b/line 16-way L2 cache cpu0: cannot disable silicon debug cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE pci0 at mainbus0 bus 0 0:31:5: mem address conflict 0xfe01/0x1000 pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x1980 rev 0x11 pchb1 at pci0 dev 4 function 0 vendor "Intel", unknown product 0x19a1 rev 0x11 vendor "Intel", unknown product 0x19a2 (class system subclass root complex event, rev 0x11) at pci0 dev 5 function 0 not configured ppb0 at pci0 dev 6 function 0 vendor "Intel", unknown product 0x19a3 rev 0x11 pci1 at ppb0 bus 1 vendor "Intel", unknown product 0x19e2 (class processor subclass Co-processor, rev 0x11) at pci1 dev 0 function 0 not configured ppb1 at pci0 dev 10 function 0 vendor "Intel", unknown product 0x19a5 rev 0x11 pci2 at ppb1 bus 2 ppb2 at pci0 dev 16 function 0 vendor "Intel", unknown product 0x19aa rev 0x11 pci3 at ppb2 bus 3 ppb3 at pci0 dev 17 function 0 vendor "Intel", unknown product 0x19ab rev 0x11 pci4 at ppb3 bus 4 ppb4 at pci4 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03 pci5 at ppb4 bus 5 "ASPEED Technology AST2000" rev 0x30 at pci5 dev 0 function 0 not configured vendor "Intel", unknown product 0x19ac (class system subclass miscellaneous, rev 0x11) at pci0 dev 18 function 0 not configured ahci0 at pci0 dev 19 function 0 vendor "Intel", unknown product 0x19b2 rev 0x11: unable to map interrupt ahci1 at pci0 dev 20 function 0 vendor "Intel", unknown product 0x19c2 rev 0x11: unable to map interrupt xhci0 at pci0 dev 21 function 0 vendor "Intel", unknown product 0x19d0 rev 0x11: couldn't map interrupt ppb5 at pci0 dev 22 function 0 vendor "Intel", unknown product 0x19d1 rev 0x11 pci6 at ppb5 bus 6 vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 0x11) at pci6 dev 0 function 0 not configured vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 0x11) at pci6 dev 0 function 1 not configured ppb6 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x19d2 rev 0x11 pci7 at ppb6 bus 7 vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 0x11) at pci7 dev 0 function 0 not configured vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 0x11) at pci7 dev 0 function 1 not configured vendor "Intel", unknown product 0x19d3 (class communications subclass miscellaneous, rev 0x11) at pci0 dev 24 function 0 not configured vendor "Intel", unknown product 0x19dc (class bridge subclass ISA, rev 0x11) at pci0 dev 31 function 0 not configured vendor "Intel", unknown product 0x19de (class memory subclass miscellaneous, rev 0x11) at pci0 dev 31 function 2 not configured vendor "Intel", unknown product 0x19df (class serial bus subclass SMBus, rev 0x11) at pci0 dev 31 function 4 not configured vendor "Intel", unknown product 0x19e0 (class serial bus unknown subclass 0x80, rev 0x11) at pci0 dev 31 function 5 not configured isa0 at mainbus0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo com1: console efifb0 at mainbus0: 1024x768, 32bpp wsdisplay at efifb0 not conf
Re: sshfs permission problem
When you run anything that writes something, that something will have your umask. If you run something as root, set root's umask before running it, not afterwards. Write a script that sets the umask and runs sshfs, then run the script using doas. On Fri, Aug 10, 2018 at 15:13, Hiltjo Posthuma wrote: > On Fri, Aug 10, 2018 at 10:38:52AM +0200, Hiltjo Posthuma wrote: >> On Fri, Aug 03, 2018 at 01:44:39PM +0200, Rudolf Sykora wrote: >> > Hello! >> > >> > I run >> > >> > doas sshfs syk...@pc109.fzu.cz: /home/ruda/mnt/fzu -o uid=1000 -o gid=1000 >> > >> > But then the mount point is owned (after the mounting) by root: >> > >> > drwx-- 1 root wheel 512 Aug 3 13:22 fzu >> > >> > Hence I cannot enter the directory as the usual (and wanted) user 'ruda'. >> > >> > 1) doas chmod 777 fzu does not help (does nothing) >> > 2) doas chown ruda:ruda fzu gives permission denied >> > >> > What can I do? >> > >> > Thanks >> > Ruda >> > >> >> Hi, >> >> I have the same issue here. >> >> chmod 777 changes the permisions, but seems to reset them automatically >> after a >> second or so. >> >> The umask suggestion doesn't work either unfortunately. >> >> On 6.3 this problem doesn't occur, but on -current it does. I'll try to >> bisect >> it later. >> >> -- >> Kind regards, >> Hiltjo >> > > I figured it out and it doesn't seem like a bug, just a changed behaviour. The > following commit changed it: > > CVS revision 1.47: > http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libfuse/fuse.c?rev=1.47&content-type=text/x-cvsweb-markup > > or git commit: > > commit 0f4d2db5a50672bad418a08041219503c0deeced > Author: helg > Date: Tue Jun 19 13:01:34 2018 + > > Changes the default mount behaviour so only the user that mounts the > file system can access it unless the allow_other mount options is > specified. The allow_other mount option makes the file system > available to other users just like any other mounted file system. > > ok mpi@ > > So the solution is to use the option: -o allow_other, for example: > sshfs -o allow_other user@host:dir /mnt/mount > > I hope this helps someone. > > -- > Kind regards, > Hiltjo
Re: sshfs permission problem
Use umask temporarily. Sent from ProtonMail Mobile On Fri, Aug 3, 2018 at 13:44, Rudolf Sykora wrote: > Hello! > > I run > > doas sshfs syk...@pc109.fzu.cz: /home/ruda/mnt/fzu -o uid=1000 -o gid=1000 > > But then the mount point is owned (after the mounting) by root: > > drwx-- 1 root wheel 512 Aug 3 13:22 fzu > > Hence I cannot enter the directory as the usual (and wanted) user 'ruda'. > > 1) doas chmod 777 fzu does not help (does nothing) > 2) doas chown ruda:ruda fzu gives permission denied > > What can I do? > > Thanks > Ruda
Re: Status of Owncloud?
Nextcloud, a government-funded project to keep your data secure... Hold on to your buts, here it comes. On Sun, Jul 22, 2018 at 19:26, Ax0n wrote: > On Jul 22, 2018 10:11, "Nicolas Schmidt" wrote: > > Hi, > > I just installed and configured owncloud on OpenBSD 6.3, and so far > everything seems to work (except for owncloud complaining about not having > an internet connection). However, when visiting http://localhost/owncloud/ > after installation, I was greeted by an unfriendly message telling me that > owncloud doesn't run properly on OpenBSD. This message didn't go into more > details, nor could I find anything on owncloud.com or openbsd.org regarding > this. > > So I'm wondering, what's the status of owncloud on OpenBSD? Is it still > supported? Are there plans to remove support for it in future releases? > > Best, > Nicolas > > I know this doesn't directly answer your question, but it seems like many > users (especially within but not limited to the OpenBSD community) started > preferring NextCloud ( https://nextcloud.com ) which appears to be > maintained by several of the original OwnCloud developers. > > --ax0n
Re: Employers, Jobs and OpenBSD
You may always apply to the UN: they just require a high-school degree, english and a second language like spanish or french, a first ITIL certificate, working knowledge of windows xp and office, ibm lotus notes (they are big on wasting charity funds on Microsoft and Lotus licenses), and a handful of buzzwords like shell script, python, visualbasic. No, I am not joking. If your cv markets your fascination about the openbsd boyband supersecret, expect nothing in return. On Wed, Jul 18, 2018 at 18:48, Rupert Gallagher wrote: > The name of the game is to select the best candidate, not to hire the average > joe. > > On Mon, Jul 16, 2018 at 05:02, Jacqueline Jolicoeur wrote: > >>> Spot the candidate that is aware of common standards, is brave enough to >>> come forward saying that the test is flowed (we ask to write /var stuff >>> inside /usr), and returns the POSIX-compliant solution, citing the >>> standard. What if they are brave enough to decide to work elsewhere? A >>> place of employment without intentional flaws in interview questions for >>> example.
Re: Employers, Jobs and OpenBSD
The name of the game is to select the best candidate, not to hire the average joe. On Mon, Jul 16, 2018 at 05:02, Jacqueline Jolicoeur wrote: >> Spot the candidate that is aware of common standards, is brave enough to >> come forward saying that the test is flowed (we ask to write /var stuff >> inside /usr), and returns the POSIX-compliant solution, citing the standard. >> What if they are brave enough to decide to work elsewhere? A place of >> employment without intentional flaws in interview questions for example.
Re: Employers, Jobs and OpenBSD
Spot the candidate that is aware of common standards, is brave enough to come forward saying that the test is flowed (we ask to write /var stuff inside /usr), and returns the POSIX-compliant solution, citing the standard. On Sun, Jul 15, 2018 at 18:31, Bodie wrote: > On 15.7.2018 17:12, Rupert Gallagher wrote: > If someone is cocky about a > certain unix-like OS on their CV but is > unable to adhere to the standards > while also using other unix-like > OSs, they are shown the door where they > came from. > > A test example that comes to mind is writing /var content into > /usr. > Many people in this list would not get a job. > What is a purpose of > such test and what is expected to be proved by this operation? Just curious, > nothing more. > On Sat, Jul 14, 2018 at 04:05, Man Hobby wrote: > >> Hi, What > is the opinion of employers about OpenBSD? There is reason >> for to learn > use OpenBSD to find job? If not, why? If there is not >> reason for to learn > use OpenBSD to find job, why use OpenBSD? @gmail.com>
Re: Employers, Jobs and OpenBSD
If someone is cocky about a certain unix-like OS on their CV but is unable to adhere to the standards while also using other unix-like OSs, they are shown the door where they came from. A test example that comes to mind is writing /var content into /usr. Many people in this list would not get a job. On Sat, Jul 14, 2018 at 04:05, Man Hobby wrote: > Hi, What is the opinion of employers about OpenBSD? There is reason for to > learn use OpenBSD to find job? If not, why? If there is not reason for to > learn use OpenBSD to find job, why use OpenBSD?
Re: FAQ: dmesg archive
Addenda http://patchwork.dpdk.org/patch/7639/ On Thu, Jun 28, 2018 at 15:10, Rupert Gallagher wrote: > This is the linux driver. I do not have the board yet, so no dmesgs. > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/phy/marvell.c?h=v4.17.3 > https://github.com/olerem/barebox/blob/master/drivers/net/phy/marvell.c > http://lists.infradead.org/pipermail/barebox/2014-November/021362.html Sent > from ProtonMail Mobile On Tue, Jun 26, 2018 at 20:50, Bryan Vyhmeister wrote: > > Looking at Supermicro's page, it's pretty easy to get some answers. > http://www.supermicro.com/products/system/Mini-ITX/SYS-E300-9A-8CN8.cfm The 4 > gigabit Intel i350-AM4 controllers should work fine since they do on other > systems of the previous C2xxx systems. However, the 4 gigabit Marvell 88E1543 > controllers are unlikely to work as best I can tell. Doing an apropos search > for Marvell does not yield a man page that mentions this chipset. Not much > has happened with msk(4) or sk(4) recently. > https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_msk.c > https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_sk.c So you > probably will not have great support at this time. Something like the E300-8D > might be a better choice. I have been looking at the X10SDV boards > (especially the X10SDV-2C-TP4F and X10SDV-2C-TP8F) personally and will be > building some firewalls with them soon. Bryan @bsdjournal.net>
Re: FAQ: dmesg archive
This is the linux driver. I do not have the board yet, so no dmesgs. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/phy/marvell.c?h=v4.17.3 https://github.com/olerem/barebox/blob/master/drivers/net/phy/marvell.c http://lists.infradead.org/pipermail/barebox/2014-November/021362.html Sent from ProtonMail Mobile On Tue, Jun 26, 2018 at 20:50, Bryan Vyhmeister wrote: > Looking at Supermicro's page, it's pretty easy to get some answers. > http://www.supermicro.com/products/system/Mini-ITX/SYS-E300-9A-8CN8.cfm The 4 > gigabit Intel i350-AM4 controllers should work fine since they do on other > systems of the previous C2xxx systems. However, the 4 gigabit Marvell 88E1543 > controllers are unlikely to work as best I can tell. Doing an apropos search > for Marvell does not yield a man page that mentions this chipset. Not much > has happened with msk(4) or sk(4) recently. > https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_msk.c > https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_sk.c So you > probably will not have great support at this time. Something like the E300-8D > might be a better choice. I have been looking at the X10SDV boards > (especially the X10SDV-2C-TP4F and X10SDV-2C-TP8F) personally and will be > building some firewalls with them soon. Bryan
Re: New laptop recommendations
What crap is this? On Tue, Jun 26, 2018 at 20:53, wrote: > Your other threads on server boards and systems make much more sense now. You are off topic, and have no fucking clue of what you are talking about.
Re: FAQ: dmesg archive
On Tue, Jun 26, 2018 at 17:39, Ryan Freeman wrote: > That is only a RAMDISK kernel. It does not have all devices enabled that the > normal full kernel does. Right, so I will be compiling under ESXi then. http://dmesgd.nycbug.org/index.cgi?do=view&id=3414
Re: FAQ: dmesg archive
Ok new question. I am about to purchase SYS-E300-9A-8CN8, because I cannot wait any longer. Does it work with OpenBSD? Let see... nope! The dmesg database shows little love for SuperMicro in general, and a single hit for a C3000 cpu in particular, with plenty of unrecognised devices: http://dmesgd.nycbug.org/index.cgi?do=view&id=3445 The problem I see with the current database is the absence of collaboration. The owner of that server may have additional information to fill in the obsd gaps, such as a dmesg from freebsd and another one from linux, and another may have links to their open-source drivers, and a third one may actually work at SuperMicro and be willing to help from the inside, but such information is neither available nor asked for... :-( On Tue, Jun 26, 2018 at 15:04, Rupert Gallagher wrote: > Answering to myself... > http://dmesgd.nycbug.org/index.cgi?NAV=dmesgd;SQLIMIT=20 Sent from ProtonMail > Mobile On Tue, Jun 26, 2018 at 14:59, Rupert Gallagher wrote: > There seems > to be a dm...@openbsd.org address where to post such stuff, but I could not > find its archive, nor I could find a searchable database. Do I have to search > harder? @protonmail.com>
Re: FAQ: dmesg archive
Answering to myself... http://dmesgd.nycbug.org/index.cgi?NAV=dmesgd;SQLIMIT=20 Sent from ProtonMail Mobile On Tue, Jun 26, 2018 at 14:59, Rupert Gallagher wrote: > There seems to be a dm...@openbsd.org address where to post such stuff, but I > could not find its archive, nor I could find a searchable database. Do I have > to search harder?
FAQ: dmesg archive
There seems to be a dm...@openbsd.org address where to post such stuff, but I could not find its archive, nor I could find a searchable database. Do I have to search harder?
Re: New laptop recommendations
I looked into all of your comments, and I thank you for it. The coreboot/libreboot way was very tempting, but not competitive pricewise. I no longer have a desktop since the past century, spoiled by three MBPs, and need something robust, light, and performing. I spotted an offer for a new Lenovo T480, i5 series 8, 8GB RAM with an empty slot for easy upgrade, dual storage (!!!) with SSD on m.2 and conventional SATA, dual lithium battery for up to 4 days of work without need to plug the power cord, a 14" display, fingerprint and smartcard reader, and a videocamera. Not happy about the clitmouse, and the meccanical mouse buttons. The best part is the cost: 999€ plus VAT. An MBP with similar specs costs north of 3000€, all soldered in. So long Apple, and hello Lenovo! :-))) On Tue, Jun 19, 2018 at 12:37, Rupert Gallagher wrote: > I'm done with my 10 years old 1200EUR MacBookPro. It served me well, every > day, but is now falling apart, finally. I would buy a new one if only Steve > Jobs would be alive and keeping Apple inspired. The new models are > meticulously designed to make you suffer: expensive, slow cpu, soldered ram, > soldered disk, small disk, bad keyboard keys, wifi only, must pay extra for > standard connectors. I have 1500EUR for a new laptop. What would you buy with > it?
Re: Theo's BOF at BSDcan
On Fri, Jun 22, 2018 at 07:10, Rupert Gallagher wrote: > There is a fact missing from the discussion: state-funded espionage companies > (NSA, Hacking Team, etc) and criminals they both purchase and profit from > bugs. My guess is that OpenBSD does not get first-hand information from Intel > because Intel knows that OpenBSD will patch it as if there is no tomorrow. I mean that there is an ethical problem here. Intel ought to come clean first, make a public statement of intent and and welcome key actors in the industry who have an established reputation of being ethically clean themselves. Until then, nobody can trust Intel. On a technical side, Intel Atom c3000 series have no Hyperthreading. They have a single thread per core. Perhaps they are easier to mantain.
Re: Theo's BOF at BSDcan
There is a fact missing from the discussion: state-funded espionage companies (NSA, Hacking Team, etc) and criminals they both purchase and profit from bugs. My guess is that OpenBSD does not get first-hand information from Intel because Intel knows that OpenBSD will patch it as if there is no tomorrow. @gmail.com>
Re: New laptop recommendations
On Tue, Jun 19, 2018 at 21:16, Scott Bonds wrote: > On 06/19, Jordan Geoghegan wrote: >>Have you considered one of the Librem laptops by Purism? I hear they're quite >>nice, and are running coreboot straight from the factory! > They run OpenBSD fine with some caveats: > https://forums.puri.sm/t/openbsd-on-libre Very good with coreboot, but the cpu is too slow: an i3 of the 8-th generation is cheaper and faster.
New laptop recommendations
I'm done with my 10 years old 1200EUR MacBookPro. It served me well, every day, but is now falling apart, finally. I would buy a new one if only Steve Jobs would be alive and keeping Apple inspired. The new models are meticulously designed to make you suffer: expensive, slow cpu, soldered ram, soldered disk, small disk, bad keyboard keys, wifi only, must pay extra for standard connectors. I have 1500EUR for a new laptop. What would you buy with it?
Re: Fwd: [OT] EU copyright reform
Quoting from [1]: <> Comments: We neved had the freedom to upload (distribute) the property of someone else without explicit licence. We do have the licence to quote, however. Sharing a link is the internet version of citing a publication. However, links are used to point at pirated copies if someone else's property. The new regulation aims at suppressing pirates, not our freedom of expression. Having said this, there is hardly any awareness of the ongoing debate on European media. On Thu, Jun 7, 2018 at 12:41, Craig Skinner wrote: > Begin forwarded message: Date: Wed, 06 Jun 2018 21:03:38 + From: Greg > Sutcliffe via Falkirk To: Falkirk User Group Subject: [Falkirk] EU > copyright reform - links from my talk Last night I gave a quick talk on the > proposed EU Copyright Reform, and the awful state it's in. We *all* need to > care about this - in it's current form it's going to wreck the internet as we > know it, and I don't sling phrases like that about lightly. You can read more > about the issues with the reform on Julia Reda's blog[1] and the Open Rights > Group have a post on it as well[2]. Both contain links to speaking with your > MEP, but I'd suggest hitting up https://www.TheyWorkForYou.com/ and getting > in touch with your MP as well - member states get a say in this as well as > the MEP parties. This is looking like a very tight vote (currently just 1 > vote in favour of it). Let's change that. Thanks Greg [1] > https://juliareda.eu/2018/06/saveyourinternet/ [2] > https://www.openrightsgroup.org/blog/2018/filters-are-for-coffee-and-water-not-copyright > @mailman.lug.org.uk> @mailman.lug.org.uk>
Re: smtpd.conf new grammar
On Thu, May 24, 2018 at 14:18, Gilles Chehade wrote: > In effect, instead of having: > accept from any for local deliver to mbox > > You will have: > action "my_action" mbox > match from any for local action "my_action" It may solve some obscure technical problem, but is a horrible thing to read and write. How about keeping the best of both worlds? Leave the old beautiful PF-like syntax to humans, and translate it into the newEgyptian(tm) on the fly?
Re: Open source RISC-V 64bit w ECC RAM & PCIe this summer
Everybody loves the idea of an open-source CPU that can be uploaded to an FPGA processor. Anybody from China who starts selling a mini-itx board and an FPGA fast enough to run risc-v will turn the market on its head in 6--10 years, killing both Intel and AMD. ARM is fabless already...
Re: Problem with OpenBSD as nfs client
> /home/filip/Documents 192.168.1.1238 1238?
Re: Virtualbox vs latest snapshot
Try qemu. Better software. Better license. Sent from ProtonMail Mobile On Tue, Apr 10, 2018 at 10:50, csszep wrote: > Hi! I installed the latest 04.10 snapshot, the install procedure went fine, > but after reboot the VM stucks at endless boot loop . It prints only the > "booting hda0:/bsd" line.. before reboot The 04.03 snapshot works fine. There > is a similar experience for someone with Virtualbox 5.2.8?
Re: NFS keeps crashing
The following patch from Microsoft seems to restore functionality. Will see in the following hours. The denial of service remains as a problem on mountd. Will get a spare pc asap and check ktrace. https://support.microsoft.com/en-us/help/4088776/windows-10-update-kb4088776
Re: NFS keeps crashing
On Sun, Apr 22, 2018 at 08:32, Otto Moerbeek wrote: > We have gone through this before. Some packages need some libraries that are > distributed as part of the base X install. There is no harm in that. You do > not need to install the server part of X of that makes you feel better. -Otto Bloatware is a luxury I cannot afford on embedded systems with limited resources where every KB and CPU cycle is accounted for. I would rather submit my recipe for a proper samba source configuration and have the maintainer do the compiling of a flavored version, but I already had negative feedback. The maintainer is dogmatic on having an obese package instead of a lean one that delivers the same functionality without the extra fat.
Re: NFS keeps crashing
On Sun, Apr 22, 2018 at 08:17, Otto Moerbeek wrote: > In that case ktracing mountd might help (as well as (packet captures) to see > what is going on. Will get back with the results.
Re: NFS keeps crashing
On Sun, Apr 22, 2018 at 05:27, wrote: > You seem to have some problems understanding feedback, here is some help. > Cut the crap already. How about dmesg first, then proper problem report? > @protonmail.com> @protonmail.com>> Give clear instructions on how to reproduce the problem. Read again, you will find everything you need to reproduce the problem. Since you are a bit slow, here is how to do it. 1. Open up you obsd console. 2. Kill mountd. 3. Run "doas mountd -d" 4. Open up your updated windows 10 5. Mount a NFS share 6. See that mountd -d crashes without warnings or errors Got it? Now you can do your thing.
Re: NFS keeps crashing
On Sat, Apr 21, 2018 at 17:38, IL Ka wrote: > I belive NFS is rarely used nowadays, especially with Windows clients. People > use samba/smb to connect *nix to Windows in most cases. Samba should be > pretty stable because OS X uses it to coexist with MS oses. I use it on osx: it is a crippled version of the original that causes endless problems with file permissions. Rock solid for the rest. I would use samba on obsd, but its package requires x11, believe it or not. I mentioned the problem in misc@ and received insults by someone occlusive and dogmatic, so I will not raise the problem again. I am compiling a proper version, but it will take days on the given hardware...
Re: NFS keeps crashing
On Sat, Apr 21, 2018 at 19:58, Otto Moerbeek wrote: > What do you mean by "the server crashes"? Does the complete OS freeze? Or is > the OS still working apart from NFS? Did one of te NFS related daemons (nfsd, > mountd, portmap) die? I mean that the mountd server crashed. I had "doas mountd -d" up and was reading its output. When it crashed it just returned the shell prompt. No warning, no errors. I have to debug a server in debug mode that does not bother leaving debug information...
Re: NFS keeps crashing
On Sat, Apr 21, 2018 at 18:09, wrote: > Hi Ilya, If it was humble you'd keep it to yourself and not bother > contemplating, or otherwise using the mailing list to think out loud what > need not say. Kind regards, Anton Lazarov Nonsense. Is a Turing award lecture worth publishing? It certainly is. So read this one: "The humble programmer" by Dijksta.
Re: NFS keeps crashing
I mean sponsors who pay for projects and compatibility updates. I also mean broader user base.
Re: NFS keeps crashing
Linux kernel truly is the kernel plus GCC plus GNU c libraries, a monilitic bloatware that requires serious computing power to compile. Clang is a much better compiler, and linux has serious problems with it. Parts of the kernel are written into gcc and c libs. I am currently focused on embedded edge microservers with decent cpu, all built with clang, and I am experimenting with obsd. What I do not like of obsd is the negative energy of its community. We all have a sympatic gene and tend to mirror the social environment. We should be mindful of it, and try to stay positive. Another thing I do not like is the absence of industrial support. I mean, am I the only one on obsd nfs with windows 10 clients? It feels too much pioneering around here...
NFS keeps crashing
This is what I observed on a controlled environment of three "windows 10 pro" 1709 clients. The obsd nfs server had a single share: /path/to/folder -network 192.168.1 -mask 255.255.255.0 When mounting a share for the first time, Windows allows browsing the network to find the resource. This is what happens: 1. The client asks for the list of nfs resources; 2. the server shows a stream of accepted mounts, no warnings, no errors; 3. while 2 happens, the client shows a warning that the server is not responding; 4. when eventually the client returns the list of nfs folders, the server crashes. The above occurs systematically. Restarting the server and repeating the client steps lead to a new server crash. The only way to mount the share is to type in the path, without browsing. When the server crashes, the debug shows no warnings and no errors. The problem did not occur with W10Pro 1703. However, the server should not crash, and if it does, it should report useful diagnostics. R
Re: NFS server down, again, and again, and again...
Update... The command "doas mountd -d" enters debug mode and displays its normal updates as clients mount the share. This is what I observed on a controlled environment of three "windows 10 pro" clients. The server had a single share: /path/to/folder -network 192.168.1 -mask 255.255.255.0 When mounting a share for the first time, Windows allows browsing the network to find the resource. This is what happens: 1. The client asks for the list of nfs resources; 2 the server shows a stream of accepted mounts, no warnings, no errors; 3. while 2 happens, the client shows a warning that the server is not responding; 4. when eventually the client returns the list of nfs folders, the server crashes. The above occurs systematically. Restarting the server and repeating the client steps lead to a new server crash. The only way to mount the share is to type in the path, without browsing. When the server crashes, the debug shows no warnings and no errors. R
Re: NFS server down, again, and again, and again...
On Thu, Apr 19, 2018 at 15:38, Zé Loff wrote: > # mountd -d > /var/log/mountd.log 2&>1 & It is the first thing I did this morning. Unfortunately it does not survive when ssh breaks out. Also, mountd -d is returning the shell prompt again, so I have no logs at all.
Re: NFS server down, again, and again, and again...
On 18 April 2018 8:04 PM, Ryan Freeman wrote: > This is how it works when your system is normal: Unfortunately my system was not "normal", because mountd -d returned the shell prompt, as I said. I also said that mountd_flags=-d prevents the OS from restarting. I had to restart from the serial cable, enter single user mode and clear mountd_flags. This required a field trip, because the server was on a remote location. Now the OS boots again, and mountd -d works as you said. However, this neither solves nor helps with the original problem. I cannot babysit mountd all day, through an ssh link, awaiting for a crash. I need portmap, mountd and nfsd to log into a file, just like other well-behaved servers do. Unfortunately they do not offer server flags to enable debug logs and specify a log file. They just use syslog, but then again, they do not say anything useful when they crash. R
Re: NFS server down, again, and again, and again...
On 18 April 2018 8:04 PM, Ryan Freeman wrote: >> On this point, ``rcctl restart mountd'' works fine. Restarting mountd >> will not harm things already mounted, they will already be handled >> by one of the running nfsd processes. It does not work fine at all. This is what I get: >doas rcctl restart mountd /etc/rc.d/mountd: restart is not supported
Re: NFS server down, again, and again, and again...
This is all I managed to retrieve from the logs (/var/log/daemons, /var/log/messages): Mar 12 09:27:20 server mountd[50607]: Socket disconnected Mar 29 18:05:30 server mountd[52162]: Socket disconnected Apr 16 12:04:07 server mountd[66430]: Socket disconnected Apr 17 17:55:26 server mountd[14081]: Socket disconnected No messages from nfsd and portmap. If the logs are true, then mountd is the daemon that is causing problems. The manual says > -d Enable debugging mode. mountd will not detach from the >controlling terminal and will print debugging messages to stderr. The above option does not work, because it detaches from the terminal: > > doas /sbin/mountd -d > Here we go. I tried "mountd_flags=-d" in rc.conf.local, and rebooted the whole OS, because mountd refuses soft restart. As a result, the OS refuses to boot. System crashed. On 18 April 2018 2:47 AM, IL Ka wrote: > You could use ktrace(1) to trace all calls and then use kdump(1) to read > them, and may help you to find what cause it to die, but it may be tricky for > anyone except nfsd developer.. > You can also try to find person who supports it by looking at last commits to: > https://github.com/openbsd/src/blame/master/sbin/nfsd/nfsd.c > and email this person, but I do not know if it will help, or talk to people > on bugs@ list. > > Or you can move to samba/smbd: SMB must have good support in Windows. > > On Wed, Apr 18, 2018 at 2:53 AM, Rupert Gallagher wrote: > >>> Do you mean nfsd server dies? >> >> I mean the NFS service as delivered by nfsd, portmap and mountd. >> >>> Does it provide core dump? >> >> No! >> >>> You do not need to restart it >> manually: just create script that checks for server existence (like >> ``/etc/rc.d/nfsd check``) and run it if it is dead. >> I usually prepare my servers from source with custom patches and settings. >> When a server dies on me, it makes a lot of noise in the logs, and it >> happens rarely. In 30+ years of activity, I have never restarted a >> production server because of clients using it! >> >> NFS is an exception. I am using the obsd default, and it dies on me under >> load and without logs. It is unreliable.
Re: NFS server down, again, and again, and again...
> Do you mean nfsd server dies? I mean the NFS service as delivered by nfsd, portmap and mountd. > Does it provide core dump? No! > You do not need to restart it manually: just create script that checks for server existence (like ``/etc/rc.d/nfsd check``) and run it if it is dead. I usually prepare my servers from source with custom patches and settings. When a server dies on me, it makes a lot of noise in the logs, and it happens rarely. In 30+ years of activity, I have never restarted a production server because of clients using it! NFS is an exception. I am using the obsd default, and it dies on me under load and without logs. It is unreliable.
NFS server down, again, and again, and again...
The crash usually occurs in the morning, when the 'windows 10 pro' clients are powered up. The obsd nfs server must be restarted manually, and the clients are happy again. No error messages, clear logs, and yet it crashes. A mistery.
Re: OpenBSD 6.3 kernel panic
http://bijanebrahimi.github.io/blog/remote-debugging-the-running-openbsd-kernel.html On Sun, Apr 15, 2018 at 08:02, Mike Larkin wrote: > PS, this bug report leaves a lot to be desired... -ml
Re: 4-ports router under $150
963Mbps On Sun, Apr 8, 2018 at 18:02, Michael Price wrote: > Was it an apu2c4 by any chance? I was thinking about picking one of those up > and was curious as to what kind of packet rates people were seeing with them.
Re: bug tracking system for OpenBSD
Just use github, and be happy.
Re: unbound reload crashes the server
On Thu, Mar 22, 2018 at 22:02, Edgar Pettijohn wrote: > It is chroot'd to /var/unbound so it looks for /etc/unbound.conf from that false root. At least that is my best guess. What is in /etc/rc.conf.local? > I have the following: unbound_flags=-c /var/unbound/etc/unbound.conf > I'm not sure why I specified the config file, but it may well have been because of the same problem you are having. Mine says unbound_flags= because the daemon uses the defaults in /etc/rc.d/unbound. The defaults agree with the manual...
unbound reload crashes the server
This happens on plain 6.1. >ls -l ls -l /var/unbound/etc/unbound.conf -rw-r--r-- 1 root wheel 4309 Mar 21 13:06 /var/unbound/etc/unbound.conf >doas rcctl start unbound unbound(ok) (log) Mar 22 20:29:34 unbound[71209:0] info: server stats for thread 0: 1 queries, 1 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Mar 22 20:29:34 unbound[71209:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0 Mar 22 20:29:43 unbound[82723:0] notice: init module 0: validator Mar 22 20:29:43 unbound[82723:0] notice: init module 1: iterator Mar 22 20:29:43 unbound[82723:0] info: start of service (unbound 1.6.1). >unbound-host -rvD openbsd.org openbsd.org has address 129.128.5.194 (insecure) openbsd.org has no IPv6 address (insecure) openbsd.org mail is handled by 6 shear.ucar.edu. (insecure) [ No DNSSEC for the (self entitled) most secure OS... ] > doas rcctl reload unbound unbound(ok) (log) Mar 22 20:31:00 unbound[97675:0] info: service stopped (unbound 1.6.1). Mar 22 20:31:00 unbound[97675:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Mar 22 20:31:00 unbound[97675:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0 Mar 22 20:31:00 unbound[97675:0] notice: Restart of unbound 1.6.1. Mar 22 20:31:00 unbound[97675:0] fatal error: Could not read config file: /etc/unbound.conf >pgrep unbound [none] So, the unbound server is down, and rcctl above is unaware of it. Why reaching to /etc/unbound.conf when the binary was compiled for /var/unbound/etc/unbound.conf? >man unbound-control | grep /unbound.conf config file /var/unbound/etc/unbound.conf is used. R
Re: OpenBSD and IPMI
I extend the question to Intel ME (similar to IPMI), cloud hosting (direct access to hardware by sysadmins) and virtual machines. I think the answer is default encryption of both disk and ram. On Fri, Mar 9, 2018 at 14:11, Denis wrote: > By reading this article > blog.rapid7.com/2013/07/02/a-penetration-testers-guide-to-ipmi/ my hair > raised. How to OpenBSD security withstands against IPMI holed solution from > top hardware vendors? Best ways to prevent potential risks for OpenBSD over > IPMI? Thanks
Re: Cloud Services and kernel mitigations and OpenBSD cli support
Cloud poses a risk to privacy that you cannot and must not ignore in business. Ignore everyone that says otherwise. --- If you are a fabless company, for example, it is easy for a cloud sysadmin to exploit the latest vulnerabilities to read your data bank and sell your secrets. Email (yahoo, hotmail, gmail, you name it) is another example of cloud service: sysadmins do not need to exploit anything, because the contents are stored in plain text. --- If you need a cloud, you better make your own. Sent from ProtonMail Mobile On Thu, Mar 8, 2018 at 11:51, Kevin Chadwick wrote: > We all know Bare metal is more secure (ignoring physical security) especially > with OpenBSD but if you need cost effective global resources on tap then I > believe you need cloud. We all know microsoft have a huge user base and > userland issues that are problematic however despite some recent Linux kernel > mitigation adoption attemps, Linux focus on kernel mitigations have been > lacklustre whilst microsoft have been comparatively active albeit enabling > and enforcing mitigations (even ASLR) for all applications by default has > been lacklustre. As cloud services are free from microsofts userland it is a > *hopeful* assumption that their security mitigation works applies to their > cloud too whereas I expect it is unlikely with Amazon and Google (AFAIK > Android fairs better than Linux for mitigations due to Google however??) > Perhaps OpenBSD mitigations still apply effectively to ec2 instances and > cloud services isolation is good enough to never undermine this, though I > find that hard to believe. Perhaps new processor developments will solve this > issue. None of this matters if you cannot get things done. I know there is > OpenBSD AWS client availability but I am unsure about Azure, Google etc. Any > advice and experience is welcome, Thankyou.
Re: Supermicro SuperServer E200-9A
Here is my take away of the day: avoid reading from Anton, because he jumped to conclusions about the C3000 series after his narrow experience with an Atom D525. Note on the side: the C3000 introduced a patch to the known C2000 bug. R
Re: Supermicro SuperServer E200-9A
I did not purchase the board, yet. The OP did. And he did well. Both Linux and FreeBSD run on it. ‐‐‐ Original Message ‐‐‐ On 27 February 2018 4:22 PM, Charlie Eddy wrote: > Rupert, I strongly suggest you actively search as quickly as possible as > Stuart suggested, or return your product. Not the first time this has > happened so don't take it personally.
Re: Supermicro SuperServer E200-9A
Note on passing: the C2000 are officially retired and discontinued. Sent from ProtonMail Mobile On Mon, Feb 26, 2018 at 23:21, Stuart Henderson wrote: > On 2018-02-26, OpenBSD user wrote: > Hello > > I want to build a OpenBSD > firewall. And I have bought a Supermicro > SuperServer E200-9A. There is > installed a A2SDi-4C-HLN4F motherboard in it. > > I'm trying to installed > OpenBSD 6.2 on it, but I have some problems. > > First I tried to boot it > from an usb stick and thought I could use the > installed keyboard to control > the installation. But under the boot > process and before I could type "i" > for install, it had turned the > keyboard off. > > Then I tried to control > the installation from the IPMI port. I can > control the installation through > it, but when I'm went to configure the > NIC's there is only a VLAN > installed. Beside the IPMI port there is also > 4 other NIC's installed on > the motherboard. And I can't see them. I type > "done" but when the > installation come to the installed hdd, there is > none to choose between. > > > I have visit the manufacturer site, but there isn't any drivers to any > *BSD. > > I have googled for other who have problems, but I can't find any > solutions. > > How do I installed OpenBSD 6.2 on the E200-9A ? > > Please > help. > > Thanks in advance > > This machine has a lot of rather new hardware > in (C3000 Denverton) and is really not at all supported yet. I found a dmesg > from RAMDISK_CD on one of these and it's full of failure starting with being > unable to enable acpi (so interrupt routing and other things aren't working), > plus we haven't even got skeleton pcidevs entries for most of the devices > (ahci, nic, etc). Realistically, at the moment, I'd say the best chances of > getting this machine supported are if you can get similar hardware in the > hands of a developer if there is anyone with interest, skills and time to > look into it, remote debugging of a system in this state is going to be slow > and painful.. OpenBSD 6.2-current (RAMDISK_CD) #379: Wed Jan 24 12:58:41 MST > 2018 dera...@amd64.openbsd.org:/usr/src/sys/al mem = 4250882048 (4053MB) > avail mem = 4118294528 (3927MB) mainbus0 at root bios0 at mainbus0: SMBIOS > rev. 3.0 @ 0x7f0c7000 (31 entries) bios0: vendor American Megatrends Inc. > version "1.0" date 08/02/2017 bios0: Supermicro Super Server acpi0 at bios0: > rev 2, can't enable ACPI cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) > Atom(TM) CPU C3338 @ 1.50: > 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT > cpu0: 2MB 64b/line 16-way L2 cache cpu0: cannot disable silicon debug cpu0: > mwait min=64, max=64, C-substates=0.2.0.2, IBE pci0 at mainbus0 bus 0 0:31:5: > mem address conflict 0xfe01/0x1000 pchb0 at pci0 dev 0 function 0 vendor > "Intel", unknown product 0x1980 rev 0x11 pchb1 at pci0 dev 4 function 0 > vendor "Intel", unknown product 0x19a1 rev 0x11 vendor "Intel", unknown > product 0x19a2 (class system subclass root complex event, rev 0x11) at pci0 > dev 5 function 0 not configured ppb0 at pci0 dev 10 function 0 vendor > "Intel", unknown product 0x19a5 rev 0x11 pci1 at ppb0 bus 1 ppb1 at pci0 dev > 17 function 0 vendor "Intel", unknown product 0x19ab rev 0x11 pci2 at ppb1 > bus 2 ppb2 at pci2 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03 > pci3 at ppb2 bus 3 "ASPEED Technology AST2000" rev 0x30 at pci3 dev 0 > function 0 not configured vendor "Intel", unknown product 0x19ac (class > system subclass miscellaneous, rev 0x11) at pci0 dev 18 function 0 not > configured ahci0 at pci0 dev 19 function 0 vendor "Intel", unknown product > 0x19b2 rev 0x11: unable to map interrupt ahci1 at pci0 dev 20 function 0 > vendor "Intel", unknown product 0x19c2 rev 0x11: unable to map interrupt > xhci0 at pci0 dev 21 function 0 vendor "Intel", unknown product 0x19d0 rev > 0x11: couldn't map interrupt ppb3 at pci0 dev 22 function 0 vendor "Intel", > unknown product 0x19d1 rev 0x11 pci4 at ppb3 bus 4 vendor "Intel", unknown > product 0x15e5 (class network subclass ethernet, rev 0x11) at pci4 dev 0 > function 0 not configured vendor "Intel", unknown product 0x15e5 (class > network subclass ethernet, rev 0x11) at pci4 dev 0 function 1 not configured > ppb4 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x19d2 rev > 0x11 pci5 at ppb4 bus 5 vendor "Intel", unknown product 0x15e5 (class network > subclass ethernet, rev 0x11) at pci5 dev 0 function 0 not configured vendor > "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 0x11) > at pci5 dev 0 function 1 not configured vendor "Intel", unknown product > 0x19d3 (class communicatio
Re: Supermicro SuperServer E200-9A
Not new at all. https://www.servethehome.com/intel-atom-c3338-benchmarks-why-denverton-is-so-sweet/ https://www.servethehome.com/intel-atom-c3558-linux-benchmarks-and-review/ https://www.servethehome.com/intel-atom-c3958-16-core-top-end-embedded-qat-linux-benchmarks-and-review/ Sent from ProtonMail Mobile On Mon, Feb 26, 2018 at 23:21, Stuart Henderson wrote: > On 2018-02-26, OpenBSD user wrote: > Hello > > I want to build a OpenBSD > firewall. And I have bought a Supermicro > SuperServer E200-9A. There is > installed a A2SDi-4C-HLN4F motherboard in it. > > I'm trying to installed > OpenBSD 6.2 on it, but I have some problems. > > First I tried to boot it > from an usb stick and thought I could use the > installed keyboard to control > the installation. But under the boot > process and before I could type "i" > for install, it had turned the > keyboard off. > > Then I tried to control > the installation from the IPMI port. I can > control the installation through > it, but when I'm went to configure the > NIC's there is only a VLAN > installed. Beside the IPMI port there is also > 4 other NIC's installed on > the motherboard. And I can't see them. I type > "done" but when the > installation come to the installed hdd, there is > none to choose between. > > > I have visit the manufacturer site, but there isn't any drivers to any > *BSD. > > I have googled for other who have problems, but I can't find any > solutions. > > How do I installed OpenBSD 6.2 on the E200-9A ? > > Please > help. > > Thanks in advance > > This machine has a lot of rather new hardware > in (C3000 Denverton) and is really not at all supported yet. I found a dmesg > from RAMDISK_CD on one of these and it's full of failure starting with being > unable to enable acpi (so interrupt routing and other things aren't working), > plus we haven't even got skeleton pcidevs entries for most of the devices > (ahci, nic, etc). Realistically, at the moment, I'd say the best chances of > getting this machine supported are if you can get similar hardware in the > hands of a developer if there is anyone with interest, skills and time to > look into it, remote debugging of a system in this state is going to be slow > and painful.. OpenBSD 6.2-current (RAMDISK_CD) #379: Wed Jan 24 12:58:41 MST > 2018 dera...@amd64.openbsd.org:/usr/src/sys/al mem = 4250882048 (4053MB) > avail mem = 4118294528 (3927MB) mainbus0 at root bios0 at mainbus0: SMBIOS > rev. 3.0 @ 0x7f0c7000 (31 entries) bios0: vendor American Megatrends Inc. > version "1.0" date 08/02/2017 bios0: Supermicro Super Server acpi0 at bios0: > rev 2, can't enable ACPI cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) > Atom(TM) CPU C3338 @ 1.50: > 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT > cpu0: 2MB 64b/line 16-way L2 cache cpu0: cannot disable silicon debug cpu0: > mwait min=64, max=64, C-substates=0.2.0.2, IBE pci0 at mainbus0 bus 0 0:31:5: > mem address conflict 0xfe01/0x1000 pchb0 at pci0 dev 0 function 0 vendor > "Intel", unknown product 0x1980 rev 0x11 pchb1 at pci0 dev 4 function 0 > vendor "Intel", unknown product 0x19a1 rev 0x11 vendor "Intel", unknown > product 0x19a2 (class system subclass root complex event, rev 0x11) at pci0 > dev 5 function 0 not configured ppb0 at pci0 dev 10 function 0 vendor > "Intel", unknown product 0x19a5 rev 0x11 pci1 at ppb0 bus 1 ppb1 at pci0 dev > 17 function 0 vendor "Intel", unknown product 0x19ab rev 0x11 pci2 at ppb1 > bus 2 ppb2 at pci2 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03 > pci3 at ppb2 bus 3 "ASPEED Technology AST2000" rev 0x30 at pci3 dev 0 > function 0 not configured vendor "Intel", unknown product 0x19ac (class > system subclass miscellaneous, rev 0x11) at pci0 dev 18 function 0 not > configured ahci0 at pci0 dev 19 function 0 vendor "Intel", unknown product > 0x19b2 rev 0x11: unable to map interrupt ahci1 at pci0 dev 20 function 0 > vendor "Intel", unknown product 0x19c2 rev 0x11: unable to map interrupt > xhci0 at pci0 dev 21 function 0 vendor "Intel", unknown product 0x19d0 rev > 0x11: couldn't map interrupt ppb3 at pci0 dev 22 function 0 vendor "Intel", > unknown product 0x19d1 rev 0x11 pci4 at ppb3 bus 4 vendor "Intel", unknown > product 0x15e5 (class network subclass ethernet, rev 0x11) at pci4 dev 0 > function 0 not configured vendor "Intel", unknown product 0x15e5 (class > network subclass ethernet, rev 0x11) at pci4 dev 0 function 1 not configured > ppb4 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x19d2 rev > 0x11 pci5 at ppb4 bus 5 vendor "Intel", unknown product 0x15e5 (class network > subclass ethernet, rev 0x11) at pci5 dev 0 fu
Re: Sharing files between OpenBSD, Linux, and Windows boxes
We used SMB locally: the server was on macos, the clients on macos, windows and linux. The problem with file permissions on macos had solution in the windows registry, but windows had a mind of its own and kept changing itself. A robust solution was to move the server to linux and enforce file permissions in samba. OpenBSD does not speak SMB fluently. We deprecated the protocol and sealed its ports for security reasons. We still use NFS: the servers are on OpenBSD, the clients are on Windows 10 Pro, MacOS and GNU/Linux. Every box talks NFS. The protocol and the implementations are not bullet-proof. OpenBSD's NFS suffered from DoS a few years ago, and we have a problem right now that smells DoS to us. We need something that does not require resetting servers in the middle of the night. We also need something that works on WAN. We have iSCSI in the pipeline. Sent from ProtonMail Mobile On Thu, Feb 15, 2018 at 00:03, Martin Hanson wrote: > How do you share files between OpenBSD, Linux, and Windows boxes? Currently I > have a setup in which I mount Samba shares that are being served from Linux > boxes and mounted on Linux boxes using cifs and on Windows boxes. This works > very well and it's both easy to administer and it's very fast. I would like > to use OpenBSD for more that just firewalling and I would like to replace > several Linux desktops with OpenBSD. However, every time I try to set this up > I run into some kind of trouble. NFS isn't a solution as file permissions is > a mess between several different OS'es with different accounts. Samba works > really great between Linux and Windows, but mounting Samba shares on OpenBSD? > I remember sharity-light, but it isn't in the ports any longer and isn't > maintained. How do you manage file sharing between these systems (if it all)? > Also, is it possible to decrypt and mount a Linux harddrive that has been > encrypted with LUKS? Many thanks in advance! Kind regards
Re: Windows clients crashing nfs server?
Hello Tom, All relevant ports are already open on the clients. This morning all clients failed to mount the shares. Resetting the software servers solved the problem. The logs are quiet. Sent from ProtonMail Mobile On Wed, Feb 14, 2018 at 19:07, Tom Smyth wrote: > Hello Rupert, I might hazard a guess that you open up Windows Firewall with > advanced security in windows pro 10 and allow the entire dynamic range of > ports that the port mapper might divert the client to, or simply allow all > traffic to / from the NFS server on the windows clients (just to test) I have > seen issues with Windows Firewall and some updates ( on windows services that > use RPC extensively such as MS SQL / SQL Browser) if your windows 10 > environments are controlled by active directory you may have to set the > windows firewall settings in Group Policy (any more than this and im > wandering dangerously off OpenBSD Topic ) :) I hope this helps Thanks On 14 > February 2018 at 15:52, Rupert Gallagher wrote: > This is a recurring problem > that is proving hard to fix. When windows 10 pro clients run their security > updates and the client restarts, they are unable to reconnect to the nfs > server. There is nothing wrong with the network, however, and the nfs servers > are up as usual. The only thing that recovers functionality is to stop and > restart portmap mountd and nfsd. Am I the only one with this problem? > > > Sent from ProtonMail Mobile -- Kindest regards, Tom Smyth Mobile: +353 87 > 6193172 The information contained in this E-mail is intended only for the > confidential use of the named recipient. If the reader of this message is not > the intended recipient or the person responsible for delivering it to the > recipient, you are hereby notified that you have received this communication > in error and that any review, dissemination or copying of this communication > is strictly prohibited. If you have received this in error, please notify the > sender immediately by telephone at the number above and erase the message You > are requested to carry out your own virus check before opening any > attachment. @protonmail.com>
Windows clients crashing nfs server?
This is a recurring problem that is proving hard to fix. When windows 10 pro clients run their security updates and the client restarts, they are unable to reconnect to the nfs server. There is nothing wrong with the network, however, and the nfs servers are up as usual. The only thing that recovers functionality is to stop and restart portmap mountd and nfsd. Am I the only one with this problem? Sent from ProtonMail Mobile
Re: Syn flood crashed my LAN
From my seat, he learned that his configuration of PF lacks SYN flooding protection. He also learned that he needs a managed switch: cisco SF and SG series are affordable and deliver ddos protection. Sent from ProtonMail Mobile On Mon, Feb 12, 2018 at 07:22, Bruno Flueckiger wrote: > On 12.02.18 01:26, Martin Hanson wrote: > Hi, > > I have a home network that > is segmented into 3 different zones using a NIC with 4 ports sitting on an > OpenBSD firewall/dhcp server. One port is connected to the Internet (ISP > router) and each of the three others has a D-Link DGS-1005D switch connected > to each. > > So.. > > LAN1 = 192.168.1.0 > LAN2 = 192.168.2.0 > LAN3 = > 192.168.3.0 > > Learning more about networking I wanted to test a SYN flood > so I set up a couple of boxes on LAN1 and LAN3 to flood a box on LAN2. I used > "hping3" with the "S" and "flood" options. > > Running a regular ping in a > terminal I could see how the response time decreased and eventually the box > began to loose packages. > > However after a while it seemed like the entire > internal network went down. > > No box on any LAN could get an IP address > from the DHCP server on the OpenBSD box. > > I eventually rebooted the > OpenBSD box, but that didn't immediately help, and only after powering down > the switches and powering the switches on again, everything worked again. > > > I have been looking through the PF documentation to see if PF somehow blocks > SYN flooding, but I am not using synproxy on any rules. > > What could cause > such a "melt down" of the entire network because of a SYN flood to a box? > > > I suspect that the D-Link switches are pretty bad and maybe are the cause of > the problem? > > I eventually will try again to see if I can determine what's > causing the "melt down", but I want to know if anyone perhaps has experienced > similar results during some testing? > > Many thanks in advance. > > Kind > regards, > > Martin You run a denial of service attack against your home > network. As a result your network denials service. Sounds like you have > proven that syn flooding is an effective denial of service attack in your > network. Yes, your switches cannot handle the amount of traffic you putting > on them. No, your switches are not the problem. Your syn flooding of the > network is causing the problem. Cheers, Bruno -- I really hope this whole > thing works, I won't be able to test everything beforehand
Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" is more data-safe and fast?
The only problem I've encountered is rsync unable to preserve the original time of files: copied files have the time of the copy. Sent from ProtonMail Mobile On Sat, Feb 10, 2018 at 01:50, wrote: >> From tom.sm...@wirelessconnect.eu Thu Feb 8 23:37:59 2018 > From: Tom Smyth >> > Date: Thu, 8 Feb 2018 19:40:23 + > Subject: Re: For a FFS on an SSD, >> which of "-o" nil, "sync" &/ "softdep" is > more data-safe and fast? > To: >> Tinker > > Also use noatime mount option so whe reading files you are not >> updating > access time But then don't complain when your favorite software >> package either doesn't work or does unexpected things. Martin >> @protonmail.ch> @wirelessconnect.eu>
Re: Kernel panic with openbsd 6.2
esxi 5.5.0 dates back to 2013. obsd runs better on qemu nowadays. To avoid the mess with x86/amd64, perhaps qemu-sparc with obsd-sparc will serve you better. Sent from ProtonMail Mobile On Fri, Jan 19, 2018 at 21:50, Mik J wrote: > Hello, I had many kernel panic these past days. This is a 6.2 openbsd VM > running on esxi 5.5
Re: Kernel memory leaking on Intel CPUs?
Yes! They are also working on risc-v. Sent from ProtonMail Mobile On Fri, Jan 5, 2018 at 19:50, ropers wrote: > On 4 January 2018 at 09:13, Rupert Gallagher wrote: > >> The Chinese have an interesting project on RISC, who is taking ages to hit >> the market. > > Is that https://www.openbsd.org/loongson.html or are you referring to > something else?
Re: Kernel memory leaking on Intel CPUs?
http://www.mcst.ru/ On Sat, Jan 6, 2018 at 08:05, Jordan Geoghegan wrote: > They make their own via the /Moscow Center of SPARC Technologies./ Check out > the Elbrus architecture, its pretty clever. It can run native SPARC binaries > and also has a fairly efficient x86 compatibility layer built into the > hardware. The way they achieve bi-endian capability is pretty neat, in > addition to their aggressively large (20+) instructions per cycle when > running native Elbrus code compiled with their VLIW support. @gmail.com> > @gmail.com>
Re: Kernel memory leaking on Intel CPUs?
Yes, it is open hardware. No, it is not COTS, unfortunately. Low cost is due to high volume, and SPARC is hard to find. On Fri, Jan 5, 2018 at 06:36, SJP Lists wrote: > SPARC architecture is open to others to develop their own CPU designs. The > Russians are not forced to buy SPARC from Oracle. @gmail.com> @protonmail.com>
Re: Kernel memory leaking on Intel CPUs?
The answer is: genuine FUD. The news is hitting the media with more emphasis than a North Corean nuclear test, the uncertainty is due to yet another hardware feature that was implemented by Intel to steal secrets across different OSs, and the doubt of whether OBSD will pass this new test. On Fri, Jan 5, 2018 at 01:58, torsten wrote: > What surprises me is the "panic" publication of this because of already known > and in *BSDs addressed concerns about hyper threatening and shared memory > well back since 1994
Re: Kernel memory leaking on Intel CPUs?
https://mobile.twitter.com/misc0110/status/948706387491786752 On Thu, Jan 4, 2018 at 16:49, Daniel Wilkins wrote: > Intel's said that it affects every processor in the last 20+ years and that > it's "not a big deal for most users" because it's only a kernel memory > *read*. @yahoo.com.br>
Re: Kernel memory leaking on Intel CPUs?
The Intel flop hits the US .mil as well, because they depend on COTS Xeons. I pity the Russians. I wonder if they pay through the nose for Oracle's power hungry hardware, or make it cheaper and power efficient of their own. On Thu, Jan 4, 2018 at 18:28, Jordan Geoghegan wrote: > The Russians heavily use SPARC for aerospace/military applications as well as > their in house domestic-use-only Elbrus machines, for what I imagine to be > reasons precisely like this. @mail.com>
Re: Kernel memory leaking on Intel CPUs?
Everybody is reading about it, including people like me that have formerly underestimated the problem... mea culpa The question is, can we have a kernel free of patches for spynet cpus? The Russians are moving to ARM-based cpus, anthough ARM is subject to UK-style Orwellian spynet law. The Chinese have an interesting project on RISC, who is taking ages to hit the market. Sent from ProtonMail Mobile On Wed, Jan 3, 2018 at 13:19, who one wrote: >Did anyone hear about this?
Re: adsuck
You will be happier by simply feeding the blacklist to unbound.
Re: adsuck
The last update is 5 years old, and its blacklists are obsolete. https://github.com/conformal/adsuck/tree/master/files Sent from ProtonMail Mobile On Thu, Dec 28, 2017 at 22:51, Stefan Wollny wrote: > Hi there! I have this little machine which serves as (squid-)proxy for my > local net. $ dmesg | grep Open OpenBSD 6.2-current (GENERIC.MP) #311: Wed Dec > 27 21:49:49 MST 2017 Basically everything is fine - except responses are kind > of slow. So I had the idea to not use squid to filter for unwanted sites but > use adsuck. I followed the advice in > /usr/local/share/doc/pkg-readmes/adsuck-2.5.0p4 which now reads: $ cat > /etc/dhclient.conf send host-name ; script "/usr/local/sbin/dhclient-adsuck"; > I had to use chflags with 'schg' to make shure that /etc/resolv.conf only > contains one line (neither 'supersede' nor 'prepend' in dhclient.conf did the > job): $ cat /etc/resolv.conf nameserver 127.0.0.1 And YES: adsuck is > activated via /etc/rc.conf.local (actually it is the very first one after > 'pkg_scripts='). It is up and running: $ top | grep adsuck 72573 _adsuck 2 0 > 2260K 4704K idle kqread 0:00 0.00% adsuck Now: If I run 'sh /etc/netstart' on > the console or an xterm I see the following: $ doas sh /etc/netstart em1: > /etc/dhclient.conf line 2: expecting statement. em1: script em1: ^ em1: > DHCPREQUEST to 255.255.255.255 em1: DHCPACK from a.b.c.d (aa:bb:cc:dd:ee:ff) > em1: bound to a.b.d.e -- renewal in 432000 seconds I am kind of stuck: What > might I have been doing wrong here??? Some kind soul around to give me a > clue? THX in advance! Best, STEFAN
Re: openbsd code coverage
Fuck you x9p anonymous coward. Sent from ProtonMail Mobile On Sat, Dec 9, 2017 at 23:02, x9p wrote: > On Sat, December 9, 2017 3:33 pm, Anders Andersson wrote: > On Sat, Dec 9, > 2017 at 12:46 PM, Rupert Gallagher > wrote: >> Code Coverage? > > Type that > into google instead, maybe you will get a better answer. > > Indeed > redirecting @protonmail.com to /dev/null provides a much more pleasant misc@- > reading experience, as suggested before. Just saw this email bcz of citation. > cheers. x9p @protonmail.com>
Re: openbsd code coverage
The meaningful term is "test coverage", where "test" is the name of a test. To make sense, you must say what you are testing AND how you are testing it. If you say "code coverage", you are just saying that you did not bother reading the papers, and you are just using a group of words without any meaning. Sent from ProtonMail Mobile On Sat, Dec 9, 2017 at 18:33, Anders Andersson wrote: > On Sat, Dec 9, 2017 at 12:46 PM, Rupert Gallagher wrote: > Code Coverage? > Type that into google instead, maybe you will get a better answer. > @protonmail.com>
Re: openbsd code coverage
Code Coverage? Sent from ProtonMail Mobile On Sat, Dec 9, 2017 at 12:32, Sergey Bronnikov wrote: > Hi, I'm working on measuring OpenBSD code coverage. The process still has > drawbacks, but some results are already available. > https://ligurio.github.io/openbsd-tests/6.2/coverage.html Sergey
Re: TRIM on SSD
https://store.steoil.com/mineral-oil-pc-kit/ Sent from ProtonMail Mobile On Fri, Dec 8, 2017 at 18:42, Rupert Gallagher wrote: > They still need air, and you give it to them. We sub the server on liquid... > Sent from ProtonMail Mobile On Fri, Dec 8, 2017 at 14:09, Kevin Chadwick > wrote: > On Fri, 08 Dec 2017 07:26:09 -0500 > I think you mean those round > things with moving heads in a chassis > with a breathing hole. No, they are > not resilient to our environment. I doubt that, we used to put them in police > cars and they were fine. We did get special ones at three times the price and > mount them specially though. Also if they do fail you are almost guaranteed > to be *able* to get the data back which is less true of s...@gmail.com>
Re: TRIM on SSD
They still need air, and you give it to them. We sub the server on liquid... Sent from ProtonMail Mobile On Fri, Dec 8, 2017 at 14:09, Kevin Chadwick wrote: > On Fri, 08 Dec 2017 07:26:09 -0500 > I think you mean those round things with > moving heads in a chassis > with a breathing hole. No, they are not resilient > to our environment. I doubt that, we used to put them in police cars and they > were fine. We did get special ones at three times the price and mount them > specially though. Also if they do fail you are almost guaranteed to be *able* > to get the data back which is less true of SSD.
Re: TRIM on SSD
I think you mean those round things with moving heads in a chassis with a breathing hole. No, they are not resilient to our environment. Sent from ProtonMail Mobile On Fri, Dec 8, 2017 at 12:03, Kevin Chadwick wrote: > On Fri, 08 Dec 2017 03:07:14 -0500 > - UFS2 on FreeBSD supports TRIM. > - > OpenBSD supports UFS2. > > Is anybody using UFS2 with TRIM on OpenBSD? Have > you considered using a high speed HDD or RAID. From the little information > given, your performance requirements don't seem to be that high?
Re: TRIM on SSD
- UFS2 on FreeBSD supports TRIM. - OpenBSD supports UFS2. Is anybody using UFS2 with TRIM on OpenBSD? Sent from ProtonMail Mobile On Tue, Dec 5, 2017 at 08:26, Rupert Gallagher wrote: > A production obsd is serving 50GB worth of NFS shares and hourly backups on > two ssds since August, and is still going strong at 550MBps over measured > 550--950Mbps LAN links. The same boots and runs the OS from a pSLC SD with > Phison controller. The ssds have a 5year warrantee, and we are doing our best > to stay within specs. The only concern is the lack of TRIM on the SD and the > NFS ssd. With TRIM, the os keeps writing on free space instead of deleting > and overwriting, for faster writing and uniform wearing of disk. Can we > safely enable TRIM on 6.2 now? Sent from ProtonMail Mobile
Re: TRIM on SSD
Support of TRIM by ... NetBSD, since 2012 Dragonfly BSD, since 2011 FreeBSD, since 2010 Linux, since 2008 OpenBSD, no. Why? Because no. But why? Because no. Just no. We like to say no. No, no, no. Ha ha, no! Rise funds and do it! No. But why? Because no. Sent from ProtonMail Mobile On Tue, Dec 5, 2017 at 08:26, Rupert Gallagher wrote: > A production obsd is serving 50GB worth of NFS shares and hourly backups on > two ssds since August, and is still going strong at 550MBps over measured > 550--950Mbps LAN links. The same boots and runs the OS from a pSLC SD with > Phison controller. The ssds have a 5year warrantee, and we are doing our best > to stay within specs. The only concern is the lack of TRIM on the SD and the > NFS ssd. With TRIM, the os keeps writing on free space instead of deleting > and overwriting, for faster writing and uniform wearing of disk. > > Can we safely enable TRIM on 6.2 now? > > Sent from ProtonMail Mobile
Re: TRIM on SSD
I know well that article, because it is several years old with no updates. Those working on ffs should do what they are supposed to do. Lack of money? Setup a stickers sale or a kickstarter, get the money and just fucking do it. Sent from ProtonMail Mobile On Wed, Dec 6, 2017 at 00:25, Mike Burns wrote: > On 2017-12-05 17.26.27 -0500, Rupert Gallagher wrote: > Sent from ProtonMail > Mobile When you implement the patch that adds TRIM you might want to build > off the work already done and lessons learned. I only spent a few seconds > searching so you might find more: > https://www.tedunangst.com/flak/post/lessons-learned-about-TRIM > https://marc.info/?l=openbsd-misc&m=144738028409142&w=2 > https://marc.info/?l=openbsd-misc&m=143453951901714&w=2 > https://marc.info/?l=openbsd-misc&m=148908000202884&w=2