Re: KVM Q35 Virtual Machines , SR-IOV PCI-E Bridges and OpenBSD jitter on attached network
Hello, I tried SR-IOV and intel I350 1Gb/s nic hardware being passed through to OpenBSD 6.6 amd64 the intel i350 passed through as a physical function on PCI-E is detected as an em(4) nic and these dont suffer from the same jitter as the IXL(4) or the AVF(4) drivers so i'm thinking there is something different in the way that em(4) interacts with the SRIOV Bridge vs the ixl(4) avf(4) interacting wih the same SRIOV Bridge later this week some hardware with ix(4) type 10G nics will come available and I will try with them .. On Mon, 4 Nov 2019 at 01:04, Tom Smyth wrote: > > Hello, > Has anyone seen jitter from 0.5ms to 500ms > on PCI-E attached (SR-IOV) Physical function / virtual function > Network interfaces on OpenBSD Machines running on > a KVM Virtual machine type (Q35) ? > > any tips for diagnosing what is causing the jitter ? > I have ruled out the driver Ixl by comparing physical / bare metal > performance vs > performance when the physical function of the nic is passed through > to the KVM Q35 guest > > I have also ruled out the hypervisor as centos Guest VMs running with > the same hardware don't suffer from the jitter issue > > > > -- > Kindest regards, > Tom Smyth. -- Kindest regards, Tom Smyth.
Re: ttyC0 floods with error messages
On 12-16 10:48, Raymond, David wrote: > I get similar stuff on console 1 but not on the others on all my > OpenBSD machines. As I use X windows and have clean consoles 2-4 > available if necessary, I just ignore it. I get similar messages in dmesg (used to be on the first console), and every couple of days or so (not a consistent period), the mouse just stops working, sometimes working again a few days after I unplug it, so I switch that way between a wireless and wired mouse until they both stop and when I get tired enough of being mouseless then I reboot. Ending message with dmesg output: OpenBSD 6.5 (GENERIC.MP) #5: Thu Aug 29 20:38:30 CEST 2019 r...@syspatch-65-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16033533952 (15290MB) avail mem = 15537967104 (14818MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebf90 (49 entries) bios0: vendor American Megatrends Inc. version "204" date 11/20/2014 bios0: ASUSTeK COMPUTER INC. X550ZA acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ECDT MCFG MSDM HPET UEFI SSDT SSDT CRAT SSDT SSDT SSDT SSDT acpi0: wakeup devices LOM_(S4) SBAZ(S4) ECIR(S4) OHC1(S4) EHC1(S4) OHC2(S4) EHC2(S4) OHC3(S4) EHC3(S4) OHC4(S4) XHC0(S4) XHC1(S4) ODD8(S3) GLAN(S4) LID_(S5) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2496.48 MHz, 15-30-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu0: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.34 MHz, 15-30-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu1: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.34 MHz, 15-30-01 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu2: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.34 MHz, 15-30-01 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu3: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu3: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu3: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 1 pa 0xfec01000, version 21, 32 pins acpiec0 at acpi0 acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PB21) acpiprt2 at acpi0: bus -1 (PB22) acpiprt3 at acpi0: bus
Re: Third server now locked up after reboot due to no keyboard attached
On Sun, Dec 15, 2019 at 12:28 PM Nick Holland wrote: > > Well...yeah. > If the boot loader echoed anything, it's behaving As Desired -- a char at > the command line means "STOP ALL BOOTING, I have something special I want > you to do". > > [...] > However, I think there are a few things you might be able to do to solve > your problem... > > 1) BIOS upgrade. Long shot, but maybe? > 2) BIOS config option? Also a long shot, but since I'd call this a > boot firmware bug, maybe some combination of USB related options would > fix this? Always a good idea. If you have console redirection configured in the BIOS, make sure redirection after boot is *disabled*, and configure the serial console in the bootloader instead. I've seen garbage characters produced by the BIOS console on some systems, but the OS and bootloader usually work better. > 3) a boot.conf file should fix -- simply putting "boot" in /etc/boot.conf > should override anything in the keyboard buffer. Need to "control" the > boot? plug in a keyboard and hold down either CTRL key, and you will be > given the boot> prompt. Note that this is not yet implemented in the UEFI bootloader: https://github.com/openbsd/src/blob/43e343f8aa17502e68dbb74fa3dd463280c74fe5/sys/arch/amd64/stand/efi64/efiboot.c#L514-L519 (Compare pc_getshifts() in .../libsa/bioscons.c, which calls BIOS interrupts. Anyone know the UEFI equivalent?) -Andrew
mkdir(2) set errno to EISDIR instead of EEXIST?
Hello misc,
Background: I'm running OpenBSD i386 6.6 stable:
$ uname -mrsv
OpenBSD 6.6 GENERIC.MP#3 i386
I've found that mkdir("/", mode) sets errno to EISDIR. Is this intended?
By reading the manpage I expected mkdir(2) to fail with EEXIST.
I know it's a bit silly to mkdir /, but I found this while porting a
program that tried to recursively create directories. (The actual bug
was a bit more convoluted: mkdir("/", mode) was called because false
assumptions on how dirname(3) behaves, but that's another story.)
I tried grepping the kernel code, but I'm not familiar at all with the
internals, so I don't have a clear idea of where that EISDIR is generated
(is it from vfs_lookup?)
Re: ttyC0 floods with error messages
USB subsystem bugs. Whoever said it was your mouse or cable is being an inaccurate jerk. Raymond, David wrote: > I get similar stuff on console 1 but not on the others on all my > OpenBSD machines. As I use X windows and have clean consoles 2-4 > available if necessary, I just ignore it. > > Dave Raymond > > > On 12/16/19, putridsou...@gmail.com wrote: > > The error does not seem to be a faulty mouse and I > > don't use a KVM switch anyway so it is not the source. > > Following on pervious reply, I tried on a new mouse. > > But was greeted with the same error: > > > > wsmouse0 detached > > ums0 detached > > uhidev0 detached > > uhidev0 at uhub0 port 4 configuration 1 interface 0 "PixArt USB Optical > > Mouse" rev 2.00/1.00 addr 2 > > uhidev0: iclass 3/1 > > ums0 at uhidev0: 3 buttons, Z dir > > wsmouse0 at ums0 mux 0 > > > > Unless I'm the unfortunate person destined to own all faulty > > mice in the world, I look forward to a solution. Is there > > anyone here who uses a desktop setup with a mouse, not greeted > > with these pesky errors. Are experts on here sure this is not > > a bug, or lack of proper driver. More info on the latter, this > > test consisted of Logitech M90 and Dell MS111-P mouse. > > > > > > > -- > David J. Raymond > david.raym...@nmt.edu > http://physics.nmt.edu/~raymond >
Re: ttyC0 floods with error messages
I get similar stuff on console 1 but not on the others on all my OpenBSD machines. As I use X windows and have clean consoles 2-4 available if necessary, I just ignore it. Dave Raymond On 12/16/19, putridsou...@gmail.com wrote: > The error does not seem to be a faulty mouse and I > don't use a KVM switch anyway so it is not the source. > Following on pervious reply, I tried on a new mouse. > But was greeted with the same error: > > wsmouse0 detached > ums0 detached > uhidev0 detached > uhidev0 at uhub0 port 4 configuration 1 interface 0 "PixArt USB Optical > Mouse" rev 2.00/1.00 addr 2 > uhidev0: iclass 3/1 > ums0 at uhidev0: 3 buttons, Z dir > wsmouse0 at ums0 mux 0 > > Unless I'm the unfortunate person destined to own all faulty > mice in the world, I look forward to a solution. Is there > anyone here who uses a desktop setup with a mouse, not greeted > with these pesky errors. Are experts on here sure this is not > a bug, or lack of proper driver. More info on the latter, this > test consisted of Logitech M90 and Dell MS111-P mouse. > > -- David J. Raymond david.raym...@nmt.edu http://physics.nmt.edu/~raymond
Re: ttyC0 floods with error messages
The error does not seem to be a faulty mouse and I don't use a KVM switch anyway so it is not the source. Following on pervious reply, I tried on a new mouse. But was greeted with the same error: wsmouse0 detached ums0 detached uhidev0 detached uhidev0 at uhub0 port 4 configuration 1 interface 0 "PixArt USB Optical Mouse" rev 2.00/1.00 addr 2 uhidev0: iclass 3/1 ums0 at uhidev0: 3 buttons, Z dir wsmouse0 at ums0 mux 0 Unless I'm the unfortunate person destined to own all faulty mice in the world, I look forward to a solution. Is there anyone here who uses a desktop setup with a mouse, not greeted with these pesky errors. Are experts on here sure this is not a bug, or lack of proper driver. More info on the latter, this test consisted of Logitech M90 and Dell MS111-P mouse.
Re: cvs checkout of src,ports and xenocara gives duplicate key msg
On Mon, Dec 16, 2019 at 10:55:17AM +0530, putridsou...@gmail.com wrote: > Currently I'm running the -stable OPENBSD-6.6 > I want to set up the ports repository so > I followed the faqs to set up a /usr/ports partition, > changed the group to wsrc and file modes to 775. > Then I added my local user to wsrc group. > After changing directory to /usr, I hit the following > command > > cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs checkout \ > -rOPENBSD_6_6 -P ports > > The output; > cvs server: duplicate key found for 'y' > U ports/.cvsignore > U ports/Makefile > ..and then the normal output followed. Based on cvs code inspection it looks like the CVSROOT/val-tags file is broken on the server. I can reproduce this with a reposync'd CVS repository, too. The last line in that file looks suspect. It contains no tag name: $ tail CVSROOT/val-tags mesa-19_0_5 y mesa-19_0_8 y LLVM_8_0_0 y LLVM_8_0_1 y UNBOUND_1_9_3 y OPENBSD_6_6 y OPENBSD_6_6_BASE y libdrm_2_4_100 y kn y y $
Re: route an IPv4 /32 to a different interface
On Sun, Dec 15, 2019 at 08:57:48PM +0100, Denis Fondras wrote: > Hi, > > I have this setup : > > em3: flags=8843 mtu 1500 > lladdr > index 4 priority 0 llprio 3 > media: Ethernet autoselect (1000baseSX full-duplex) > status: active > inet6 fe80::aa9:b803:8a7a:ca72%em3 prefixlen 64 scopeid 0x4 > inet 172.16.0.254 netmask 0xff00 broadcast 172.16.0.255 > em4: flags=8843 mtu 1500 > lladdr > index 5 priority 0 llprio 3 > media: Ethernet autoselect (1000baseSX full-duplex) > status: active > inet 172.16.0.249 netmask 0xfffc broadcast 172.16.0.251 > inet6 fe80::29ae:98d:f238:fd68%em4 prefixlen 64 scopeid 0x5 > > I have a computer with IPv4 address 172.16.0.248 connected to em3. > When I try to ping it, obviously it goes to em4. > > How can I route 172.16.0.248 through em3 ? > > I tried with : > * route add 172.16.0.248/32 172.16.0.254 -iface em3 > * route add 172.16.0.248/32 -llinfo -link -static -iface em3 > but without luck. > You have overlapping networks and you try to add an IP from the more specific into the less specific block. That is going to be tricky and it will most probably not work in all cases (e.g. hosts on the more specific network would not be able to talk to that IP). While it may be possible to coerce the routing table into doing the right thing it will probably not work well. One way to work around this is using rdomains another is renumbering the network. -- :wq Claudio
Re: route an IPv4 /32 to a different interface
On Sun, Dec 15, 2019 at 08:29:42PM +, Tom Smyth wrote: > Hi Denis, > > ok ..I hadnt read your email fully sorry about that... > > what are you trying to achieve here? > > you have a 172.16.0.249/30 address on em3 which includes > 172.16.0.248-127.16.0.251 > > and then you have a 172.16.0.254/24 which includes the entire range of > 172.16.0.0-172.16.0.255 > > I think you are making life tougher on your self and who ever has to > diagnose the system after you... > it is private IP space co can you not put them on different networks > and do meat and Potatoes Routing ? > > the other thing you need to consider is that you need to turn on proxy > arp (which can be very counter productive and cause other issues ) so > that your host responds to arp requests for > > 172.16.0.249 and 172.16.0.250 on em3 (assuming you want hosts on the > network attached to em3 to be able to talk the ips connected to em4) > > the other concern I would have is that you are trying to route traffic > to an ip that is a reserved ip 172.16.0.248 is the network address of > em4 according to your configuration... > > I hope this helps... > Thank you, I will try to renumber, this sounds like the best idea :)
