isakmp crash
Hello Misc, I have 2 firewalls in a failover setup running site-to-site vpn tunnels. Once in a while ISAKMP stops, not always i can find the stop error but 2 times i have seen now this error : sendmsg (48, 0x7f7dee10, 0): No buffer space available The systems are on OpenBSD 6.0 now but on 5.9 we had the same issue. Anyone know a fix/workaround for this ? Br, Peter
Re: current/i386 does not boot
On Sep 12 21:48:04, n...@holland-consulting.net wrote: > On 09/12/17 14:16, Jan Stary wrote: > > On Sep 12 19:29:16, h...@stare.cz wrote: > >> This is current/i386 from https://ftp.eu.openbsd.org/pub/OpenBSD > >> The upgrade went just fine as always, but the installed /bsd > >> just goes to a black screen at some point during the boot sequence; > >> the machine does not answer to a ping. > > > > Ech, it's an amd64 machine. Sorry for the noise. > > > >> Here is a previous dmesg on the same machine: > >> http://stare.cz/dmesg/intel-i7.20170827 > > > > And here is the amd64 dmesg. > > http://stare.cz/dmesg/intel-i7.20170911 > > > > > > To get a lesson out of this screwup: why exactly is it > > that an i386 bsd.rd boots at this but an i386 bsd does not? > > well... short answer is the kernels are different. > bsd.rd is smaller than the full kernel, AND has "built in" > utilities...so there's a lot missing from bsd.rd. > > "Blank screen" sounds to me like drm issue. At the "boot>" prompt, you > could try a "boot -c" then "disable inteldrm" at the ukc prompt. If it > comes up, sounds like an unhappy regression from something that worked a > couple weeks ago. (I see your working dmesg has inteldrm handling the > display). > > However, before I say bug, I'm confused...you keep talking about i386 > not booting, but it's amd64 that you have shown as having worked. So > I'm a little confused here. What's the actual problem? > > old amd64 worked, new amd64 doesn't? > old amd64 worked, new i386 doesn't? > > Is there any possibilities you got i386 and amd64 binaries mixed, maybe > kernel i386 and amd64 X or other way around, such as by changing > platforms by "upgrade"? (WRONG! re-install). It's an amd64 machine where current/amd64 has always worked. The dmesg are at http://stare.cz/dmesg/intel-i7.* Yesterday, I "upgraded" the machine to current/i386. That's where I observed that bsd.rd boots but bsd does not. It was an i386 bsd.rd that booted and an i386 bsd that did not. After ealizing this, I upgraded again, this time to current/amd64 - which works fine, like it always has. I believe you are right about the inteldrm. Usually, the boot sequence switches to a smaller font once it gets to graphics. After the i386 upgrade, it stayed 80x25 before it went black. That's hardly a bug report of course. Thank you Jan
Re: current/i386 does not boot
On 09/12/17 14:16, Jan Stary wrote: > On Sep 12 19:29:16, h...@stare.cz wrote: >> This is current/i386 from https://ftp.eu.openbsd.org/pub/OpenBSD >> The upgrade went just fine as always, but the installed /bsd >> just goes to a black screen at some point during the boot sequence; >> the machine does not answer to a ping. > > Ech, it's an amd64 machine. Sorry for the noise. > >> Here is a previous dmesg on the same machine: >> http://stare.cz/dmesg/intel-i7.20170827 > > And here is the amd64 dmesg. > http://stare.cz/dmesg/intel-i7.20170911 > > > To get a lesson out of this screwup: why exactly is it > that an i386 bsd.rd boots at this but an i386 bsd does not? well... short answer is the kernels are different. bsd.rd is smaller than the full kernel, AND has "built in" utilities...so there's a lot missing from bsd.rd. "Blank screen" sounds to me like drm issue. At the "boot>" prompt, you could try a "boot -c" then "disable inteldrm" at the ukc prompt. If it comes up, sounds like an unhappy regression from something that worked a couple weeks ago. (I see your working dmesg has inteldrm handling the display). However, before I say bug, I'm confused...you keep talking about i386 not booting, but it's amd64 that you have shown as having worked. So I'm a little confused here. What's the actual problem? old amd64 worked, new amd64 doesn't? old amd64 worked, new i386 doesn't? Is there any possibilities you got i386 and amd64 binaries mixed, maybe kernel i386 and amd64 X or other way around, such as by changing platforms by "upgrade"? (WRONG! re-install). Nick.
drm:pid20265:drm_do_get_edid *WARNING* VGA-1: EDID block 0 invalid
Hi misc, # uname -a OpenBSD iris.int.autonsys.com 6.1 GENERIC.MP#21 amd64 # syspatch -l 001_dhcpd 002_vmmfpu 003_libressl 004_softraid_concat 005_pf_src_tracking 006_libssl 007_freetype 008_exec_subr 009_icmp_opts 010_perl 012_wsmux 013_icmp6_linklocal 014_libcrypto 015_sigio 016_sendsyslog 017_fuse 018_recv 019_tcp_usrreq 020_sockaddr 021_ptrace 022_fcntl 023_wsdisplay 024_sosplice 025_ieee80211 026_smap 027_net80211_replay on Firewall Micro Appliance With 4x Gigabit Intel LAN Ports https://www.amazon.com/Firewall-Micro-Appliance-Gigabit-Barebone/dp/B01GIVQI3M I noticed tail -20 dmesg.txt error: [drm:pid20265:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 8 Raw EDID: 00 ff ff ff ff ff ff 00 5a 63 1f 70 ff 01 01 01 1b 11 01 03 fb ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff drm:pid20265:drm_do_get_edid *WARNING* VGA-1: EDID block 0 invalid. uhidev0 at uhub1 port 1 configuration 1 interface 0 "DELL Dell USB Entry Keyboard" rev 1.10/1.78 addr 4 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 variable keys, 6 key codes wskbd0 at ukbd0: console keyboard, using wsdisplay0 ukbd0: was console keyboard wskbd0 detached ukbd0 detached uhidev0 detached complete dmesg is below. This seems to be a benign VGA related error. https://bugzilla.redhat.com/show_bug.cgi?id=1381762 What should I disable in the kernel to get a rid of the error? Thank you for your attention. Predrag OpenBSD 6.1 (GENERIC.MP) #19: Thu Aug 3 14:59:44 CEST 2017 rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4165738496 (3972MB) avail mem = 4034809856 (3847MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebea0 (51 entries) bios0: vendor American Megatrends Inc. version "5.6.5" date 08/15/2016 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT TCPA MCFG HPET SSDT SSDT SSDT UEFI SSDT TPM2 acpi0: wakeup devices EHC1(S4) PXSX(S4) PXSX(S4) PXSX(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) Celeron(R) CPU J1900 @ 1.99GHz, 2000.47 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu0: 1MB 64b/line 16-way L2 cache cpu0: TSC frequency 2000465520 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 83MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu1: 1MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu2: 1MB 64b/line 16-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu3: 1MB 64b/line 16-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 87 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus 2 (RP02) acpiprt3 at acpi0: bus 3 (RP03) acpiprt4 at acpi0: bus 4 (RP04) acpiec0 at acpi0: not present acpicpu0 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500
Re: Can't get cvs checkout for src and ports as a normal user to work
On Tue, Sep 12, 2017 at 07:04:54PM +, Lea Chescotta wrote: > Hi, i'd trying to make a checkout of the sources and ports to my fresh > openbsd 6.1 install, following this guide > https://www.openbsd.org/anoncvs.html but when i try to make the checkout i > get some errors. > > I did this steps as root: > # user mod -G wsrc usuario In https://www.openbsd.org/faq/faq5.html#wsrc it says after a similar command (with exampleuser in place of usuario): "This change takes effect with exampleuser's next login." Given that the permissions you display below are ok, I suggest you try again with a freshly logged in shell for usuario. > # cd /usr > # mkdir -p xenocara ports src > # chgrp wsrc xenocara ports src > # chmod 775 xenocara ports src > > And as a normal user: > $ cd /usr > $ ls -la > total 92 > drwxrwxr-x 18 root wsrc512 Sep 12 11:32 . > drwxr-xr-x 13 root wheel 512 Sep 8 13:50 .. > drwxr-xr-x 7 root wheel 512 Apr 1 17:06 X11R6 > drwxr-xr-x 2 root wheel 5632 Sep 8 13:45 bin > drwxr-xr-x 2 root wheel 1024 Sep 7 11:20 games > drwxr-xr-x 28 root bin3072 Sep 7 11:20 include > drwxr-xr-x 6 root wheel 3072 Sep 12 05:18 lib > drwxr-xr-x 5 root wheel 512 Sep 7 11:20 libdata > drwxr-xr-x 6 root wheel 1024 Sep 7 11:20 libexec > drwxr-xr-x 11 root wheel 512 Sep 12 12:21 local > drwxr-xr-x 2 root wheel 512 Apr 1 16:39 mdec > drwxrwx--- 2 build wobj512 Sep 7 11:19 obj > drwxrwxr-x 34 root wsrc 1024 Sep 12 11:29 ports > drwxr-xr-x 2 root wheel 4096 Sep 8 13:45 sbin > drwxr-xr-x 16 root wheel 512 Apr 1 16:39 share > drwxrwxr-x 2 root wsrc512 Sep 12 11:28 src > drwxrwxr-x 2 root wsrc512 Sep 12 11:32 xenocara > drwxrwx--- 2 build wobj512 Sep 7 14:34 xobj > > But, when i try to cvs checkout: > $ cvs -qd anon...@obsdacvs.cs.toronto.edu:/cvs checkout -rOPENBSD_6_1 -P src > cvs checkout: warning: cannot make directory CVS in .: Permission denied > cvs checkout: in directory src: > cvs checkout: cannot open CVS/Entries for reading: No such file or directory > cvs checkout: cannot open CVS/Tag: No such file or directory > cvs checkout: cannot open CVS/Tag: No such file or directory > cvs checkout: cannot write src/Makefile: Permission denied > cvs checkout: cannot write src/Makefile.cross: Permission denied > cvs checkout: cannot open CVS/Tag: No such file or directory > cvs [checkout aborted]: cannot make directory src/bin: No such file or > directory
Can't get cvs checkout for src and ports as a normal user to work
Hi, i'd trying to make a checkout of the sources and ports to my fresh openbsd 6.1 install, following this guide https://www.openbsd.org/anoncvs.html but when i try to make the checkout i get some errors. I did this steps as root: # user mod -G wsrc usuario # cd /usr # mkdir -p xenocara ports src # chgrp wsrc xenocara ports src # chmod 775 xenocara ports src And as a normal user: $ cd /usr $ ls -la total 92 drwxrwxr-x 18 root wsrc512 Sep 12 11:32 . drwxr-xr-x 13 root wheel 512 Sep 8 13:50 .. drwxr-xr-x 7 root wheel 512 Apr 1 17:06 X11R6 drwxr-xr-x 2 root wheel 5632 Sep 8 13:45 bin drwxr-xr-x 2 root wheel 1024 Sep 7 11:20 games drwxr-xr-x 28 root bin3072 Sep 7 11:20 include drwxr-xr-x 6 root wheel 3072 Sep 12 05:18 lib drwxr-xr-x 5 root wheel 512 Sep 7 11:20 libdata drwxr-xr-x 6 root wheel 1024 Sep 7 11:20 libexec drwxr-xr-x 11 root wheel 512 Sep 12 12:21 local drwxr-xr-x 2 root wheel 512 Apr 1 16:39 mdec drwxrwx--- 2 build wobj512 Sep 7 11:19 obj drwxrwxr-x 34 root wsrc 1024 Sep 12 11:29 ports drwxr-xr-x 2 root wheel 4096 Sep 8 13:45 sbin drwxr-xr-x 16 root wheel 512 Apr 1 16:39 share drwxrwxr-x 2 root wsrc512 Sep 12 11:28 src drwxrwxr-x 2 root wsrc512 Sep 12 11:32 xenocara drwxrwx--- 2 build wobj512 Sep 7 14:34 xobj But, when i try to cvs checkout: $ cvs -qd anon...@obsdacvs.cs.toronto.edu:/cvs checkout -rOPENBSD_6_1 -P src cvs checkout: warning: cannot make directory CVS in .: Permission denied cvs checkout: in directory src: cvs checkout: cannot open CVS/Entries for reading: No such file or directory cvs checkout: cannot open CVS/Tag: No such file or directory cvs checkout: cannot open CVS/Tag: No such file or directory cvs checkout: cannot write src/Makefile: Permission denied cvs checkout: cannot write src/Makefile.cross: Permission denied cvs checkout: cannot open CVS/Tag: No such file or directory cvs [checkout aborted]: cannot make directory src/bin: No such file or directory
Re: current/i386 does not boot
On Sep 12 19:29:16, h...@stare.cz wrote: > This is current/i386 from https://ftp.eu.openbsd.org/pub/OpenBSD > The upgrade went just fine as always, but the installed /bsd > just goes to a black screen at some point during the boot sequence; > the machine does not answer to a ping. Ech, it's an amd64 machine. Sorry for the noise. > Here is a previous dmesg on the same machine: > http://stare.cz/dmesg/intel-i7.20170827 And here is the amd64 dmesg. http://stare.cz/dmesg/intel-i7.20170911 To get a lesson out of this screwup: why exactly is it that an i386 bsd.rd boots at this but an i386 bsd does not? Jan
Re: current/i386 does not boot
On Sep 12 19:29:16, h...@stare.cz wrote:
> This is current/i386 from https://ftp.eu.openbsd.org/pub/OpenBSD
> The upgrade went just fine as always, but the installed /bsd
> just goes to a black screen at some point during the boot sequence;
> the machine does not answer to a ping.
>
> Here is a previous dmesg on the same machine:
> http://stare.cz/dmesg/intel-i7.20170827
And here is a dmesg of the currnt /bsd.rd which boot fine:
OpenBSD 6.2-beta (RAMDISK_CD) #125: Mon Sep 11 11:23:18 MDT 2017
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz ("GenuineIntel" 686-class) 3.50
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,LAHF,PERF,ITSC,SENSOR,ARAT
real mem = 3673346048 (3503MB)
avail mem = 3593797632 (3427MB)
mainbus0 at root
bios0 at mainbus0: date 03/31/11, BIOS32 rev. 0 @ 0xfa960, SMBIOS rev. 2.4 @
0xf0100 (36 entries)
bios0: vendor Award Software International, Inc. version "F3" date 03/31/2011
bios0: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP HPET MCFG ASPT SSPT EUDS MATS TAMG APIC SSDT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
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
, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus 1 (PEX0)
acpiprt4 at acpi0: bus -1 (PEX1)
acpiprt5 at acpi0: bus -1 (PEX2)
acpiprt6 at acpi0: bus -1 (PEX3)
acpiprt7 at acpi0: bus -1 (PEX4)
acpiprt8 at acpi0: bus -1 (PEX5)
acpiprt9 at acpi0: bus 2 (PEX6)
acpiprt10 at acpi0: bus 3 (PEX7)
acpicpu at acpi0 not configured
"PNP0C0C" at acpi0 not configured
"ICD0001" at acpi0 not configured
"INT3F0D" at acpi0 not configured
bios0: ROM list: 0xc/0xd800 0xce000/0x2a00! 0xd1000/0x1000
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09
vga1 at pci0 dev 2 function 0 "Intel HD Graphics 2000" rev 0x09
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
"Intel 6 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
ehci0 at pci0 dev 26 function 0 "Intel 6 Series USB" rev 0x05: apic 2 int 18
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00
addr 1
"Intel 6 Series HD Audio" rev 0x05 at pci0 dev 27 function 0 not configured
ppb0 at pci0 dev 28 function 0 "Intel 6 Series PCIE" rev 0xb5: apic 2 int 16
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 6 "Intel 6 Series PCIE" rev 0xb5: apic 2 int 18
pci2 at ppb1 bus 2
re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E-VL
(0x2c80), msi, address 50:e5:49:36:ec:0d
rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 5
ppb2 at pci0 dev 28 function 7 "Intel 6 Series PCIE" rev 0xb5: apic 2 int 19
pci3 at ppb2 bus 3
xhci0 at pci3 dev 0 function 0 "Etron EJ168 xHCI" rev 0x01: msi
usb1 at xhci0: USB revision 3.0
uhub1 at usb1 configuration 1 interface 0 "Etron xHCI root hub" rev 3.00/1.00
addr 1
ehci1 at pci0 dev 29 function 0 "Intel 6 Series USB" rev 0x05: apic 2 int 23
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00
addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xa5
pci4 at ppb3 bus 4
pcib0 at pci0 dev 31 function 0 "Intel H67 LPC" rev 0x05
ahci0 at pci0 dev 31 function 2 "Intel 6 Series AHCI" rev 0x05: msi, AHCI 1.3
ahci0: device on port 0 didn't come ready, TFD: 0x80
ahci0: CLO did not complete
ahci0: port 0: 3.0Gb/s
ahci0: port 1: 6.0Gb/s
ahci0: port 2: 3.0Gb/s
ahci0: port 3: 3.0Gb/s
ahci0: port 4: 3.0Gb/s
ahci0: port 5: 3.0Gb/s
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct
fixed naa.50015179593bd675
sd0: 38166MB, 512 bytes/sector, 78165360 sectors, thin
sd1 at scsibus0 targ 1 lun 0: SCSI3 0/direct
fixed naa.5000c5002eda7d71
sd1: 1430799MB, 512 bytes/sector, 2930277168 sectors
sd2 at scsibus0 targ 2 lun 0: SCSI3 0/direct
fixed naa.5000c5002f119d73
sd2: 1430799MB, 512 bytes/sector, 2930277168 sectors
sd3 at scsibus0 targ 3 lun 0: SCSI3 0/direct fixed
naa.50024e920592fbeb
sd3: 953869MB, 512 bytes/sector, 1953525168 sectors
sd4 at scsibus0 targ 4 lun 0: SCSI3 0/direct
fixed naa.50004cf207132b48
sd4: 953868MB, 512 bytes/sector, 1953523055 sectors
sd5 at scsibus0 targ 5 lun 0: SCSI3 0/direct fixed
naa.5000c50013baac5f
sd5: 305245MB, 512 bytes
current/i386 does not boot
This is current/i386 from https://ftp.eu.openbsd.org/pub/OpenBSD The upgrade went just fine as always, but the installed /bsd just goes to a black screen at some point during the boot sequence; the machine does not answer to a ping. Here is a previous dmesg on the same machine: http://stare.cz/dmesg/intel-i7.20170827 Is anyone seeing the same? Jan
Any plans for multiqueueing (and dynamic-size sectors) for the disk/fs subsystem?
Hi! Any plans for multiqueueing in the disk/fs subsystem? At least in the current absence of multiqueueing, my benchmarks (made on /dev/rsd0c) show that 16KB-aligned 16KB accesses are the fastest on the SSD:s I tested (recent Samsung SATA & NVME). http://undeadly.org/cgi?action=article&sid=20100417195756 tells there is indeed 4KB sector support internally. Based on my benchmarks, if I could up it to 16KB, I would do it. I will benchmark the filesystem in 4KB mode first though. Thanks, Tinker
Re: (Possibly OT) Trouble installing kanboard
Ah. Awesome, thank you!
BR, Andreas
tis 12 sep. 2017 kl. 16:14 skrev Martijn van Duren <
openbsd+m...@list.imperialat.at>:
> On 09/12/17 15:38, Andreas Thulin wrote:
> > Hi all!
> >
> > This may be OT, and if so I apologise (and appreciate being pushed in the
> > right direction). I'm trying to install and run kanboard (
> > https://kanboard.net) on my 6.1-stable amd64 VPS using httpd + php
> 7.0.16 +
> > php-fpm-7.0.
> >
> > At first, the web GUI installer complained (Internal Error: PHP extension
> > required: "gd"), so I installed php-gd, and
> >
> > # rcctl restart php70_fpm
> > as well as
> > # rcctl restart httpd
> >
> > but I still get the same error message. My php_info() page claims I have
> gd
> > ("shared", whatever that means) support.
> Extensions aren't loaded in by default.
>
> # cp /etc/php-7.0.sample/gd.ini /etc/php-7.0
> # rcctl restart php70_fpm
> >
> > There are a few different components involved here, so I'm not sure where
> > to start trouble-shooting. Any pointers would help.
> >
> > BR
> > Andreas
> >
>
> martijn@
>
Re: Filtering other network layer protocols with PF
On Mon, 11 Sep 2017 10:26:22 -0500 Christopher Snell wrote: > Hi, > > I have an AT&T fiber connection at home that relies on a crappy, > proprietary, and insecure [1] router that does proprietary > authentication with upstream equipment via EAP over 802.1x. Some > folks have figured out how to bypass it by putting the AT&T router > behind their actual firewalls and proxying the 802.1x packets to/from > the AT&T device, thus faking out the upstream gateway. > > Unfortunately, the common solution [2] for this is Linux-specific and > relies on their PF_RING stuff. I was hoping to proxy this protocol in > OpenBSD without having to use something slow like pcap. As far as I > can tell from reading man pages, PF does not support this network > layer protocol (0x888E). Does anybody have any ideas on how I might > efficiently capture these packets and copy them to another interface? > > Chris > > [1] https://www.nomotion.net/blog/sharknatto/ > [2] https://github.com/jaysoffian/eap_proxy Hi, not exactly answer to your question, but: I have similar situation, where my ISP gives me crappy device whose uplink is ADSL, and downlink is ethernet. By default, it does PAP-authenticated ppooe, NAT and ingress filtering on uplink. I managed to configure this device in 'bridge mode', and put two-nic (PC Engines' APU2) OpenBSD firewall behind it, which calls pppoe, NATs, filters, etc. The rest of my home LAN plugs into internal interface of mentioned firewall. ISP--adsl I still can't secure ISP's device, but I can filter traffic which enters and leaves my LAN. Regards, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: Useless firmware in /etc/firmware/ for unsupported device
On Tue, Sep 12, 2017 at 09:44:15AM -0400, Puffymon wrote: > Hi. > When I ran OpenBSD first time at my AMD PC, > it didn't try to fetch radeondrm(4) firmware. > So I had to run "fw_update radeondrm" > > Then after reboot it didn't try to load radeondrm(4) for my Kaveri APU > That is a big pain, I don't have 2D and 3D accelerations. > Xorg's log file tells me that modesetting is not supported. > My question is: > If kernel doesn't support radeon kaveri, > why would I need useless /etc/firmware/radeon_kaveri_* files? You should know, you are the one who decided to fetch them... > The second question is: > Are there any plans to support kaveri and other radeon graphics cards? --
Re: (Possibly OT) Trouble installing kanboard
On 09/12/17 15:38, Andreas Thulin wrote:
> Hi all!
>
> This may be OT, and if so I apologise (and appreciate being pushed in the
> right direction). I'm trying to install and run kanboard (
> https://kanboard.net) on my 6.1-stable amd64 VPS using httpd + php 7.0.16 +
> php-fpm-7.0.
>
> At first, the web GUI installer complained (Internal Error: PHP extension
> required: "gd"), so I installed php-gd, and
>
> # rcctl restart php70_fpm
> as well as
> # rcctl restart httpd
>
> but I still get the same error message. My php_info() page claims I have gd
> ("shared", whatever that means) support.
Extensions aren't loaded in by default.
# cp /etc/php-7.0.sample/gd.ini /etc/php-7.0
# rcctl restart php70_fpm
>
> There are a few different components involved here, so I'm not sure where
> to start trouble-shooting. Any pointers would help.
>
> BR
> Andreas
>
martijn@
Useless firmware in /etc/firmware/ for unsupported device
Hi. When I ran OpenBSD first time at my AMD PC, it didn't try to fetch radeondrm(4) firmware. So I had to run "fw_update radeondrm" Then after reboot it didn't try to load radeondrm(4) for my Kaveri APU That is a big pain, I don't have 2D and 3D accelerations. Xorg's log file tells me that modesetting is not supported. My question is: If kernel doesn't support radeon kaveri, why would I need useless /etc/firmware/radeon_kaveri_* files? The second question is: Are there any plans to support kaveri and other radeon graphics cards? dmesg: OpenBSD 6.2-beta (GENERIC.MP) #85: Sat Sep 9 17:44:54 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 7457595392 (7112MB) avail mem = 7224561664 (6889MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xecd20 (55 entries) bios0: vendor American Megatrends Inc. version "V8.1" date 04/15/2015 bios0: MSI MS-7721 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET UEFI IVRS SSDT SSDT CRAT SSDT SSDT acpi0: wakeup devices SBAZ(S4) ECIR(S4) P0PC(S4) OHC1(S4) EHC1(S4) OHC2(S4) EHC2(S4) OHC3(S4) EHC3(S4) OHC4(S4) PE20(S4) PE21(S4) PE23(S4) PB21(S4) PB22(S4) PB31(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G, 3296.28 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,FSGSBASE,BMI1 cpu0: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: TSC frequency 3296275620 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G, 3293.86 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,FSGSBASE,BMI1 cpu1: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G, 3293.85 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,FSGSBASE,BMI1 cpu2: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G, 3293.85 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,FSGSBASE,BMI1 cpu3: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu3: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu3: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 1 pa 0xfec01000, version 21, 32 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (P0PC) acpiprt2 at acpi0: bus -1 (PE20) acpiprt3 at acpi0: bus -1 (PE21) acpiprt4 at acpi0: bus -1 (PE23) acpiprt5 at acpi0: bus -1 (PB21) acpiprt6 at acpi0: bus -1 (PB22) acpiprt7 at acpi0: bus 1 (PB31) acpiprt8 at acpi0: bus -1 (PB32)
(Possibly OT) Trouble installing kanboard
Hi all!
This may be OT, and if so I apologise (and appreciate being pushed in the
right direction). I'm trying to install and run kanboard (
https://kanboard.net) on my 6.1-stable amd64 VPS using httpd + php 7.0.16 +
php-fpm-7.0.
At first, the web GUI installer complained (Internal Error: PHP extension
required: "gd"), so I installed php-gd, and
# rcctl restart php70_fpm
as well as
# rcctl restart httpd
but I still get the same error message. My php_info() page claims I have gd
("shared", whatever that means) support.
There are a few different components involved here, so I'm not sure where
to start trouble-shooting. Any pointers would help.
BR
Andreas
ipv4/ipv6 dual-stack configuration on OpenBSD6.0
Hello misc@, I'm trying to find an *authoritative* walkthrough configuring an OpenBSD-6.0 amd64 machine that currently runs fine as an ipv4 router for my pppoe vdsl connection. The ipv4 network is a public /29. No NAT of any description runs on this machine. There's two NICs, re0 which connects to a vdsl modem and re1 which is the WAN and is directlt connected to a switch, and pppoe0 controlling the connection. I have a /64 for the WAN and a /48 for the LAN requesting ipv6 delegation. This is native IPv6. I think I'll need dhcpv6 to hand out ipv6 addresses? I'm looking for something like this: https://www.openbsd.org/faq/faq6.html#Setup but for ipv6 configs (ideally ipv4/6 dual stack). So far, searching has turned up bits and pieces but some of it is old, there's differences between versions, need something ideally specific to OpenBSD 6.0 so that I'm confident it's setup right for this version. any ideas? thanks, -- J.
Re: Open /dev/mem file failed when running as a root priviledge
On 2017-09-12, Nan Xiao wrote: > Hi trondd, > > Thanks for your answer! > > I try to use "sysctl" command to modify "kern.allowkmem"'s value: > > # sysctl kern.allowkmem=1 > sysctl: kern.allowkmem: Operation not permitted > > Since it doesn't work. So I create a "/etc/sysctl.conf" and add > follwing value: > > kern.allowkmem=1 > > After referring the manuals of sysctl(https://man.openbsd.org/sysctl.8) > and sysctl.conf(https://man.openbsd.org/sysctl.conf.5), I can't find > how to reload the sysctl.conf, so I have no choine but to reboot it and > it takes effect. > > So the only method of reloading sysctl.conf is just reboot? Sorry for > my further question. Irrespective of how you reload sysctl.conf for "normal" sysctls (which is a different issue and came up on misc@ recently), the kern.allowkmem sysctl can *only* be raised before securelevel is set during boot. (Alternatively the allowkmem variable can be poked directly via ddb).
Re: Open /dev/mem file failed when running as a root priviledge
On 12/09/17 03:58, Nan Xiao wrote: > Hi all, > > Greetings from me! > > I want to run dmidecode (https://github.com/mirror/dmidecode) on OpenBSD > 6.1, but executing it will report following errors: I also need the output of dmidecode and I do the following in by boxes: /etc/rc.securelevel: if [[ -x /usr/local/sbin/dmidecode ]]; then /usr/local/sbin/dmidecode > /var/run/dmidecode.boot fi It runs the script at an early stage, before the change of kern.securelevel so access to /dev/mem is allowed. G
