FAQ/Multimedia: Burning CDs and DVDs
Hi there! I just noticed that the sections on burning CDs and DVDs are no longer present in OpenBSD's FAQ related to multimedia. Is this intentional? I didn't see anything on this on tech@ or misc@... Best, STEFAN pEpkey.asc Description: application/pgp-keys
Solved: thunderbird core-dumps on amd64-current latest with 'pledge "stdio", syscall 87'
For the records: I received a solution by gjones5...@netscape.net: Add the following to the end of /usr/local/lib/thunderbird/defaults/pref/all-openbsd.js // enable pledging the content process pref("security.sandbox.content.level", 1); pref("security.sandbox.pledge.main","stdio rpath wpath cpath inet proc exec prot _exec flock ps sendfd recvfd dns vminfo tty drm unix fattr getpw mcast video"); pref("security.sandbox.pledge.content","stdio rpath wpath cpath inet recvfd send fd prot_exec unix drm ps"); Am 27.10.19 um 19:09 schrieb Stefan Wollny: > Hello! > > I just updated the system and the packages to the latest versions available > on 'ftp.hostserver.de' on two different laptops (Schenker/clavo and Lenovo > Thinkpad T450S). > > Here are the infos from the Schenker: > > $ dmesg | grep Open > OpenBSD 6.6-current (GENERIC.MP) #402: Sat Oct 26 22:53:27 MDT 2019 > > $ pkg_info | grep thunder > thunderbird-68.2.0 Mozilla e-mail, rss and usenet client > thunderbird-i18n-de-68.2.0 de language pack for Thunderbird > > ls -alh /usr/local/bin/thunderbird > -rwxr-xr-x 1 root bin 206K Oct 25 05:33 /usr/local/bin/thunderbird* > > $ thunderbird > Abort trap (core dumped) > > $ dmesg | grep thunder > thunderbird[15793]: pledge "stdio", syscall 87 > thunderbird[69048]: pledge "stdio", syscall 87 > > Could this somehow be specific to my laptops? dmesg from the Schenker below. > > Any other infos needed? > > Any advice welcome. > > TIA. > > Best, > STEFAN > > > OpenBSD 6.6-current (GENERIC.MP) #402: Sat Oct 26 22:53:27 MDT 2019 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 17079074816 (16287MB) > avail mem = 16548741120 (15782MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) > bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 > bios0: Notebook W65_67SZ > acpi0 at bios0: ACPI 5.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT > SSDT DMAR > acpi0: wakeup devices RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) > PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) > XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.24 MHz, 06-3c-03 > 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 > 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 > 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 > 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-C
thunderbird core-dumps on amd64-current latest with 'pledge "stdio", syscall 87'
Hello! I just updated the system and the packages to the latest versions available on 'ftp.hostserver.de' on two different laptops (Schenker/clavo and Lenovo Thinkpad T450S). Here are the infos from the Schenker: $ dmesg | grep Open OpenBSD 6.6-current (GENERIC.MP) #402: Sat Oct 26 22:53:27 MDT 2019 $ pkg_info | grep thunder thunderbird-68.2.0 Mozilla e-mail, rss and usenet client thunderbird-i18n-de-68.2.0 de language pack for Thunderbird ls -alh /usr/local/bin/thunderbird -rwxr-xr-x 1 root bin 206K Oct 25 05:33 /usr/local/bin/thunderbird* $ thunderbird Abort trap (core dumped) $ dmesg | grep thunder thunderbird[15793]: pledge "stdio", syscall 87 thunderbird[69048]: pledge "stdio", syscall 87 Could this somehow be specific to my laptops? dmesg from the Schenker below. Any other infos needed? Any advice welcome. TIA. Best, STEFAN OpenBSD 6.6-current (GENERIC.MP) #402: Sat Oct 26 22:53:27 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16548741120 (15782MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.24 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1),
Re: Ocaml's owl fail to build
Thanks Stuart! Will investigate as you suggested. Best, STEFAN Am 25.10.19 um 15:21 schrieb Stuart Henderson: > On 2019-10-25, Stefan Wollny wrote: >> Ping... >> >> Anyone? >> >> >> Am 22.10.19 um 17:21 schrieb Stefan Wollny: >>> Hi there! >>> >>> Any Ocaml experts around who managed to install 'owl'? Installation of >>> owl fails as 'eigen' and 'open-blas' fail to build. >>> >>> I am running amd64-current. >>> >>> Any suggestions what I might miss??? > > No idea about owl/Ocaml, but you will need to use a C++11 compiler to build > eigen: > >>> # g++ -O3 -std=c++11 -I. -I./unsupported/ -c -fPIC -ansi >>> -Wno-extern-c-compat -Wno-c++11-long-long >>> -Wno-invalid-partial-specialization -Ofast -march=native -mfpmath=sse >>> -funroll-loops -ffast-math eigen_tensor.cpp -o eigen_tensor.o >>> # cc1plus: error: invalid option argument '-Ofast' >>> # cc1plus: error: unrecognized command line option "-std=c++11" >>> # cc1plus: error: unrecognized command line option >>> "-Wno-invalid-partial-specialization" >>> # *** Error 1 in >>> /home/sw/.opam/ocaml-base-compiler/.opam-switch/build/eigen.0.1.4/_build/default/eigen_cpp/lib >>> (Makefile:8 'all') > > It should use c++ (which is clang on amd64), not g++ (old gcc). >
Re: Ocaml's owl fail to build
Ping... Anyone? Am 22.10.19 um 17:21 schrieb Stefan Wollny: > Hi there! > > Any Ocaml experts around who managed to install 'owl'? Installation of > owl fails as 'eigen' and 'open-blas' fail to build. > > I am running amd64-current. > > Any suggestions what I might miss??? > > TIA! > > Best, > STEFAN > > > > 8<~~~ > $ opam switch list > # switch compilerdescription >default ocaml-system.4.07.1 default > → ocaml-base-compiler ocaml-base-compiler.4.09.0 ocaml-base-compiler > > $ opam install owl > The following actions will be performed: > ∗ install eigen 0.1.4 [required by owl] > ∗ install conf-openblas 0.2.0 [required by owl] > ∗ install owl 0.6.0 > = ∗ 3 = > Do you want to continue? [Y/n] Y > > <><> Gathering sources >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><> > [eigen.0.1.4] found in cache > [owl.0.6.0] found in cache > > <><> Processing actions > <><><><><><><><><><><><><><><><><><><><><><><><><><><><> > [ERROR] The compilation of conf-openblas failed at "/bin/sh -exc cc > $CFLAGS test.c -lopenblas". > [ERROR] The compilation of eigen failed at > "/home/sw/.opam/ocaml-base-compiler/bin/dune build -p eigen > eigen_cpp/libeigen_cpp_stubs.a". > > #=== ERROR while compiling eigen.0.1.4 > # > # context 2.0.5 | openbsd/x86_64 | ocaml-base-compiler.4.09.0 | > https://opam.ocaml.org#e785ffef > # path~/.opam/ocaml-base-compiler/.opam-switch/build/eigen.0.1.4 > # command ~/.opam/ocaml-base-compiler/bin/dune build -p eigen > eigen_cpp/libeigen_cpp_stubs.a > # exit-code 1 > # env-file~/.opam/log/eigen-84391-d0f245.env > # output-file ~/.opam/log/eigen-84391-d0f245.out > ### output ### > # make eigen_cpp/lib/libeigen.{a,so} (exit 1) > # (cd _build/default/eigen_cpp/lib && /usr/bin/make) > # g++ -O3 -std=c++11 -I. -I./unsupported/ -c -fPIC -ansi > -Wno-extern-c-compat -Wno-c++11-long-long > -Wno-invalid-partial-specialization -Ofast -march=native -mfpmath=sse > -funroll-loops -ffast-math eigen_tensor.cpp -o eigen_tensor.o > # cc1plus: error: invalid option argument '-Ofast' > # cc1plus: error: unrecognized command line option "-std=c++11" > # cc1plus: error: unrecognized command line option > "-Wno-invalid-partial-specialization" > # *** Error 1 in > /home/sw/.opam/ocaml-base-compiler/.opam-switch/build/eigen.0.1.4/_build/default/eigen_cpp/lib > (Makefile:8 'all') > > > #=== ERROR while compiling conf-openblas.0.2.0 > # > # context 2.0.5 | openbsd/x86_64 | ocaml-base-compiler.4.09.0 | > https://opam.ocaml.org#e785ffef > # path > ~/.opam/ocaml-base-compiler/.opam-switch/build/conf-openblas.0.2.0 > # command /bin/sh -exc cc $CFLAGS test.c -lopenblas > # exit-code 1 > # env-file~/.opam/log/conf-openblas-84391-ad8886.env > # output-file ~/.opam/log/conf-openblas-84391-ad8886.out > ### output ### > # + cc test.c -lopenblas > # test.c:1:10: fatal error: 'cblas.h' file not found > # #include > # ^ > # 1 error generated. > > > > <><> Error report > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > ┌─ The following actions failed > │ λ build conf-openblas 0.2.0 > │ λ build eigen 0.1.4 > └─ > ╶─ No changes have been performed > # Run eval $(opam env) to update the current shell environment > >8~~~ > > $ pkg_info | grep eigen > eigen-1.0.5 lightweight C++ template library for linear algebra > > $ pkg_info | grep blas- > blas-3.8.0p0Basic Linear Algebra Subprograms > cblas-1.0p6 C interface to the BLAS library >
Ocaml's owl fail to build
Hi there! Any Ocaml experts around who managed to install 'owl'? Installation of owl fails as 'eigen' and 'open-blas' fail to build. I am running amd64-current. Any suggestions what I might miss??? TIA! Best, STEFAN 8<~~~ $ opam switch list # switch compilerdescription default ocaml-system.4.07.1 default → ocaml-base-compiler ocaml-base-compiler.4.09.0 ocaml-base-compiler $ opam install owl The following actions will be performed: ∗ install eigen 0.1.4 [required by owl] ∗ install conf-openblas 0.2.0 [required by owl] ∗ install owl 0.6.0 = ∗ 3 = Do you want to continue? [Y/n] Y <><> Gathering sources ><><><><><><><><><><><><><><><><><><><><><><><><><><><><> [eigen.0.1.4] found in cache [owl.0.6.0] found in cache <><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><><><> [ERROR] The compilation of conf-openblas failed at "/bin/sh -exc cc $CFLAGS test.c -lopenblas". [ERROR] The compilation of eigen failed at "/home/sw/.opam/ocaml-base-compiler/bin/dune build -p eigen eigen_cpp/libeigen_cpp_stubs.a". #=== ERROR while compiling eigen.0.1.4 # # context 2.0.5 | openbsd/x86_64 | ocaml-base-compiler.4.09.0 | https://opam.ocaml.org#e785ffef # path~/.opam/ocaml-base-compiler/.opam-switch/build/eigen.0.1.4 # command ~/.opam/ocaml-base-compiler/bin/dune build -p eigen eigen_cpp/libeigen_cpp_stubs.a # exit-code 1 # env-file~/.opam/log/eigen-84391-d0f245.env # output-file ~/.opam/log/eigen-84391-d0f245.out ### output ### # make eigen_cpp/lib/libeigen.{a,so} (exit 1) # (cd _build/default/eigen_cpp/lib && /usr/bin/make) # g++ -O3 -std=c++11 -I. -I./unsupported/ -c -fPIC -ansi -Wno-extern-c-compat -Wno-c++11-long-long -Wno-invalid-partial-specialization -Ofast -march=native -mfpmath=sse -funroll-loops -ffast-math eigen_tensor.cpp -o eigen_tensor.o # cc1plus: error: invalid option argument '-Ofast' # cc1plus: error: unrecognized command line option "-std=c++11" # cc1plus: error: unrecognized command line option "-Wno-invalid-partial-specialization" # *** Error 1 in /home/sw/.opam/ocaml-base-compiler/.opam-switch/build/eigen.0.1.4/_build/default/eigen_cpp/lib (Makefile:8 'all') #=== ERROR while compiling conf-openblas.0.2.0 # # context 2.0.5 | openbsd/x86_64 | ocaml-base-compiler.4.09.0 | https://opam.ocaml.org#e785ffef # path ~/.opam/ocaml-base-compiler/.opam-switch/build/conf-openblas.0.2.0 # command /bin/sh -exc cc $CFLAGS test.c -lopenblas # exit-code 1 # env-file~/.opam/log/conf-openblas-84391-ad8886.env # output-file ~/.opam/log/conf-openblas-84391-ad8886.out ### output ### # + cc test.c -lopenblas # test.c:1:10: fatal error: 'cblas.h' file not found # #include # ^ # 1 error generated. <><> Error report <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> ┌─ The following actions failed │ λ build conf-openblas 0.2.0 │ λ build eigen 0.1.4 └─ ╶─ No changes have been performed # Run eval $(opam env) to update the current shell environment >8~~~ $ pkg_info | grep eigen eigen-1.0.5 lightweight C++ template library for linear algebra $ pkg_info | grep blas- blas-3.8.0p0Basic Linear Algebra Subprograms cblas-1.0p6 C interface to the BLAS library
Re: OpenBSD Project
Am 22.09.19 um 20:52 schrieb Mihai Popescu: >> No. > > Security, privacy or too messy? > Theo's answer was deep going, detailed and terminal. Nothing to add.
s.th. strange happening?
Hi there! As I never did any changes to 'www/squid/Makefile' the following irritates me: /usr/ports $ doas cvs -q up -Pd -A cvs server: conflict: INDEX is modified but no longer in the repository C INDEX M www/squid/Makefile Can some kind soul give me a hint? Anything I should do? TIA. Best, STEFAN
Re: mirror download speed variation => Back to normal
Am 09.01.19 um 17:53 schrieb Stuart Henderson: > On 2019-01-09, Stefan Wollny wrote: >> On 08.01.19 14:24, Mihai Popescu wrote: >>> ... > > I'm currently getting 6.7MByte/s over v6 and 3.95MByte/s over v4 > from ftp.hostserver.de to the UK. So it's not a global problem. > As phessler said, send him traceroute and your source IP offlist. > > Apparently they (phessler@/benno@) have taken care of the issue. This morning download rates are back to what I usually had in the past. THANK YOU very much! Well apprecciated. Best, STEFAN
Re: mirror download speed variation
On 08.01.19 14:24, Mihai Popescu wrote: > Hi, > > I use to retrieve my install sets from a mirror, after I start the > install procedure with minirootxx.fs > > Since the mirrors in my country are updating late and they have some > problems in doing it right, I used ftp.hostserver.de. The download was > working fine, something around 3MBps. This mirror started few days ago > to provide me only with 64KBps constantly, no matter if i do http or > https. > > I tried cdn.openbsd.org too, the download is super fast for me, like > 30MBps. Still, sometimes it drops to 64KBps too, and stays there. I've > read some articles about CDN networks, but I am not able to see the > big picture. > > So, I still have two questions about mirrors: > Can a mirror limit your download speed ? > Do a CDN url point to an existing mirror, or is it a diffeent server? > > Thank you. I can confirm Mihai's observation: http://ftp.hostserver.de is remarkable slow for 2~3 weeks, even from within Frankfurt. From memory I'd say from around the week before xmas download rates dropped to 20kb/s what usually was ~2mb/s. The Austrian mirror gave me this morning ~4mb/s! I fetch like so: export SERVER=http://ftp2.eu.openbsd.org/pub/OpenBSD/snapshots export ARCH=amd64 export VERSION=64wget -4 --no-proxy --no-cache --no-cookies --backups=2 \ $SERVER/$ARCH/BOOT{IA32,X64}.EFI \ $SERVER/$ARCH/INSTALL.$ARCH \ $SERVER/$ARCH/BUILDINFO \ $SERVER/$ARCH/index.txt \ $SERVER/$ARCH/SHA256{,.sig} \ $SERVER/$ARCH/bsd{,.mp,.rd} \ $SERVER/$ARCH/{base,comp,man}$VERSION.tgz \ $SERVER/$ARCH/x{base,font,serv,share}$VERSION.tgz
Re: Key-based FDE /w UEFI fails => SUCCESS
Am 02.12.18 um 13:26 schrieb Stefan Wollny: > Am 30.11.18 um 16:38 schrieb Joel Sing: >> On Thursday 29 November 2018 20:38:23 Stefan Wollny wrote: [ ..] > SUCCESS! > > With this boot params the system came up as expected. > > THANK YOU once again for caring and your precious time! Much appreciated. > > Let me know if I shall do some tests prior to taking the machine to > production. > > Best, > STEFAN > Just an additional note: After having successfully reinstalled from by backup rebooting again required to set 'boot sr0a:/bsd'. Maybe this is somehow related to this https://marc.info/?l=openbsd-misc&m=154341622617488&w=2 and/or this https://marc.info/?l=openbsd-misc&m=154332857825943&w=2 ???
Re: Key-based FDE /w UEFI fails => SUCCESS
Am 30.11.18 um 16:38 schrieb Joel Sing: > On Thursday 29 November 2018 20:38:23 Stefan Wollny wrote: >> Hi there! >> >> I need help / advice with a fresh install onto a Thinkpad T450s which I >> recently bought on eBay. >> >> The system starts with UEFI enabled and was running fine with a rather >> small SSD without FDE. dmesg from some recent posts may be found. >> >> I followed the steps as given in the FAQ >> (http://www.openbsd.org/faq/faq14.html#softraid) with a new, larger SSD >> and the key disk both initialized with >> 'fdisk -iy -g -b 960 sd0' (and '... sd2' for the key disk). >> >> On both disks I created a 'a'-partion with type RAID as zero'd the first >> blocks. >> >> softraid is activated with 'bioctl -c C -k sd2a -l sd0a softraid0'. >> >> The installation was without noticable deviation to a non-FDE installation. >> >> The layout is identical to an other FDE-secured laptop which starts with >> BIOS: >> sd0a / >> sd0b swap >> sd0d /tmp >> sd0e /var >> sd0f /usr >> sd0g /usr/local >> sd0h /home >> (As this is a 1TB-SSD each partition has lots of capacity...) >> >> Yet after rebooting the first time I get the following: >> >> probing: pc0 mem[352K 204K 3256M 4832M] >> disk: hd0 hd1 sr0* >> >>>> OpenBSD/amd64 BOOTS64 3.40 >> >> open(hd0a:/etc/boot.con f): Invalid argument >> boot> >> cannot open hd0a:/etc/random.seed: Invalid argument >> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >> failed(22). will try /bsd >> boot> >> cannot open hd0a:/etc/random.seed: Invalid argument >> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >> failed(22). will try /bsd >> Turning timeout off. >> boot> >> >> At this point I am lost. Tried to google for any information that makes >> sense but only found very old posts (from 2011 and older) which didn't >> provide hints on how to proceed. >> >> Anybody with a clue? > > The 'sr0*' in the above output shows that the boot loader found the softraid > volume and believes that it is bootable. What should have happened is that > the > boot loader identified that the disk you booted from is part of the softraid > volume and switched to sr0 as the boot device - for some reason it did not > and > continued to try to boot from hd0 instead. > > You should be able to boot by manually specifying: > > boot sr0a:/bsd > > at the boot> prompt. > > If that works we'll have to track down the reason why the automatic switching > of the boot device failed (line 146 of sys/arch/amd64/stand/libsa/dev_i386.c > and the code that leads up to it). > SUCCESS! With this boot params the system came up as expected. THANK YOU once again for caring and your precious time! Much appreciated. Let me know if I shall do some tests prior to taking the machine to production. Best, STEFAN
Key-based FDE /w UEFI fails
Hi there! I need help / advice with a fresh install onto a Thinkpad T450s which I recently bought on eBay. The system starts with UEFI enabled and was running fine with a rather small SSD without FDE. dmesg from some recent posts may be found. I followed the steps as given in the FAQ (http://www.openbsd.org/faq/faq14.html#softraid) with a new, larger SSD and the key disk both initialized with 'fdisk -iy -g -b 960 sd0' (and '... sd2' for the key disk). On both disks I created a 'a'-partion with type RAID as zero'd the first blocks. softraid is activated with 'bioctl -c C -k sd2a -l sd0a softraid0'. The installation was without noticable deviation to a non-FDE installation. The layout is identical to an other FDE-secured laptop which starts with BIOS: sd0a/ sd0bswap sd0d/tmp sd0e/var sd0f/usr sd0g/usr/local sd0h/home (As this is a 1TB-SSD each partition has lots of capacity...) Yet after rebooting the first time I get the following: probing: pc0 mem[352K 204K 3256M 4832M] disk: hd0 hd1 sr0* >> OpenBSD/amd64 BOOTS64 3.40 open(hd0a:/etc/boot.con f): Invalid argument boot> cannot open hd0a:/etc/random.seed: Invalid argument booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try /bsd boot> cannot open hd0a:/etc/random.seed: Invalid argument booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try /bsd Turning timeout off. boot> At this point I am lost. Tried to google for any information that makes sense but only found very old posts (from 2011 and older) which didn't provide hints on how to proceed. Anybody with a clue? TIA. Best, STEFAN
Re: latest iridium-browser on amd64-current => solved
On 09.11.18 10:25, Stefan Wollny wrote: [ ... ] Thank you, robert@! Iridium is fine again.
Re: latest iridium-browser on amd64-current core dumps
Additional info from gdb: [ ... ] > Loaded symbols for /usr/local/lib/libgmp.so.10.0 > Reading symbols from /usr/libexec/ld.so...done. > Loaded symbols for /usr/libexec/ld.so > #0 0x1e4c44b648e5 in ChromeMain () from /usr/local/iridium/iridium > (gdb) bt #0 0x134869f648e5 in ChromeMain () from /usr/local/iridium/iridium #1 0x13486c445689 in ChromeMain () from /usr/local/iridium/iridium #2 0x13486c44fc52 in ChromeMain () from /usr/local/iridium/iridium #3 0x13486c444ffe in ChromeMain () from /usr/local/iridium/iridium #4 0x134869f6328b in ChromeMain () from /usr/local/iridium/iridium #5 0x134869f63056 in _start () from /usr/local/iridium/iridium #6 0x in ?? () (gdb) l 1 /* $OpenBSD: boot.c,v 1.16 2018/10/23 04:01:45 guenther Exp $ */ 2 3 /* 4* Copyright (c) 1998 Per Fogelstrom, Opsycon AB 5* 6* Redistribution and use in source and binary forms, with or without 7* modification, are permitted provided that the following conditions 8* are met: 9* 1. Redistributions of source code must retain the above copyright 10 *notice, this list of conditions and the following disclaimer. (gdb) bt full #0 0x134869f648e5 in ChromeMain () from /usr/local/iridium/iridium No symbol table info available. #1 0x13486c445689 in ChromeMain () from /usr/local/iridium/iridium No symbol table info available. #2 0x13486c44fc52 in ChromeMain () from /usr/local/iridium/iridium No symbol table info available. #3 0x13486c444ffe in ChromeMain () from /usr/local/iridium/iridium No symbol table info available. #4 0x134869f6328b in ChromeMain () from /usr/local/iridium/iridium No symbol table info available. #5 0x134869f63056 in _start () from /usr/local/iridium/iridium No symbol table info available. #6 0x in ?? () No symbol table info available. (gdb) f #0 0x134869f648e5 in ChromeMain () from /usr/local/iridium/iridium (gdb) info f Stack level 0, frame at 0x7f7f62e0: rip = 0x134869f648e5 in ChromeMain; saved rip 0x13486c445689 called by frame at 0x7f7f6400 Arglist at 0x7f7f62c8, args: Locals at 0x7f7f62c8, Previous frame's sp is 0x7f7f62e0 Saved registers: rbp at 0x7f7f62d0, rip at 0x7f7f62d8 (gdb) Any other info I can provide? Best, STEFAN
Re: latest iridium-browser on amd64-current core dumps
Quick update: Am 09.11.18 um 10:25 schrieb Stefan Wollny: [ ... ] > > Will this be solved with the next snapshots? > Short answer: No! $ dmesg | grep Open OpenBSD 6.4-current (GENERIC.MP) #427: Fri Nov 9 01:09:51 MST 2018 (new full dmesg at the end) $ pkg_info | grep iridium iridium-2018.11.70 Iridium browser $ iridium --version Iridium 2018.11 $ /usr/local/bin/iridium [1109/150939.014189:ERROR:icu_util.cc(172)] Invalid file descriptor to ICU data received. Trace/BPT trap (core dumped) $ doas gdb /usr/local/iridium/iridium iridium.core [ ... ] Core was generated by `iridium'. Program terminated with signal 5, Trace/breakpoint trap. Reading symbols from /usr/lib/libpthread.so.25.1...done. Loaded symbols for /usr/lib/libpthread.so.25.1 Loaded symbols for /usr/local/iridium/iridium Reading symbols from /usr/X11R6/lib/libX11.so.16.1...done. Loaded symbols for /usr/X11R6/lib/libX11.so.16.1 Reading symbols from /usr/X11R6/lib/libX11-xcb.so.2.0...done. Loaded symbols for /usr/X11R6/lib/libX11-xcb.so.2.0 Reading symbols from /usr/X11R6/lib/libxcb.so.4.0...done. Loaded symbols for /usr/X11R6/lib/libxcb.so.4.0 Reading symbols from /usr/X11R6/lib/libXcomposite.so.4.0...done. Loaded symbols for /usr/X11R6/lib/libXcomposite.so.4.0 Reading symbols from /usr/X11R6/lib/libXcursor.so.5.0...done. Loaded symbols for /usr/X11R6/lib/libXcursor.so.5.0 Reading symbols from /usr/X11R6/lib/libXdamage.so.4.0...done. Loaded symbols for /usr/X11R6/lib/libXdamage.so.4.0 Reading symbols from /usr/X11R6/lib/libXext.so.13.0...done. Loaded symbols for /usr/X11R6/lib/libXext.so.13.0 Reading symbols from /usr/X11R6/lib/libXfixes.so.6.0...done. Loaded symbols for /usr/X11R6/lib/libXfixes.so.6.0 Reading symbols from /usr/X11R6/lib/libXi.so.12.1...done. Loaded symbols for /usr/X11R6/lib/libXi.so.12.1 Reading symbols from /usr/X11R6/lib/libXrender.so.6.0...done. Loaded symbols for /usr/X11R6/lib/libXrender.so.6.0 Reading symbols from /usr/X11R6/lib/libXtst.so.11.0...done. Loaded symbols for /usr/X11R6/lib/libXtst.so.11.0 Reading symbols from /usr/local/lib/libgmodule-2.0.so.4200.7...done. Loaded symbols for /usr/local/lib/libgmodule-2.0.so.4200.7 Reading symbols from /usr/local/lib/libgobject-2.0.so.4200.7...done. Loaded symbols for /usr/local/lib/libgobject-2.0.so.4200.7 Reading symbols from /usr/local/lib/libglib-2.0.so.4201.0...done. Loaded symbols for /usr/local/lib/libglib-2.0.so.4201.0 Reading symbols from /usr/local/lib/libintl.so.6.0...done. Loaded symbols for /usr/local/lib/libintl.so.6.0 Reading symbols from /usr/local/lib/libpcre.so.3.0...done. Loaded symbols for /usr/local/lib/libpcre.so.3.0 Reading symbols from /usr/local/lib/libsmime3.so.53.0...done. Loaded symbols for /usr/local/lib/libsmime3.so.53.0 Reading symbols from /usr/local/lib/libnss3.so.53.0...done. Loaded symbols for /usr/local/lib/libnss3.so.53.0 Reading symbols from /usr/local/lib/libnssutil3.so.53.0...done. Loaded symbols for /usr/local/lib/libnssutil3.so.53.0 Reading symbols from /usr/local/lib/libplds4.so.24.0...done. Loaded symbols for /usr/local/lib/libplds4.so.24.0 Reading symbols from /usr/local/lib/libplc4.so.24.0...done. Loaded symbols for /usr/local/lib/libplc4.so.24.0 Reading symbols from /usr/local/lib/libnspr4.so.24.0...done. Loaded symbols for /usr/local/lib/libnspr4.so.24.0 Reading symbols from /usr/local/lib/libcups.so.6.4...done. Loaded symbols for /usr/local/lib/libcups.so.6.4 Reading symbols from /usr/local/lib/libgio-2.0.so.4200.7...done. Loaded symbols for /usr/local/lib/libgio-2.0.so.4200.7 Reading symbols from /usr/lib/libexpat.so.12.0...done. Loaded symbols for /usr/lib/libexpat.so.12.0 Reading symbols from /usr/local/lib/libdbus-1.so.11.2...done. Loaded symbols for /usr/local/lib/libdbus-1.so.11.2 Reading symbols from /usr/lib/libevent.so.4.1...done. Loaded symbols for /usr/lib/libevent.so.4.1 Reading symbols from /usr/lib/libm.so.10.1...done. Loaded symbols for /usr/lib/libm.so.10.1 Reading symbols from /usr/lib/libz.so.5.0...done. Loaded symbols for /usr/lib/libz.so.5.0 Reading symbols from /usr/local/lib/libuuid.so.14.0...done. Loaded symbols for /usr/local/lib/libuuid.so.14.0 Reading symbols from /usr/X11R6/lib/libdrm.so.7.6...done. Loaded symbols for /usr/X11R6/lib/libdrm.so.7.6 Reading symbols from /usr/X11R6/lib/libXss.so.6.0...done. Loaded symbols for /usr/X11R6/lib/libXss.so.6.0 Reading symbols from /usr/X11R6/lib/libXrandr.so.7.1...done. Loaded symbols for /usr/X11R6/lib/libXrandr.so.7.1 Reading symbols from /usr/local/lib/libatk-1.0.so.21809.2...done. Loaded symbols for /usr/local/lib/libatk-1.0.so.21809.2 Reading symbols from /usr/local/lib/libatk-bridge-2.0.so.0.0...done. Loaded symbols for /usr/local/lib/libatk-bridge-2.0.so.0.0 Reading symbols from /usr/local/lib/libatspi.so.0.2...done. Loaded symbols for /usr/local/lib/libatspi.so.0.2 Reading symbols from /usr/local/lib/libpangocairo-1.0.so.3800.1...done. Loaded symbols for /usr/local/lib/libpangocairo-1.0.so.3800.1 Reading symbols from /usr/local/l
latest iridium-browser on amd64-current core dumps
Unfortunatelly I have to meet deadlines, can't investigate further into the following: $ pkg_info | grep iridium iridium-2018.11.70 Iridium browser $ /usr/local/bin/iridium [1109/094309.877362:ERROR:icu_util.cc(172)] Invalid file descriptor to ICU data received. Trace/BPT trap (core dumped) This happens disregarding if started with or without "--enable-unveil". Will this be solved with the next snapshots? (dmesg below) Sorry - but today I am unable to provide more information. Best, STEFAN OpenBSD 6.4-current (GENERIC.MP) #425: Sun Nov 4 21:32:53 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16552189952 (15785MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.33 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 120 degC acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x acpicmos0 at acpi0 "PNPC000" at acpi0 not configured acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: LID0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "BAT" serial 0001 type LION oem "Notebook" "PNP0C14" at acpi0 not configured acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: LCD0 cpu0: Enhanced
Re: iridium-browser + unveil
Am 08.11.18 um 12:47 schrieb Florian Obser: > The point of unveil in chrome is that it can't exfiltrate your ssh > private key. Got it! Thank you for making things clear.
Re: iridium-browser + unveil
Am 08.11.18 um 09:03 schrieb Stefan Wollny: > Hi there, > > just a little nit with the iridium-browser unveiled: > > I changed the 'exec' command in /usr/local/bin/iridium like so: > - LANG=${_l} exec "/usr/local/iridium/iridium" "${@}" > + LANG=${_l} exec "/usr/local/iridium/iridium" "--enable-unveil" "${@}" > > With this change I can browse the web as before. BUT: My startpage is a > html-file in the users home directory containing a huge collection of > links to web sites. I use this file at home and at work where I am > forced to use the most popular unsafe OS. With iridium unveiled this > page is no longer accessible instead I get 'ERR_FILE_NOT_FOUND'. > > Switching back to the exec without "--enable-unveil" and iridium finds > the file again. Easily reproducible. > > With other browsers (e.g. FF, otter, netsurf, links+) this particular > file is accessible. No reason not to enable unveil on iridium in > particular as it just has been updated (in ports). > Found an easy solution: While access to the user's home directory is not permitted, access to the subfolders _is_ allowed. Simply copied that particular file to ~/Downloads/, changed the path in iridium's settings and we're back to familiar operations. :-) Now: How to give permission to access my home directory?
iridium-browser + unveil
Hi there, just a little nit with the iridium-browser unveiled: I changed the 'exec' command in /usr/local/bin/iridium like so: - LANG=${_l} exec "/usr/local/iridium/iridium" "${@}" + LANG=${_l} exec "/usr/local/iridium/iridium" "--enable-unveil" "${@}" With this change I can browse the web as before. BUT: My startpage is a html-file in the users home directory containing a huge collection of links to web sites. I use this file at home and at work where I am forced to use the most popular unsafe OS. With iridium unveiled this page is no longer accessible instead I get 'ERR_FILE_NOT_FOUND'. Switching back to the exec without "--enable-unveil" and iridium finds the file again. Easily reproducible. With other browsers (e.g. FF, otter, netsurf, links+) this particular file is accessible. No reason not to enable unveil on iridium in particular as it just has been updated (in ports). Best, STEFAN
Re: Problem with keyboard layout
PROBLEM SOLVED! :-) Am 24.10.18 um 09:49 schrieb Matthieu Herrb: > On Wed, Oct 24, 2018 at 08:41:41AM +0200, Stefan Wollny wrote: >> Am 24.10.18 um 07:40 schrieb Matthieu Herrb: >>> On Tue, Oct 23, 2018 at 01:19:18PM +0200, Stefan Wollny wrote: >>>> Am 22.10.18 um 10:45 schrieb Stefan Wollny: >>>>> Am 10/22/18 um 9:57 AM schrieb Stefan Wollny: >>>>> [ ... ] >>>>>> >>>>>> $ cat /etc/wsconsctl.conf | grep encoding >>>>>> keyboard.encoding=de# use different keyboard encoding >>>>>> >>>>>> Yet this setting seems not to be recognized: >>>>>> $ doas wsconsctl | grep encoding >>>>>> keyboard.encoding=unknown_0 >>> >>> This probably means that you have some other wsconsctl commands that >>> modify the layout after the initial switch to the 'de' layout. >>> >> >> Hi Matthieu, >> >> thanks for caring. >> >> For the time being I found an intermediate solution: Instead using >> Fluxbox as window manager I use LXQt and within changed all >> localisations to 'Germany' which survived a reboot. > > That's probably because LXQt saves the xkb settings in your session > and restores them. >> >> What puzzled me is the fact that I did not (knowingly) changed any >> settings which might explain this behaviour. The first line in the >> '.xsession'-file used to be >> export LANG=de_DE.UTF-8 >> and with this I had German keyboard layout when entering the password >> (luckily right now no special characters different to English layout). >> At present (due to my experimental changes) I have >> export LC_CTYPE="en_US.UTF-8" >> and thus English is expected when entering username & password. > > The locale settings (LC_CTYPE / LANG) don't change the keyboard > layout, unless you have something in your .profile, .xsession or > similar files that change it. > >> Which other process / program might influence wscons? > > I don't know. But as long as on X startup you have > keyboard.encoding=unknown_0 you will get the us layout by default. > > If you haven't added anything to /etc/rc.local or any package that > installs a custom rc.d script fiddling with wsconsctl, I've no idea > why your machines ends up with the unknown_0 layout (which means > KB_USER internally). > Hi Matthieu, thank you very much for guiding me! With your explanation I took special care at the messages on the screen at startup, searching for any hints what might influence the keyboard settings. Obviously I must have accidentially deleted within "/etc/sysctl.conf" the '#' in front of the line machdep.forceukbd=1 which I once had added as a reminder. Recommenting the line solved the issue. As noone else had this problem it must have been me. Thanks again and sorry for the noise! Best, STEFAN
Re: Problem with keyboard layout
Am 24.10.18 um 07:40 schrieb Matthieu Herrb: > On Tue, Oct 23, 2018 at 01:19:18PM +0200, Stefan Wollny wrote: >> Am 22.10.18 um 10:45 schrieb Stefan Wollny: >>> Am 10/22/18 um 9:57 AM schrieb Stefan Wollny: >>> [ ... ] >>>> >>>> $ cat /etc/wsconsctl.conf | grep encoding >>>> keyboard.encoding=de# use different keyboard encoding >>>> >>>> Yet this setting seems not to be recognized: >>>> $ doas wsconsctl | grep encoding >>>> keyboard.encoding=unknown_0 > > This probably means that you have some other wsconsctl commands that > modify the layout after the initial switch to the 'de' layout. > Hi Matthieu, thanks for caring. For the time being I found an intermediate solution: Instead using Fluxbox as window manager I use LXQt and within changed all localisations to 'Germany' which survived a reboot. What puzzled me is the fact that I did not (knowingly) changed any settings which might explain this behaviour. The first line in the '.xsession'-file used to be export LANG=de_DE.UTF-8 and with this I had German keyboard layout when entering the password (luckily right now no special characters different to English layout). At present (due to my experimental changes) I have export LC_CTYPE="en_US.UTF-8" and thus English is expected when entering username & password. Which other process / program might influence wscons? Best, STEFAN
Re: Problem with keyboard layout
Am 22.10.18 um 10:45 schrieb Stefan Wollny: > Am 10/22/18 um 9:57 AM schrieb Stefan Wollny: > [ ... ] >> >> $ cat /etc/wsconsctl.conf | grep encoding >> keyboard.encoding=de# use different keyboard encoding >> >> Yet this setting seems not to be recognized: >> $ doas wsconsctl | grep encoding >> keyboard.encoding=unknown_0 >> > [ ... ] > Additional information: > This issue seems to be related to the X server. Initially I noticed this > behaviour when starting with xenodm. Switching to a console outside of X > gives me the expected German keyboard layout. The same if I disable > xenodm in /etc/rc.conf.local and start OpenBSD into a console: Initially > I have the German keyboard layout but once I start X via 'startx' I get > the US layout. > *At least I know now where to find the symbols blindly :/ * > > Thus here is the Xorg.0.log which has the line > Option "XkbLayout" "us" > close to the end. > Unfortunately the issue persists with the last published version of amd64/current. New dmesg and Xorg.0.log below. Anyone with a clue what might be cause of wsconsctl not using the encoding as defined in the conf-file? unveil(2)-related? Any other information I should provide? TIA. Best, STEFAN OpenBSD 6.4-current (GENERIC.MP) #380: Mon Oct 22 20:06:50 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16552185856 (15785MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.33 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.85 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.85 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.85 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4
Re: Problem with keyboard layout
Am 10/22/18 um 9:57 AM schrieb Stefan Wollny: [ ... ] > > $ cat /etc/wsconsctl.conf | grep encoding > keyboard.encoding=de# use different keyboard encoding > > Yet this setting seems not to be recognized: > $ doas wsconsctl | grep encoding > keyboard.encoding=unknown_0 > [ ... ] Additional information: This issue seems to be related to the X server. Initially I noticed this behaviour when starting with xenodm. Switching to a console outside of X gives me the expected German keyboard layout. The same if I disable xenodm in /etc/rc.conf.local and start OpenBSD into a console: Initially I have the German keyboard layout but once I start X via 'startx' I get the US layout. *At least I know now where to find the symbols blindly :/ * Thus here is the Xorg.0.log which has the line Option "XkbLayout" "us" close to the end. [ 536.726] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [ 536.726]linear framebuffer access unavailable [ 536.740] (--) Using wscons driver on /dev/ttyC4 [ 536.748] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 536.748] X Protocol Version 11, Revision 0 [ 536.748] Build Operating System: OpenBSD 6.4 amd64 [ 536.748] Current Operating System: OpenBSD asterix.heim.netz 6.4 GENERIC.MP#376 amd64 [ 536.748] Build Date: 21 October 2018 11:05:48PM [ 536.748] [ 536.748] Current version of pixman: 0.34.0 [ 536.749]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 536.749] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 536.749] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 22 10:32:24 2018 [ 536.749] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [ 536.749] (==) No Layout section. Using the first Screen section. [ 536.749] (==) No screen section available. Using defaults. [ 536.749] (**) |-->Screen "Default Screen Section" (0) [ 536.749] (**) | |-->Monitor "" [ 536.749] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 536.749] (==) Automatically adding devices [ 536.749] (==) Automatically enabling devices [ 536.749] (==) Not automatically adding GPU devices [ 536.749] (==) Max clients allowed: 256, resource mask: 0x1f [ 536.749] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [ 536.749] (==) ModulePath set to "/usr/X11R6/lib/modules" [ 536.749] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [ 536.749] (II) Loader magic: 0x1c454c971000 [ 536.749] (II) Module ABI versions: [ 536.749]X.Org ANSI C Emulation: 0.4 [ 536.749]X.Org Video Driver: 23.0 [ 536.749]X.Org XInput driver : 24.1 [ 536.749]X.Org Server Extension : 10.0 [ 536.749] (--) PCI:*(0:0:2:0) 8086:0416:1558:0655 rev 6, Mem @ 0xf780/4194304, 0xe000/268435456, I/O @ 0xf000/64 [ 536.749] (II) LoadModule: "glx" [ 536.750] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [ 536.752] (II) Module glx: vendor="X.Org Foundation" [ 536.752]compiled for 1.19.6, module version = 1.0.0 [ 536.752]ABI class: X.Org Server Extension, version 10.0 [ 536.752] (==) Matched modesetting as autoconfigured driver 0 [ 536.752] (==) Assigned the driver to the xf86ConfigLayout [ 536.752] (II) LoadModule: "modesetting" [ 536.752] (II) Loading /usr/X11R6/lib/modules/drivers/modesetting_drv.so [ 536.752] (II) Module modesetting: vendor="X.Org Foundation" [ 536.752]compiled for 1.19.6, module version = 1.19.6 [ 536.752]Module class: X.Org Video Driver [ 536.752]ABI class: X.Org Video Driver, version 23.0 [ 536.752] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 536.753] (**) modeset(0): claimed PCI slot 0@0:2:0 [ 536.753] (II) modeset(0): using default device [ 536.753] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 536.753] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 536.753] (==) modeset(0): RGB weight 888 [ 536.753] (==) modeset(0): Default visual is TrueColor [ 536.753] (II)
Problem with keyboard layout
Hi there! I have reported this a few days ago on bugs but the issue seemed to be solved with amd64/current as of Sunday morning but reappeared on Sunday afternoons version (German time). System is OpenBSD 6.4-current (GENERIC.MP) #375: Sun Oct 21 09:29:13 MDT 2018 (full dmesg at the end) $ cat .profile | grep LC export LC_CTYPE="de_DE.UTF-8" ~ $ locale LANG=de_DE.UTF-8 LC_COLLATE="de_DE.UTF-8" LC_CTYPE=de_DE.UTF-8 LC_MONETARY="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_ALL= $ cat /etc/wsconsctl.conf | grep encoding keyboard.encoding=de# use different keyboard encoding Yet this setting seems not to be recognized: $ doas wsconsctl | grep encoding keyboard.encoding=unknown_0 Trying to do $ doas wsconsctl keyboard.encoding=de drops the system into ddb without access to the keyboard (thus it is not possible to type 'trace'... ) Is this s.th. known? How to proceed? Best, STEFAN OpenBSD 6.4-current (GENERIC.MP) #375: Sun Oct 21 09:29:13 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16552185856 (15785MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.31 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.83 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.83 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1)
Re: pf.conf: identifying a specific user from dhcpd-table
Am 10.10.18 um 14:58 schrieb Peter N. M. Hansteen: > On Wed, Oct 10, 2018 at 02:48:24PM +0200, Stefan Wollny wrote: >> >> I'd like to set up PF to forward this port (25565) without a pre-defined >> IP as macro as the dhcpd.conf has a line defining tables for abandoned >> ("-A"), changed ("-C") and present leases ("-L"). According to man >> dhcpd(8) those tables may be used with PF. But how??? I couldn't find >> examples. >> >> Do I have to tell PF about these tables in pf.conf? Or don't I need >> these tables at all? > > You do need to include the tables in your pf.conf. I'm a bit surprised > the example at https://home.nuug.no/~peter/pftutorial/#33 did not show up in > your search. > > - P > YES - this is exactly what I've been looking for! (I use Google via 'startpage.com' - maybe this makes a difference???) Thank you very much, Peter. BTW: Am I this blind that I oversaw this in your book??? I had it with me on the train yesterday but I didn't see this solution. Will take a 20th look tonight. 'Thank you' again for so much help here on the list, but as well for the fine book! Best, STEFAN
pf.conf: identifying a specific user from dhcpd-table
Hi there! I've google'd quite a while and read the FAQ and many man-pages - but I didn't find an example for my pf.conf (or simply overlooked it...): The system is amd64-current. The client is Win7-laptop serving as Minecraft-server, thus port 25565 needs to be forwarded but IP may change. I have set up OpenBSD as firewall-router serving additionally as dhcpd-server plus running a transparent squid. IP-forwarding is set in /etc/sysctl. Basically everything is running fine, my users surf the net and send/receive mail. Just that the other kids cannot reach my son's Minecraft-server on the inside from the outside. I could assign a static address to this laptop and use this address setting up a specific rule for this one port. But this is not the way I'd prefer to go. I'd like to set up PF to forward this port (25565) without a pre-defined IP as macro as the dhcpd.conf has a line defining tables for abandoned ("-A"), changed ("-C") and present leases ("-L"). According to man dhcpd(8) those tables may be used with PF. But how??? I couldn't find examples. Do I have to tell PF about these tables in pf.conf? Or don't I need these tables at all? What would the syntax actually be for the dhcpd-client (e.g.'enderman'), s.th like the following tries? pass on $ext_if from $int_if:peer to any binat-to $ext_if port 25565 This is not specific to client 'enderman'... another try: pass out on $ext_if inet from $int_if to any \ nat-to enderman:peer static-port pass in on $ext_if inet from any to $int_if rdr-to enderman:peer This rule is not specific to port 25565, though. Please help - I am pretty confused... TIA. Best, STEFAN
Parse error
Hi there! Running on amd64-current: $ dmesg | grep Open OpenBSD 6.4-beta (GENERIC.MP) #328: Wed Sep 26 22:29:16 MDT 2018 Switched to /usr/ports and did: $ doas make clean I got: [ ... ] ===> lang/gforth ===> Cleaning for gforth-0.7.3p3 ===> lang/ghc *** Parse error in /usr/ports/lang/ghc: Need an operator in 'amd64' (Makefile:61) *** Parse error: Need an operator in '.endfor' (Makefile:65) ===> Exiting lang/ghc with an error *** Error 1 in lang (/usr/ports/infrastructure/mk/bsd.port.subdir.mk:178 'clean') ===> Exiting lang with an error *** Error 1 in /usr/ports (infrastructure/mk/bsd.port.subdir.mk:178 'clean') Did I s.th. wrong or is this a bug? $ ls -alh /usr/ports/lang/ghc/ total 64 drwxrwxr-x6 wsrc 512B Jul 9 13:00 . drwxrwxr-x 115 wsrc 3.0K Sep 25 21:01 .. drwxrwxr-x2 wsrc 512B Jul 9 13:07 CVS -rw-rw-r--1 wsrc 8.3K Aug 21 00:45 Makefile -rw-rw-r--1 wsrc 929B Mar 31 01:16 distinfo drwxrwxr-x3 wsrc 512B Jul 9 13:00 files -rw-rw-r--1 wsrc 4.4K Jan 22 2018 ghc.port.mk drwxrwxr-x3 wsrc 1.0K Jul 9 13:00 patches drwxrwxr-x3 wsrc 512B Jul 9 13:00 pkg Best, STEFAN
Re: WiFi: Join + wpa_supplicant
Am 09/05/18 um 14:37 schrieb Stefan Sperling: Hi Stefan! > On Wed, Sep 05, 2018 at 01:39:53PM +0200, Stefan Wollny wrote: >> After a 'sh /etc/netstart' 'ifconfig gives me the following: >> >> iwm0: flags=8943 mtu 1500 >> lladdr 80:fa:5b:14:xx:yy >> index 1 priority 4 llprio 3 >> trunk: trunkdev trunk0 >> groups: wlan >> media: IEEE802.11 autoselect (HT-MCS0 mode 11n) >> status: no network >> ieee80211: join chan 36 bssid 84:b2:61:96:aa:bb 83% >> wpaprotos wpa2 wpaakms 802.1x wpaciphers ccmp wpagroupcipher ccmp >> ... >> trunk0: flags=8843 mtu 1500 >> lladdr 80:fa:5b:14:xx:yy >> index 7 priority 0 llprio 3 >> trunk: trunkproto failover >> trunkport iwm0 >> trunkport re0 master >> groups: trunk >> media: Ethernet autoselect >> status: no carrier >> >> Only after I had commented the join-line for this network I was able to >> reattach to my mobile phone's net. > > Let me guess: Your mobile phone is on a 2 GHz channel (1-13)? BINGO! > > If that is true, then the AP on channel 36 (5 GHz) with good RSSI (83%) > will always win because this is how join was taught to make decisions: > > * Given two APs, determine the "better" one of the two. > * We compute a score based on the following attributes:o > * > * crypto: wpa2 > wpa1 > wep > open > * band: 5 GHz > 2 GHz provided 5 GHz rssi is above threshold > * rssi: rssi1 > rssi2 as a numeric comparison with a slight > * disadvantage for 2 GHz APs > * > * Crypto carries most weight, followed by band, followed by rssi. > Another fine example of OpenBSD's philosophy of "sane defaults"! >> Attaching to this particular net would be helpful - saves some time >> avoiding workaraounds... > > You can use 'ifconfig iwm0 nwid phone' to override auto-join decisions > and always attach to a network called 'phone'. To re-enable automatic > network selection you can use: ifconfig iwm0 -nwid > Thank you for the hint - I have tried it before but did s.th. wrong as now it "just works". Best, STEFAN
Re: WiFi: Join + wpa_supplicant
Am 09/05/18 um 13:05 schrieb Peter Hessler: > On 2018 Sep 05 (Wed) at 12:12:05 +0200 (+0200), Stefan Wollny wrote: > :Hi there, > : > :I am a little bit confused: Do I read the docs correct assuming that > :defining a join-list in /etc/hostname. and wpa_supplicant are > :mutually exclusive? > : > :I have set up a join-list and now I need to attach to a network where I > :can only login with credetials "user" and "user-password"... > : > :TIA. > : > :Kind regards, > :STEFAN > : > > Hi Stefan > > While they are not mutually exclusive, more work will need to be done in > wpa_supplicant to make this a transparent exercise. While I'm not a > regular user of wpa_supplicant, if you restart wpa_supplicant once you > are connected to an 802.1X network it should work. > > Hi Peter, thank you for your reply - unfortunately the system does not connect. I have set up networks via trunk-interface with hostname.iwm0 having the join-list. This "just works" (well done, btw!). After setting up the wpa_supplicant in the rc.d-file (changed the default ath0 to iwm0) and wpa_supplicant.conf (with the applicable credentials) I added to hostname.iwm0 the following: join wpa wpaakms 802.1x After a 'sh /etc/netstart' 'ifconfig gives me the following: iwm0: flags=8943 mtu 1500 lladdr 80:fa:5b:14:xx:yy index 1 priority 4 llprio 3 trunk: trunkdev trunk0 groups: wlan media: IEEE802.11 autoselect (HT-MCS0 mode 11n) status: no network ieee80211: join chan 36 bssid 84:b2:61:96:aa:bb 83% wpaprotos wpa2 wpaakms 802.1x wpaciphers ccmp wpagroupcipher ccmp ... trunk0: flags=8843 mtu 1500 lladdr 80:fa:5b:14:xx:yy index 7 priority 0 llprio 3 trunk: trunkproto failover trunkport iwm0 trunkport re0 master groups: trunk media: Ethernet autoselect status: no carrier Only after I had commented the join-line for this network I was able to reattach to my mobile phone's net. Attaching to this particular net would be helpful - saves some time avoiding workaraounds... Adding a dmesg to avoid questions. Thanks in advance! Kind regards, STEFAN OpenBSD 6.4-beta (GENERIC.MP) #286: Sat Sep 1 22:23:18 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 1655720 (15785MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.24 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,M
WiFi: Join + wpa_supplicant
Hi there, I am a little bit confused: Do I read the docs correct assuming that defining a join-list in /etc/hostname. and wpa_supplicant are mutually exclusive? I have set up a join-list and now I need to attach to a network where I can only login with credetials "user" and "user-password"... TIA. Kind regards, STEFAN
Re: KDE-apps okular, kmahjongg
Am 07/04/18 um 16:13 schrieb Stuart Henderson: > On 2018-07-04, Stefan Wollny wrote: >> Somehow the dbus-daemon is not recognized although started as 'rcctl ls >> started' shows. And > > That is a system dbus-daemon but you didn't have a session dbus-daemon. > >> Finally I added 'export $(dbus-launch)' to .xinitrc (plus kdeinit4) and >> those KDE apps now do get started as they did until last week. >> >> Is this expected behaviour? I didn't find anything related to this in >> the man pages or the FAQ - if it is could s.o. please point my sore eyes >> to the relevant documentation? > > There was a fallback in the dbus port for the case where the session bus > was missing, it was removed for a bit, but it seems few people bother > to read the dbus pkg-readme and most software which needs it doesn't > fail with a very informative error message, so it has gone back in > for now... > > The fallback is not great because it means that each program wanting > to use dbus has its own separate session bus - there's only supposed to > be a single one. > > You are supposed to run the session bus like this: > > $ cat /usr/local/share/doc/pkg-readmes/dbus-* > > $OpenBSD: README-main,v 1.3 2017/11/01 06:27:31 ajacoutot Exp $ > > +--- > | Running dbus-1.12.8p0v0 on OpenBSD > +--- > > To start a session bus instance of dbus-daemon (needed by applications > installing /usr/local/share/dbus-1/services/*.service files), add the > following lines to your Xsession script before starting the window manager > (see dbus-launch(1) for more info) -- note that some session/login managers, > like gnome-session(1) already handle this automatically. > > e.g. console login: ~/.xinitrc > if [ -x /usr/local/bin/dbus-launch -a -z "${DBUS_SESSION_BUS_ADDRESS}" ]; then > eval `dbus-launch --sh-syntax --exit-with-session` > fi > > e.g. graphical display manager: ~/.xsession > if [ -x /usr/local/bin/dbus-launch -a -z "${DBUS_SESSION_BUS_ADDRESS}" ]; then > eval `dbus-launch --sh-syntax --exit-with-x11` > fi > > Thank you, Stuart! Excellent explanation and precise help, right to the point!
Re: KDE-apps okular, kmahjongg
Am 07/02/18 um 09:43 schrieb Stefan Wollny: > > > Am 06/25/18 um 22:36 schrieb Stefan Wollny: >> Hi there, >> >> I run amd64-current with the latest public snapshots: >> $ dmesg | grep Open >> OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 >> < Full dmesg at the end > >> >> Although I try to follow reading src-changes and topics on misc@ as >> close as possible I might have missed something lately. Until a few days >> ago okular and kmahjongg came up without a comment. Now I cannot start >> them (havn't tried other KDE apps) >> >> >> $ okular >> okular(68871)/kdeui (kdelibs): Session bus not found >> To circumvent this problem try the following command (with Linux and bash) >> export $(dbus-launch) >> KCrash: Application 'okular' crashing... >> KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit >> KCrash: Connect >> sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 >> Warning: connect() failed: : No such file or directory >> KCrash: Attempting to start /usr/local/libexec/drkonqi directly >> drkonqi(78427)/kdeui (kdelibs): Session bus not found >> To circumvent this problem try the following command (with Linux and bash) >> export $(dbus-launch) >> >> ~ $ kmahjongg >> kmahjongg(43798)/kdeui (kdelibs): Session bus not found >> To circumvent this problem try the following command (with Linux and bash) >> export $(dbus-launch) >> KCrash: Application 'kmahjongg' crashing... >> KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit >> KCrash: Connect >> sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 >> Warning: connect() failed: : No such file or directory >> KCrash: Attempting to start /usr/local/libexec/drkonqi directly >> drkonqi(34562)/kdeui (kdelibs): Session bus not found >> To circumvent this problem try the following command (with Linux and bash) >> export $(dbus-launch) >> >> What did I miss / what am I doing wrong here? >> >> In /etc/rc.conf.local I have: >> pkg_scripts=freshclam clamd messagebus avahi_daemon cupsd smartd >> cups_browsed >> >> (cups isn't working for a looong time but that should be a different thread) >> >> Anyone got a clue what might be wrong with my system or what knob to >> turn? Or is this just a temporary annnoyance that ought to go away in a >> short time? >> >> TIA. >> >> Best, >> STEFAN >> >> > > Now that I am back in business having updated the system (new dmesg at > the end) and all installed packages I tried again ... yet neither > kmahjongg nor okular are working: > > ~ $ pkg_info | grep kmah > kmahjongg-4.14.3p3 Mah Jongg solitare board game for KDE > libkmahjongg-4.14.3p1 common library for Mah Jongg-based KDE games > > ~ $ pkg_info | grep oku > libmusicbrainz5-5.0.1p4 library for audio metadata lookup (v5) > okular-4.14.3p7 KDE document viewer > > ~ $ kmahjongg > kmahjongg(25428)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > KCrash: Application 'kmahjongg' crashing... > KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit > KCrash: Connect > sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 > Warning: connect() failed: : No such file or directory > KCrash: Attempting to start /usr/local/libexec/drkonqi directly > drkonqi(30570)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > > ~ $ okular > okular(31187)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > KCrash: Application 'okular' crashing... > KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit > KCrash: Connect > sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 > Warning: connect() failed: : No such file or directory > KCrash: Attempting to start /usr/local/libexec/drkonqi directly > drkonqi(23688)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > > > ~ $ doas rcctl ls started > apmd > avahi_daemon > clamd > cron > cups_browsed > cupsd > freshclam > messagebus > ntpd > pflogd > postgresql > sensorsd > slaacd > smartd > smtpd > sndiod > sshd > syslogd > > > Has anyone a clue what might be missing? Wrong
Re: KDE-apps okular, kmahjongg
Am 06/25/18 um 22:36 schrieb Stefan Wollny: > Hi there, > > I run amd64-current with the latest public snapshots: > $ dmesg | grep Open > OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 > < Full dmesg at the end > > > Although I try to follow reading src-changes and topics on misc@ as > close as possible I might have missed something lately. Until a few days > ago okular and kmahjongg came up without a comment. Now I cannot start > them (havn't tried other KDE apps) > > > $ okular > okular(68871)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > KCrash: Application 'okular' crashing... > KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit > KCrash: Connect > sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 > Warning: connect() failed: : No such file or directory > KCrash: Attempting to start /usr/local/libexec/drkonqi directly > drkonqi(78427)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > > ~ $ kmahjongg > kmahjongg(43798)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > KCrash: Application 'kmahjongg' crashing... > KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit > KCrash: Connect > sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 > Warning: connect() failed: : No such file or directory > KCrash: Attempting to start /usr/local/libexec/drkonqi directly > drkonqi(34562)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > > What did I miss / what am I doing wrong here? > > In /etc/rc.conf.local I have: > pkg_scripts=freshclam clamd messagebus avahi_daemon cupsd smartd > cups_browsed > > (cups isn't working for a looong time but that should be a different thread) > > Anyone got a clue what might be wrong with my system or what knob to > turn? Or is this just a temporary annnoyance that ought to go away in a > short time? > > TIA. > > Best, > STEFAN > > Now that I am back in business having updated the system (new dmesg at the end) and all installed packages I tried again ... yet neither kmahjongg nor okular are working: ~ $ pkg_info | grep kmah kmahjongg-4.14.3p3 Mah Jongg solitare board game for KDE libkmahjongg-4.14.3p1 common library for Mah Jongg-based KDE games ~ $ pkg_info | grep oku libmusicbrainz5-5.0.1p4 library for audio metadata lookup (v5) okular-4.14.3p7 KDE document viewer ~ $ kmahjongg kmahjongg(25428)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'kmahjongg' crashing... KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/local/libexec/drkonqi directly drkonqi(30570)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) ~ $ okular okular(31187)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'okular' crashing... KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/local/libexec/drkonqi directly drkonqi(23688)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) ~ $ doas rcctl ls started apmd avahi_daemon clamd cron cups_browsed cupsd freshclam messagebus ntpd pflogd postgresql sensorsd slaacd smartd smtpd sndiod sshd syslogd Has anyone a clue what might be missing? Wrong permissions? Any hint welcome. TIA! Best, STEFAN OpenBSD 6.3-current (GENERIC.MP) #82: Sun Jul 1 15:37:34 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16552341504 (15785MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT
Re: Softraid0-Problem: Inappropriate file type or format (Was: KDE-apps okular, kmahjongg)
Am 06/28/18 um 23:49 schrieb Stefan Wollny: > Hi there! > > Unfortunately I have to hijack my own thread as it has the last working dmesg. > > Right after I had asked on misc@ about those KDE-apps I upgraded to the > latest snapshot for amd64-current. By this I was hit by the > "libxshmfence.so.0.0-issue". > https://marc.info/?l=openbsd-tech&m=153003604704089&w=2 > > Well - running -current is usually rock-solid, but I am well aware that every > now-and-then things might go wrong and will be corrected by the devs with the > next snapshot (or the one thereafter). Happens remarkably seldom but > obviously here I had to make use of the next snapshot, which I did: Wham! I > cannot log-in to the system any more! > > "booting sr0a:/bsd: sr0a:/bsd: Inappropriate file type or format > failed(79). will try /bsd" > > Yes - this system is fully encrypted, secured by a key-disk. I have dd'ed two > more copies of this key, both behave the same. Thus I dare to suppose that > there is no technical issue with the key (in particular as the other two > USB-keys have not been attached at the time of the last upgrade). > > Most likely I did unknowingly s.th. really dumb. > > OK - how to proceed? Yes - I am lucky having backed up the relevant data the > night before. My fallback solution is to simply reinstall everything. > Annoying, as it will take a little time, but I will survive. > > My question is, as I can boot into 'bsd.rd', what alternative(s) I have to > '# bioctl -c C -k /dev/sd1a -l /sd0a softraid0' > softraid0: chunk sd0a already in use > > bsd.rd-dmesg shows at the end sd1 being the USB-key-disk and sd2 being the > unencrypted OpenBSD-crypto-file, thus I used sd0 with 'bioctl'. > > Anyone a clue what might have gone wrong and how to proceed (except > reinstallation)? > > TIA! > > Best, > STEFAN > For the records: After some more reading of man-pages, the OpenBSD FAQ and some other sites by the devs I realized that nothing is wrong with softraid(0) as the encrypted disk (sd0) shows up as sd2. This 'disk' is accessible via bsd.rd. All that needed to be done was fsck'ing the partitions (/usr needed help) and updating the system via bsd.rd to be back in business. Another fine example that it takes a lot to wreck OpenBSD, actually. To all devs: THANK YOU! Best, STEFAN
Softraid0-Problem: Inappropriate file type or format (Was: KDE-apps okular, kmahjongg)
Hi there! Unfortunately I have to hijack my own thread as it has the last working dmesg. Right after I had asked on misc@ about those KDE-apps I upgraded to the latest snapshot for amd64-current. By this I was hit by the "libxshmfence.so.0.0-issue". https://marc.info/?l=openbsd-tech&m=153003604704089&w=2 Well - running -current is usually rock-solid, but I am well aware that every now-and-then things might go wrong and will be corrected by the devs with the next snapshot (or the one thereafter). Happens remarkably seldom but obviously here I had to make use of the next snapshot, which I did: Wham! I cannot log-in to the system any more! "booting sr0a:/bsd: sr0a:/bsd: Inappropriate file type or format failed(79). will try /bsd" Yes - this system is fully encrypted, secured by a key-disk. I have dd'ed two more copies of this key, both behave the same. Thus I dare to suppose that there is no technical issue with the key (in particular as the other two USB-keys have not been attached at the time of the last upgrade). Most likely I did unknowingly s.th. really dumb. OK - how to proceed? Yes - I am lucky having backed up the relevant data the night before. My fallback solution is to simply reinstall everything. Annoying, as it will take a little time, but I will survive. My question is, as I can boot into 'bsd.rd', what alternative(s) I have to '# bioctl -c C -k /dev/sd1a -l /sd0a softraid0' softraid0: chunk sd0a already in use bsd.rd-dmesg shows at the end sd1 being the USB-key-disk and sd2 being the unencrypted OpenBSD-crypto-file, thus I used sd0 with 'bioctl'. Anyone a clue what might have gone wrong and how to proceed (except reinstallation)? TIA! Best, STEFAN Am 25.06.2018 um 22:36 schrieb Stefan Wollny: > Hi there, > > I run amd64-current with the latest public snapshots: > $ dmesg | grep Open > OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 > < Full dmesg at the end > > > [ ... ] > > > > OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 17079074816 (16287MB) > avail mem = 16420831232 (15660MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) > bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 > bios0: Notebook W65_67SZ > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT > SSDT SSDT DMAR > acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) > PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) > EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.34 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,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 99MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.85 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 1, core 0, package 0 > cpu3 at mainbus0
KDE-apps okular, kmahjongg
Hi there, I run amd64-current with the latest public snapshots: $ dmesg | grep Open OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 < Full dmesg at the end > Although I try to follow reading src-changes and topics on misc@ as close as possible I might have missed something lately. Until a few days ago okular and kmahjongg came up without a comment. Now I cannot start them (havn't tried other KDE apps) $ okular okular(68871)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'okular' crashing... KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/local/libexec/drkonqi directly drkonqi(78427)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) ~ $ kmahjongg kmahjongg(43798)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'kmahjongg' crashing... KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/local/libexec/drkonqi directly drkonqi(34562)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) What did I miss / what am I doing wrong here? In /etc/rc.conf.local I have: pkg_scripts=freshclam clamd messagebus avahi_daemon cupsd smartd cups_browsed (cups isn't working for a looong time but that should be a different thread) Anyone got a clue what might be wrong with my system or what knob to turn? Or is this just a temporary annnoyance that ought to go away in a short time? TIA. Best, STEFAN OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16420831232 (15660MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.34 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.85 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,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-4210M CPU @ 2.60GHz, 3092.84 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,S
Re: lock order reversal in dmesg?
Am 06/04/18 um 23:01 schrieb Stuart Henderson: > On 2018-06-02, Jungle Boogie wrote: >> With one of the snapshots from Friday 1 June, I'm seeing more info in my >> dmesg >> than I typically do. Has some extra debugging been turned on? > > Yes. > > Here you go. Best, STEFAN OpenBSD 6.3-current (GENERIC.MP) #75: Mon Jun 4 00:06:10 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16420855808 (15660MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.33 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,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 using xsaveopt cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,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-4210M CPU @ 2.60GHz, 3092.84 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,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-4210M CPU @ 2.60GHz, 3092.84 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,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, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 120 degC acpicmos0 at acpi0 "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not configured "ETD0403" at acpi0 not configured "PNPC000" at acpi0 not configured acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: LID0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "BAT" serial 0001 type LION oem "Notebook" "PNP0C14" at acpi0 not configured "INT340E" at acpi0 not configured acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: LCD0 cpu0: Enhanced SpeedStep 3093 MHz: speeds: 2601, 2600, 2500, 2300, 2200, 2100, 2000, 1800, 1700, 1600, 1400, 1300, 1200, 1100, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 ppb0 at pci0 dev 1 function 0 "Intel Core 4G P
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 03/12/18 um 15:02 schrieb Kevin Chadwick: > On Mon, 12 Mar 2018 12:25:40 +0100 > > >> into normal operations. Guess I have to do >> 'installboot sd2' > > I know it is more to type but you can use uids to make sure it is the > right disk too. > You are right - that would have been the better way. I checked beforehand via disklabel if sd0 and sd1 are the actual RAID volumes and sd2 is the decrypted volume. Everything now is fine again: With the key disk inserted OpenBSD starts as usual. Thank you devs for your fine work - the problem sat in front of the screen ;-) Lesson learnt.
Re: Fwd: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Gesendet: Sonntag, 11. März 2018 um 22:41 Uhr > Von: "Stefan Wollny" > An: misc > Betreff: Re: Fwd: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument > Hi Alexander, > > thank you for taking your time to look at my problem! Really appreciate it! > >> Am 11.03.2018 um 22:04 schrieb Alexander Hall: >> 3. Did you by any chance detach the filesystem at any time? IIRC >> that would make it not auto-assemble after reboot, which might >> explain some of the observed behaviours. > Mmmh - this is s.th. I cannot rule out for shure. Last time the system > was work flawless I had an encrypted external HD attached to make my > daily backup. Maybe I did a 'bioctl -d' on the sdx the sd0 was attached > to after disencryption (no - sd0 isn't always attached to sd2! This can > be anything from 2 to 7, usually) instead of the sd-number the external > HD was attached to... > > If so - is there any chance to recover? For the records: As I was able to boot into bsd.rd on the shell I did: 'bioctl -c C -k /dev/sd1a -l /dev/sd0a softraid0' After a reboot I could start via 'boot sr0a:/bsd' into normal operations. Guess I have to do 'installboot sd2' now as this is what the RAID-volume was attached to. Thanks to all of you who took some time and provided help! Best, STEFAN
Re: Fwd: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 11.03.2018 um 22:04 schrieb Alexander Hall: > 2. Your key disk or sd0 disk raid metadata could be corrupt. Forgot this one: I have three different key disks - none of them gets the system a go.
Re: Fwd: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Hi Alexander, thank you for taking your time to look at my problem! Really appreciate it! Am 11.03.2018 um 22:04 schrieb Alexander Hall: > 3. Did you by any chance detach the filesystem at any time? IIRC > that would make it not auto-assemble after reboot, which might > explain some of the observed behaviours. Mmmh - this is s.th. I cannot rule out for shure. Last time the system was work flawless I had an encrypted external HD attached to make my daily backup. Maybe I did a 'bioctl -d' on the sdx the sd0 was attached to after disencryption (no - sd0 isn't always attached to sd2! This can be anything from 2 to 7, usually) instead of the sd-number the external HD was attached to... If so - is there any chance to recover? > 4. Did you by any chance run installboot on sd0 or sd1? That'd be wrong. I tried but without success. Obviously. Thanks again and have a nice week! Best, STEFAN
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 09.03.2018 um 00:55 schrieb Stefan Wollny: > Am 09.03.2018 um 00:09 schrieb Stefan Wollny: >> Am 08.03.2018 um 23:25 schrieb Stefan Wollny: >>> Am 08.03.2018 um 22:11 schrieb Stefan Wollny: >>> >>>> Am 08.03.2018 um 17:44 schrieb Stefan Wollny: >>>>> Gesendet von meinem BlackBerry 10-Smartphone. >>>>> Originalnachricht >>>>> Von: Kevin Chadwick >>>>> Gesendet: Donnerstag, 8. März 2018 17:28 >>>>> An: misc@openbsd.org >>>>> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >>>>> >>>>> On Thu, 8 Mar 2018 14:47:43 +0100 >>>>> >>>>> >>>>>> Has anyone a clue what might have happend and how to solve the issue? >>>>>> I searched the net but didn't find any substantial infos on this. As >>>>>> the error happends with all three USB-keys I have this is unlikely to >>>>>> be cause of the trouble. >>>>> The bootloader normally lists the disks that the bios sees beforehand >>>>> e.g. >>>>> >>>>> disk: hd0+ hd1+ sr0* >>>>>>> OpenBSD/amd64 BOOT 3.34 >>>>> Perhaps they have been moved around? >>>>> >>>>> >>>>> I tried >>>>> >>>>> boot hd1a:/bsd >>>>> >>>>> but got the same message. >>>>> >>>>> I can enter # fsck -fy hd0a but this just gets me a prompt without any >>>>> action. BTW: This is a SSD. >>>>> >>>> OK - back at home I downloaded install63.iso and burned a CD which does >>>> start. Choosing "(U)pgrade" I am presented with "Available disks are: >>>> sd0 sd1" - but both are "not a valid root disk". Back to the shell I >>>> tried fdisk but I get "fdisk: sd0: No such file or directory" >>>> >>>> Could this be an issue with the bootloader or is it the encryption of >>>> softraid0 that hinders the upgrade? >>>> >> tb@ provided another valuable hint: >> I can start the boot-process with 'boot sr0a:/bsd' but this ends with a >> panic: >> >> ... >> softraid0 at root >> scsibus4 at softraid0:256 targets >> panic: root device (...) not found >> Stopped at db_enter+0x5: popq %rbp >> TID PID UID PRFLAGS PFLAGS CPU COMMAND >> * 0 0 0 0X1 0X200 OK swapper >> ... >> > OK . final remarks for tonight: > > I can start 'boot sr0a:/bsd.rd' but trying to upgrade is the same > dead-end road - "sd0 is not a valid root device". > > 'fdisk sd0' shows the expected '*' before the partition number. > > 'disklabel sd0' shows the expected fstype "RAID" 'for sd0a. > > Doing 'bioctl -c C -l /dev/sd0a' says "KDF hint has invalid size". > > 'installboot -nv sd0a' misses '/usr/mdec/biosboot' - there is only > '/usr/mdec/mbr'. > > While the 'upgrade' started from 'boot sr0a:/bsd.rd' does not see 'sd0' > the 'install' process started from the CD actually does. Someone an idea how to proceed? I'd hate to reinstall everything... TIA. STEFAN
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 09.03.2018 um 00:09 schrieb Stefan Wollny: > Am 08.03.2018 um 23:25 schrieb Stefan Wollny: >> Am 08.03.2018 um 22:11 schrieb Stefan Wollny: >> >>> Am 08.03.2018 um 17:44 schrieb Stefan Wollny: >>>> Gesendet von meinem BlackBerry 10-Smartphone. >>>> Originalnachricht >>>> Von: Kevin Chadwick >>>> Gesendet: Donnerstag, 8. März 2018 17:28 >>>> An: misc@openbsd.org >>>> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >>>> >>>> On Thu, 8 Mar 2018 14:47:43 +0100 >>>> >>>> >>>>> Has anyone a clue what might have happend and how to solve the issue? >>>>> I searched the net but didn't find any substantial infos on this. As >>>>> the error happends with all three USB-keys I have this is unlikely to >>>>> be cause of the trouble. >>>> The bootloader normally lists the disks that the bios sees beforehand >>>> e.g. >>>> >>>> disk: hd0+ hd1+ sr0* >>>>>> OpenBSD/amd64 BOOT 3.34 >>>> Perhaps they have been moved around? >>>> >>>> >>>> I tried >>>> >>>> boot hd1a:/bsd >>>> >>>> but got the same message. >>>> >>>> I can enter # fsck -fy hd0a but this just gets me a prompt without any >>>> action. BTW: This is a SSD. >>>> >>> OK - back at home I downloaded install63.iso and burned a CD which does >>> start. Choosing "(U)pgrade" I am presented with "Available disks are: >>> sd0 sd1" - but both are "not a valid root disk". Back to the shell I >>> tried fdisk but I get "fdisk: sd0: No such file or directory" >>> >>> Could this be an issue with the bootloader or is it the encryption of >>> softraid0 that hinders the upgrade? >>> > tb@ provided another valuable hint: > I can start the boot-process with 'boot sr0a:/bsd' but this ends with a > panic: > > ... > softraid0 at root > scsibus4 at softraid0:256 targets > panic: root device (...) not found > Stopped at db_enter+0x5: popq %rbp > TID PID UID PRFLAGS PFLAGS CPU COMMAND > * 0 0 0 0X1 0X200 OK swapper > ... > OK . final remarks for tonight: I can start 'boot sr0a:/bsd.rd' but trying to upgrade is the same dead-end road - "sd0 is not a valid root device". 'fdisk sd0' shows the expected '*' before the partition number. 'disklabel sd0' shows the expected fstype "RAID" 'for sd0a. Doing 'bioctl -c C -l /dev/sd0a' says "KDF hint has invalid size". 'installboot -nv sd0a' misses '/usr/mdec/biosboot' - there is only '/usr/mdec/mbr'. While the 'upgrade' started from 'boot sr0a:/bsd.rd' does not see 'sd0' the 'install' process started from the CD actually does. Sigh - I need some sleep...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 08.03.2018 um 23:25 schrieb Stefan Wollny: > Am 08.03.2018 um 22:11 schrieb Stefan Wollny: > >> Am 08.03.2018 um 17:44 schrieb Stefan Wollny: >>> Gesendet von meinem BlackBerry 10-Smartphone. >>> Originalnachricht >>> Von: Kevin Chadwick >>> Gesendet: Donnerstag, 8. März 2018 17:28 >>> An: misc@openbsd.org >>> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >>> >>> On Thu, 8 Mar 2018 14:47:43 +0100 >>> >>> >>>> Has anyone a clue what might have happend and how to solve the issue? >>>> I searched the net but didn't find any substantial infos on this. As >>>> the error happends with all three USB-keys I have this is unlikely to >>>> be cause of the trouble. >>> The bootloader normally lists the disks that the bios sees beforehand >>> e.g. >>> >>> disk: hd0+ hd1+ sr0* >>>>> OpenBSD/amd64 BOOT 3.34 >>> Perhaps they have been moved around? >>> >>> >>> I tried >>> >>> boot hd1a:/bsd >>> >>> but got the same message. >>> >>> I can enter # fsck -fy hd0a but this just gets me a prompt without any >>> action. BTW: This is a SSD. >>> >> OK - back at home I downloaded install63.iso and burned a CD which does >> start. Choosing "(U)pgrade" I am presented with "Available disks are: >> sd0 sd1" - but both are "not a valid root disk". Back to the shell I >> tried fdisk but I get "fdisk: sd0: No such file or directory" >> >> Could this be an issue with the bootloader or is it the encryption of >> softraid0 that hinders the upgrade? >> tb@ provided another valuable hint: I can start the boot-process with 'boot sr0a:/bsd' but this ends with a panic: ... softraid0 at root scsibus4 at softraid0:256 targets panic: root device (...) not found Stopped at db_enter+0x5: popq %rbp TID PID UID PRFLAGS PFLAGS CPU COMMAND * 0 0 0 0X1 0X200 OK swapper ...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 08.03.2018 um 23:25 schrieb Stefan Wollny: > Am 08.03.2018 um 22:11 schrieb Stefan Wollny: > >> Am 08.03.2018 um 17:44 schrieb Stefan Wollny: >>> Gesendet von meinem BlackBerry 10-Smartphone. >>> Originalnachricht >>> Von: Kevin Chadwick >>> Gesendet: Donnerstag, 8. März 2018 17:28 >>> An: misc@openbsd.org >>> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >>> >>> On Thu, 8 Mar 2018 14:47:43 +0100 >>> >>> >>>> Has anyone a clue what might have happend and how to solve the issue? >>>> I searched the net but didn't find any substantial infos on this. As >>>> the error happends with all three USB-keys I have this is unlikely to >>>> be cause of the trouble. >>> The bootloader normally lists the disks that the bios sees beforehand >>> e.g. >>> >>> disk: hd0+ hd1+ sr0* >>>>> OpenBSD/amd64 BOOT 3.34 >>> Perhaps they have been moved around? >>> >>> >>> I tried >>> >>> boot hd1a:/bsd >>> >>> but got the same message. >>> >>> I can enter # fsck -fy hd0a but this just gets me a prompt without any >>> action. BTW: This is a SSD. >>> >> OK - back at home I downloaded install63.iso and burned a CD which does >> start. Choosing "(U)pgrade" I am presented with "Available disks are: >> sd0 sd1" - but both are "not a valid root disk". Back to the shell I >> tried fdisk but I get "fdisk: sd0: No such file or directory" >> >> Could this be an issue with the bootloader or is it the encryption of >> softraid0 that hinders the upgrade? >> > ??? > Running dmesg from the CD-shell the system "sees" sd0 (the internel SSD) > and sd1 (the USB with the key). Having attached another USB drive I see > this is recognizes as sd2. But running 'fdisk sd2' or 'disklabel sd2' I > get "No such file or directory" (and consequently as well when trying to > mount this external drive). > > Puzzled... > tb@ hit me with the clue stick: MAKEDEV was the missing part to mount the external USB drive. Now: Here's the dmesg OpenBSD 6.3-beta (RAMDISK_CD) #38: Thu Mar 8 10:01:01 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 17079074816 (16287MB) avail mem = 16557678592 (15790MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.25 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu at acpi0 not configured acpitz at acpi0 not configured "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not configured "ETD0403" at acpi0 not configured "PNPC000" at acpi0 not configured "PNP0C0C" at acpi0 not configured "PNP0C0E" at acpi0 not configured "PNP0C0D" at acpi0 not configured "ACPI0003" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT340E" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi pci1 at ppb0 bus 1 vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06 wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) "Intel Core 4G HD Audio" rev 0x06 at pci0 dev 3 function 0 not configured xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHC
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 08.03.2018 um 22:11 schrieb Stefan Wollny: > Am 08.03.2018 um 17:44 schrieb Stefan Wollny: >> Gesendet von meinem BlackBerry 10-Smartphone. >> Originalnachricht >> Von: Kevin Chadwick >> Gesendet: Donnerstag, 8. März 2018 17:28 >> An: misc@openbsd.org >> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >> >> On Thu, 8 Mar 2018 14:47:43 +0100 >> >> >>> Has anyone a clue what might have happend and how to solve the issue? >>> I searched the net but didn't find any substantial infos on this. As >>> the error happends with all three USB-keys I have this is unlikely to >>> be cause of the trouble. >> The bootloader normally lists the disks that the bios sees beforehand >> e.g. >> >> disk: hd0+ hd1+ sr0* >>>> OpenBSD/amd64 BOOT 3.34 >> Perhaps they have been moved around? >> >> >> I tried >> >> boot hd1a:/bsd >> >> but got the same message. >> >> I can enter # fsck -fy hd0a but this just gets me a prompt without any >> action. BTW: This is a SSD. >> > OK - back at home I downloaded install63.iso and burned a CD which does > start. Choosing "(U)pgrade" I am presented with "Available disks are: > sd0 sd1" - but both are "not a valid root disk". Back to the shell I > tried fdisk but I get "fdisk: sd0: No such file or directory" > > Could this be an issue with the bootloader or is it the encryption of > softraid0 that hinders the upgrade? > ??? Running dmesg from the CD-shell the system "sees" sd0 (the internel SSD) and sd1 (the USB with the key). Having attached another USB drive I see this is recognizes as sd2. But running 'fdisk sd2' or 'disklabel sd2' I get "No such file or directory" (and consequently as well when trying to mount this external drive). Puzzled...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 08.03.2018 um 17:44 schrieb Stefan Wollny: > > Gesendet von meinem BlackBerry 10-Smartphone. > Originalnachricht > Von: Kevin Chadwick > Gesendet: Donnerstag, 8. März 2018 17:28 > An: misc@openbsd.org > Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument > > On Thu, 8 Mar 2018 14:47:43 +0100 > > >> Has anyone a clue what might have happend and how to solve the issue? >> I searched the net but didn't find any substantial infos on this. As >> the error happends with all three USB-keys I have this is unlikely to >> be cause of the trouble. > The bootloader normally lists the disks that the bios sees beforehand > e.g. > > disk: hd0+ hd1+ sr0* >>> OpenBSD/amd64 BOOT 3.34 > Perhaps they have been moved around? > > > I tried > > boot hd1a:/bsd > > but got the same message. > > I can enter # fsck -fy hd0a but this just gets me a prompt without any > action. BTW: This is a SSD. > OK - back at home I downloaded install63.iso and burned a CD which does start. Choosing "(U)pgrade" I am presented with "Available disks are: sd0 sd1" - but both are "not a valid root disk". Back to the shell I tried fdisk but I get "fdisk: sd0: No such file or directory" Could this be an issue with the bootloader or is it the encryption of softraid0 that hinders the upgrade?
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Gesendet von meinem BlackBerry 10-Smartphone. Originalnachricht Von: Kevin Chadwick Gesendet: Donnerstag, 8. März 2018 17:28 An: misc@openbsd.org Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument On Thu, 8 Mar 2018 14:47:43 +0100 > Has anyone a clue what might have happend and how to solve the issue? > I searched the net but didn't find any substantial infos on this. As > the error happends with all three USB-keys I have this is unlikely to > be cause of the trouble. The bootloader normally lists the disks that the bios sees beforehand e.g. disk: hd0+ hd1+ sr0* >> OpenBSD/amd64 BOOT 3.34 Perhaps they have been moved around? I tried boot hd1a:/bsd but got the same message. I can enter # fsck -fy hd0a but this just gets me a prompt without any action. BTW: This is a SSD.
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Hi there! I need help or some hints on how to proceed: My system a laptop running amd64-current fully encrypted, key-based. I start from BIOS, not UEFI. Two days ago I updated to the then latest snapshot and apparently s.th. went wrong: At reboot the system stops after >> OpenBSD/amd64 BOOT 3.34 open(hd0a:/etc/boot.conf): Invalide argument boot> cannot open hd0a:/etc/random.seed: Invalid argument booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try /bsd Turning timeout off. boot> Has anyone a clue what might have happend and how to solve the issue? I searched the net but didn't find any substantial infos on this. As the error happends with all three USB-keys I have this is unlikely to be cause of the trouble. At present I only have a USB-stick with install62.fs with me (roughly 3~4 weeks old) which only starts if I change from BIOS to UEFI. As all data from /home is redundantly backed up I could reinstall everything but would prefer to avoid it. There are dmesgs from this laptop with some older posts. Obviously no current dmesg possible... Any hint/idea/suggestion welcome! TIA. Best, STEFAN
Disable external USB devices
Hi there! This is a purely academical question out of curiosity: Is it possible to disable all external USB interfaces without cutting the wire on OpenBSD? You've heard stories of laptops/servers/routers with other OSes being infected by some clever programms on USB sticks automatically attaching to the running system without leaving obvious traces. Assumption is that with OpenBSD and nothing like 'hotplug-diskmount' installed this should not with be able, even with an unprivileged user being logged in (with proper doas(1) rules applied). Nevertheless let us assume some smart blackhat successfully finds a way to infect a running OpenBSD system by attaching a USB device circumventing e.g. a full-disk encryption. Or think of a desktop PC under the table where such a device is not obviously visible. It may not help with Intel-like hardware bugs but deactivated USB ports should be an extra hurdle for the casual attacker. Of course any change should require physical access, 'root' and a reboot (like with chflags(1)). I think disabling umass(4) at boot-time or permanently might achieve s.th. like this - but what would be the side effects to consider? KARL comes to my mind. As the only OpenBSD system at hand is my laptop I do not dare to test by disabling umass(4) as it is fully-encrypted with the key on a USB stick. (Fiddling with the kernel on a production system seems to be a second-class option anyway, right?) And if 'they' sneak into the system e.g. via ugen(4)-attached devices... yes, I am aware that with enough time, money and physical access 'they' will find a way, someday. There's no safe computer - except not having one. Anyway - which other ports/interfaces are at risk and could easily be disabled alike? Bluetooth seems rather safe... ;-) Is there another smart way to do s.th. like the described? I found nothing in the FAQ. Feasibility in practice might be a matter of the level of paranoia ... or are blocked USB interfaces nowadays a required precaution? Time for a BIG THANKYOU to the developers for the most trustworthy OS out there! Best,STEFAN
Re: adsuck
Am 12/28/17 um 23:58 schrieb Rupert Gallagher: > The last update is 5 years old, and its blacklists are obsolete. > > https://github.com/conformal/adsuck/tree/master/files > > Sent from ProtonMail Mobile > Hi Rupert, you are quite right - the default blacklist from mvps is outdated. This is why I weekly do the following (serves my requirements and speed is no priority): #!/bin/sh # # /home//Downloads/mvps must exist! # # clean up first: rm -f /home//Downloads/mvps/* # cd /home//Downloads/mvps wget -4 -nc --no-proxy --no-cache --no-cookies http://winhelp2002.mvps.org/hosts.zip unzip hosts.zip # dos2unix HOSTS # # no comments egrep -v '^#' HOSTS > Hosts # # no empty lines sed -n -i '/0\.0\.0\.0 /,$p' Hosts # # check if anything does _not_ go to 0.0.0.0 if [[ $(awk '{print $1}' Hosts | uniq) != '0.0.0.0' ]]; then printf "mvps-hosts-File manipulated! Bye, bye! \n"; exit 1 fi # # Show the date of update in /etc/hosts echo "## Updated: `date +%Y-%m-%d`" > hosts_date # # Replace all 0.0.0.0 with 127.0.0.1 (aka 'localhost') sed 's/0.0.0.0/127.0.0.1/' Hosts > hosts.tmp # # build new hosts-file cat hosts_date /home//hosts_private hosts.tmp > hosts # # Keep last hosts-file doas cp /etc/hosts /etc/hosts.last # # Replace old with new hosts-file doas cp hosts /etc/hosts # # Back to home cd /home/ # reconnect with new hosts-file print "reconnect NOW " doas sh /etc/netstart As I will give Jordan's solution a go I will check other blacklists as well. Best, STEFAN
Re: adsuck
Am 12/28/17 um 23:34 schrieb ed...@pettijohn-web.com: > You need dhcpcd from ports. I don't think the base client supports scripts. Ah - I see. So it should be safe to delete that very line in dhclient.conf - if base's dhclient doesn't support scripts and yet everything is running fine this should not do any harm. Thank you for pointing this out. Beside Jordan Geoghegan's suggestion I received a similar solution in PM. I vaguely remember Stuart Henderson having suggested this kind of setup as it only uses what comes with base. Will do my homework of reading the man pages (in particular a.th. related to 'unbound') first. Thank you all! All the best for 2018! STEFAN
adsuck
Hi there! I have this little machine which serves as (squid-)proxy for my local net. $ dmesg | grep Open OpenBSD 6.2-current (GENERIC.MP) #311: Wed Dec 27 21:49:49 MST 2017 Basically everything is fine - except responses are kind of slow. So I had the idea to not use squid to filter for unwanted sites but use adsuck. I followed the advice in /usr/local/share/doc/pkg-readmes/adsuck-2.5.0p4 which now reads: $ cat /etc/dhclient.conf send host-name ; script "/usr/local/sbin/dhclient-adsuck"; I had to use chflags with 'schg' to make shure that /etc/resolv.conf only contains one line (neither 'supersede' nor 'prepend' in dhclient.conf did the job): $ cat /etc/resolv.conf nameserver 127.0.0.1 And YES: adsuck is activated via /etc/rc.conf.local (actually it is the very first one after 'pkg_scripts='). It is up and running: $ top | grep adsuck 72573 _adsuck20 2260K 4704K idle kqread0:00 0.00% adsuck Now: If I run 'sh /etc/netstart' on the console or an xterm I see the following: $ doas sh /etc/netstart em1: /etc/dhclient.conf line 2: expecting statement. em1: script em1: ^ em1: DHCPREQUEST to 255.255.255.255 em1: DHCPACK from a.b.c.d (aa:bb:cc:dd:ee:ff) em1: bound to a.b.d.e -- renewal in 432000 seconds I am kind of stuck: What might I have been doing wrong here??? Some kind soul around to give me a clue? THX in advance! Best, STEFAN
FF vs. Chrome/Chromium
Hi there! Last night I enjoyed reading through the different presentation slides from EuroBSDcon 2017. Relating to Theo's presentation on 'Pledge and Privsep' (https://www.openbsd.org/papers/eurobsdcon2017-pledge.pdf) he states that firefox cannot be pledged while "chrome was strongly pledged in <1 week". I assume that this actually is 'chromium', right? Disregarding any addons, is it valid to say that for OpenBSD users chromium is "safer" than FF as the latter is not pledgeable? Just curious. STEFAN
Re: Lenovo T440s
Am 08/04/17 um 06:38 schrieb Bryan Linton: > A few extra lines of harmless dmesg spam are a small price to pay > for having all the work the developers put in to bring newer drm > code and Skylake support to OpenBSD. > > I extend my own thanks to all those involved in such a feat. +1
Re: Mounting DVD with single file burned onto
Hi Josh! Thanks for caring! Am 07/19/17 um 22:58 schrieb Josh Grosse: > On Wed, Jul 19, 2017 at 09:24:56PM +0200, Stefan Wollny wrote: >> Hi there! >> >> Please excuse if this matter is not strictly OpenBSD-related even though >> I use OpenBSD. > > That's OK, I happen to be the maintainer of archivers/p7zip, and also of > sysutils/shunt, which you may want to experiment with. Way back in the > old days when I backed up to CD and later DVD, I used shunt to split > backups into disc-sized chunks and burn them in the backup pipeline. > I haven't used it in years, but it should work for this purpose. > >> When it comes to backups one usual advice (among others) is to make use >> of different storage types. So I have tar'ed one folder (~32GB) and >> zip'd with p7zip. man p7 explains the '-v{size}bkmg'-switch but I got >> "System ERROR: E_NOTIMPL". > > I am unable to recreate this problem on amd64. I just used > > $ vmctl create 100mb.file -s 100m > $ 7z a test.7z 100mb.file -v5k > > I obtained 4 output files, test.7z.0001 thru test.7z.0004. > This is the actual command and result: $ tar cf - /home/sw/Bilder/Nikon\ Transfer/20170430_Keukenhof/ | 7z a -t7z -m0=lzma -mx=9 -mfb=64 -md=32m -ms=on -v4880m -si Keukenhof_20170430.tar.7z tar: Removing leading / from absolute path names in the archive 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=de_DE.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs x64) System ERROR: E_NOTIMPL tar: Failed write to archive volume: 1: Broken pipe BUT: If I do it seperately like in your example it _does_ work out fine: $ 7z a -v4480m -t7z -m0=lzma -mx=9 -mfb=64 -md=32m -ms=on Keukenhof_20170430.7z Keukenhof_20170430.tar 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=de_DE.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs x64) Scanning the drive: 1 file, 35988090880 bytes (34 GiB) Creating archive: Keukenhof_20170430.7z Items to compress: 1 [ ... ] {I am aware that this is not fast but time is not an issue here.} >> ... Using split(1) I ended with several files of >> ~4.5GB each of which got burned to a DVD like so: >> >> $ doas growisofs -dvd-compat -Z /dev/rcd0c= > > This is your key problem. The ISO file in "" needs to be > a CD9660/UFS file system when you use this form of the growisofs(1m) > command. Instead, it contains random compressed bits. This is why you > cannot mount it. > > Practice burning with DVD-RW or DVD+RW media. You can continue to play > with it until you have your procedure correct, usable, and reproducable. > OK - seems I need more patience with mkhybrid-documentation... Thanks again - I will do my best to do my homework! Best, STEFAN
Mounting DVD with single file burned onto
Hi there! Please excuse if this matter is not strictly OpenBSD-related even though I use OpenBSD. When it comes to backups one usual advice (among others) is to make use of different storage types. So I have tar'ed one folder (~32GB) and zip'd with p7zip. man p7 explains the '-v{size}bkmg'-switch but I got "System ERROR: E_NOTIMPL". Using split(1) I ended with several files of ~4.5GB each of which got burned to a DVD like so: $ doas growisofs -dvd-compat -Z /dev/rcd0c= Burning took some time but finished without issues. NOW: How to get access to the part-file on the DVD? I cannot mount the DVD to get access to the part-file. Following the FAQ I used mkhybrid to produce .iso but this resulted in a significantly smaller file of ~340MB - beside that I doubt that this iso-file is correct it is a waste to burn this onto a DVD. I dd'ed the part-file to .iso which has the very same size and got burned to a DVD having the same result: I cannot mount the DVD to get access to the part-file. I read the applicable man-pages and searched in the archives, stackexchange and Google, but only found explanations on how to get a folder of a movie on _one_ DVD. I instead want to backup raw data. If I can't reassemble the part-files this is not a 'backup' but waste of time and money. Obviously I overlook something - could some kind soul give me hit with the clue stick? TIA. Best, STEFAN
Limit internet connection by time of day and number of hours
Hi there! "Security" means to constantly re-evaluate your options and processes - right? So the other day I checked the settings in the Fritz!Box router and remembered that they had implemented a time quota for a defined group of users (=IPs). Example: My young son has a tablet and a mobile phone (both Android) and has access to the internet with any device within a defined time frame and an overall maximum of x hours, individually set for each day of the week. In the rare cases that he needs more time he uses the joker named "Mama" ... ;-) (Side note: Just like pocket money the allowed time is regularly revised for age and experience - not behaviour!) Consider other situations where you'd like to meet your responsibilities: - There may be usual office times from 06:30 am to 21:00 pm (some people like to work early, other late): Outside of this time frame access to the internet may not be acceptable (with rare exections) - or might mean that a machine is hijacked to be a part of a bot or to do some bitcoin calculations... whatever. - Within this time frame noone is legally permitted to work longer than 8 hours based on his login credentials to the office net (not device). - Just some specified servers do backups to the cloud and e.g. are granted access the internet exclusively at night time (thus being exceptions to the general rule above). - The web and mail servers are seperate to the office net and always-on. The technical quest is in principal the same as the one I described above. Simply spoken: If noone of the 'guys and gals' responsible for safe and smooth operations is around the internet is turned off (or s/he gets paid overtime hours :-)). Can s.th. like this set up with OpenBSD being the central router? I searched the FAQ and several man-pages but didn't get an idea of how to proceed. My very first idea (=dream) was "e.g. set the general time frame with PF" and "the individual quotas or access times within anchors". Unfortunately nothing appropriate was found by the "leading" internet search engine. If someone has found a solution to such a task it would be great to get to know how this was achieved, of course with OpenBSD. Please: I am just curious and interested to learn about my (realistic) options. TIA. Best, STEFAN
Re: installboot(8)
Am 07/05/17 um 17:59 schrieb Joel Sing: > On Tuesday 04 July 2017 20:55:25 Paul de Weerd wrote: >> On Tue, Jul 04, 2017 at 08:34:56PM +0200, Stefan Wollny wrote: >> | Hi there! >> | >> | Sorry if this may sound like a rather stupid question: >> | (Referencing the examples section of man installboot(8)) >> | >> | Can s.o. verifiy that instead of >> | # installboot sd0 >> | >> | it is equally safe to issue >> | # installboot >> | (the DUID itself, of course)? >> | >> | My system is fully encrypted with sd1 usually being the (unencrypted) >> | boot disk - but if external USB disks are attached that number seems not >> | to be quaranteed. >> >> simply `installboot $(df -h / | grep -o -E '[ws]d[0-9]+')` >> >> There's definitely a difference between using the device name and the >> DUID: >> >> [weerd@pom] $ doas installboot -v `awk -F. '/ \/ / {print $1}' /etc/fstab` >> Using / as root >> installing bootstrap on /dev/rsd14c >> using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot >> 5c0d9a38cc895a7d: softraid volume with 0 disk(s) >> 5c0d9a38cc895a7d: installing boot loader on softraid volume >> /usr/mdec/boot is 6 blocks x 16384 bytes >> >> [weerd@pom] $ doas installboot -v $(df -h / | grep -o -E '[ws]d[0-9]+') >> Using / as root >> installing bootstrap on /dev/rsd14c >> using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot >> sd14: softraid volume with 1 disk(s) >> sd14: installing boot loader on softraid volume >> /usr/mdec/boot is 6 blocks x 16384 bytes >> sd0a: installing boot blocks on /dev/rsd0c, part offset 144 >> master boot record (MBR) at sector 0 >> partition 3: type 0xA6 offset 64 size 1953520001 >> /usr/mdec/biosboot will be written at sector 64 >> >> So if I were you, I'd continue using the device for now. > > Note that this will only apply in the case where the disk is a bootable > softraid volume - in the non-softraid case either is fine and the DUID is > likely preferable. > Hi Joel, THANK YOU for caring. This is actually a bootable softraid volume (key-based encryption of the entire disk of the laptop): This is the physical disk:u $ dmesg | grep sd0 sd0 at scsibus1 targ 5 lun 0: SCSI3 0/direct fixed naa.500253887007d4c5 sd0: 976762MB, 512 bytes/sector, 2000409264 sectors, thin And this is the softraid volume I boot from: sd1 at scsibus3 targ 1 lun 0: SCSI2 0/direct fixed sd1: 976756MB, 512 bytes/sector, 2000397143 sectors I have set up a little script for updating to the latest published version of ~current-amd64. In the course of the discussions related to KARL I noticed that I didn't run installboot at the end of the process. This is why I asked. Following your advice I will adjust the script I use at home with my (unencrypted) backup server to use the DUID. Best, STEFAN
Re: installboot(8)
Am 07/04/17 um 20:55 schrieb Paul de Weerd: > On Tue, Jul 04, 2017 at 08:34:56PM +0200, Stefan Wollny wrote: > | Hi there! > | > | Sorry if this may sound like a rather stupid question: > | (Referencing the examples section of man installboot(8)) > | > | Can s.o. verifiy that instead of > | # installboot sd0 > | > | it is equally safe to issue > | # installboot > | (the DUID itself, of course)? > | > | My system is fully encrypted with sd1 usually being the (unencrypted) > | boot disk - but if external USB disks are attached that number seems not > | to be quaranteed. > > simply `installboot $(df -h / | grep -o -E '[ws]d[0-9]+')` > > There's definitely a difference between using the device name and the > DUID: > > [weerd@pom] $ doas installboot -v `awk -F. '/ \/ / {print $1}' /etc/fstab` > Using / as root > installing bootstrap on /dev/rsd14c > using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot > 5c0d9a38cc895a7d: softraid volume with 0 disk(s) > 5c0d9a38cc895a7d: installing boot loader on softraid volume > /usr/mdec/boot is 6 blocks x 16384 bytes > > [weerd@pom] $ doas installboot -v $(df -h / | grep -o -E '[ws]d[0-9]+') > Using / as root > installing bootstrap on /dev/rsd14c > using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot > sd14: softraid volume with 1 disk(s) > sd14: installing boot loader on softraid volume > /usr/mdec/boot is 6 blocks x 16384 bytes > sd0a: installing boot blocks on /dev/rsd0c, part offset 144 > master boot record (MBR) at sector 0 > partition 3: type 0xA6 offset 64 size 1953520001 > /usr/mdec/biosboot will be written at sector 64 > > So if I were you, I'd continue using the device for now. > Thank you - excellent explanation and advice! Best, STEFAN
installboot(8)
Hi there! Sorry if this may sound like a rather stupid question: (Referencing the examples section of man installboot(8)) Can s.o. verifiy that instead of # installboot sd0 it is equally safe to issue # installboot (the DUID itself, of course)? My system is fully encrypted with sd1 usually being the (unencrypted) boot disk - but if external USB disks are attached that number seems not to be quaranteed. TIA! Best, STEFAN
Re: acme-client(1) and http_proxy
Gesendet: Mittwoch, 26. April 2017 um 06:16 Uhr Von: "Predrag Punosevac" An: misc@openbsd.org Betreff: Re: acme-client(1) and http_proxy [ ... ] > Best, > Predrag > > P.S. In all my years on this mailing list I have seen nothing but the > most insightful, helpful, and polite answers by Mr. Stuart Henderson. +1 > If he had labeled my post as a "Fake news :)" I would reflect on it > before posting again in the same thread. Words of wisdom here
Re: OpenBSD 6.1, boot can't find kernel anymore => issue solved on my part
Gesendet: Dienstag, 25. April 2017 um 14:39 Uhr Von: "Stefan Wollny" An: misc@openbsd.org Betreff: Re: OpenBSD 6.1, boot can't find kernel anymore Gesendet: Montag, 24. April 2017 um 17:27 Uhr Von: "Todd C. Miller" An: "Nicolas Vollmar" Cc: misc@openbsd.org Betreff: Re: OpenBSD 6.1, boot can't find kernel anymore You need to post your /var/run/dmesg.boot if you want someone to help you debug this. - todd I am struck (most likely) by the same issue since this morning. I upgraded amd64-current from ftp.hostserver.de. The problem is a little bit more tricky as the system is fully encrypted (key-based). The usb-key itself seems to be untampered as the system is unlocked and the system wants to start. Yet: --- quote --- boot> booting sr0a:/bsd: sr0a:/bsd: Inappropriate file type of format failed(79). will try /bsd Turning timeout off boot> --- end of quote --- At that point the startup process stops. But I am able to enter "bsd.rd" and the rd-kernel starts. As I am not at home it is not possible to get an internet connection thus trying to rerun the upgrade is not possible. But with the ramdisk system I am able to mount / and /home and thus able to copy the previous bsd.mp to /bsd. Still no luck, just that it now says "... format failed(0)." Interestingly at the boot prompt I can issue a "ls". Beside the usual suspects I see after the line for "bsd.rd" the following: --- quote --- stat(sr0a:/./sys): No such file or directory --- end of quote --- I was able to save a dmesg from the bsd.rd which is attached as txt-file. I guess once I am back at home having a LAN connection I will be able to rerun the upgrade process. Does someone have any idea what I might do until then? (And Yes - I have a full backup ;-) ) Best, STEFAN Just as a follow-up: I managed to boot with an older kernel still residing on the disk. For what reason ever the bsd.mp-file was not downloaded entirely - just about 2MB. Now I am back on the track. Sorry for the noise. Best, STEFAN
Re: OpenBSD 6.1, boot can't find kernel anymore
Gesendet: Montag, 24. April 2017 um 17:27 Uhr Von: "Todd C. Miller" An: "Nicolas Vollmar" Cc: misc@openbsd.org Betreff: Re: OpenBSD 6.1, boot can't find kernel anymore You need to post your /var/run/dmesg.boot if you want someone to help you debug this. - todd I am struck (most likely) by the same issue since this morning. I upgraded amd64-current from ftp.hostserver.de. The problem is a little bit more tricky as the system is fully encrypted (key-based). The usb-key itself seems to be untampered as the system is unlocked and the system wants to start. Yet: --- quote --- boot> booting sr0a:/bsd: sr0a:/bsd: Inappropriate file type of format failed(79). will try /bsd Turning timeout off boot> --- end of quote --- At that point the startup process stops. But I am able to enter "bsd.rd" and the rd-kernel starts. As I am not at home it is not possible to get an internet connection thus trying to rerun the upgrade is not possible. But with the ramdisk system I am able to mount / and /home and thus able to copy the previous bsd.mp to /bsd. Still no luck, just that it now says "... format failed(0)." Interestingly at the boot prompt I can issue a "ls". Beside the usual suspects I see after the line for "bsd.rd" the following: --- quote --- stat(sr0a:/./sys): No such file or directory --- end of quote --- I was able to save a dmesg from the bsd.rd which is attached as txt-file. I guess once I am back at home having a LAN connection I will be able to rerun the upgrade process. Does someone have any idea what I might do until then? (And Yes - I have a full backup ;-) ) Best, STEFAN OpenBSD 6.1-current (RAMDISK_CD) #15: Mon Apr 24 11:04:03 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 17079074816 (16287MB) avail mem = 16557711360 (15790MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 2594.40 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2594397370 Hz cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu at acpi0 not configured acpitz at acpi0 not configured "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not configured "ETD0403" at acpi0 not configured "PNPC000" at acpi0 not configured "PNP0C0C" at acpi0 not configured "PNP0C0E" at acpi0 not configured "PNP0C0D" at acpi0 not configured "ACPI0003" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT340E" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi pci1 at ppb0 bus 1 vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06 wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) "Intel Core 4G HD Audio" rev 0x06 at pci0 dev 3 function 0 not configured xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x05: msi usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 "Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured ehci0 at pci0 dev 26 function 0 "Intel 8 Series USB" rev 0x05: apic 2 int 16 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel 8 Series HD Audio" rev 0x05 at pci0 dev 27 function 0 not configured ppb1 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd5 pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 2 "Intel 8 Series PCIE" rev 0xd5: msi pci3 at ppb2 bus 3 iwm0 at pci3 dev 0 function 0 "Intel Dual Band Wireless AC 7260" rev 0xbb, msi ppb3 at pci0 dev 28 function 3 "Intel 8 Series PCIE" rev 0xd5: msi pci4 at ppb3 bus 4 rtsx0 at pci4 dev 0 function 0 "Realtek RTL8411 Card Reader" rev 0x01: msi sdmmc0 at rtsx0: 4-bit re0 at pci4 dev
Firefox: Recenty instable
Hi there, for the last 3~4 days (always running the latest of public amd64-current) firefox behaviour was kind of "unfamiliar" - regular crashes after a few minutes. Starting firefox in a xterm gave me this: ~ $ firefox firefox:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program 1489350944851 addons.update-checker WARNUpdate manifest for e10sroll...@mozilla.org did not contain an updates property 1489350944986 addons.update-checker WARNUpdate manifest for fire...@getpocket.com did not contain an updates property 1489350944998 addons.update-checker WARNUpdate manifest for webcom...@mozilla.org did not contain an updates property 1489350945009 addons.update-checker WARNUpdate manifest for aushel...@mozilla.org did not contain an updates property 1489350945022 addons.update-checker WARNUpdate manifest for {972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property Assertion failure: addr == p, at /usr/obj/ports/firefox-52.0/firefox-52.0/js/src/jit/ProcessExecutableMemory.cpp:322 Segmentation fault (core dumped) Am I right supposing that the most likely answer will be "Wait for the next snap!"? :-) Best, STEFAN OpenBSD 6.1-beta (GENERIC.MP) #7: Sat Mar 11 18:32:03 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16556789760 (15789MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec080 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! TCPA SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 2594.34 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2594337860 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 2594.00 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 2594.00 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 2594.00 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x
Re: Please: Is there ANY chance that Linux binaries might run again???
Am 03/09/17 um 21:55 schrieb Marc Espie: ... > In my opinion, there's more chance vmm will eventually be mature > enough to run a virtual linux machine than the return of userland > linux emulation. > This is what I am hoping for - it is just this particular piece of software that I need from time to time. Anything else I can achieve with what OpenBSD offers (or more precisely: what the OpenBSD-devs kindly provide). But who knows - maybe some future version of LibreOffice (or any other free/open program) is good enough to meet my requirements (in particular formats).
Re: Please: Is there ANY chance that Linux binaries might run again???
Am 03/09/17 um 22:44 schrieb bofh: > On Tue, Mar 7, 2017 at 4:01 PM, Stefan Wollny wrote: > >> Hi there, >> >> I have to live up to my obligations - and one of them is to be able to >> work with M$-Word docs. I used to do this with SoftMaker's office suite, >> but since Linux-compat is gone I am stuck with LibreOffice which is just >> a PITA. >> > > If you have Internet access, why not use Google Docs or one of the other > web based apps? > For the very reason I use OpenBSD: Confidentiality. The financial industry takes 'confidentiality' quite serious - if you're in a weak position. ;-) Technically I may be the 'owner' of the documents but legally it is my client. And being just a self-employed mini-business I cannot engage a big legal dept to discuss any implications that may arise from using web-/cloud-based office solutions. Nevertheless: Thank you for bringing such a solution up. Best, STEFAN
Re: Please: Is there ANY chance that Linux binaries might run again???
> Gesendet: Donnerstag, 09. März 2017 um 09:43 Uhr > Von: "Stuart Henderson" > An: misc@openbsd.org > Betreff: Re: Please: Is there ANY chance that Linux binaries might run again??? > > On 2017-03-07, Stefan Wollny wrote: > > at home this is the way I go, too. But I have to travel to my client's > > place (by train!) and when working in the evening in the hotel room like > > tonight (as I have to leave the office building by 8 pm at the latest) > > it is somewhat inconvenient to take a second laptop with me. > > Is qemu any good for this or is it too slow? I am not at all familiar with qemu but doesn't this imply to run Win* on my OpenBSD-system? NEVER, EVER! > > Otherwise the easiest way at present is probably to dual-boot or boot > Linux from a USB stick, or run it on a remote system. Shorthandedly this is my way to get the job done: Installed Linux on a USB3-Stick with dd-comand from iso. Runs acceptably fast. Just need to switch from BIOS to UEFI. The only thing I noticed: Working at some distance to the WLAN access point with OpenBSD I have a connection but not with Linux though using the same hardware (iwm0). Another good reason to stick with OpenBSD and donate (already I miss the anticipation of receiving another set of CDs). > > Additionally, while the answer to "is there any chance" is no, the > answer to "any chance 32-bit Linux binaries will run on OpenBSD/amd64" > would be "hell no". :-D Is it correct then to imply that 64-bit binaries might run? > > > Yes - I will (again) contact SoftMaker trying to persuade them to > > provide an OpenBSD-version of their office suite. But they seem to have > > none with some decent Unix/OpenBSD-knowledge, just Linux. Sigh... > > They'll need a new binary for every OS uodate, and a different one for > 32/64 bit. While I'd love to see it (I paid for softmaker office and prefer > it over libreoffice or MSWord), I think this is unrealistic. > Yupp - I know why I asked here. I've used it on OpenBSD until Linux-compat was gone and everytime I tried to work with LibreOffice since I missed Softmake's office tools even more. (BTW - if the city of Munich had chosen to use Softmaker's office with LiMux I bet there would habe been less complaints about compatability with M$-documents. My 2c.) Just to be clear: LibreOffice is accaptable as long as it is LibreOffice only! Even though I am aware of the implications that come with an OpenBSD-version for Softmaker I will still ask - sometimes one has to try the unrelistic to make a progress. ;-) (As they support Mozilla's Thunderbird I hope they will at least listen before saying NO.)
Re: Please: Is there ANY chance that Linux binaries might run again???
Am 03/07/17 um 22:50 schrieb Damian McGuckin: > On Tue, 7 Mar 2017, Ingo Schwarze wrote: > >> Regarding your task at hand: >> >> If you want to run MS Word, your best bet is running MS Windows. >> If you want to run binary-only Linux software, your best bet is >> running Linux. Ideally, on dedicated hardware that is not >> connected to the Internet. > > We use OpenBSD for crucial server infrastructure, Linux for some > end-user applications, and have a Windows Machine to which anyone can > connect with an RDP client like 'rdesktop'. We use Windows Terminal > Server if lots of people need a Windows system. > > Regards - Damian > > Pacific Engineering Systems International, 277-279 Broadway, Glebe NSW 2037 > Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted > here > Views & opinions here are mine and not those of any past or present > employer > Hi Damian, at home this is the way I go, too. But I have to travel to my client's place (by train!) and when working in the evening in the hotel room like tonight (as I have to leave the office building by 8 pm at the latest) it is somewhat inconvenient to take a second laptop with me. Yes - I will (again) contact SoftMaker trying to persuade them to provide an OpenBSD-version of their office suite. But they seem to have none with some decent Unix/OpenBSD-knowledge, just Linux. Sigh... Best, STEFAN
Re: Please: Is there ANY chance that Linux binaries might run again???
Am 03/07/17 um 22:43 schrieb Ingo Schwarze: > Hi, > > Stefan Wollny wrote on Tue, Mar 07, 2017 at 10:01:49PM +0100: > >> ANY chance that there will be a way to run Linux binaries again? > > Usually, i'm wary of making definite statements about the future, > but in this case, a clear "NO" semms like a very safe bet. > > Syscall compat layers cause maintenance effort, risk of bugs, and > provide absolutely no benefit with respect to the project goals. > So even if somebody would submit a perfect, clean implementation > and credibly volunteer to maintain it, i don't think it would stand > a chance of getting committed. > > > Regarding your task at hand: > > If you want to run MS Word, your best bet is running MS Windows. > If you want to run binary-only Linux software, your best bet is > running Linux. Ideally, on dedicated hardware that is not > connected to the Internet. > > Some people run such systems they need for special non-Internet > tasks in virtual machines. I wouldn't recommend that, though. > Separate, physically disconnected hardware is safer and faster. > If you create documents for paying clients, buying the required > hardware is likely to quickly amortize - or if not, you have > worse problems with your business model than the choice of the > operating system best suited to each of your tasks. > > Yours, > Ingo > Hi Ingo, thanks for your quick reply - I am aware of the good reasons to abandon Linux-compat - not going to question this. Nevertheless tonight I need to work on a 50+ pages Word-doc and the only tool at hand is LibreOffice which ... . Using "Windoof" is not an option for me - it feels like my system getting cancer. SoftMaker's Linux-based Word-clone is a proven good and acceptable alternative as it's compatibility with Word (in particular with formats) is exceptionally good (closed source with a decent price and page 49 IS page 49! Will it eventually be possible to run a Linux system with OpenBSD's vmm(4)? Even though this might be considered to be just a "second class" solution to my quest - it would allow me to stay with OpenBSD, only going the Linux-way for specific tasks inside. Best, STEFAN
Please: Is there ANY chance that Linux binaries might run again???
Hi there, I have to live up to my obligations - and one of them is to be able to work with M$-Word docs. I used to do this with SoftMaker's office suite, but since Linux-compat is gone I am stuck with LibreOffice which is just a PITA. As at the end of the day I have to deliver results in a form my clients wants and pays for; switching to e.g. LaTeX is not an option (= is not paid). "If you only have a hammer, every task looks like a nail!" - I will have to use a Linux Live-CD system to deliver shorthandedly. But I'd really prefer to stick to OpenBSD on my main production system. ANY chance that there will be a way to run Linux binaries again? (On my own risk, of course!) With search engines I only found outdated information. Either which way, any hint is welcome. Best, STEFAN
Re: splassert: yield message on 5 Feb snapshot (amd64)
Am 02/09/17 um 18:02 schrieb Martin Pieuchot: > On 09/02/17(Thu) 17:55, Stefan Wollny wrote: >> Am 02/08/17 um 17:57 schrieb Hrvoje Popovski: >>> On 8.2.2017. 17:51, Scott Vanderbilt wrote: >>>> Updated a machine to latest (5 Feb.) snapshot of amd64. I'm now seeing >>>> the following message after booting that I've not recalled seeing before: >>>> >>>>splassert: yield: want 0 have 1 >>> >>> >>> add sysctl kern.splassert=2 ... >>> >> >> Here you go: >> >> OpenBSD 6.0-current (GENERIC.MP) #163: Sun Feb 5 13:55:12 MST 2017 >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > This should be fixed now. Please update from source or wait for the next > snapshot. If the problem still persist, report back. > Hi Martin, at least with $ dmesg | grep Open OpenBSD 6.0-current (GENERIC.MP) #166: Wed Feb 8 19:15:03 MST 2017 the issue still persists. I'll check with the next snapshot. Thank you for caring! Best, STEFAN
Re: splassert: yield message on 5 Feb snapshot (amd64)
Am 02/08/17 um 17:57 schrieb Hrvoje Popovski: > On 8.2.2017. 17:51, Scott Vanderbilt wrote: >> Updated a machine to latest (5 Feb.) snapshot of amd64. I'm now seeing >> the following message after booting that I've not recalled seeing before: >> >>splassert: yield: want 0 have 1 > > > add sysctl kern.splassert=2 ... > Here you go: OpenBSD 6.0-current (GENERIC.MP) #163: Sun Feb 5 13:55:12 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16556802048 (15789MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec080 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! TCPA SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(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) Core(TM) i5-4210M CPU @ 2.60GHz, 2594.40 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2594401360 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 2594.00 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 2594.00 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,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 2594.00 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 120 degC "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not configured "ETD0403" at acpi0 not configured tpm0 at acpi0: TPM_ addr 0xfed4/0x5000: Infineon SLB9635 1.2 rev 0x10 "PNPC000" at acpi0 not configured acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: LID0 acpiac0 at acpi0: AC unit offline acpibat0 at acpi0: BAT0 model "BAT" serial 0001 type LION oem "Notebook" "PNP0C14" at acpi0 not configured "INT340E" at acpi0 not configured acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: LCD0 cpu0: Enhanced SpeedStep 2594 MHz: speeds: 2601, 2600, 2500, 2300, 2200, 2100, 2000, 1800, 1700, 1600, 1400, 1300, 1200, 1100, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 ppb0 at pci0 dev 1 function 0 "In
Re: Ripping CDs and DVDs
> Gesendet: Sonntag, 30. Oktober 2016 um 16:21 Uhr > Von: "Simon Ruderich" > An: "Vijay Sankar" > Cc: misc > Betreff: Re: Ripping CDs and DVDs > > On Sat, Oct 22, 2016 at 05:44:59PM -0500, Vijay Sankar wrote: > > Hi, > > > > In preparation for my retirement in 2050, I am setting up a media server > > for all my DVDs and CDs. > > > > For ripping CD's, I was planning to use abcde as follows: > > > > abcde -q high -o mp3 > > Hello, > > For long term storage you might want to consider a more modern > format like flac (for lossless compression) or ogg/vorbis (better > quality than mp3). > > I use cdparanoia and oggenc (for ogg/vorbis). I think abcde can > use flac/vorbis too, but haven't used it. > [ ... ] Hi Vijay, thank you for your question as I learned about the "-q"-switch for abcde. Interested I tried it last night and noticed that it is not working on my amd64-current box. Actually this is compliant with the man page as this switch is listed but not explained (but it is on the Ubuntu-based Linux-box I cross-checked). How did you manage to use this switch on OpenBSD? Beside this I would second Simon on choosing the 'flac' format. Best, STEFAN
Re: System broken???
Am 12.08.2016 um 21:14 schrieb Theo de Raadt: > why don't YOU invest your time > figuring out that first? This is what I have been doing for the last 36 hours, no sleep - no success... Please forget it. Sorry for the noise.
System broken???
I know that the majority of people on this list are quite experienced with hardware as well: Maybe it is a hardware issue, likely not OpenBSD-related... Since the night before last my system writes "q"s where ever possible... Startup is not possible because at the "boot: " prompt very fast "q"s are printed that would be taken as input if is hit. (BIOS, not UEFI) My system is ~amd64-current. I can't copy a dmesg as I cannot start the system. A few days ago I asked about help as thunderbird was disfunct due to W^X issues - the dmesg I posted then is the last I can point your interest to. This was solved and the night after I updated t'bird via ports the system went broke. :-( The input buffer apparently was filled with "q"s and then started beeping waking up the entire family. If I use a Linux-Live-CD on the troublesome machine the very same behaviour happens if I open a xterm or click into the address bar in the browser. My system is fully encrypted with a key disk. Yes, I can use the SSD in an other laptop, but X does not not start. The console there is a decent workaround to transfer the relevant files to an external disk. Unless s.o. has an idea about how to solve this issue I will have to send this laptop to the manufacturer as I still have guarantee. It is just that since today I urgently need particularly this machine. Very frustrated... (I use a Linux box instead with an awfully bad screen). Any hint is welcome. TIA. Best, STEFAN
Re: thunderbird segfaults
Am 08/08/16 um 17:21 schrieb Theo Buehler: > > A fix for thunderbird is being worked on: > THANK YOU - THANK YOU - THANK YOU!!! Just updated via ports and thunderbird is fine again!
No automatic start of privoxy
Hi there! My proxy server running privoxy and squid died the other day and as a replacement I set up an old Thinkpad T60 running ~i386-current: OpenBSD 6.0-current (GENERIC.MP) #2009: Sun Aug 7 20:43:06 MDT 2016 (Full dmesg at the end.) I have the following in /etc/rc.conf.local: pkg_scripts=freshclam clamd messagebus avahi_daemon privoxy squid cupsd BUT: 'privoxy' does not start at system-startup as the other progs do. So I added the following to /etc/rc.local: rcctl start privoxy No success. I changed the line in /etc/rc.local to privoxy --user _privoxy /etc/privoxy/config No success. After startup I tried to run $ doas rcctl start privoxy No success: rcctl quits with privoxy(failed) The only thing that _does_ work is running $ doas privoxy --user _privoxy /etc/privoxy/config Strange ... I never noticed this behaviour with the old server (i386-current GENERIC). After reboot privoxy always came up as expected, just like squid did and does now. Maybe it is a case of screwed permissions, maybe s.th. else. Could some kind soul point me into the right direction? What am I missing / doing wrong? TIA. Best, STEFAN OpenBSD 6.0-current (GENERIC.MP) #2009: Sun Aug 7 20:43:06 MDT 2016 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz cpu0: FPU,V86,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,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF,SENSOR real mem = 3219472384 (3070MB) avail mem = 3145105408 (2999MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 12/22/06, BIOS32 rev. 0 @ 0xfd6b0, SMBIOS rev. 2.4 @ 0xe0010 (68 entries) bios0: vendor LENOVO version "79ETC9WW (2.09 )" date 12/22/2006 bios0: LENOVO 2007VG2 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz cpu1: FPU,V86,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,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF,SENSOR ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "PNP0303" at acpi0 not configured "IBM0057" at acpi0 not configured "ATM1200" at acpi0 not configured acpibat0 at acpi0: BAT0 model "92P1139" serial 2887 type LION oem "Panasonic" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: LCD0 acpivideo1 at acpi0: VID_ acpivout at acpivideo1 not configured bios0: ROM list: 0xc/0xfe00 0xd/0x1000 0xd1000/0x1000 0xdc000/0x4000! 0xe/0x1! cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2000, 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03 ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: apic 1 int 16 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility X1300 M52-64" rev 0x00 drm0 at radeondrm0 radeondrm0: apic 1 int 16 azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog Devices AD1981HD audio0 at azalia0 ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int 20 pci2 at ppb1 bus 2 em0 at pci2 dev 0 function 0 "Intel 82573L" rev 0x00: msi, address 00:15:58:81:15:fb ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int 21 pci3 at ppb2 bus 3 wpi0 at pci3 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02:
Solved: Copy-Paste not possible from a xterm
> Gesendet: Montag, 08. August 2016 um 21:51 Uhr > Von: "Edgar Pettijohn" > An: "Mihai Popescu" > Cc: misc@openbsd.org > Betreff: Re: Copy-Paste not possible from a xterm > > I can't remember which of these I use because it's a muscle memory deal, but > it's either ctrl + insert or shift + insert after highlighting the text of > course. I think it requires some magic words in a resource file somewhere to > use the clipboard. > Hi Edgar, thanks again for taking the time to reply. Actually 'shift + insert' does copy the content of the clipboard. But this content is not the marked-up line from xterm! Example: Using a graphical editor like e.g. NEdit I can mark a line within and copy this line to the clipboard via 'ctrl + c'. It is this content that could be inserted via 'shift + insert'. BUT my issue is different: Until recently I could copy and paste from a xterm by simply marking a line (or several lines) and by pressing left and right mouse buttons simultaneously this line / these lines were copied at the position of the cursor. It is this behaviour that seemed to no longer working on my system. Dimitrij Czarkoff posted the relevant section of man mouse(4): Option "Emulate3Buttons" Re-reading this several times lead to the solution. The system is a laptop with two buttons below the touchpad but I have an external mouse attached with a physical third button - simply pressing this button did the trick. Sigh... no idea why the emulation of the third button does no longer work. Will test this with the external mouse detached - but not tonight. Thank you all!!! Best, STEFAN
Re: Copy-Paste not possible from a xterm
> Gesendet: Montag, 08. August 2016 um 21:36 Uhr > Von: "Mihai Popescu" > An: misc@openbsd.org > Betreff: Re: Copy-Paste not possible from a xterm > > > For some time now I cannot copy-paste text from a xterm window by > > simultaneously \ > > pressing left and right mouse buttons. > > > Anyone an idea? > > Um, carpal tunnel syndrome? > Nice - but no. > I know somebody unable to double click after a heavy drinking night. > But he was able to manage this by clicking one time followed by Enter > key. So, no panic. > Looks to me that I missed to find the right words to explain the issue correctly. My bad. New try: I open an xterm and e.g. want to see the content of /etc/fstab. So I issue $ cat /etc/fstab Now I want to copy one line to thunderbird or a web client via firefox. I used to do this by marking the relevant line, change to the other application (say: the web client) and press left and right mouse buttons simultaneously. Until some time ago this procedure inserted the marked-up line at the position of the cursor. No double-click, no Enter. Standard Unix - right? Exactly this procedure is disfunct on my system. No idea why, no idea where to look at. No big thing, just wondering if I missed s.th. or else. I know how to circumvent this non-behaviour in most cases. Just wanted to know if s.o. else witnessed the same and maybe has an answer. Maybe I need to additionally post some specific settings I am not aware of. OK? Best, STEFAN
Re: thunderbird segfaults
> Gesendet: Montag, 08. August 2016 um 18:08 Uhr > Von: "Theo de Raadt" > An: "Stefan Wollny" > Cc: "Theo Buehler" , misc@openbsd.org, dco...@gmail.com > Betreff: Re: thunderbird segfaults > [ ... ] > > > So much space and no separate /usr/local ? why? > > > > > Lazyness :-) and not being a developer I find it suitable for my needs > > (flexibility with growing needs under /usr ): If _really_ necessary (about > > once in 2 years) I simply install everything fresh but /home. > > You installed using non-default methods. > > You are on your own. > I am aware of this - no complaints! It is just that until last week thunderbird has been working flawless. > Seriously. Do you think we select these defaults to be a pain? > Of course not! A long time ago having only a small disk I was bitten by poor estimation of how much I need for /usr, /usr/local, /usr/ports, /usr/src and /usr/X11R6. Going with one single /usr-partition (mounted read-only) was an easy solution fitting my needs not being a developer. It didn't come to my mind that this may be troublesome as everything worked as expected and 'man disklabel(8)' recommends this for disks > 2 GB - my lame excuse for being lazy ;-). I agree that with the introduction of pledge(2) I should better do my homework again. Splitting /usr (using 21GB) at least into /usr and /usr/local is no big thing as by now I know better what I want - probably should set up an additional /usr/local/bin to be mounted 'wxallowed' unless it is possible to run individual binaries 'W^X allowed' (or even better "not necessary"...). Just a thought - the last aspect might be worth mentioning in 'man disklabel(8)'. I'd like to thank you and all the others who took the time to reply. All the best, STEFAN
Re: thunderbird segfaults
Hi Theo! > Gesendet: Montag, 08. August 2016 um 17:21 Uhr > Von: "Theo Buehler" > An: misc@openbsd.org > Betreff: Re: thunderbird segfaults > > > disklayout: > > a: 5122.2M / > > b: 1019.8M swap > > d: 10244.6M /tmp > > e: 15359.0M /var > > f:30718.0M /usr > > g: 914285.1M/home > > > > /usr is mounted read-only > > /var is mounted no-exec > > So much space and no separate /usr/local ? why? > Lazyness :-) and not being a developer I find it suitable for my needs (flexibility with growing needs under /usr ): If _really_ necessary (about once in 2 years) I simply install everything fresh but /home. > If this is really the case, please make sure /usr is mounted wxallowed, > see https://www.openbsd.org/faq/upgrade60.html > Yes - it is mounted wxallowed (Janne@ was the very first today to ask this). > > $ thunderbird > > out of memory > > Assertion failure: [unhandlable oom] OOM in createJitRuntime, at > > > > /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt.cpp:1228 > > Segmentation fault (core dumped) > > Known problem: https://marc.info/?t=14705703312&r=1&w=2 > > > thunderbird(30766): mmap W^X violation > > soffice.bin(68962): mprotect W^X violation > [..] > > xpcshell(5887): mmap W^X violation > > A fix for thunderbird is being worked on: > https://marc.info/?l=openbsd-ports&m=147066911817646&w=2 > David Coppa kindly posted this to me as well. This is good to know and I will patiently wait and see if I can do some tests. This awful thing named "day job" prevented easy thinking: Should have checked bugs@ myself - thanks for pointing me in this direction. > The others will follow as soon as someone finds the time. > Theo@ attested to me some time ago that this is way beyond my skills... sadly I have to admit that he is right. Thank you for taking the time to reply. Best, STEFAN
Re: thunderbird segfaults
> Gesendet: Montag, 08. August 2016 um 16:40 Uhr > Von: "Edgar Pettijohn" > An: "Stefan Wollny" > Cc: Tinker , misc@openbsd.org > Betreff: Re: thunderbird segfaults > > I've had problems in the past trying to build a port that fails and then > install the binary version and it work. So if you haven't already maybe try > deleting it and reinstall the binary from a mirror. Hi Edgar, thank you for replying - unfortunately this didn't work out either. I just did a 'pkg_delete' and 'pkg_add' dance but not success. Still segfaults. Best, STEFAN > > Sent from my iPhone > > > On Aug 8, 2016, at 9:23 AM, Stefan Wollny wrote: > > > > Hi Tinker! > > > > Thank you for replying! My answers are in-line (sorry for the awful > formatting - the web-client is a PITA) > > > > Best, > > STEFAN > > > > > > Am 08.08.2016 15:02 schrieb Tinker: > > > >Please describe more, > > > > * Any idea of your memory situation (ulimit -a , RAM and swap > >available, actual memory consumption)? > > > > > > RAM as given in the dmesg: > > > >real mem = 17082359808 (16291MB) > >avail mem = 16560173056 (15793MB) > > > > > > As copy/paste is not possible the following is a transcript for 'ulimit > -a': > > time(cpu-seconds) unlimited > > file(blocks) unlimited > > coredump(blocks) unlimited > > data(kbytes) 1572864 > > stack(kbytes) 4096 > > lockedmem(kbytes) 5390336 > > memory(kbytes)16141956 > > nofiles(descriptors) 512 > > processes 256 > > > > > > disklayout: > > a: 5122.2M / > > b: 1019.8M swap > > d: 10244.6M /tmp > > e: 15359.0M /var > > f:30718.0M /usr > > g: 914285.1M/home > > > > /usr is mounted read-only > > /var is mounted no-exec > > > > > > > > * Also does it crash on start or can you use it for a while > > > > > > NO - it doesn't start at all as stated in my original post: > > > >$ thunderbird > >out of memory > >Assertion failure: [unhandlable oom] OOM in createJitRuntime, at > > > /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt. > cpp:1228 > >Segmentation fault (core dumped) > > > > > > > >The following is beyond my level of experience but are you sure that > >you run it in an isolated enough mode so no plugins or other config > >can interfere. > > > > > > Well ... thunderbird was doing fine until I got a fresh ~current-version > before last weekend. S.th. must have changed since then. I even recompiled the > system from a fresh checkout of cvs-src this morning and tried to do 'make > update' from ports - no success, sadly. > > > > > > > >On 2016-08-08 19:44, Stefan Wollny wrote: > > > >Hi there! > > > >My system: > >OpenBSD 6.0-current (GENERIC.MP) #2335: Sun Aug 20:50:41 MDT 2016 > >(Full dmesg at the end.) > > > >I don't know if this is only with my system but since the last few > >days Mozilla's thunderbird segfaults. > > > >$ thunderbird > >out of memory > >Assertion failure: [unhandlable oom] OOM in createJitRuntime, at > > > /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt. > cpp:1228 > >Segmentation fault (core dumped) > > > >gdb -c thunderbird.core says > >Programm terminated with signal 11, Segmentation fault. > >#0 0x185a890c472a in ?? () > > > >Running 'doas make update' in /usr/ports/mozilla-thunderbird ends > with > >the following: > >[...] > >Executing > /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/xpcshell -g > >/usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/bin/ -a > >/usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/bin/ -f > > > /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps > /installer/precompile_cache.js > >-e precompile_startupcache("resource://gre/"); > >out of memory > >Assertion failure: [unhandlable oom] OOM in createJitRuntime, at > > > /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt. > cpp:1228 > >Traceback (
Re: thunderbird segfaults
Hi Tinker! Thank you for replying! My answers are in-line (sorry for the awful formatting - the web-client is a PITA) Best, STEFAN Am 08.08.2016 15:02 schrieb Tinker: Please describe more, * Any idea of your memory situation (ulimit -a , RAM and swap available, actual memory consumption)? RAM as given in the dmesg: real mem = 17082359808 (16291MB) avail mem = 16560173056 (15793MB) As copy/paste is not possible the following is a transcript for 'ulimit -a': time(cpu-seconds) unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 1572864 stack(kbytes) 4096 lockedmem(kbytes) 5390336 memory(kbytes)16141956 nofiles(descriptors) 512 processes 256 disklayout: a: 5122.2M / b: 1019.8M swap d: 10244.6M /tmp e: 15359.0M /var f:30718.0M /usr g: 914285.1M/home /usr is mounted read-only /var is mounted no-exec * Also does it crash on start or can you use it for a while NO - it doesn't start at all as stated in my original post: $ thunderbird out of memory Assertion failure: [unhandlable oom] OOM in createJitRuntime, at /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt.cpp:1228 Segmentation fault (core dumped) The following is beyond my level of experience but are you sure that you run it in an isolated enough mode so no plugins or other config can interfere. Well ... thunderbird was doing fine until I got a fresh ~current-version before last weekend. S.th. must have changed since then. I even recompiled the system from a fresh checkout of cvs-src this morning and tried to do 'make update' from ports - no success, sadly. On 2016-08-08 19:44, Stefan Wollny wrote: Hi there! My system: OpenBSD 6.0-current (GENERIC.MP) #2335: Sun Aug 20:50:41 MDT 2016 (Full dmesg at the end.) I don't know if this is only with my system but since the last few days Mozilla's thunderbird segfaults. $ thunderbird out of memory Assertion failure: [unhandlable oom] OOM in createJitRuntime, at /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt.cpp:1228 Segmentation fault (core dumped) gdb -c thunderbird.core says Programm terminated with signal 11, Segmentation fault. #0 0x185a890c472a in ?? () Running 'doas make update' in /usr/ports/mozilla-thunderbird ends with the following: [...] Executing /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/xpcshell -g /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/bin/ -a /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/bin/ -f /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/precompile_cache.js -e precompile_startupcache("resource://gre/"); out of memory Assertion failure: [unhandlable oom] OOM in createJitRuntime, at /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt.cpp:1228 Traceback (most recent call last): File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.py", line 406, in main() File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.py", line 400, in main args.source, gre_path, base) File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.py", line 161, in precompile_cache errors.fatal('Error while running startup cache precompilation') File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/python/mozbuild/mozpack/errors.py", line 103, in fatal self._handle(self.FATAL, msg) File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/python/mozbuild/mozpack/errors.py", line 98, in _handle raise ErrorMessage(msg) mozpack.errors.ErrorMessage: Error: Error while running startup cache precompilation gmake[1]: *** [/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.mk:41: stage-package] Error 1 gmake[1]: Leaving directory '/usr/ports/pobj/thunderbird-45.2.0/build-amd64/mail/installer' gmake: *** [/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/../mail/build.mk:19: install] Error 2 *** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2763 '/usr/ports/pobj/thunderbird-45.2.0/fake-amd64/.fake-done'
Re: thunderbird segfaults
I forgot to mention that '/usr' is mounted 'wxallowed'. > Gesendet: Montag, 08. August 2016 um 13:44 Uhr > Von: "Stefan Wollny" > An: misc@openbsd.org > Betreff: thunderbird segfaults > > Hi there! > > My system: > OpenBSD 6.0-current (GENERIC.MP) #2335: Sun Aug 20:50:41 MDT 2016 > (Full dmesg at the end.) > > I don't know if this is only with my system but since the last few days > Mozilla's thunderbird segfaults. > > $ thunderbird > out of memory > Assertion failure: [unhandlable oom] OOM in createJitRuntime, at > /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt.cpp:1228 > Segmentation fault (core dumped) > > gdb -c thunderbird.core says > Programm terminated with signal 11, Segmentation fault. > #0 0x185a890c472a in ?? () > > Running 'doas make update' in /usr/ports/mozilla-thunderbird ends with the > following: > [...] > Executing /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/xpcshell -g > /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/bin/ -a > /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/bin/ -f > /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/precompile_cache.js > -e precompile_startupcache("resource://gre/"); > out of memory > Assertion failure: [unhandlable oom] OOM in createJitRuntime, at > /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt.cpp:1228 > Traceback (most recent call last): > File > "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.py", > line 406, in main() > File > "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.py", > line 400, in main args.source, gre_path, base) > File > "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.py", > line 161, in precompile_cache errors.fatal('Error while running startup cache > precompilation') > File > "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/python/mozbuild/mozpack/errors.py", > line 103, in fatal self._handle(self.FATAL, msg) > File > "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/python/mozbuild/mozpack/errors.py", > line 98, in _handle raise ErrorMessage(msg) > mozpack.errors.ErrorMessage: Error: Error while running startup cache > precompilation > gmake[1]: *** > [/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.mk:41: > stage-package] Error 1 > gmake[1]: Leaving directory > '/usr/ports/pobj/thunderbird-45.2.0/build-amd64/mail/installer' > gmake: *** > [/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/../mail/build.mk:19: > install] Error 2 > *** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2763 > '/usr/ports/pobj/thunderbird-45.2.0/fake-amd64/.fake-done') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1891 > '/usr/ports/packages/amd64/all/thunderbird-45.2.0.tgz') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2416: > '_internal-package') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1917 > '/usr/ports/update/amd64/thunderbird-45.2.0') > *** Error 1 in /usr/ports/mail/mozilla-thunderbird > (/usr/ports/infrastructure/mk/bsd.port.mk:2396 'update') > > > Anyone an idea what might go wrong here? I am lost... > > TIA. > > Best, > STEFAN > > > > OpenBSD 6.0-current (GENERIC.MP) #2335: Sun Aug 7 20:50:41 MDT 2016 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 17082359808 (16291MB) > avail mem = 16560173056 (15793MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) > bios0: vendor American Megatrends Inc. version "1.05.01" date 08/05/2015 > bios0: Notebook W65_67SZ > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT > SSDT DMAR > acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) > PXSX(S4) RP04(S4) RLAN(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) > RP07(S4) PXSX(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.26 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACP
Copy-Paste not possible from a xterm
Hi there! My system: OpenBSD 6.0-current (GENERIC.MP) #2335: Sun Aug 20:50:41 MDT 2016 (Full dmesg at the end.) For some time now I cannot copy-paste text from a xterm window by simultaneously pressing left and right mouse buttons. Anyone an idea? TIA. Best, STEFAN OpenBSD 6.0-current (GENERIC.MP) #2335: Sun Aug 7 20:50:41 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17082359808 (16291MB) avail mem = 16560173056 (15793MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.05.01" date 08/05/2015 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) RLAN(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.26 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.83 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.83 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.83 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 120 degC "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not configured "ETD0403" at acpi0 not configured "PNPC000" at acpi0 not configured acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: LID0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "BAT" serial 0001 type LION oem "Notebook" "PNP0C14" at acpi0 not configured "INT340E" at acpi0 not configured acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: LCD0 cpu0: Enhanced SpeedStep 3093 MHz: speeds: 2601, 2600, 2500, 2300, 2200, 2100, 2000, 1800, 1700, 1600, 1400, 1300, 1200, 1100, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi pci1 at ppb0 bus 1 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1920x1080 wsdisplay0 at int
thunderbird segfaults
Hi there! My system: OpenBSD 6.0-current (GENERIC.MP) #2335: Sun Aug 20:50:41 MDT 2016 (Full dmesg at the end.) I don't know if this is only with my system but since the last few days Mozilla's thunderbird segfaults. $ thunderbird out of memory Assertion failure: [unhandlable oom] OOM in createJitRuntime, at /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt.cpp:1228 Segmentation fault (core dumped) gdb -c thunderbird.core says Programm terminated with signal 11, Segmentation fault. #0 0x185a890c472a in ?? () Running 'doas make update' in /usr/ports/mozilla-thunderbird ends with the following: [...] Executing /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/xpcshell -g /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/bin/ -a /usr/ports/pobj/thunderbird-45.2.0/build-amd64/dist/bin/ -f /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/precompile_cache.js -e precompile_startupcache("resource://gre/"); out of memory Assertion failure: [unhandlable oom] OOM in createJitRuntime, at /usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/js/src/jscntxt.cpp:1228 Traceback (most recent call last): File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.py", line 406, in main() File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.py", line 400, in main args.source, gre_path, base) File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.py", line 161, in precompile_cache errors.fatal('Error while running startup cache precompilation') File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/python/mozbuild/mozpack/errors.py", line 103, in fatal self._handle(self.FATAL, msg) File "/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/python/mozbuild/mozpack/errors.py", line 98, in _handle raise ErrorMessage(msg) mozpack.errors.ErrorMessage: Error: Error while running startup cache precompilation gmake[1]: *** [/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/toolkit/mozapps/installer/packager.mk:41: stage-package] Error 1 gmake[1]: Leaving directory '/usr/ports/pobj/thunderbird-45.2.0/build-amd64/mail/installer' gmake: *** [/usr/ports/pobj/thunderbird-45.2.0/thunderbird-45.2.0/mozilla/../mail/build.mk:19: install] Error 2 *** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2763 '/usr/ports/pobj/thunderbird-45.2.0/fake-amd64/.fake-done') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1891 '/usr/ports/packages/amd64/all/thunderbird-45.2.0.tgz') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2416: '_internal-package') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1917 '/usr/ports/update/amd64/thunderbird-45.2.0') *** Error 1 in /usr/ports/mail/mozilla-thunderbird (/usr/ports/infrastructure/mk/bsd.port.mk:2396 'update') Anyone an idea what might go wrong here? I am lost... TIA. Best, STEFAN OpenBSD 6.0-current (GENERIC.MP) #2335: Sun Aug 7 20:50:41 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17082359808 (16291MB) avail mem = 16560173056 (15793MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.05.01" date 08/05/2015 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) RLAN(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.26 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.83 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSG
firefox and thunderbird crashes
Hi there! Trying to use the latest available snapshot of amd64-current I notice that lately firefox and thunderbird crash way too often. Does s.o. else experience this as well? firefox-47.0Mozilla web browser firefox-i18n-de-47.0 de language pack for Firefox thunderbird-45.1.1 Mozilla e-mail, rss and usenet client thunderbird-i18n-de-45.1.1 de language pack for Thunderbird 'wxallowed' is set on /usr. Might be some dependencies or add-ons... Best, STEFAN OpenBSD 6.0-beta (GENERIC.MP) #2241: Fri Jul 1 00:22:57 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17082359808 (16291MB) avail mem = 16560115712 (15792MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.05.01" date 08/05/2015 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) RLAN(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.25 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.84 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.84 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 120 degC "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not configured "ETD0403" at acpi0 not configured "PNPC000" at acpi0 not configured acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: LID0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "BAT" serial 0001 type LION oem "Notebook" "PNP0C14" at acpi0 not configured "INT340E" at acpi0 not configured acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: LCD0 cpu0: Enhanced SpeedStep 3093 MHz: speeds: 2601, 2600, 2500, 2300, 2200, 2100, 2000, 1800, 1700, 1600, 1400, 1300, 1200, 1100, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 ppb0 at pci0 dev 1 function 0 "Intel
Re: ntpd tries to connect via ipv6
Am 05/31/16 um 18:36 schrieb Sonic: > Getting many such log entries: > === > May 31 08:53:34 stargate ntpd[5702]: tls connect failed: > 2607:f8b0:4009:808::2004 (www.google.com): connect: No route to host > May 31 09:08:35 stargate ntpd[15803]: tls connect failed: > 2607:f8b0:4009:808::2004 (www.google.com): connect: No route to host > May 31 09:23:36 stargate ntpd[92515]: tls connect failed: > 2607:f8b0:4009:808::2004 (www.google.com): connect: No route to host > === > > ntpd.conf has the line: constraints from "https://www.google.com"; > > System has no ipv6 addresses. Unbound is resolving DNS server with "do-ip6: > no". > > resolv.conf uses "nameserver 127.0.0.1" (Unbound serving on this address) > > normal lookups (dig) only return the ipv4 address for www.google.com > > Why does ntpd attempt to connect on an ipv6 address? > > Thanks, > > Chris > I asked this just last week. Carlin Bingham's answer solved the issue for me (http://article.gmane.org/gmane.os.openbsd.misc/231185): In /etc/resolv.conf, add: family inet4 (Well: I actually added it in /etc/resolv.conf.tail ...) Best, STEFAN
Re: Print-to-file crashes firefox and xombrero
This still persists. New dmesg for #2127 below. @Stuart: Please note that with this version of ~current-amd64 reports "mmap W^X violation" for thunderbird. Best, STEFAN Am 05/25/16 um 18:24 schrieb Stefan Wollny: > Hi there! > > Running the latest available amd64-snapshot I noticed that when trying > to print from a web-page to a local file (PDF) firefox (and xombrero) > reliably crash. > > This is the source: > http://www.spiegel.de/netzwelt/web/norbert-hofer-donald-trump-und-ueberwachung-sascha-lobo-kolumne-a-1094061-druck.html > > Printing to paper (via cups) is fine. > > Running firefox (46.0.1) from a xterm I see when printing to a file: > Segmentation fault (core dumped) > > '$ gdb file firefox.core' says: > Core was generated by `firefox'. > Program terminated with signal 10, Bus error. > #0 0x1e522521106e in ?? () > > As xombrero (1.6.4p0v1) also crashes when trying to print the page to a > pdf-file: > Started in a xterm xombrero crashes with the remark: > Bus error (core dumped) > > '$ gdb file xombrero.core' says: > Core was generated by `xombrero'. > Program terminated with signal 10, Bus error. > #0 0x04b4c29c106e in ?? () > > Any other information required? Is this just a temporary issue with > ~current? Though printing other pages resulted in a crash as well this > one does it reliably. But: Just an annoyance - after some retries the > pdf was finally produced. > > Best, > STEFAN > > OpenBSD 6.0-beta (GENERIC.MP) #2127: Thu May 26 08:25:13 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17082359808 (16291MB) avail mem = 16560046080 (15792MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.05.01" date 08/05/2015 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) RLAN(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.25 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.84 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.84 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpip
Print-to-file crashes firefox and xombrero
Hi there! Running the latest available amd64-snapshot I noticed that when trying to print from a web-page to a local file (PDF) firefox (and xombrero) reliably crash. This is the source: http://www.spiegel.de/netzwelt/web/norbert-hofer-donald-trump-und-ueberwachung-sascha-lobo-kolumne-a-1094061-druck.html Printing to paper (via cups) is fine. Running firefox (46.0.1) from a xterm I see when printing to a file: Segmentation fault (core dumped) '$ gdb file firefox.core' says: Core was generated by `firefox'. Program terminated with signal 10, Bus error. #0 0x1e522521106e in ?? () As xombrero (1.6.4p0v1) also crashes when trying to print the page to a pdf-file: Started in a xterm xombrero crashes with the remark: Bus error (core dumped) '$ gdb file xombrero.core' says: Core was generated by `xombrero'. Program terminated with signal 10, Bus error. #0 0x04b4c29c106e in ?? () Any other information required? Is this just a temporary issue with ~current? Though printing other pages resulted in a crash as well this one does it reliably. But: Just an annoyance - after some retries the pdf was finally produced. Best, STEFAN OpenBSD 6.0-beta (GENERIC.MP) #2119: Wed May 25 00:22:16 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17082359808 (16291MB) avail mem = 16560050176 (15792MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.05.01" date 08/05/2015 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) RLAN(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.25 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.84 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.84 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 120 degC "INT3F0D" at acpi0 no
Re: ntpd: How to make TLS connection via IPv4?
Am 05/23/16 um 15:50 schrieb Carlin Bingham: >> My question is: Is it possible to persuade ntpd to make that >> > connection via IPv4? 'man ntpd.conf' does not mention this. Any other >> > hint on how to achive this other than remove the "block"-line in pf.conf? >> > > In /etc/resolv.conf, add: > > family inet4 BINGO! That was the missing piece of the puzzle! Added it to 'resolv.conf.tail', though. (Maybe someone with more insight to the issue updates 'man ntpd.conf' with this info?) Thanks for your quick reply, Carlin! Best, STEFAN
ntpd: How to make TLS connection via IPv4?
Hi there! I have 2 i386- and 2 amd64-machines, all running ~current. All report in /var/log/messages lines like the following: May 23 15:01:57 idefix ntpd[19978]: tls connect failed: 2a00:1450:4005:803::2004 (www.google.com): connect: No route to host Obviously this is from constraints from "https://www.google.com"; in /etc/ntpd.conf. On every machine I have the following line in pf.conf: block quick inet6 all I think it is a valid guess that this prevents ntpd to make the connection. My question is: Is it possible to persuade ntpd to make that connection via IPv4? 'man ntpd.conf' does not mention this. Any other hint on how to achive this other than remove the "block"-line in pf.conf? Additional info: One of the i386 acts as proxy (squid + privoxy) for the others (not inline, not transparent), but can be passed by. This machine could as well be a central ntp-server for my little network. TIA. Best, STEFAN ~~ /etc/ntpd.conf ~~ listen on * servers pool.ntp.org sensor * constraints from "https://www.google.com"; ~~ dmesg ~~ OpenBSD 6.0-beta (GENERIC.MP) #2100: Sat May 21 21:00:16 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17082359808 (16291MB) avail mem = 16560041984 (15792MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.05.01" date 08/05/2015 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) RLAN(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(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) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.25 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.83 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.83 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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-4210M CPU @ 2.60GHz, 3092.83 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 120 degC "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not co
Re: ftp/www.openbsd.org will be down for an upgrade today.
Am 05/08/16 um 20:03 schrieb Bob Beck: > There will be an extended downtime of the main ftp and www sites for > an upgrade today starting in approximately one hour's time from now. > > The mirror sites should be unaffected - so use a mirror if you > discover the main site is unavailable today. > Anyone know of an up2date mirror of 'current.html'? (Google just found one with the latest entries from 2005...) :-( TIA. STEFAN
Re: 5.9 discs in the wild. Europe/Germany
Arrived today in Germany :-) Thx to everybody who made this possible. Best, STEFAN Am 04/21/16 um 05:45 schrieb noah pugsley: > Thank you all for the best little correctness focused general purpose > operating system in the known universe. > > With all the nonsense created every day, a little sanity now and then, is > cherished by the wisest men. > > > http://noahpugsley.net/59.jpg > > > Cheers, > > -noah > > P.S. garbage.fm you both better be at bsdcan. I want to complain about > everything !OpenBSD. And I think you do too.
Can't build X
Hi there! Today I fetched the latest sources from http://ftp.hostserver.de and rebuild GENERIC.MP (dmesg at the end) and userland. Then moved on for X. I followed the instructions on "5.4 - Building X" (http://www.openbsd.org/faq/faq5.html#Xbld): $ doas rm -rf /usr/xobj/* $ cd /usr/xenocara/ $ doas make bootstrap $ doas make obj $ doas make build And this is what happend: [ ... ] libtool: link: ar cru .libs/libXpm.a Attrib.o CrBufFrI.o CrBufFrP.o CrDatFrI.o CrDatFrP.o CrIFrBuf.o CrIFrDat.o CrIFrP.o CrPFrBuf.o CrPFrDat.o CrPFrI.o Image.o Info.o RdFToBuf.o RdFToDat.o RdFToI.o RdFToP.o WrFFrBuf.o WrFFrDat.o WrFFrI.o WrFFrP.o create.o data.o hashtab.o misc.o parse.o rgb.o scan.o libtool: link: ranlib .libs/libXpm.a libtool: link: ( cd ".libs" && rm -f "libXpm.la" && ln -s "../libXpm.la" "libXpm.la" ) Making all in sxpm gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I/usr/xenocara/lib/libXpm/sxpm -I.. -I/usr/xenocara/lib/libXpm/include -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wcast-qual -Wmissing-noreturn -Wmissing-format-attribute -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -I/usr/X11R6/include -O2 -pipe -MT sxpm.o -MD -MP -MF .deps/sxpm.Tpo -c -o sxpm.o /usr/xenocara/lib/libXpm/sxpm/sxpm.c /usr/xenocara/lib/libXpm/sxpm/sxpm.c:55:21: error: libintl.h: No such file or directory /usr/xenocara/lib/libXpm/sxpm/sxpm.c:64: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:66: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:67: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:68: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:69: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:71: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:72: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:73: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:74: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:75: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:76: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:77: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:78: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:79: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:80: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:81: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:82: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:83: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:84: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:85: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:86: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:87: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:88: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:89: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:90: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:91: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:92: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:93: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:94: warning: initialization discards qualifiers from pointer target type /usr/xenocara/lib/libXpm/sxpm/sxpm.c:95: warning: initialization discards qualifiers from pointer target type /usr/xe
smtpctl(97175): syscall 141 ""
Hi there! Fetching the lastest amd64-current snapshot or compiling with the latest sources results in the error message smtpctl(97175): syscall 141 "" Any operation that requires root privileges via 'doas' or at startup terminate with Bad system call (core dumped) Is this an issue already known or should I provide more information? I can 'ssh' to the machine. The last working dmesg is attached. Best, STEFAN OpenBSD 5.9-current (GENERIC.MP) #1970: Mon Mar 28 17:02:06 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error f7 real mem = 8279707648 (7896MB) avail mem = 8024420352 (7652MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (43 entries) bios0: vendor Apple Inc. version "IM91.88Z.008D.B08.0904271717" date 04/27/09 bios0: Apple Inc. iMac9,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT acpi0: wakeup devices EC__(S3) OHC1(S3) EHC1(S3) OHC2(S3) EHC2(S3) GIGE(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2500 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU E8135 @ 2.66GHz, 1592.26 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR cpu0: 6MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 265MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E8135 @ 2.66GHz, 1592.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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR cpu1: 6MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-255 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (IXVE) acpicpu0 at acpi0: !C3(100@57 mwait.3@0x31), !C2(500@1 mwait@0x10), C1(1000@1 mwait), PSS acpicpu1 at acpi0: !C3(100@57 mwait.3@0x31), !C2(500@1 mwait@0x10), C1(1000@1 mwait), PSS "APP0002" at acpi0 not configured acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB "PNP0A08" at acpi0 not configured "PNP0C02" at acpi0 not configured "APP0001" at acpi0 not configured "PNP0C09" at acpi0 not configured "PNP0200" at acpi0 not configured "PNP0103" at acpi0 not configured "PNP" at acpi0 not configured "PNP0C04" at acpi0 not configured "PNP0C02" at acpi0 not configured "PNP0B00" at acpi0 not configured "PNP0100" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured "PNP0C0F" at acpi0 not configured cpu0: Enhanced SpeedStep 1592 MHz: speeds: 2660, 2394, 2128, 1862, 1596 MHz memory map conflict 0xffc0/0x40 pci0 at mainbus0 bus 0 0:3:5: mem address conflict 0xd350/0x8 pchb0 at pci0 dev 0 function 0 "NVIDIA MCP79 Host" rev 0xb1 "NVIDIA MCP79 Memory" rev 0xb1 at pci0 dev 0 function 1 not configured pcib0 at pci0 dev 3 function 0 "NVIDIA MCP79 ISA" rev 0xb2 "NVIDIA MCP79 Memory" rev 0xb1 at pci0 dev 3 function 1 not configured nviic0 at pci0 dev 3 function 2 "NVID
FAQ: 14.21.5 - Softraid notes
Hi there! Out of curiosity: What is the rationale behind the last sentence in FAQ: 14.21.5 - Softraid notes: "You may not want to specify the root device by DUID." I dare to ask as the installer sets DUIDs for every partition incl. "/". With this in mind I wonder why the root device should not be specified by the DUID. This sentence lacks at least a hint on why not. (Maybe it is just a misinterpretation of "may not" in this context - to me this reads as "should not" like "better don't do it".) TIA. Best, STEFAN
Re: Strange 'pkg_add -ui' log
Am 02/11/16 um 21:30 schrieb Marc Espie: > On Thu, Feb 11, 2016 at 08:36:48PM +0100, Stefan Wollny wrote: ... > That's the infamous cups update bug, which I haven't been able to fix yet. > > Nope, your system is not okay. Run pkg_check, then rerun pkg_add -u > @Marc @Nigel Thank you for your quick replies. I followed your advice (running pkg_check twice just to be shure) and 'pkg_add -u' was alright showing the expected log entries. Best, STEFAN