kernel (6.2 amd-64 mp) relinking failed on cloned disk
Hello I cloned a disk that had OpenBSD installed via dd if=/dev/r{source_dev} of=/dev/r{target_dev} bs=16m Now when I boot from the cloned disk I get the following error login: reorder_kernel: kernel relinking failed; see /usr/share/compile/GENERIC.MP /relink.log When I cat "relink.log" I get (SHA256) /bsd: FAILED Does this mean that a machine specific hash / checksum required to validate / execute the kernel relink is not working or what? Otherwise the machine works fine. Is the error a real cause for concern? Cloning a working setup with dd as I did saves me a bunch of time vs. installing and configuring a new system. Also, how to correct the error, if possible? Thanks
Re: 4-ports router under $150
> Stuart Henderson wrote: > > APU and APU2 are both rock solid for many people on OpenBSD. If seeing > problems there I would first look for hardware issues e.g. is the power > supply faulty, or are there any mPCIe cards that might be causing > problems? > My PC Engines APU & APU2 were both unstable running 5.7 & 5.8. Specific to you question the mPCIe was equipped with an Atheros AR9281 WLAN Card. In addition my current move to a distinct/discrete access point was hastened by a buggy Zyxel USG20w that implemented Dynamic Frequency Selection (DFS) Please note the Zyzel & PC Engines both intermittently caused subnet “collisions” that necessitated power cycle of numerous networks hosts. After several months of stability with the USG a patch to remediate KRACK caused DFS to to run idle and disconnect during channel scan. In effort to remediate I configured a Hawking HW7ACB and found (subnet collisions) no longer an issue however occasional wireless disconnects occurred. After installing WiFi Explorer I determined that all channels (1 - 161) were noisy and contained overlap in my urban apartment complex. In effort to remediate I’ve configured a Hawking HW7ACB with channel number 165. At this point my network stability is considered good.
Re: Virtualbox vs latest snapshot
On 04/11/18 10:50, Stuart Henderson wrote: On 2018-04-10, csszepwrote: 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? There's a recent bootloader problem, possibly following the update to clang 6, that affects some machines. I suspect this might be involved here. Ah, that might (?) explain what was happening to me with a Lenovo Thinkpad X1 Carbon? Not a VM. Stuck in an endless boot loop, with a flash of a "heap full" message before the next reboot. Tried the same snapshot on an older Thinkpad and no issues. Looked like it was a possible SSD problem (from what I could find in the archives), so I tried the 6.3 installer and that was fine. Repeated the snapshot install and got back into the endless rebooting. To confirm if this is the problem, can you install the older snapshot as normal, then update kernel and file sets to the newer one? (follow the "Upgrade without the install kernel" steps on http://www.openbsd.org/faq/upgrade63.html, except skip the part about running installboot do install a new bootloader). Can you report back either way please (preferably to bugs@, with dmesg and anything special about the VM config).. If it is the same thing it would be useful for developers to have a way to reproduce the problem that doesn't involve specific hardware..
Re: 4-ports router under $150
On 2018-04-08, Patrick Dohmanwrote: > As much as I’d rather not point the blame I found the APU platform buggy when > running OpenBSD. > Yes there are reports of stability with other O.S however subtle > hardware/firmware bugs appeared on several OpenBSD releases. APU and APU2 are both rock solid for many people on OpenBSD. If seeing problems there I would first look for hardware issues e.g. is the power supply faulty, or are there any mPCIe cards that might be causing problems?
Re: Date of yesterday
On 2018-04-09, Paul de Weerdwrote: > On Sun, Apr 08, 2018 at 11:12:43PM -0700, Philip Guenther wrote: >| On Sun, Apr 8, 2018 at 10:54 PM, Robert Klein wrote: >| >| > this works for me: >| > >| > date -r $(( $(date +%s) - 1 * 24 * 60 * 60 )) +%Y_%m_%d >| > >| >| Did you test that after 11pm on the day when daylight-saving time ends and >| the clock is turned back, resulting in a 25 hour long day? > > For those special occassions there's: > > date -j `date +%Y%m%d1200` +%s > > Turning this into: > > date -r $(($(date -j `date +%Y%m%d1200` +%s) - 86400)) +%Y_%m_%d > > Less perl (and less typing) at the expense of a total of 3 invocations > of date. Although I loathe the natural language parsing options built > into Linux date(1), this sort of thing is rather convenient. > >| I would use this: >|perl -MPOSIX=strftime,mktime -le '@d=localtime(); $d[3]--; mktime(@d); >| print strftime("%Y_%m_%d",@d)' >| >| Philip Guenther > > Paul 'abolish DST now' de Weerd The time I usually need yesterday's date is when constructing a filename for things like log files or mailboxes that have been rotated in a job run overnight, often in monthly.local. For this, I just cheat and set a timezone that is a bit behind... `date -z US/Pacific +%Y-%m-%d` Obviously no good if your timezone is within a couple of hours east of the date line...
Re: Virtualbox vs latest snapshot
On 2018-04-10, csszepwrote: > 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? > There's a recent bootloader problem, possibly following the update to clang 6, that affects some machines. I suspect this might be involved here. To confirm if this is the problem, can you install the older snapshot as normal, then update kernel and file sets to the newer one? (follow the "Upgrade without the install kernel" steps on http://www.openbsd.org/faq/upgrade63.html, except skip the part about running installboot do install a new bootloader). Can you report back either way please (preferably to bugs@, with dmesg and anything special about the VM config).. If it is the same thing it would be useful for developers to have a way to reproduce the problem that doesn't involve specific hardware..
Re: OpenBSD-based network switch with >16 GigE ports.
On Sat, Apr 07, 2018 at 12:01:54AM +0200, Karel Gardas wrote: > > > Hello, > > I'm looking to buy a new switch for house network. Ideally I'd like to setup > everything here on OpenBSD, but I'm not lucky > to find any OpenBSD-based switch. I need just GigE ports, at least 18-20. > Preferably fanless. 1-2U shallow depth into small rack. > I know all those Marvells, Broadcoms etc. holding majority in switch business > with strict NDAs are not OpenBSD friendly, but > still hope something may have slipped from my sight. There is some hope: Broadcom recently published their SDKLT as open source. https://www.broadcom.com/products/ethernet-connectivity/software/sdklt A switch with a Tomahawk ASIC might be a bit oversized for you home network. ;-) Remi > > Any advice appreciated. > > Thanks! > Karel
Re: Virtualbox vs latest snapshot
On Tue, Apr 10, 2018 at 5:21 PM, David Higgswrote: > On Tue, Apr 10, 2018 at 9:27 AM, Juan Francisco Cantero Hurtado < > i...@juanfra.info> wrote: > >> On Tue, Apr 10, 2018 at 11:26:44AM +0200, Janne Johansson wrote: >> > Yes, same here. First boot after update to Apr10 snap worked, then >> > fw_update and pkg_add -u and so on, and now it immediately reboots after >> > loading the kernel from the bootloader. >> >> Maybe a stupid idea, but can you both try changing the settings to a >> different OS (like Linux 64 bits or Windows) or changing the hypervisor >> to KVM or Hyper-V?. > > > > Was experiencing the same issue, but now appears to be fixed as of > snapshot #151 dated April 10. > > Sorry for any confusion, I spoke too soon. What I ACTUALLY did was booted #151 from the snapshot cd63.iso. Virtualbox hard drive currently reports BOOT 3.34, will not load bsd or bsd.rd. cd63.iso uses CDBOOT 3.29, appears to boot everything fine. Suspect the problem is with this boot code, but I do not have the expertise to diagnose further. Hope this helps. --david > >> > 2018-04-10 10:50 GMT+02:00 csszep : >> > >> > > 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? >> > > >> > >> > >> > >> > -- >> > May the most significant bit of your life be positive. >> >> -- >> Juan Francisco Cantero Hurtado http://juanfra.info >> >> >
Re: Virtualbox vs latest snapshot
On Tue, Apr 10, 2018 at 9:27 AM, Juan Francisco Cantero Hurtado < i...@juanfra.info> wrote: > On Tue, Apr 10, 2018 at 11:26:44AM +0200, Janne Johansson wrote: > > Yes, same here. First boot after update to Apr10 snap worked, then > > fw_update and pkg_add -u and so on, and now it immediately reboots after > > loading the kernel from the bootloader. > > Maybe a stupid idea, but can you both try changing the settings to a > different OS (like Linux 64 bits or Windows) or changing the hypervisor > to KVM or Hyper-V?. Was experiencing the same issue, but now appears to be fixed as of snapshot #151 dated April 10. --david > > 2018-04-10 10:50 GMT+02:00 csszep: > > > > > 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? > > > > > > > > > > > -- > > May the most significant bit of your life be positive. > > -- > Juan Francisco Cantero Hurtado http://juanfra.info > >
httpd - serving index.html & index.php at the same time
Hi All, Is there a way to serve both static and dynamic content, eg. index.html and index.php within the same server { } definition? I am looking for something like: server "default" { listen on $ext_addr port 80 root "/htdocs" directory index "index.html" # not needed as it's the default location "/files/*" { root "/htdocs/files" directory auto index } location "^/phpapp/*" { root "/htdocs/phpapp" directory index "index.php" fastcgi socket "/run/php-fpm.sock" } } Is this possible at all or do I need split static and dynamic content based on server { }? Thanx!! Mischa
Re: Cannot access internet with virtual switch
> Sent: Monday, April 09, 2018 at 6:50 PM > From: "Aham Brahmasmi"> To: misc@openbsd.org > Subject: Re: Cannot access internet with virtual switch > > > Sent: Saturday, April 07, 2018 at 5:02 AM > > From: "Ayaka Koshibe" > > To: "Aham Brahmasmi" > > Cc: misc@openbsd.org > > Subject: Re: Cannot access internet with virtual switch > > > > On Fri, Apr 6, 2018 at 4:40 PM, Aham Brahmasmi > > wrote: > > > Hello misc, > > > > > > Problem > > > A physical server with a switch (add em0 up) cannot access the internet. > > > However, the same host with a bridge (add em0 up) can access the > > > internet. > > > > > > Steps > > > $ ifconfig > > > em0: flags=8843 mtu 1500 > > > lladdr 22:22:22:22:22:22 > > > index 1 priority 0 llprio 3 > > > groups: egress > > > media: Ethernet autoselect (1000baseT full-duplex,master) > > > status: active > > > inet 20.20.20.20 netmask 0xff00 broadcast 20.20.20.255 > > > ... > > > $ doas route -n show > > > Routing tables > > > > > > Internet: > > > Destination GatewayFlags Refs Use Mtu Prio Iface > > > default 20.20.20.1 UGS0 1XXX - 8 em0 > > > 224/4 127.0.0.1 URS00 32768 8 lo0 > > > 127/8 127.0.0.1 UGRS 00 32768 8 lo0 > > > 127.0.0.1 127.0.0.1 UHhl 1X 32768 1 lo0 > > > 20.20.20/24 20.20.20.20UCn1 9XX - 4 em0 > > > 20.20.20.1 33:33:33:33:33:33 UHLch 1 1XXX - 3 em0 > > > 20.20.20.20 44:44:44:44:44:44 UHLl 0X - 1 em0 > > > 20.20.20.25520.20.20.20UHb00 - 1 em0 > > > $ ping 8.8.8.8 > > > PING 8.8.8.8 (8.8.8.8): 56 data bytes > > > 64 bytes from 8.8.8.8: icmp_seq=0 ttl=61 time=x.xxx ms > > > ... > > > $ doas ifconfig switch0 create > > > $ doas ifconfig switch0 add em0 > > > $ doas ifconfig switch0 up > > > $ ping 8.8.8.8 > > > PING 8.8.8.8 (8.8.8.8): 56 data bytes > > > ^C > > > --- 8.8.8.8 ping statistics --- > > > 31 packets transmitted, 0 packets received, 100.0% packet loss > > > > Hi, > > > > Seems you haven't started switchd(8), or connected your switch to it > > -- it shouldn't forward traffic until you do so. > > > Hi Koshibe-san, > > Thank you for your reply. > > I have started switchd and connected to it. However, I still cannot > ping 8.8.8.8. Starting switchd in debug mode results in output which > broadly says error and closes the switch. > > Steps (after the above switch0 up) > $ cat /etc/switchd.conf > listen on 0.0.0.0 tls port 6633 > $ doas switchd -d > listen on 0.0.0.0 6633 > > (On another session) > $ switchctl connect /dev/switch0 > > (Back to main session) > ofrelay_input_done: ... > /dev/switch0 > any: ... > switch_learn: ... > packet_input: ... > any > /dev/switch0: ... > (above block repeated multiple times) > ... > ofrelay_input_done: connection 1.1: 76 bytes from switch 1 > 0401004c 0013 00020004 040d00a9 0013 0001 0010 > 0010 00c88be2 d687ac1f 6b2e22ce > 8100026f 08004500 006f42d2 > /dev/switch0 > any: version 1_3 type ERROR length 76 xid 19 > error type BAD_ACTION code 4 > ofp13_input: message not supported: ERROR > ofrelay_close: connection 1.1 closed > switch_remove: switch 1 removed. > > (Another session) > $ tail -10 /var/log/messages > Apr 9 XX:XX:XX MachineName /bsd: arp: attempt to add entry for GATEWAY_IP > on em0 by XX:XX:XX:XX:XX:XX on tap0 > (above message repeated infrequently) > > If it helps in any way, this machine is a dedicated/bare-metal machine > on a large dedicated/bare-metal machine provider's network. The em0 > interface is in the egress group, has a public IP and is connected to > the internet via the provider's network equipment. > > The end goal in using the switch is to enable multiple OpenBSD VM's with > with non-contiguous public IPs to be connected to the Internet as real > hosts. In https://www.openbsd.org/faq/faq6.html#VMMnet, this is the > Option 4, except using a switch instead of a bridge and public IPs > on the host network. > > Regards, > ab > -|-|-|-|-|-|-|-- Hi, I have tried to locate the piece of code that might be causing the switch to close. In order to do so, I first looked at the specification 1.3.5 [1] for Openflow protocol, specifically the ERROR message. This is because the error that causes the switch to close is the "message not supported: ERROR" message. This led me to page 113 (out of 177). Reading through it led me to the following: "If the error message is in response to a specific message from the controller, then the xid field of the header in the error message must match that of the
Relayd and ipv6
Hello! I’m setting up Relayd for a few services in my lab as a test bed and couldn’t find answers in the docs on expected behavior. Is it better/worse/no difference to split ip4 from ip6 redirects and relays: Combined: redirect "ldap" { listen on $ext_addr port 389 listen on $ext_v6 port 389 forward to check tcp } Split: redirect "smtprelay4" { listen on $ext_addr port 25 forward to check tcp } redirect "smtprelay6" { listen on $ext_v6 port 25 forward to check tcp } Does it depend on whether it’s a relay or redirect? My pf rules end looking like this for the redirects: anchor "ldap" all { pass in quick on rdomain 0 inet6 proto tcp from any to “ip6 addr" port = 389 flags S/SA keep state (tcp.established 600) rdr-to port 389 round-robin pass in quick on rdomain 0 inet proto tcp from any to “ip4 addr" port = 389 flags S/SA keep state (tcp.established 600) rdr-to port 389 round-robin } with the table containing both the ip4 and ip6 address. Thanks! Scott
Re: Unable to use vmm on Xiaomi Air laptop: failed to enter VMM mode
On Tue, Apr 10, 2018 at 10:43:20PM +0800, Justin Yang wrote: > Hi, > > I just make vmm working on my Xiaomi Air laptop. I go to BIOS and set it to > legacy mode rather than UEFI mode, which is the default one. Then I > reinstall OpenBSD, and now vmm works like a charm, that "failed to > identify" line also disappears. > > So I guess there might be something wrong with UEFI itself or OpenBSD's > UEFI support, but not sure. > Thanks for the followup Justin. -ml > 2018-04-09 23:41 GMT+08:00 Mike Larkin: > > > On Mon, Apr 09, 2018 at 01:47:36AM +0800, Justin Yang wrote: > > > Hi,all: > > > > > > I just bought the Xiaomi Mi Air 12.5 laptop and installed OpenBSD-current > > > after reading this blog: https://jcs.org/2017/05/22/xiaomiair. > > > > > > Almost all the functions work except the vmm part. I am not able to > > start a > > > guest with the error in dmesg: > > > > > > cpu3: failed to enter VMM mode > > > cpu2: failed to enter VMM mode > > > cpu1: failed to enter VMM mode > > > > > > > > > I have searched on Google and tried my best to overcome this error, but > > > still could not figure it out. Could you help me please? I attach my > > dmesg > > > and {pf, sysctl, vm}.conf files in this email. Tell me if you need more > > > information. Thanks. > > > > > > -- > > > Justin Yang > > > > You also have "failed to identify" lines during boot. > > > > Can you try bumping the "10" in cpu_start_secondary (just bump both > > occurrances, it's in cpu.c) to someting like 1000, and also in > > vmm_start > > (in vmm.c0 and see if that fixes things? > > > > I am wondering if we aren't waiting long enough in this machine for these > > IPIs > > to complete. > > > > -ml > > > > > OpenBSD 6.3-current (GENERIC.MP) #147: Fri Apr 6 23:18:13 MDT 2018 > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > real mem = 4156014592 (3963MB) > > > avail mem = 4022935552 (3836MB) > > > mpath0 at root > > > scsibus0 at mpath0: 256 targets > > > mainbus0 at root > > > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8a6f1000 (64 entries) > > > bios0: vendor INSYDE Corp. version "XMAKB200P0200" date 11/02/2017 > > > bios0: Timi TM1607 > > > acpi0 at bios0: rev 2 > > > acpi0: sleep states S0 S3 S4 S5 > > > acpi0: tables DSDT FACP UEFI UEFI MSDM SSDT SSDT TPM2 SSDT SSDT ASF! > > ASPT BOOT DBGP HPET APIC MCFG SSDT SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP > > DBG2 SSDT SSDT DMAR FPDT BGRT > > > acpi0: wakeup devices PWRB(S4) LID0(S3) GLAN(S4) XHC_(S3) XDCI(S4) > > HDAS(S4) RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) > > RP08(S4) RP10(S4) RP11(S4) [...] > > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > > acpihpet0 at acpi0: 2399 Hz > > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > > cpu0 at mainbus0: apid 0 (boot processor) > > > cpu0: Intel(R) Core(TM) m3-7Y30 CPU @ 1.00GHz, 1197.63 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, > > FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT, > > DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP, > > LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2, > > SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT, > > IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > > cpu0: 256KB 64b/line 8-way L2 cache > > > cpu0: smt 0, core 0, package 0 > > > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > > > cpu0: apic clock running at 23MHz > > > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE > > > cpu1 at mainbus0: apid 2 (application processor) > > > cpu1: Intel(R) Core(TM) m3-7Y30 CPU @ 1.00GHz, 960.01 MHz > > > 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, > > FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT, > > DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP, > > LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2, > > SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT, > > IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > > cpu1: 256KB 64b/line cpu1: failed to identify > > > 8-way L2 cachecpu2 at mainbus0 > > > : apid 1 (application processor) > > > cpu1: smt 0, core 1, package 0 > > > cpu2: Intel(R) Core(TM) m3-7Y30 CPU @ 1.00GHz, 897.91 MHz > > > 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, > > FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT, > > DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP, > > LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2, > > SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT, > > IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > > cpu2: 256KB 64b/line 8-way L2 cache > > > cpu2:
Re: OpenBSD VMM VMs Crash
On Tue, Apr 10, 2018 at 02:31:15PM +, Olivier Cherrier wrote: > On Sat, Apr 07, 2018 at 11:46:42AM -0700, mlar...@azathoth.net wrote: > > > So i looked up logs and stuff and came to the point that my issues are > > > exactly this ones: > > > http://openbsd-archive.7691.n7.nabble.com/vmd-VMs-are-stopping-with-vcpu-0-run-ioctl-failed-Invalid-argument-td333259.html > > > > > > It seems the issue was not further discussed and/or fixed? > > > > > > Regards, > > > Aaron > > > > > > -- > > > Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > > > Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion > > > GPG: 0x7A65E38D55BE96FE > > > Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE > > > > > > > You are jumping to conclusions. > > > > All we know is that your VMs failed to run at some point. Whether or not it > > is "exactly the same" as that other post is unknown, since you didn't run > > with > > VMM_DEBUG and give us any more info. Or even submit a proper bug report. > > > > For what it's worth, I'm still working on that other issue. > > For me, the issue never went away. > I would say it is even more frequent now than before (end of 2017). > > > -- > Olivier Cherrier > Phone: +352691754777 > mailto:o...@symacx.com Yep, I dusted off that tree and spent a few hours on it last night. Hopefully have a working diff soon; the EPT misconfigurations are gone but I'm running into a uvm page list accounting error now that results in panics when the VMs are torn down. I know why it's happening but the alternative approach is a bit more messy and I'd hoped to stay away from that. But maybe I'll have no choice. -ml
mg editor regexp-replace
Folks, On a recent install of OpenBSD 6.3 amd64, I was attempting to comment out a bunch of code using the base mg editor when I encountered behaviour that surprised me (i.e. not emacs-like). I used query-replace-regexp to replace the start-of-line anchor "^" by "# ". When I hit space to replace, the "# " was always inserted into the current line at the current character position, rather than moving to the beginning of the next line. The cause seems to be that in regexec, the start anchor matches the start of search string and hence the current character position (dot). Adding the REG_NOTBOL flag to regexec when dot is not at start of line seemed to solve the issue. However, that uncovered another defect, in that attempting to replace text in an empty line caused a segmentation fault (caused, I think, by ltext(clp) returning NULL). The following patch to re_search.c (in function re_forwsrch) solves both issues for me, although I suspect my fumbling code could be improved. I'd be happy by submit via sendbug, if this is deemed worthy of such. --- a/re_search.c Tue Apr 10 15:36:48 2018 +++ b/re_search.c Tue Apr 10 15:42:11 2018 @@ -310,6 +310,7 @@ { int tbo, tdotline, error; struct line *clp; + char*search_str; clp = curwp->w_dotp; tbo = curwp->w_doto; @@ -332,8 +333,9 @@ while (clp != (curbp->b_headp)) { regex_match[0].rm_so = tbo; regex_match[0].rm_eo = llength(clp); - error = regexec(_buff, ltext(clp), RE_NMATCH, regex_match, - REG_STARTEND); + if ((search_str = ltext(clp)) == NULL) search_str = ""; + error = regexec(_buff, search_str, RE_NMATCH, regex_match, + (tbo==0?0:REG_NOTBOL)|REG_STARTEND); if (error != 0) { clp = lforw(clp); tdotline++; Best Regards, -mark
Re: Having problems sleeping a used computer
On Mon, Apr 09, 2018 at 11:51:19PM +0200, Peter J. Philipp wrote: > Hi, > > I inherited a computer which I want to make a sleeping backup computer. The > idea is that it sleeps during the day and then I wake it with arp -W and it > receives backups and then it goes back to sleep, but I'm running into > problems. > > First with a snapshot kernel when I wake the box I get this, and the system > is inoperable (due to the ahci not coming ready, 3rd line from top, sorry > about the flash on my camera, I had one shot and I didn't want to repeat the > moment). The screenshot is here: > > http://centroid.eu/private/ahci-problem.jpg > > Then I added a longer timeout on ahci and it at least put the wake state into > a stable state, here is my patch but it's far from perfect: I have expanded on the patch a little bit, it can guarantee a resume from suspend exactly once, after that the box won't suspend anymore, but is otherwise useable. Here the new patch. After my signature follows a dmesg with exactly one suspend to ram (S3) and a wake on lan to bring it back. Index: ic/ahci.c === RCS file: /cvs/src/sys/dev/ic/ahci.c,v retrieving revision 1.32 diff -u -p -u -r1.32 ahci.c --- ic/ahci.c 21 Aug 2017 21:43:46 - 1.32 +++ ic/ahci.c 10 Apr 2018 16:34:06 - @@ -1488,6 +1488,17 @@ ahci_port_portreset_finish(struct ahci_p int rc, s, retries = 0; s = splbio(); + + /* +* if we have a quirky AHCI hardware, reset it immediately +* instead of trying something and having to reset anyhow +*/ + if ((ap->ap_sc->sc_flags & AHCI_F_QUIRKAROUND)) { + ahci_port_comreset(ap); + ahci_port_portreset_wait(ap); + retries = 1; + } + retry: if (ahci_port_portreset_poll(ap)) { rc = ENODEV; @@ -2756,7 +2767,11 @@ ahci_pwait_eq(struct ahci_port *ap, bus_ for (i = 0; i < n * 1000; i++) { if ((ahci_pread(ap, r) & mask) == target) return (0); - delay(1000); + + if ((ap->ap_sc->sc_flags & AHCI_F_QUIRKAROUND)) + delay(5000); + else + delay(1000); } return (1); Index: ic/ahcivar.h === RCS file: /cvs/src/sys/dev/ic/ahcivar.h,v retrieving revision 1.10 diff -u -p -u -r1.10 ahcivar.h --- ic/ahcivar.h21 Aug 2017 21:43:46 - 1.10 +++ ic/ahcivar.h10 Apr 2018 16:34:06 - @@ -124,6 +124,7 @@ struct ahci_softc { #define AHCI_F_IPMS_PROBE (1<<1) /* IPMS on failed PMP probe */ #define AHCI_F_NO_PMP (1<<2) /* ignore PMP capability */ #define AHCI_F_NO_MSI (1<<3) /* disable MSI */ +#define AHCI_F_QUIRKAROUND (1<<4) /* Intel 6 HD for now */ u_int sc_ncmds; Index: pci/ahci_pci.c === RCS file: /cvs/src/sys/dev/pci/ahci_pci.c,v retrieving revision 1.14 diff -u -p -u -r1.14 ahci_pci.c --- pci/ahci_pci.c 3 Jan 2018 20:10:40 - 1.14 +++ pci/ahci_pci.c 10 Apr 2018 16:34:06 - @@ -275,6 +275,9 @@ ahci_intel_attach(struct ahci_softc *sc, { sc->sc_flags |= AHCI_F_NO_PMP; + if (PCI_PRODUCT(pa->pa_id) == PCI_PRODUCT_INTEL_6SERIES_AHCI_1) + sc->sc_flags |= AHCI_F_QUIRKAROUND; + return (0); } Thanks, maybe you have some ideas how to make this work better? Regards, -peter OpenBSD 6.3-current (GENERIC.MP) #7: Tue Apr 10 18:33:01 CEST 2018 p...@theta.centroid.eu:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4259340288 (4062MB) avail mem = 4123140096 (3932MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xeafb0 (100 entries) bios0: vendor American Megatrends Inc. version "E7728MLN.208" date 08/15/2011 bios0: MEDIONPC MS-7728 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC SSDT MCFG SLIC HPET acpi0: wakeup devices BR20(S3) EUSB(S3) USBE(S3) PEX0(S4) RTL_(S1) PEX1(S4) PEX2(S4) PEX3(S4) PEX4(S4) PEX5(S4) PEX6(S4) PEX7(S4) P0P1(S4) P0P2(S3) P0P3(S3) P0P4(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz, 3293.02 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges,
Re: OpenBSD VMM VMs Crash
On Sat, Apr 07, 2018 at 11:46:42AM -0700, mlar...@azathoth.net wrote: > > So i looked up logs and stuff and came to the point that my issues are > > exactly this ones: > > http://openbsd-archive.7691.n7.nabble.com/vmd-VMs-are-stopping-with-vcpu-0-run-ioctl-failed-Invalid-argument-td333259.html > > > > It seems the issue was not further discussed and/or fixed? > > > > Regards, > > Aaron > > > > -- > > Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > > Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion > > GPG: 0x7A65E38D55BE96FE > > Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE > > > > You are jumping to conclusions. > > All we know is that your VMs failed to run at some point. Whether or not it > is "exactly the same" as that other post is unknown, since you didn't run > with > VMM_DEBUG and give us any more info. Or even submit a proper bug report. > > For what it's worth, I'm still working on that other issue. For me, the issue never went away. I would say it is even more frequent now than before (end of 2017). -- Olivier Cherrier Phone: +352691754777 mailto:o...@symacx.com
Re: Unable to use vmm on Xiaomi Air laptop: failed to enter VMM mode
Hi, I just make vmm working on my Xiaomi Air laptop. I go to BIOS and set it to legacy mode rather than UEFI mode, which is the default one. Then I reinstall OpenBSD, and now vmm works like a charm, that "failed to identify" line also disappears. So I guess there might be something wrong with UEFI itself or OpenBSD's UEFI support, but not sure. 2018-04-09 23:41 GMT+08:00 Mike Larkin: > On Mon, Apr 09, 2018 at 01:47:36AM +0800, Justin Yang wrote: > > Hi,all: > > > > I just bought the Xiaomi Mi Air 12.5 laptop and installed OpenBSD-current > > after reading this blog: https://jcs.org/2017/05/22/xiaomiair. > > > > Almost all the functions work except the vmm part. I am not able to > start a > > guest with the error in dmesg: > > > > cpu3: failed to enter VMM mode > > cpu2: failed to enter VMM mode > > cpu1: failed to enter VMM mode > > > > > > I have searched on Google and tried my best to overcome this error, but > > still could not figure it out. Could you help me please? I attach my > dmesg > > and {pf, sysctl, vm}.conf files in this email. Tell me if you need more > > information. Thanks. > > > > -- > > Justin Yang > > You also have "failed to identify" lines during boot. > > Can you try bumping the "10" in cpu_start_secondary (just bump both > occurrances, it's in cpu.c) to someting like 1000, and also in > vmm_start > (in vmm.c0 and see if that fixes things? > > I am wondering if we aren't waiting long enough in this machine for these > IPIs > to complete. > > -ml > > > OpenBSD 6.3-current (GENERIC.MP) #147: Fri Apr 6 23:18:13 MDT 2018 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 4156014592 (3963MB) > > avail mem = 4022935552 (3836MB) > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8a6f1000 (64 entries) > > bios0: vendor INSYDE Corp. version "XMAKB200P0200" date 11/02/2017 > > bios0: Timi TM1607 > > acpi0 at bios0: rev 2 > > acpi0: sleep states S0 S3 S4 S5 > > acpi0: tables DSDT FACP UEFI UEFI MSDM SSDT SSDT TPM2 SSDT SSDT ASF! > ASPT BOOT DBGP HPET APIC MCFG SSDT SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP > DBG2 SSDT SSDT DMAR FPDT BGRT > > acpi0: wakeup devices PWRB(S4) LID0(S3) GLAN(S4) XHC_(S3) XDCI(S4) > HDAS(S4) RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) > RP08(S4) RP10(S4) RP11(S4) [...] > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > acpihpet0 at acpi0: 2399 Hz > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel(R) Core(TM) m3-7Y30 CPU @ 1.00GHz, 1197.63 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, > FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT, > DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP, > LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2, > SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT, > IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > cpu0: 256KB 64b/line 8-way L2 cache > > cpu0: smt 0, core 0, package 0 > > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > > cpu0: apic clock running at 23MHz > > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE > > cpu1 at mainbus0: apid 2 (application processor) > > cpu1: Intel(R) Core(TM) m3-7Y30 CPU @ 1.00GHz, 960.01 MHz > > 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, > FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT, > DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP, > LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2, > SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT, > IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > cpu1: 256KB 64b/line cpu1: failed to identify > > 8-way L2 cachecpu2 at mainbus0 > > : apid 1 (application processor) > > cpu1: smt 0, core 1, package 0 > > cpu2: Intel(R) Core(TM) m3-7Y30 CPU @ 1.00GHz, 897.91 MHz > > 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, > FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT, > DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP, > LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2, > SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT, > IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > cpu2: 256KB 64b/line 8-way L2 cache > > cpu2: failed to identify > > cpu2: smt 1, core 0, package 0 > > cpu3 at mainbus0: apid 3 (application processor) > > cpu3: Intel(R) Core(TM) m3-7Y30 CPU @ 1.00GHz, 897.91 MHz > > 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, >
Re: Virtualbox vs latest snapshot
On Tue, Apr 10, 2018 at 11:26:44AM +0200, Janne Johansson wrote: > Yes, same here. First boot after update to Apr10 snap worked, then > fw_update and pkg_add -u and so on, and now it immediately reboots after > loading the kernel from the bootloader. Maybe a stupid idea, but can you both try changing the settings to a different OS (like Linux 64 bits or Windows) or changing the hypervisor to KVM or Hyper-V?. > > > 2018-04-10 10:50 GMT+02:00 csszep: > > > 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? > > > > > > -- > May the most significant bit of your life be positive. -- Juan Francisco Cantero Hurtado http://juanfra.info
KARL, config -e, syspatch difficulties
I have a Kettop box with J1900 cpu which is proving a bit of a pain. I have very limited time (and knowledge) to spend on this but ... It worked fine with 6.1 i386 (amd64 has been flaky at best with 6.1 and 6.2, I haven't tried 6.3). With 6.2 although bsd.rd was fine to do a fresh install, booting with the installed kernel failed. Eventually after much reading of mailing lists I realised it was the inteldrm driver and discovered "config -ef /bsd". This fix didn't survive a reboot though and after more time and reading, I worked out what bsd.booted was and the effect KARL was having. Next step was to disable KARL. This doesn't seem to weaken my security to me as the only time the box is rebooted is after an upgrade to a new version or with syspatch and it's easy enough to relink once and then disable it again. Then I spotted that syspatch doesn't actually update the installed kernel if KARL is disabled. That was easy enough to work round with a trivial script. Finally my question - have I understood what's going on and is this all intended? I couldn't find anything documented (reading the source is beyond me I'm afraid) about these interactions. I suspect the "right" way to deal with my problem would be to compile my own kernel but I am trying to avoid having to do this. I couldn't find any other way to disable a driver on boot. By the time I had enough idea what was going on to think about filing a bug 6.3 was getting close and I had read messages (can't remember if on misc or bugs) that said that inteldrm had been fixed. If it would help I can open or add to a bug. Regards, George.
Re: Date of yesterday
this will be my final answer - and which certainly does not want to be a polemic: No, at school I wasn't told about an'leap second', an intercalar second! But, I only went in third - some here will be able to tell you what this level is, personally I don't know the correspondence, with other cultures, but it's pretty low... then I became "computer self-taught", until I could do a developer training (Java, SQL, Web) where even there, we weren't spoken to. My wife, who has a master's degree in history, just learned today by me what it is! I had no idea it was so complex! I thank those who responded decently, such as : - Daniel Ouellet for his link on "timezones" where I learned that some had a duration of 45, even 30". - Tom Smyth, with his reference to summer time - which I did not understand in Philip Guenther's initial message, nor that he had THE right answer! - Philip Guenther, himself, who tried to be explicit. - and, also Theo Buethler... I don't have to be ashamed to ask questions, I don't have to be ashamed not to know things... I appreciate learning, and I'm sorry I don't know so much, and not "in control" - that is, the degree of knowledge and practice of few persons. On the other hand, I am ashamed of some messages that came to insult me personally... directly! Knowledge and mastery are not necessary and useful reasons for despising others, or those who know less! Now, if I am such a disgrace to you, in my interventions, in my participations, all you have to do is banish me, remove me from the list... which would be in no way constructive, and even less positive. i.e: I have learned some things, such as the use of CVS, thanks to the intelligent cooperation of some here on this list... and certainly, others... Personally, I stay, because learning from others doesn't scare me... That, to participate, even if I know much less than others does not frighten me, and will never proccur me of shame! Even if I'm wrong, in my participations! Thanks all. "Have a nice day" Le 04/09/18 à 23:31, Martin Schröder a écrit : > 2018-04-09 20:58 GMT+02:00 Stephane HUC "PengouinBSD": >> get the current timestamp, subtracting 86400 seconds is not reliable to >> get yesterday's date to the nearest second? > > Did they teach leap seconds in your school yet? > > Best > Martin > -- ~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<< Stephane HUC as PengouinBSD or CIOTBSD b...@stephane-huc.net
A thank you for Scid & Stockfish
Just a note to bcallah@ to express great thanks for porting the chess applications scid and stockfish-9 to OpenBSD. I'm well chuffed. :)
Re: Virtualbox vs latest snapshot
Yes with pure sw virtualization. With hardware virtualization enabled (vt-x,amd-v) not do it, and amd64 guests recommends hw virtualization. Anyway thanks, for the answers., i just want to know if i only have a problem. Thx csszep 2018-04-10 12:58 GMT+02:00 Kevin Chadwick: > On Tue, 10 Apr 2018 11:09:33 +0200 > > > > Hi! > > > > I'm using Virtualbox for years with OpenBSD guest without any serious > > issue. But of course maybe it's a Virtualbox bug. > > OK, good luck but bear in mind that Virtualbox once thought it was a > good idea to try to patch the running kernel. > > https://marc.info/?l=openbsd-misc=133210764423153=2 > >
SPDIF not working with azalia(4) based card
Hi misc@ I have an azalia(4) based card integrated in my motherboard connected to a receiver through SPDIF, but I can't make it output any sound, only if I connect the cable to the 3.5mm headphone jack. And yes, I already toggled the outputs.mode to digital through mixerctl(1). When I play something audioctl(1) shows bytes going through and the receiver blinks, which means something is getting there, the sound is just not being output through SPDIF. To note that this receiver is properly working with SPDIF under Windows on the same machine and also on another crappy machine (with OpenBSD) with an NVIDIA MCPxx chipset (sorry I don't have a dmesg available for that one right now). Please find attached audioctl, mixerctl and dmesg (with AZALIA_DEBUG), and let me know which obvious knob I'm missing to enable/change? /mestre OpenBSD 6.3-current (GENERIC.MP) #13: Mon Apr 9 23:36:52 WEST 2018 serial@skoll.helheim.local:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34243928064 (32657MB) avail mem = 33199009792 (31661MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbc8b9018 (61 entries) bios0: vendor American Megatrends Inc. version "1002" date 11/07/2012 bios0: ASUSTeK COMPUTER INC. CROSSHAIR V FORMULA-Z acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT IVRS acpi0: wakeup devices SBAZ(S4) P0PC(S4) UHC1(S4) UHC2(S4) UHC4(S4) UHC6(S4) UHC7(S4) PC02(S4) PC03(S4) PC04(S4) PC05(S4) PC06(S4) PC07(S4) PC09(S4) PC0A(S4) PC0B(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 FX(tm)-8350 Eight-Core Processor, 4013.99 MHz 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,TOPEXT,CPCTR,ITSC,BMI1 cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 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 200MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD FX(tm)-8350 Eight-Core Processor, 4013.51 MHz 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,TOPEXT,CPCTR,ITSC,BMI1 cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 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 0, core 1, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD FX(tm)-8350 Eight-Core Processor, 4013.51 MHz 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,TOPEXT,CPCTR,ITSC,BMI1 cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 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 2, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD FX(tm)-8350 Eight-Core Processor, 4013.51 MHz 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,TOPEXT,CPCTR,ITSC,BMI1 cpu3: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 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 0, core 3, package 0 cpu4 at mainbus0: apid 20 (application processor) cpu4: AMD FX(tm)-8350 Eight-Core Processor, 4013.51 MHz cpu4:
Re: Virtualbox vs latest snapshot
On Tue, 10 Apr 2018 11:09:33 +0200 > Hi! > > I'm using Virtualbox for years with OpenBSD guest without any serious > issue. But of course maybe it's a Virtualbox bug. OK, good luck but bear in mind that Virtualbox once thought it was a good idea to try to patch the running kernel. https://marc.info/?l=openbsd-misc=133210764423153=2
Re: Virtualbox vs latest snapshot
Yes, same here. First boot after update to Apr10 snap worked, then fw_update and pkg_add -u and so on, and now it immediately reboots after loading the kernel from the bootloader. 2018-04-10 10:50 GMT+02:00 csszep: > 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? > -- May the most significant bit of your life be positive.
Re: 4-ports router under $150
That sounds bang on what MIPS64 Qualcomm AR7xxx platforms can do ~400-500mbit slow path operations is pretty much peak you see with them regardless of implementation. -Joel On 10 April 2018 at 20:38, Tom Smythwrote: > Hi Michael, > > I did some brief testing on 6.1/ 6.2 > simple routing 780Mb./s TCP performance simple routed > with GRE tunnels about 450 Mb/s TCP Performance simple routed > +Gre Encapsulation > (1500 byte packets) > > > > On 8 April 2018 at 17: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. > > > > Michael > > > > On Sun, Apr 8, 2018 at 1:41 AM, flipchan wrote: > > > >> I run a apu board with 3 ports with openbsd 6.2 and coreboot, i > recommend > >> it > >> > >> On April 8, 2018 2:01:50 AM UTC, jungle boogie > > >> wrote: > >> >Thus said Jordan Geoghegan on Sat, 7 Apr 2018 17:57:16 -0700 > >> >> The Edgerouter 6 is going to be coming out shortly, that is what I am > >> > > >> >> holding out for to run my home network on. > >> >> > >> >> > >> > > >> >Just curious, why this and not amd64 bit with something like the > >> >pcengine apu2 board? I know it only has three NICs, so it's likely a > >> >non-started for the OP, but it's 64bit amd. > >> > > >> >I don't know the MSRP of the ER6. Do you? > >> > >> -- > >> Take Care Sincerely flipchan layerprox dev > >> > > > > -- > 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. > >
Re: Virtualbox vs latest snapshot
Hi! I'm using Virtualbox for years with OpenBSD guest without any serious issue. But of course maybe it's a Virtualbox bug. thx csszep 2018-04-10 11:51 GMT+02:00 Kevin Chadwick: > On Tue, 10 Apr 2018 10:50:27 +0200 > > > > There is a similar experience for someone with Virtualbox 5.2.8? > > Hasn't Virtualbox always sucked. When I used Linux as one of my > workstation desktops many moons ago. Vmware ran OpenBSD fast, nicely and > easily. > > Any of KVM/Xen/Vmware/Hyper-V are more accurate emulators of hardware! > >
Re: Virtualbox vs latest snapshot
On Tue, 10 Apr 2018 10:50:27 +0200 > There is a similar experience for someone with Virtualbox 5.2.8? Hasn't Virtualbox always sucked. When I used Linux as one of my workstation desktops many moons ago. Vmware ran OpenBSD fast, nicely and easily. Any of KVM/Xen/Vmware/Hyper-V are more accurate emulators of hardware!
Virtualbox vs latest snapshot
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: 4-ports router under $150
Hi Michael, I did some brief testing on 6.1/ 6.2 simple routing 780Mb./s TCP performance simple routed with GRE tunnels about 450 Mb/s TCP Performance simple routed +Gre Encapsulation (1500 byte packets) On 8 April 2018 at 17:02, Michael Pricewrote: > 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. > > Michael > > On Sun, Apr 8, 2018 at 1:41 AM, flipchan wrote: > >> I run a apu board with 3 ports with openbsd 6.2 and coreboot, i recommend >> it >> >> On April 8, 2018 2:01:50 AM UTC, jungle boogie >> wrote: >> >Thus said Jordan Geoghegan on Sat, 7 Apr 2018 17:57:16 -0700 >> >> The Edgerouter 6 is going to be coming out shortly, that is what I am >> > >> >> holding out for to run my home network on. >> >> >> >> >> > >> >Just curious, why this and not amd64 bit with something like the >> >pcengine apu2 board? I know it only has three NICs, so it's likely a >> >non-started for the OP, but it's 64bit amd. >> > >> >I don't know the MSRP of the ER6. Do you? >> >> -- >> Take Care Sincerely flipchan layerprox dev >> -- 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.
Re: 4-ports router under $150
Hi Patrick of all the MikroTik Platforms you have mentioned the MikroTik 2011UiAS is probably the least stable platform we have ever used from MikroTik, We have had alot of weird issues with that platform in ROuter OS6 (packets no longer being natted... no log entry for a reason not natting them and poor tunnel stability with them. (we have thousands of MikroTik in the Field) and this is not just our experience it is other client experience also regarding the APU2 the only minor issue I have had was poor SD cards and poor msata cards other than that the platform has been solid for us... like I said SD cards the S may stand for S*#t :) also the guys at PC engines have been very helpful to support us on hardware questions On 8 April 2018 at 15:39, Patrick Dohmanwrote: > As much as I’d rather not point the blame I found the APU platform buggy when > running OpenBSD. > Yes there are reports of stability with other O.S however subtle > hardware/firmware bugs appeared on several OpenBSD releases. > I’m actually in the other boat when it comes to hardware stability being an > excuse however openbsd'd excellent embedded footprint does well at disclosing > subtle hardware issues. > I’m currently running a MikroTik 2011UiAS that is built on A mips processor. > Quite honestly I’ve found the secret of stability on the network hardware > arena to be distinct/discrete hardware. > Router ——> Firewall —— > Switch ——> Access point. Call me throw back to the > 2001 however the result of one issue cascading across all protocols to heavy > a load for one chip/box. > B.T.W im currently running a 6.2 DB on a Dell GX620 & things are stable. > Regards > Patrick > >> On Apr 8, 2018, at 7:42 AM, Karel Gardas wrote: >> >> On Sat, 7 Apr 2018 20:28:14 -0700 >> Jordan Geoghegan wrote: >> >>> >>> On 04/07/18 19:01, jungle boogie wrote: Thus said Jordan Geoghegan on Sat, 7 Apr 2018 17:57:16 -0700 > The Edgerouter 6 is going to be coming out shortly, that is what I am > holding out for to run my home network on. > > Just curious, why this and not amd64 bit with something like the pcengine apu2 board? I know it only has three NICs, so it's likely a non-started for the OP, but it's 64bit amd. I don't know the MSRP of the ER6. Do you? >>> Because I don't like amd64 and avoid it when possible. I like the idea >>> of having a niche architecture for my internet facing machines. >> >> niche archs are nice, but if you do not have code of firmware to see what's >> its doing inside, then it's kind of meaningless. >> PC Engines can provide you with their coreboot modified sources if you like >> to see them... > -- 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.
Re: is there foomatic-rip for lpd on openBSD 6.3?
On 10 April 2018 at 09:58, Theo Buehlerwrote: >> I do read man pages. But 1) As far as I can tell, you will not find any >> information anywhere about foomatic-rip (or any other smart filter) > > use the pkglocatedb package: > https://www.openbsd.org/faq/faq15.html#PkgFind > Ok. This is good to know. Thanks Ruda
Re: is there foomatic-rip for lpd on openBSD 6.3?
On Tue, Apr 10, 2018 at 09:28:53AM +0200, Rudolf Sykora wrote: > Dear Predrag, > > > Around here we actually read man pages and pkg-readmes > > I do read man pages. But 1) As far as I can tell, you will not find any > information anywhere about foomatic-rip (or any other smart filter) use the pkglocatedb package: https://www.openbsd.org/faq/faq15.html#PkgFind
Re: is there foomatic-rip for lpd on openBSD 6.3?
Dear Predrag, > Around here we actually read man pages and pkg-readmes I do read man pages. But 1) As far as I can tell, you will not find any information anywhere about foomatic-rip (or any other smart filter) when you just install the system, and 2), on a similar note, you can only read pkg-readmes when you have the packages already installed. I didn't know it all goes with the cups-filters package. > Here is my post which would have answered your question. > > https://marc.info/?l=openbsd-ports=141490031517069=2 No. I read your post before I asked. It's actually one of the few things I found. But there you say: install foomatic-rip. It does not mention where to get it. Thanks Ruda