Re: No longer able to mount NFS shares
The nfs server isn't running Linux, is it? Try adding -o tcp as a mount option On April 4, 2022 5:54:22 PM EDT, Aric Gregson wrote: >Hello, > >I have several NFS mount points shared on my local network from a >FreeNAS server running version 11.1-U7. My OBSD client computer is >running 7.0 GENERIC#224 amd64. > >For the past year or so it has been very slow to connect to the NFS >server, so slow in fact that I use the '-b' option to fork to the >background and stopped trying to mount at boot. About six months ago I >moved our home network to an Ubiquiti set-up. Since then my OBSD client >is even slower to connect. I have Macs running different levels of Mac >OS that, while now take up to 15s to connect, all do connect. Also, a >Raspberry Pi 4 server can connect quickly to the same shares. > >Once connected, writes are fast and I do not lose connection. > >For the last 48h I have not been able to connect from the OBSD client >at all. I have restarted the server to no effect. All other clients on >the network can connect to the NFS shares. > >Example of what happens with the command: > >doas mount_nfs -T -i -b 192.168.1.21:/mnt/XFree/backups/share >/share > >mount_nfs: bad MNT RPC: RPC: Timed out > >Any suggestions would be greatly appreciated. > >Thanks, Aric >
Re: Used Cores / Threads CPU E3-1230 V2
On 4/5/22 6:29 PM, Heiko wrote: Hello List, I use a Xeon(R) CPU E3-1230 V2 on bios0: Supermicro X9SCL/X9SCM This is a 4 Core 8 Threads cpu. In dmesg, cpu0 to cpu7 are displayed as follows: cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz, 3300.47 MHz, 06-3a-09 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR, ... MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu at mainbus0: not configured Now I'm a bit confused about the views in top and htop. top shows me cpu0 to cpu3. htop shows me 1 to 8, but 5 to 8 is shown as "offline" It is (uname -a): OpenBSD user@host 7.1 GENERIC.MP#461 amd64 and some kernels before. Now my question, in "top" only the physical cores are displayed. In "htop" all that are also shown in dmesg. But why are the cpu4 to cpu8 displayed as "offline". Is really only cpu0 to cpu3 used and not cpu4 to cpu7, how can I interpret that correctly? Thank you for the clarification in advance. /Heiko It is my understanding that HT/SMT is disabled in OpenBSD by default. A web search about that should give you more info.
Re: RISC-V board to buy
On 2022-04-05, Martin wrote: > Hi list, > > Can anybody know where to buy SiFive HiFive Unmatched (preferred) or > Microsemi PolarFire SoC Icicle Kit to run 7.1 on RISC-V architecture? Can't > find it in stock anywhere. Farnell have some of the Microsemi boards.
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
19.10.2021 10:14, kasak пишет: 18.10.2021 23:18, kasak пишет: Hello everyone! I have one mini router, made from gigabyte GB-SBCAP4200 barebone It has nothing special. Just base openbsd, without any additional packages and modifications. for some reason, sysupgrade does not upgrade this system. It successfully boot new kernel, but do not process the upgrade, Just load 6.9 back. This is dmesg from loading 7.0 and further: OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 8415617024 (8025MB) avail mem = 8156545024 (7778MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 bios0: Gigabyte Technology Co., Ltd. Default string acpi0 at bios0: ACPI 6.0 acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09 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,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 1MB 64b/line 16-way L2 cache cpu0: apic clock running at 19MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus 1 (RP03) acpiprt4 at acpi0: bus 2 (RP04) acpiprt5 at acpi0: bus 3 (RP05) acpiprt6 at acpi0: bus 4 (RP06) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "PNP0C0C" at acpi0 not configured aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins "INT33A1" at acpi0 not configured "MSFT0101" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu at acpi0 not configured acpipwrres at acpi0 not configured acpitz at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not configured "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI 1.3.1 ahci0: PHY offline on port 0 ahci0: port 1: 6.0Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 1 lun 0: naa.50026b7783a249ed sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi pci3 at ppb2 bus 3 re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:4f rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi pci4 at ppb3 bus 4 re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:51 rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0 xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI 1.0 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured isa0 at mainbus0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 efifb at mainbus0 not configured softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: CHECK AND RESET THE DATE! OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021 r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8415617024 (8025MB) avail mem = 8145182720 (7767MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1"
Re: OpenBSD-7.1beta aarch64 on RPI4 black screen after "Booting sd0a:"
try a...@openbsd.org list and do some reading first
Re: BOGUS behavior on 6.9 Spark vs. 6.9 amd64
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 5 Apr 2022 13:59:17 +0200 Janne Johansson wrote: > Den tis 5 apr. 2022 kl 13:46 skrev Duncan Patton a Campbell > : > > I have 6.9 installed on an amd64 and a sparc64. On the amd tar/gzip etc. > > work as > > always, producing .gz files that can be uncompressed with gunzip. > > > > But on the sparc64, things go sideways. Instead of calling the gzip it is > > invoking xz (which is a bogon of another era). Why is this? How can > > I return the sparc to normal behavior? > > I suggest checking the PATH and "which gzip" to see if the sparc is > calling out to a non-system binary when you run "gzip". Yup. Thanks. It was picking up xz I had in /root/bin ... Dhu > > -- > May the most significant bit of your life be positive. > > -- Je suis Canadien. Ce n'est pas Francais ou Anglaise. C'est une esp`ece de sauvage: ne obliviscaris, vix ea nostra voco;-) -BEGIN PGP SIGNATURE- iQIcBAEBAgAGBQJiTDqPAAoJEI6Vun3D6YUPRbkQAKn4uqfxduimZKnmxOVHa/Cj S3IqhBrvmqRuFtdPKftmR7dIyVqp7tSpVZXCDwsH1vPmJ1TJAjsuo1FQmcehCHy/ ByBMdwYLGQui+3yLxUjgJIRvCen0JHZGZhOY3J6MtGIz5Wyh1DlmvUjH8EQpkjVd wRfD79DjA2Xo8mXUKfnF+ZZbTE55sKdfyNVgsOcz5q8DMVeQBKHbLPm0/IAspKak 8aJ8oiq3G9Sng49PEnRG/H5PSshj1FvYxKp6UWKNaN7UZ6E7sh0Pfpwn7JNnLZMf PAKwc6EskU6U7S/mX0AbVSUL7Kw50oPl/hvCBQSbQiPAs4RKjHnsDhQOmBtHCnJz g1N7V11xsnuAnyEu7QtcxcO38wRlsrxKd+q9gEU1m43UNTLkf+pS4DZOD3LIJF6C 70vFGsRDIWujuxx7G/h3aTS7YYgP6AwYOu0r46Ux145uleRAo1g/J6zOQXArLnXX zmLEjfB4j5JV5Fih0rK6dtAqG8Hj4E7JFSzFDV1+8Sig+f/mJR2dcICPHLn4wyL7 xQREzs42NDqRGwgm5kOBVYrG1cv9fO+nIUX37gOF3dbP2w9nb4we0+xK9detCW0n Ft9/b0MOgd6h6XMBzMxKWUrVVaW09j/1g5d6DZ8BCPbJ29JcWSK/qsz6I2nRNZh2 JA9TFzMOpqwUmjm1g1Ss =8l5R -END PGP SIGNATURE-
Re: BOGUS behavior on 6.9 Spark vs. 6.9 amd64
Den tis 5 apr. 2022 kl 13:46 skrev Duncan Patton a Campbell : > I have 6.9 installed on an amd64 and a sparc64. On the amd tar/gzip etc. > work as > always, producing .gz files that can be uncompressed with gunzip. > > But on the sparc64, things go sideways. Instead of calling the gzip it is > invoking xz (which is a bogon of another era). Why is this? How can > I return the sparc to normal behavior? I suggest checking the PATH and "which gzip" to see if the sparc is calling out to a non-system binary when you run "gzip". -- May the most significant bit of your life be positive.
BOGUS behavior on 6.9 Spark vs. 6.9 amd64
Howdy All? I have 6.9 installed on an amd64 and a sparc64. On the amd tar/gzip etc. work as always, producing .gz files that can be uncompressed with gunzip. But on the sparc64, things go sideways. Instead of calling the gzip it is invoking xz (which is a bogon of another era). Why is this? How can I return the sparc to normal behavior? RSVP Thanks, Dhu sparc: babayaga# uname -a OpenBSD babayaga.neotext.ca 6.9 GENERIC#0 sparc64 babayaga# sha256 atest.tar SHA256 (atest.tar) = 539f8782dbb4728bbe0da9e8b09fd486fc3c3640b049fc061907f666a15bc9ff babayaga# gzip atest.tar babayaga# l atest.* -rw-r--r-- 1 root wheel 274136 Apr 5 04:17 atest.tar.xz babayaga# gunzip atest.* gunzip: atest.tar.xz: File already has `.xz' suffix, skipping amd64: atlas:/tmp# uname -a OpenBSD atlas.indx.ca 6.9 GENERIC.MP#3 amd64 atlas:/tmp# sha256 atest.tar SHA256 (atest.tar) = 539f8782dbb4728bbe0da9e8b09fd486fc3c3640b049fc061907f666a15bc9ff atlas:/tmp# gzip atest.tar atlas:/tmp# l atest.* -rw-r--r-- 1 root wheel 277213 Apr 5 04:18 atest.tar.gz atlas:/tmp# gunzip atest.tar.gz atlas:/tmp# l atest.* -rw-r--r-- 1 root wheel 430080 Apr 5 04:18 atest.tar atlas:/tmp# sha256 atest.tar SHA256 (atest.tar) = 539f8782dbb4728bbe0da9e8b09fd486fc3c3640b049fc061907f666a15bc9ff -- Je suis Canadien. Ce n'est pas Francais ou Anglaise. C'est une esp`ece de sauvage: ne obliviscaris, vix ea nostra voco;-)
Re: OpenBSD-7.1beta EM7455 with default ports config detects as umb0 without AT ports
On 2022-04-05, Martin wrote: > Hi list, > > Just connected EM7455 modem (factory default port configuration with MBIM + > AT port + NMEA port + DM port) to a machine with latest 7.1beta snapshot. > > The modem detected as umb0, but no AT port or NMEA port detected at all. > > How did developers implement any alternative mechanism to access AT command > port and NMEA port to obtain GPS data from modem? OpenBSD doesn't have a way to do that. You may be able to get at them if you run a kernel with umb disabled. -- Please keep replies on the mailing list.
Re: OpenBSD benchmarks
On 2022-04-04, Nicolas Goy wrote: > Hello, > > I'd like to make some 10gbit/s benchmarks for an OpenBSD based router. > > I was wondering if there was some "standard" pf ruleset I could use to > have a meaningful metric. It might be useful to have PF disabled, and PF enabled with a simple "pass" rule. More than that and it's likely to be more dependent on the actual traffic and ruleset so probably not so useful unless you are trying to hand optimize the ruleset to squeeze as much performance as possible out of a system. Make sure you do measure routing performance (packet source and sink on different machines) and not local stack performance (tcpbench/iperf/whatever on the machine itself). If you publish them somewhere please do include dmesg and description of the test setup. > Also, I'm curious if anymody is aware of such existing benchmarks. http://bluhm.genua.de/perform/results/perform.html (repeated tests over time showing some effects of changes in the kernel; the FORWARD and FORWARD6 graphs are probably what you're interested in here) https://undeadly.org/cgi?action=article;sid=20220319123157 (pps tests with a diff that is not yet committed) https://undeadly.org/cgi?action=article=20160302155046 (older but some suggestions of software that can be useful for testing) -- Please keep replies on the mailing list.
Re: How to track system changes?
Den tis 5 apr. 2022 kl 03:20 skrev Eric Thomas : > Very valuable insights. That’s a great idea. > The rysnc script was ksh/bash or cron? Ideally I’d like to use Python to > tackle something like this but I’m not against learning shell. Sounds a lot like rsnapshot (available in ports), the end result should be the same on the remote, and there you can look for changed entries. > > Something I came up with which worked out really well at my employer was > > a backup system that used rsync and the --link-dest option to make a useful -- May the most significant bit of your life be positive.
