Re: Brand new server - bad adventures
On Wed, Jan 22, 2020 at 11:30:51PM +0300, Özgür Kazancci wrote: > Hello everyone! Greetings to misc people! > > Got a brand new dedicated server with a hardware: Intel Xeon-E 2274G - 64GB > DDR4 ECC 2666MHz - 2x SSD NVMe 960GB > and installed "brand new" OpenBSD 6.6 on it. (I'm managing it remotely via > KVM/IPMI) > > After the first boot, dmesg is outputting sequentally between few seconds > delays: > "wsdisplay0 at inteldrm0 mux 1 > init: can't open /dev/console: Device not configured" and the system doesn't > boot at all. Is it possible that it does actually boot but that you just don't see the messages. Did you try pinging the machine or accessing it through SSH? > > Please refer to the screenshot attached: https://ibb.co/sQbt7F7 > > And after few hours of forums/IRC-logs readings, I tried to try the > suggestion of lots of similar-people: "disable inteldrm" > > To do that, during the boot I typed "boot -c", then got a brand new error > (IPMI/KVM freezes, no more keyboard input): > "kbc: cmd word write error" (with a weird cursor) > Please refer to the screenshot attached: https://ibb.co/QchqhtY > > Anyways, wanted to skip that -for now-, rebooted the server again, and > booted into bsd.rd, mounted the / and /usr on the harddisk, chrooted into > there and did; > "config -ef /bsd", then "disable inteldrm" and "quit" to save the changes. > Finally rebooted. > > The system booted up fine! Got the login prompt shell, logged in, well, with > -an another- brand new error :) > > "reorder_kernel: failed - see /usr/...GENERIC.MP/relink.log" This sometimes indicates that the previous boot got to the kernel re-linking stage but that it got interrupted there. I see this on VMs if I forcefully reboot them as soon as the login prompt appears. > > I guess that was because I modified the kernel, anyway, wanted to skip that > too -for now-. Did what I always do the first: syspatch > > installed the patches, rebooted the system, aand...Tada! "inteldrm0 is back, > b1tch3z!" :) > > Dmesg has again: "init: can't open /dev/console: Device not configured" and > delays there. No boot, again. > > My questions are: > > How can I get the rid of the error "init: can't open /dev/console: Device > not configured" to be able to boot into the system? > > if that was the only way (disabling inteldrm), would I repeat it each time I > issue syspatch? > > And each time syspatch (re)installs the kernel, should I get the error > "reorder_kernel: failed", because I modified (disabled inteldrm) kernel? > > Any words on "kbc: cmd word write error" when I tried the 'boot -c'? > > I thank you for your time in reading all these, > And many thanks for your suggestions, in advance! > > Best, > Özgür Kazancci -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: Slow performance when using mu(4e)
Xiyue Deng writes: > Xiyue Deng writes: > >> Hi, >> >> Recently I tried to use mu4e on OpenBSD. However the indexing >> performance is dreadly slow compared to my Linux box. There was also an >> issue report on mu upstream[1] where someone reported mu can only >> process ~7msg/s on OpenBSD. I suspect it's because of the slow write >> performance on FFS, which in my case can only process ~2msg/s when the >> index file grows large (over 1GB) (BTW my box is mips64el/Loongson >> running 6.6-stable so it's even slower). The read part is probably OK >> as when re-indexing it can quickly skip already indexed items but when >> adding new contents to the index it becomes slow again. Would like to >> ask for some suggestions on how to improve this situation. >> >> Thanks in advance. >> >> [1] https://github.com/djcb/mu/issues/1335 > > Ping. Would like to get some advice on how to improve this situation. Hi again, So I digged a little more and it turned out that the slow performance is more likely caused by the limited memory on my Loongson box (1GB), which caused a lot of biowait when the swap is involved and resulted in very slow performance overall. Opened a bug upstream to track this[1]. [1] https://github.com/djcb/mu/issues/1549 signature.asc Description: PGP signature
Re: install libreoffice OpenBSD 6.6
On 1/22/20 7:55 PM, Jovany Leandro G.C wrote: hello community, i recently install OpenBSD 6.6 and works great. now i try install libreoffice and throws: quirks-3.182 signed on 2020-01-22T10:10:52Z Can't install rasqal-0.9.33p2 because of libraries |library gmp.10.0 not found | not found anywhere Direct dependencies for rasqal-0.9.33p2 resolve to libgcrypt-1.8.5 raptor-2.0.15p2 pcre-8.41p2 e2fsprogs-1.42.12p5 mpfr-3.1.5.2p1 Full dependency tree is libxslt-1.1.33 e2fsprogs-1.42.12p5 libyajl-2.1.0 curl-7.66.0 libgpg-error-1.36p0 pcre-8.41p2 xz-5.2.4 libiconv-1.16p0 raptor-2.0.15p2 libgcrypt-1.8.5 libxml-2.9.9 gettext-runtime-0.20.1p0 mpfr-3.1.5.2p1 nghttp2-1.39.2 Can't install redland-1.0.17p6: can't resolve rasqal-0.9.33p2 Can't install libreoffice-6.3.2.2v0: can't resolve redland-1.0.17p6 Couldn't install libreoffice-6.3.2.2v0 rasqal-0.9.33p2 redland-1.0.17p6 what can i do? thanks any help Looks like you installed a snapshot and then waited a bit too long before you tried to install the package. If this is the case, check the snapshots//directory and the snapshots/Packages// directory and compare the dates. if they are the same, update your base system, then update any currently installed packages and finally install libreoffice.
Re: rate limit echo request
On 1/22/20 10:42 PM, myml...@gmx.com wrote: Hi, I'm just wondering if there is a way to rate limit icmp echo request. i.e. pings. I tried the following rule but it errors out with "syntax error" pass in quick on em1 inet proto icmp from 192.168.0.23 to 192.168.1.2 icmp-type echoreq (max-src-conn-rate 1/2, overload flush) I'm trying to avoid even standard pings and especially "ping -f". Additionally, I was wondering if there would be a way to block icmp that's over a certain size. "ping -s". Thanks in advance!!! Sorry, This is fresh install of snapshot from 10/17 on amd64 OpenBSD 6.6-current (GENERIC.MP) #613: Thu Jan 16 13:52:56 MST 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8487612416 (8094MB) avail mem = 8217923584 (7837MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8d318000 (86 entries) bios0: vendor American Megatrends Inc. version "5.12" date 07/08/2019 bios0: Protectli FW6 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP APIC FPDT MCFG SSDT FIDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT SSDT SSDT DBGP DBG2 DMAR ASF! acpi0: wakeup devices PS2K(S0) PS2M(S0) RP09(S0) PXSX(S0) RP10(S0) PXSX(S0) RP11(S0) PXSX(S0) RP12(S0) PXSX(S0) RP13(S0) PXSX(S0) RP01(S0) PXSX(S0) RP02(S0) PXSX(S0) [...] 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) i5-7200U CPU @ 2.50GHz, 2395.20 MHz, 06-8e-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,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,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 24MHz 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) i5-7200U CPU @ 2.50GHz, 2394.43 MHz, 06-8e-09 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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2394.43 MHz, 06-8e-09 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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2394.43 MHz, 06-8e-09 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,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus -1 (RP09) acpiprt5 at acpi0: bus -1 (RP10) acpiprt6 at acpi0: bus -1 (RP11) acpiprt7 at acpi0: bus -1 (RP12) acpiprt8 at acpi0: bus -1 (RP13) acpiprt9 at acpi0: bus 1 (RP01) acpiprt10 at acpi0: bus 2 (RP02) acpiprt11 at acpi0: bus 3 (RP03) acpiprt12 at acpi0: bus 4 (RP04) acpiprt13 at acpi0: bus 5 (RP05)
rate limit echo request
Hi, I'm just wondering if there is a way to rate limit icmp echo request. i.e. pings. I tried the following rule but it errors out with "syntax error" pass in quick on em1 inet proto icmp from 192.168.0.23 to 192.168.1.2 icmp-type echoreq (max-src-conn-rate 1/2, overload flush) I'm trying to avoid even standard pings and especially "ping -f". Additionally, I was wondering if there would be a way to block icmp that's over a certain size. "ping -s". Thanks in advance!!!
Re: install libreoffice OpenBSD 6.6
Hi What command did you use to install libreoffice and what is your PKG_PATH? On Thu, Jan 23, 2020 at 1:59 PM Jovany Leandro G.C wrote: > > > hello community, > > i recently install OpenBSD 6.6 and works great. > > now i try install libreoffice and throws: > > > quirks-3.182 signed on 2020-01-22T10:10:52Z > Can't install rasqal-0.9.33p2 because of libraries > |library gmp.10.0 not found > | not found anywhere > Direct dependencies for rasqal-0.9.33p2 resolve to libgcrypt-1.8.5 > raptor-2.0.15p2 pcre-8.41p2 e2fsprogs-1.42.12p5 mpfr-3.1.5.2p1 > Full dependency tree is libxslt-1.1.33 e2fsprogs-1.42.12p5 libyajl-2.1.0 > curl-7.66.0 libgpg-error-1.36p0 pcre-8.41p2 xz-5.2.4 libiconv-1.16p0 > raptor-2.0.15p2 libgcrypt-1.8.5 libxml-2.9.9 gettext-runtime-0.20.1p0 > mpfr-3.1.5.2p1 nghttp2-1.39.2 > Can't install redland-1.0.17p6: can't resolve rasqal-0.9.33p2 > Can't install libreoffice-6.3.2.2v0: can't resolve redland-1.0.17p6 > Couldn't install libreoffice-6.3.2.2v0 rasqal-0.9.33p2 redland-1.0.17p6 > > > what can i do? > > thanks any help > > > -- > Jovany Leandro G.C > Desarrollador Software Libre > Cel: (57) 3165387562 > Git: https://gitlab.com/bit4bit > Fossil: https://efossils.somxslibres.net > E-Sitio: https://www.somxslibres.net > -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
install libreoffice OpenBSD 6.6
hello community, i recently install OpenBSD 6.6 and works great. now i try install libreoffice and throws: quirks-3.182 signed on 2020-01-22T10:10:52Z Can't install rasqal-0.9.33p2 because of libraries |library gmp.10.0 not found | not found anywhere Direct dependencies for rasqal-0.9.33p2 resolve to libgcrypt-1.8.5 raptor-2.0.15p2 pcre-8.41p2 e2fsprogs-1.42.12p5 mpfr-3.1.5.2p1 Full dependency tree is libxslt-1.1.33 e2fsprogs-1.42.12p5 libyajl-2.1.0 curl-7.66.0 libgpg-error-1.36p0 pcre-8.41p2 xz-5.2.4 libiconv-1.16p0 raptor-2.0.15p2 libgcrypt-1.8.5 libxml-2.9.9 gettext-runtime-0.20.1p0 mpfr-3.1.5.2p1 nghttp2-1.39.2 Can't install redland-1.0.17p6: can't resolve rasqal-0.9.33p2 Can't install libreoffice-6.3.2.2v0: can't resolve redland-1.0.17p6 Couldn't install libreoffice-6.3.2.2v0 rasqal-0.9.33p2 redland-1.0.17p6 what can i do? thanks any help -- Jovany Leandro G.C Desarrollador Software Libre Cel: (57) 3165387562 Git: https://gitlab.com/bit4bit Fossil: https://efossils.somxslibres.net E-Sitio: https://www.somxslibres.net
Re: Brand new server - bad adventures
Hi Hrvoje, I've just sent the sendbug -P output on the system, with needed information filled, to bugs@openbsd. Regards. On 23/01/2020 01:26, Hrvoje Popovski wrote: On 22.1.2020. 21:30, Özgür Kazancci wrote: Hello everyone! Greetings to misc people! Got a brand new dedicated server with a hardware: Intel Xeon-E 2274G - 64GB DDR4 ECC 2666MHz - 2x SSD NVMe 960GB and installed "brand new" OpenBSD 6.6 on it. (I'm managing it remotely via KVM/IPMI) Hi, could you install snapshot on this box and if problem is still there send report to bugs@openbsd https://www.openbsd.org/report.html at least in report send "sendbug -P" from that box
Re: Brand new server - bad adventures
Hello Tom, and many thanks for all your prompt replies. I've posted dmesg to bugs and dmesg, with further details there. I'm going to post here the dmesg output, obviously, I cannot reach the dmesg when it hangs/fails to boot (when inteldrm is enabled, the boot-up hangs with filling "console error" messages preventing any keyboard reaction), so the following dmesg was fetched when I logged the system in (a.k.a. without inteldrm). The BIOS of that motherboard is on its default settings, except, SpeedStep is disabled. dmesg: OpenBSD 6.6 (GENERIC.MP) #4: Wed Jan 15 10:55:43 MST 2020 r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68294201344 (65130MB) avail mem = 66211708928 (63144MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x6fc71000 (44 entries) bios0: vendor American Megatrends Inc. version "L2.02K" date 12/18/2019 bios0: ASRockRack E3C246D4U2-2T acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SPMI SSDT AAFT SSDT SSDT HPET SSDT SSDT UEFI LPIT SSDT SSDT DBGP DBG2 SSDT DMAR SSDT SPCR SSDT WSMT EINJ ERST BERT HEST BGRT acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) UAR1(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) E-2274G CPU @ 4.00GHz, 3992.38 MHz, 06-9e-0a cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,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 24MHz 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) Xeon(R) E-2274G CPU @ 4.00GHz, 3990.71 MHz, 06-9e-0a cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Xeon(R) E-2274G CPU @ 4.00GHz, 3990.71 MHz, 06-9e-0a cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) E-2274G CPU @ 4.00GHz, 3990.71 MHz, 06-9e-0a cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Xeon(R) E-2274G CPU @ 4.00GHz, 3990.71 MHz, 06-9e-0a cpu4:
Re: OpenBSD PPPOE
The hostname.filename should follow vlan or vnetid? Regards, -- Peter Wong 016-396 3326 On Wed, Jan 22, 2020 at 2:35 PM Peter J. Philipp wrote: > On Wed, Jan 22, 2020 at 09:49:18AM +0800, Peter Wong wrote: > > Yes, my ISP operate pppoe with vlan. How to configure my fxp0 using vlan > id > > 500? > > > > > > Regards, > > -- > > Peter Wong > > 016-396 3326 > > Hi Peter Wong, > > My PPPoE router uses VLAN id #7 (IEEE 802.1q protocol), this is how I set > up > the vlan: > > eta$ more /etc/hostname.vlan7 > description "T-Online Internet" > vnetid 7 parent cnmac0 > up mtu 1508 > eta$ ifconfig vlan7 > vlan7: flags=8843 mtu 1508 > lladdr fc:ec:da:04:8d:68 > description: T-Online Internet > index 9 priority 0 llprio 3 > encap: vnetid 7 parent cnmac0 txprio packet rxprio outer > groups: vlan > media: Ethernet autoselect (1000baseT full-duplex) > status: active > > You may make your vlan similarly by setting vnetid to 500. And then > instead of > your fxp interface you'd use vlan. In my case it's vlan7. > > Hope that helps, > -peter >
Re: Brand new server - bad adventures
Hello Ozgur, if you are very stuck and you want to get you could set the console to com0 on the openbsd boot screen and manage it via serial (to get around the drm issue for now ) just make sure the bios screen you turn off logos (text boot up) and set the openbsd console settings to the same speed as your bios serial console settings (so that you have a seamless view of going from bios / post screen to the openbsd console as Jonathan said, if you set the boot up to legacy bios (rather than efi firmware) you will probably have better luck with the screen, dmesg would be very helpful in identifying the hardware config on your OpenBSD Box Hope this helps, Tom Smyth On Wed, 22 Jan 2020 at 22:59, Jonathan Gray wrote: > On Wed, Jan 22, 2020 at 11:30:51PM +0300, Özgür Kazancci wrote: > > Hello everyone! Greetings to misc people! > > > > Got a brand new dedicated server with a hardware: Intel Xeon-E 2274G - > 64GB > > DDR4 ECC 2666MHz - 2x SSD NVMe 960GB > > and installed "brand new" OpenBSD 6.6 on it. (I'm managing it remotely > via > > KVM/IPMI) > > > > After the first boot, dmesg is outputting sequentally between few seconds > > delays: > > "wsdisplay0 at inteldrm0 mux 1 > > init: can't open /dev/console: Device not configured" and the system > doesn't > > boot at all. > > > > Please refer to the screenshot attached: https://ibb.co/sQbt7F7 > > > > And after few hours of forums/IRC-logs readings, I tried to try the > > suggestion of lots of similar-people: "disable inteldrm" > > > > To do that, during the boot I typed "boot -c", then got a brand new error > > (IPMI/KVM freezes, no more keyboard input): > > "kbc: cmd word write error" (with a weird cursor) > > Please refer to the screenshot attached: https://ibb.co/QchqhtY > > > > Anyways, wanted to skip that -for now-, rebooted the server again, and > > booted into bsd.rd, mounted the / and /usr on the harddisk, chrooted into > > there and did; > > "config -ef /bsd", then "disable inteldrm" and "quit" to save the > changes. > > Finally rebooted. > > > > The system booted up fine! Got the login prompt shell, logged in, well, > with > > -an another- brand new error :) > > > > "reorder_kernel: failed - see /usr/...GENERIC.MP/relink.log" > > > > I guess that was because I modified the kernel, anyway, wanted to skip > that > > too -for now-. Did what I always do the first: syspatch > > > > installed the patches, rebooted the system, aand...Tada! "inteldrm0 is > back, > > b1tch3z!" :) > > > > Dmesg has again: "init: can't open /dev/console: Device not configured" > and > > delays there. No boot, again. > > > > My questions are: > > > > How can I get the rid of the error "init: can't open /dev/console: Device > > not configured" to be able to boot into the system? > > > > if that was the only way (disabling inteldrm), would I repeat it each > time I > > issue syspatch? > > It would be helpful if you would include a full dmesg. > > 1024x768 is the default mode when there are no connected outputs. > > You should see > wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using wskbd0 > > The way inteldrm claims the console changes depending on whether or not > you are booting via efi. > > -- Kindest regards, Tom Smyth.
Re: Brand new server - bad adventures
On Wed, Jan 22, 2020 at 11:30:51PM +0300, Özgür Kazancci wrote: > Hello everyone! Greetings to misc people! > > Got a brand new dedicated server with a hardware: Intel Xeon-E 2274G - 64GB > DDR4 ECC 2666MHz - 2x SSD NVMe 960GB > and installed "brand new" OpenBSD 6.6 on it. (I'm managing it remotely via > KVM/IPMI) > > After the first boot, dmesg is outputting sequentally between few seconds > delays: > "wsdisplay0 at inteldrm0 mux 1 > init: can't open /dev/console: Device not configured" and the system doesn't > boot at all. > > Please refer to the screenshot attached: https://ibb.co/sQbt7F7 > > And after few hours of forums/IRC-logs readings, I tried to try the > suggestion of lots of similar-people: "disable inteldrm" > > To do that, during the boot I typed "boot -c", then got a brand new error > (IPMI/KVM freezes, no more keyboard input): > "kbc: cmd word write error" (with a weird cursor) > Please refer to the screenshot attached: https://ibb.co/QchqhtY > > Anyways, wanted to skip that -for now-, rebooted the server again, and > booted into bsd.rd, mounted the / and /usr on the harddisk, chrooted into > there and did; > "config -ef /bsd", then "disable inteldrm" and "quit" to save the changes. > Finally rebooted. > > The system booted up fine! Got the login prompt shell, logged in, well, with > -an another- brand new error :) > > "reorder_kernel: failed - see /usr/...GENERIC.MP/relink.log" > > I guess that was because I modified the kernel, anyway, wanted to skip that > too -for now-. Did what I always do the first: syspatch > > installed the patches, rebooted the system, aand...Tada! "inteldrm0 is back, > b1tch3z!" :) > > Dmesg has again: "init: can't open /dev/console: Device not configured" and > delays there. No boot, again. > > My questions are: > > How can I get the rid of the error "init: can't open /dev/console: Device > not configured" to be able to boot into the system? > > if that was the only way (disabling inteldrm), would I repeat it each time I > issue syspatch? It would be helpful if you would include a full dmesg. 1024x768 is the default mode when there are no connected outputs. You should see wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using wskbd0 The way inteldrm claims the console changes depending on whether or not you are booting via efi.
Re: Brand new server - bad adventures
On 22.1.2020. 21:30, Özgür Kazancci wrote: > Hello everyone! Greetings to misc people! > > Got a brand new dedicated server with a hardware: Intel Xeon-E 2274G - > 64GB DDR4 ECC 2666MHz - 2x SSD NVMe 960GB > and installed "brand new" OpenBSD 6.6 on it. (I'm managing it remotely > via KVM/IPMI) Hi, could you install snapshot on this box and if problem is still there send report to bugs@openbsd https://www.openbsd.org/report.html at least in report send "sendbug -P" from that box
Re: DNS lookups on a different port for testing?
Claus Assmann wrote: > The functional tests for sendmail use ldns-testns as DNS server > which provides specific test data and error behaviours. > It runs on a port > 1024 to avoid requiring root access. you can use a combination of pf.conf rdr-to and 127.0.0.2 etc. i.e., bind to port 5353, have pf rdr 127.0.0.2:53 to 5353. this requires root to setup, but not afterwards.
PF is ignored by IPsec Tunnel (iked)
Hello *, when running and IPsec Tunnel in the exactly same setup as described here: https://www.openbsd.org/faq/faq17.html#clientikev2 On the roadwarrior my pf rules are completely ignored. Doesn't matter if I try to nat the outgoing traffic on enc0 or to block it entirely. PF is completely omitted. I remember that this hasn't always been that way. Is this due to my incompetencies or does the FAQ require an update ? g Stephan
Brand new server - bad adventures
Hello everyone! Greetings to misc people! Got a brand new dedicated server with a hardware: Intel Xeon-E 2274G - 64GB DDR4 ECC 2666MHz - 2x SSD NVMe 960GB and installed "brand new" OpenBSD 6.6 on it. (I'm managing it remotely via KVM/IPMI) After the first boot, dmesg is outputting sequentally between few seconds delays: "wsdisplay0 at inteldrm0 mux 1 init: can't open /dev/console: Device not configured" and the system doesn't boot at all. Please refer to the screenshot attached: https://ibb.co/sQbt7F7 And after few hours of forums/IRC-logs readings, I tried to try the suggestion of lots of similar-people: "disable inteldrm" To do that, during the boot I typed "boot -c", then got a brand new error (IPMI/KVM freezes, no more keyboard input): "kbc: cmd word write error" (with a weird cursor) Please refer to the screenshot attached: https://ibb.co/QchqhtY Anyways, wanted to skip that -for now-, rebooted the server again, and booted into bsd.rd, mounted the / and /usr on the harddisk, chrooted into there and did; "config -ef /bsd", then "disable inteldrm" and "quit" to save the changes. Finally rebooted. The system booted up fine! Got the login prompt shell, logged in, well, with -an another- brand new error :) "reorder_kernel: failed - see /usr/...GENERIC.MP/relink.log" I guess that was because I modified the kernel, anyway, wanted to skip that too -for now-. Did what I always do the first: syspatch installed the patches, rebooted the system, aand...Tada! "inteldrm0 is back, b1tch3z!" :) Dmesg has again: "init: can't open /dev/console: Device not configured" and delays there. No boot, again. My questions are: How can I get the rid of the error "init: can't open /dev/console: Device not configured" to be able to boot into the system? if that was the only way (disabling inteldrm), would I repeat it each time I issue syspatch? And each time syspatch (re)installs the kernel, should I get the error "reorder_kernel: failed", because I modified (disabled inteldrm) kernel? Any words on "kbc: cmd word write error" when I tried the 'boot -c'? I thank you for your time in reading all these, And many thanks for your suggestions, in advance! Best, Özgür Kazancci
Re: Android (MTP) with OpenBSD: Tiny success story
devel/adb was installed successfully (OpenBSD 6.6). Sorry for that fisrt comment. Then I just got fresh ports. This new report is actual. Adb tool works fine! I made several tests for shell, pull, backup, reboot. The device is the same: mentioned by me before for described umass-method. Android: 4.1.2, baseband & build: Apr 1 2013 -- Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html
DNS lookups on a different port for testing?
The functional tests for sendmail use ldns-testns as DNS server which provides specific test data and error behaviours. It runs on a port > 1024 to avoid requiring root access. There's code in sendmail to set the IP and port for a NS: _res.nsaddr_list[0].sin_family = AF_INET; _res.nsaddr_list[0].sin_addr = *ns; _res.nsaddr_list[0].sin_port = htons(port); _res.nscount = 1; but this does not work (anymore) on OpenBSD -- AFAICT the resolver implementation (asr?) has a hardcoded port (53). Is there some way to set a different port for testing? I also tried to link sendmail against libbind but then it fails during executtion: sendmail:/usr/lib/libc.so.95.0: ../sendmail/sendmail : WARNING: symbol(__p_type_syms) size mismatch, relink your program sendmail:/usr/lib/libc.so.95.0: ../sendmail/sendmail : WARNING: symbol(_res) size mismatch, relink your program fill_fd: before readcf: fd 0 not open: Bad file descriptor Any (simple?) suggestion to get this working on OpenBSD (just for functional testing)? -- Address is valid for this mailing list only, please do not reply to it direcly, but to the list.
Re: Kernel Panics with rtorrent
Hi Victor, I hit what appears to be the same panic in April: https://marc.info/?l=openbsd-bugs=155568856220887=2 On Thu, Jan 16, 2020 at 6:12 PM Victor Tarabola Cortiano wrote: > I was having mutiple kernel panics while using rtorrent with over 60 > active torrents and multiple files. I don't think I've ever seen a program stress OpenBSD as hard as rtorrent does. A while back I came to the conclusion that part of the problem is excessive gettimeofday() in libtorrent, but didn't investigate further. > I would get multiple "re0: watchdog timeout" messages I've gotten many (very, very, very many) of those over four years using re(4), especially in conjunction with rtorrent. Panics rare; usually I only lost network (which only came back with a reboot) and observed serious system performance degradation (as in keyboard/mouse barely worked). Reading the archives and cvs log it seems that there have been many race conditions in the driver, some of which have been fixed, some which are still present. These show up less than they used to, I assume due to kernel and driver improvements, but it's still bad enough that after years of constantly encountering watchdog timeouts on re(4) I switched to different networking hardware. -- Anthony J. Bentley
Re: Game controller / gamepad recommendation
On Wed, Jan 22, 2020, at 12:29 AM, Raf Czlonka wrote: > Hi all, > > I'm in a search for a game controller / gamepad for OpenBSD and > found an old article on OpenBSD Journal[0] regarding (support for) > an Xbox 360 one. SDL2 got some tweaks since [1] that allow using the Xbox 360 (wired) gamepad for all SDL2 games/applications. This is probably the most popular and best designed of all supported gamepads at this moment. > Good ol' Logitech has two gamepads - one wired[1] and one wireless[2] I have a Logitech F310 and it's probably the best option compatibility-wise you can switch between traditional joystick/DInput (D) mode and Xbox360 pad/XInput (X) mode with a switch on the back. > Has anyone tried Xbox One controller or Valve's, recently discontinued, > Steam Controller? I have those and they don't work. Unfortunately these gamepad manufacturers have abandoned any idea of portability and don't even provide USB HID descriptors. Instead it seems that everything is run through a custom driver for each device. The Linux kernel has special entries to detect the XBox One controller and send an initialization sequence that seems to be required. It may be possible to come up with an approach similar to our XBox360 implementation, but someone needs to come up with this. I also have a Steam controller. Interestingly, it attaches as mouse + keyboard by default if I recall it correctly. However, getting it to fully work as a gamepad also seems to require coming up with a way to provide a uhid descriptor. > I'd prefer a wireless one but a wired one will be just fine if it > "just works" and/or is superior to a wireless one. Yes, I'm well > aware that there's no Bluetooth support on OpenBSD but am thinking > of a wireless Logitech-style, i.e. with a wireless USB dongle. I'm not aware of any Bluetooth-less wireless gamepad option, but would like to hear of it if it exists. [...] > it here as, from what I understand, some emulators/games require > analogue control. SDL1 and those using joystick API otherwise would fall in this category. Again, the F310 has a switch to serve both modes. games/sdl-jstest has test binaries for D and X mode that can be used to see what works and what doesn't. [...] [1] https://marc.info/?l=openbsd-ports-cvs=154653811709620=2 -- tfrohw...@fastmail.com PGP Public Key: https://pgp.mit.edu/pks/lookup?op=get=0xE1A22D58D20C6D22
