Re: Troobleshooting help for UVM

2018-05-02 Thread sven falempin
On Wed, May 2, 2018, 14:57 Jeremie Courreges-Anglas  wrote:

> On Wed, May 02 2018, sven falempin  wrote:
> > 6.3 + syspatch
> >
> > UVM: pid  (perl), uid 0 killed: out of swap
> >
> > no ddb, i m not using swap in perl afaik, and it seems strange
> > a userland script can 'kill' UVM
>
> I read the error message as "uvm could not find free mem and killed
> a perl process running as root".
>
> >
> > OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > real mem = 2080227328 (1983MB)
> > avail mem = 2010144768 (1917MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf68b0 (9 entries)
> > bios0: vendor SeaBIOS version "2:1.10.2-58953eb7" date 04/01/2014
> > bios0: OpenStack Foundation OpenStack Nova
> > acpi0 at bios0: rev 0
> > acpi0: sleep states S3 S4 S5
> > acpi0: tables DSDT FACP SSDT APIC
> > acpi0: wakeup devices
> > acpitimer0 at acpi0: 3579545 Hz, 24 bits
> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: Intel Core Processor (Haswell, no TSX), 2394.83 MHz
> > cpu0:
> >
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,VMX,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,ARAT,MELTDOWN
> > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
> > 64b/line 16-way L2 cache
> > cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> > cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> > cpu0: smt 0, core 0, package 0
> > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> > cpu0: apic clock running at 999MHz
> > ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
> > acpiprt0 at acpi0: bus 0 (PCI0)
> > acpicpu0 at acpi0: C1(@1 halt!)
> > "ACPI0006" at acpi0 not configured
> > acpicmos0 at acpi0
> > "PNP0A06" at acpi0 not configured
> > "PNP0A06" at acpi0 not configured
> > "PNP0A06" at acpi0 not configured
> > pvbus0 at mainbus0: KVM
> > pci0 at mainbus0 bus 0
> > pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
> > pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
> > pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
> > channel 0 wired to compatibility, channel 1 wired to compatibility
> > pciide0: channel 0 disabled (no drives)
> > pciide0: channel 1 disabled (no drives)
> > uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int
> 11
> > piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0
> int 9
> > iic0 at piixpm0
> > vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
> > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> > wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> > virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
> > vio0 at virtio0: address fa:16:3e:ec:59:66
> > virtio0: msix shared
> > virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00
> > vioblk0 at virtio1
> > scsibus1 at vioblk0: 2 targets
> > sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct
> fixed
> > sd0: 10240MB, 512 bytes/sector, 20971520 sectors
> > virtio1: msix shared
> > virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory" rev 0x00
> > viomb0 at virtio2
> > virtio2: apic 0 int 10
> > isa0 at pcib0
> > isadma0 at isa0
> > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> > com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> > pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> > pckbd0 at pckbc0 (kbd slot)
> > wskbd0 at pckbd0: console keyboard, using wsdisplay0
> > pms0 at pckbc0 (aux slot)
> > wsmouse0 at pms0 mux 0
> > pcppi0 at isa0 port 0x61
> > spkr0 at pcppi0
> > usb0 at uhci0: USB revision 1.0
> > uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev
> > 1.00/1.00 addr 1
> > vmm0 at mainbus0: VMX/EPT
> > uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB
> > Tablet" rev 2.00/0.00 addr 2
> > uhidev0: iclass 3/0
> > ums0 at uhidev0: 3 buttons, Z dir
> > wsmouse1 at ums0 mux 0
> > vscsi0 at root
> > scsibus2 at vscsi0: 256 targets
> > softraid0 at root
> > scsibus3 at softraid0: 256 targets
> > root on sd0a (fe232e2f6ab8c86a.a) swap on sd0b dump on sd0b
> > WARNING: / was not properly unmounted
> > fd0 at fdc0 drive 1: density unknown
> >
> > No swap actually :
> >
> > fe232e2f6ab8c86a.a / ffs rw,wxallowed 1 1
> > swap /var/run mfs rw,nodev,nosuid,-s=32M 0 0
>
> The "out of swap" message seems generic.  Maybe your script (or another
> process) simply consumed too much memory?
>
> --
> jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE
>


found 

Re: smtpd relay problem

2018-05-02 Thread mazocomp
Hi!

Try to modify my configs under your username and address:

/etc/mail/smtpd.conf:
-
table aliases file:/etc/mail/aliases
table secrets file:/etc/mail/secrets

listen on lo0

accept for local alias  deliver to mbox
accept for any relay via tls+auth://mazoc...@disroot.org:587 auth 
-

/etc/mail/secrets:
-
mazocomp mazoc...@disroot.org:my_password
-

/home/mazocomp/.mailrc:
-
set ask
set crt
set from=mazoc...@disroot.org
ignore message-id received date fcc status resent-date resent-message-id 
resent-from in-reply-to
-

You might also want to fetch mail via IMAP or POP3,
here is my /home/mazocomp/.fdm.conf (# pkg_add fdm):
-
action "inbox" mbox "/var/mail/%u"
account "Leonid Bobrov" imaps server "disroot.org"
user "mazocomp" pass "my_password"
match all action "inbox"
-

Also note that you might want to not delete
your mail at gmail server, so after pass "my_password"   
append: keep

Also I do not know if gmail uses default IMAPS port, 
so you have to manually after server "disroot.org"
write: port 123



Re: Troobleshooting help for UVM

2018-05-02 Thread Jeremie Courreges-Anglas
On Wed, May 02 2018, sven falempin  wrote:
> 6.3 + syspatch
>
> UVM: pid  (perl), uid 0 killed: out of swap
>
> no ddb, i m not using swap in perl afaik, and it seems strange
> a userland script can 'kill' UVM

I read the error message as "uvm could not find free mem and killed
a perl process running as root".

>
> OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 2080227328 (1983MB)
> avail mem = 2010144768 (1917MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf68b0 (9 entries)
> bios0: vendor SeaBIOS version "2:1.10.2-58953eb7" date 04/01/2014
> bios0: OpenStack Foundation OpenStack Nova
> acpi0 at bios0: rev 0
> acpi0: sleep states S3 S4 S5
> acpi0: tables DSDT FACP SSDT APIC
> acpi0: wakeup devices
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel Core Processor (Haswell, no TSX), 2394.83 MHz
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,VMX,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,ARAT,MELTDOWN
> cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
> 64b/line 16-way L2 cache
> cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 999MHz
> ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpicpu0 at acpi0: C1(@1 halt!)
> "ACPI0006" at acpi0 not configured
> acpicmos0 at acpi0
> "PNP0A06" at acpi0 not configured
> "PNP0A06" at acpi0 not configured
> "PNP0A06" at acpi0 not configured
> pvbus0 at mainbus0: KVM
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
> pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
> pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
> channel 0 wired to compatibility, channel 1 wired to compatibility
> pciide0: channel 0 disabled (no drives)
> pciide0: channel 1 disabled (no drives)
> uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
> piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int 9
> iic0 at piixpm0
> vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
> vio0 at virtio0: address fa:16:3e:ec:59:66
> virtio0: msix shared
> virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00
> vioblk0 at virtio1
> scsibus1 at vioblk0: 2 targets
> sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct fixed
> sd0: 10240MB, 512 bytes/sector, 20971520 sectors
> virtio1: msix shared
> virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory" rev 0x00
> viomb0 at virtio2
> virtio2: apic 0 int 10
> isa0 at pcib0
> isadma0 at isa0
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> wsmouse0 at pms0 mux 0
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev
> 1.00/1.00 addr 1
> vmm0 at mainbus0: VMX/EPT
> uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB
> Tablet" rev 2.00/0.00 addr 2
> uhidev0: iclass 3/0
> ums0 at uhidev0: 3 buttons, Z dir
> wsmouse1 at ums0 mux 0
> vscsi0 at root
> scsibus2 at vscsi0: 256 targets
> softraid0 at root
> scsibus3 at softraid0: 256 targets
> root on sd0a (fe232e2f6ab8c86a.a) swap on sd0b dump on sd0b
> WARNING: / was not properly unmounted
> fd0 at fdc0 drive 1: density unknown
>
> No swap actually :
>
> fe232e2f6ab8c86a.a / ffs rw,wxallowed 1 1
> swap /var/run mfs rw,nodev,nosuid,-s=32M 0 0

The "out of swap" message seems generic.  Maybe your script (or another
process) simply consumed too much memory?

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE



Re: Disabling message CRCs in SSHD

2018-05-02 Thread Hess THR
Thanks. Appreciate it!! :)

> Sent: Saturday, April 28, 2018 at 11:11 AM
> From: "Darren Tucker" 
> To: "Hess THR" 
> Cc: "OpenBSD Misc List" 
> Subject: Re: Disabling message CRCs in SSHD
>
> On 28 April 2018 at 03:20, Hess THR  wrote:
> > Based on the:
> >
> > http://www.vegardno.net/2017/03/fuzzing-openssh-daemon-using-afl.html
> >
> > I tried to search for these code pieces (I know he was using openbsd-compat 
> > and not the original OpenSSH code) but didn't found it, didn't even find 
> > similar for disabling message CRCs:
> 
> Short answer: It's gone, you can ignore that part.
> 
> Long answer: CRC32 was the message integrity method for SSH Protocol
> v1 and the last of the SSH1 code was removed[0] in the 7.6 release[1]
> (in part because CRC32 a weak integrity guarantee compared to a proper
> MAC).
> 
> [0] https://github.com/openssh/openssh-portable/commit/3d6d09f2
> [1] https://www.openssh.com/releasenotes.html#7.6
> 
> -- 
> Darren Tucker (dtucker at dtucker.net)
> GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860  37F4 9357 ECEF 11EA A6FA (new)
> Good judgement comes with experience. Unfortunately, the experience
> usually comes from bad judgement.
> 



Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

2018-05-02 Thread Jan Vlach
> Last time I checked, we don't support LoadTable.
> 
> -ml
> 

Thank you Mike for your reply. I have no clue about ACPI. Is this a new
way how vendors extend ACPI? Is there generally a way to switch it to
some "legacy" mode or is this endgame? 
Is there some info I could get from the system before I send it back
that could later down the road when someone is interested? Would getting
an acpidump from Linux and/or FreeBSD help at this point? 

Thank you again,
Jan



Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

2018-05-02 Thread Hrvoje Popovski
On 2.5.2018. 19:06, Mike Larkin wrote:
> On Wed, May 02, 2018 at 06:51:51PM +0200, Jan Vlach wrote:
>>> Last time I checked, we don't support LoadTable.
>>>
>>> -ml
>>>
>>
>> Thank you Mike for your reply. I have no clue about ACPI. Is this a new
>> way how vendors extend ACPI? Is there generally a way to switch it to
>> some "legacy" mode or is this endgame? 
>> Is there some info I could get from the system before I send it back
>> that could later down the road when someone is interested? Would getting
>> an acpidump from Linux and/or FreeBSD help at this point? 
>>
>> Thank you again,
>> Jan
> 
> kettenis@ may know more, I think he knows about this issue already. It's just
> a missing piece of the standard we didn't implement yet. An AML dump may
> be useful, yes.
> 
> -ml
> 

Hi,

it seems that this is the same problem as on r640/r740. Please see

http://openbsd-archive.7691.n7.nabble.com/acpi-panic-on-dell-r640-and-r740xd-td339288.html





Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

2018-05-02 Thread Mike Larkin
On Wed, May 02, 2018 at 06:51:51PM +0200, Jan Vlach wrote:
> > Last time I checked, we don't support LoadTable.
> > 
> > -ml
> > 
> 
> Thank you Mike for your reply. I have no clue about ACPI. Is this a new
> way how vendors extend ACPI? Is there generally a way to switch it to
> some "legacy" mode or is this endgame? 
> Is there some info I could get from the system before I send it back
> that could later down the road when someone is interested? Would getting
> an acpidump from Linux and/or FreeBSD help at this point? 
> 
> Thank you again,
> Jan

kettenis@ may know more, I think he knows about this issue already. It's just
a missing piece of the standard we didn't implement yet. An AML dump may
be useful, yes.

-ml



Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

2018-05-02 Thread Mike Larkin
On Wed, May 02, 2018 at 11:28:47AM +0200, Jan Vlach wrote:
> R440 WAS( Re: Dell PowerEdge R430/R440 support)
> Reply-To: 
> In-Reply-To: <20180425150215.gh20...@diehard.n-r-g.com>
> 
> Hello misc@
> 
> 
> the Dell PowerEdge R440 server arrived for testing and it panics on boot
> to installed system. Installer works fine, it's the reboot into
> installed system that fails. Both 6.3-release and 6.3-current behave the
> same. (OpenBSD 6.3-current (RAMDISK_CD) #12: Wed Apr 25 22:56:41 MDT
> 2018; dmesg below)
> 
> I've turned PERC H330 into HBA mode and setup raid1 softraid from 3
> disks.
> 
> last screen on monitor with panic (rewritten by hand, sorry for possible 
> typos, photo at
> https://synchronicity.cz/bsd/ )
> 

Last time I checked, we don't support LoadTable.

-ml

> ### LAST PANIC SCREEN
> acpiprt81 at acpi0: bus -1 (SR3A)
> acpiprt82 at acpi0: bus -1 (SR3B)
> acpiprt83 at acpi0: bus -1 (SR3C)
> acpiprt84 at acpi0: bus -1 (SR3D)
> acpiprt85 at acpi0: bus -1 (MCP6)
> acpiprt86 at acpi0: bus -1 (MCP7)
> acpicpu0 at acpi0LoadTable
> 0140 Called: \_SB_.SCK0.CP00.ISTT
> 0140 Called: \_SB_.SCK0.CP00.ISTT
> 034d Called: \_SB_.SCK0.CP00._OSC
>   arg0: 0x80620488 cnt:05 stk: 00 buffer: 10 {16, a6, 77, 40,
> 0c, 29, be, 47, 9e, bd, d8, 70, 58, 71, 39, 53}
>   arg1: 0x80627988 cnt:01 stk:00 integer: 1 arg2: 0x80629388 
> cnt:01 stk:00 integer: 2
>   arg3: 0x8061d188 cnt:04 stk:00 buffer: 0c {00, 00, 00, 00, 3b,
> 03, 00, 00, ff, ff, ff, ff}
> 034d Called: \_SB_.SCK0.CP00._OSC
>   arg0: 0x80620488 cnt:05 stk: 00 buffer: 10 {16, a6, 77, 40,
> 0c, 29, be, 47, 9e, bd, d8, 70, 58, 71, 39, 53}
>   arg1: 0x80627988 cnt:01 stk:00 integer: 1
>   arg2: 0x80629388 cnt:01 stk:00 integer: 2
>   arg3: 0x8061d188 cnt:04 stk:00 buffer: 0c {00, 00, 00, 00, 3b,
> 03, 00, 00, ff, ff, ff, ff}
> panic: aml_die aml_parse:4194
> 
> This is reproducible at every boot.  I've tried to boot bsd.rd and mount root 
> fs to
> run acpidump, but it just says Abort trap.
> 
> Disabling acpi in UKC gets me to different panic, but this is probably
> barking at wrong tree at this point. 
> 
> There's also MARVELL 88SE9230 AHCI driver with two SSD drives I don't
> need. Installer complains about port softreset, haven't tried the
> functionality yet. 
> 
> There are some performance settings in bios
> (https://synchronicity.cz/bsd/bios/IMG_20180430_150250.jpg) but random
> fiddling without understanding didn't help me at this point.
> 
> Is there anything else to help debug this? I should have this box for
> another week or so (2 weeks from this monday 30.4.). 
> 
> Cluestick please?
> 
> Thank you,
> Jan
> 
> ### Screenshots and boot video at: https://synchronicity.cz/bsd/ ; installer
> dmesg follows.
> 
> files:
> - https://synchronicity.cz/bsd/dmesg.txt # same as below
> - https://synchronicity.cz/bsd/openbsd%206.3-release.mp4 # boot
>   including BIOS for 6.3-release
> - https://synchronicity.cz/bsd/openbsd%20installer.mp4 # boot into
>   6.3-current installer
> - https://synchronicity.cz/bsd/panic%20bsd.mp%206.3-current.jpg # panic
>   with bsd.mp
> - https://synchronicity.cz/bsd/panic%20bsd.sp%206.3-curent.jpg # panic
>   with bsd.sp
> 
> 
> ### DMESG
> 
> OpenBSD 6.3-current (RAMDISK_CD) #12: Wed Apr 25 22:56:41 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 101524992000 (96821MB)
> avail mem = 98444308480 (93883MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x6cb09000 (62 entries)
> bios0: vendor Dell Inc. version "1.3.7" date 02/09/2018
> bios0: Dell Inc. PowerEdge R440
> acpi0 at bios0: rev 2
> acpi0: tables DSDT FACP SSDT TPM2 WD__ HPET APIC MCFG MIGT MSCT NFIT PCAT 
> PCCT RASF SLIT SRAT SVOS OEM4 SSDT SSDT SSDT DMAR HEST BERT ERST EINJ
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz, 2494.65 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,MPX,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,AVX512CD,AVX512BW,AVX512VL,PKU,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: cannot disable silicon debug
> cpu0: apic clock running at 24MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.0.2, 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
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at 

Re: dhclient expects IPv4 address in dhclient.conf

2018-05-02 Thread Marc Peters
On Wed, May 02, 2018 at 04:24:50PM +0200, Janne Johansson wrote:
> Seems common on other dhcpd's too:
> https://lists.isc.org/pipermail/dhcp-users/2012-May/015511.html
> 

ah, the option has a different name for IPv6 nameservers. Does the base
dhclient recognize these different options, or do i have to give
isc-dhcp-client a try for this? 



Re: neovim :Man command not working on 6.3 -stable and only partially on -current

2018-05-02 Thread devmsv
On Wed, May 02, 2018 at 03:57:28PM +0200, devmsv wrote:
> Hi, I am using editors/neovim the :Man command to view man pages without
> exiting vim does not work on 6.3.
> In -current (6.3 GENERIC.MP#22 amd64) I am able to read manpages
> specifying the section:
> 
> :Man 1 man
> 
> I have seen that devel/msgpack as been updated between 6.3 and -current
> so don't know it it has something to do or is neovim but it should have
> been fixed according to https://github.com/neovim/neovim/pull/6766
> 
> Does anybody experience similar problem?
> 
It's seems that when there is only one section :Man works correctly on
-current in -stable it's completely broken.



Re: dhclient expects IPv4 address in dhclient.conf

2018-05-02 Thread Marc Peters
Am 2. Mai 2018 16:24:50 MESZ schrieb Janne Johansson :
>2018-05-02 16:06 GMT+02:00 Marc Peters :
>
>> Hi misc,
>> dhclient hates me. I would like to prepend an IPv6 nameserver in the
>> dhclient configuration on my router when connecting to my ISP, but
>> dhclient gives me following error:
>>
>> em1: /etc/dhclient.conf line 17: expecting IPv4 address.
>> em1: prepend domain-name-servers "::1"
>> em1: ^
>> dhclient.conf ist plain simple:
>> ~ $ grep -v "#" /etc/dhclient.conf
>>
>> supersede host-name "router";
>>
>> prepend domain-name-servers 127.0.0.1;
>>
>> prepend domain-name-servers "::1";
>>
>> Is this intended?
>>
>>
>Seems common on other dhcpd's too:
>https://lists.isc.org/pipermail/dhcp-users/2012-May/015511.html

This looks like a server issue and fixed in the meantime, otherwise the Windows 
Clients won't get any v6 nameservers, as they don't get it from the RAs.

My issue is with dhclient setting something in /etc/resolve.conf.

-- 
Sent from my cell phone



smtpd relay problem

2018-05-02 Thread Rudolf Sykora
Hello misc,

I just wanted to send mail through my gmail account
using smtpd in the relay mode.
I am unsuccessful so far, and do not understand what's
going wrong.

smtpd log of the attempt to send the email follows.
Can anybody help, please?

Thanks
Ruda

odin# smtpd -dv
debug: init ssl-tree
debug: init ca-tree
debug: init ssl-tree
debug: using "fs" queue backend
debug: using "ramqueue" scheduler backend
debug: using "ram" stat backend
info: OpenSMTPD 6.0.4 starting
debug: init ssl-tree
debug: init ca-tree
debug: init ssl-tree
debug: using "fs" queue backend
debug: using "ramqueue" scheduler backend
debug: using "ram" stat backend
debug: init ssl-tree
debug: init ca-tree
debug: init ssl-tree
debug: using "fs" queue backend
debug: using "ramqueue" scheduler backend
debug: using "ram" stat backend
setup_peer: klondike -> control[44050] fd=4
setup_peer: klondike -> pony express[21680] fd=5
setup_peer: control -> klondike[96213] fd=4
debug: init ssl-tree
debug: init ca-tree
debug: init ssl-tree
debug: using "fs" queue backend
debug: using "ramqueue" scheduler backend
debug: using "ram" stat backend
setup_peer: control -> lookup[58540] fd=5
setup_proc: klondike done
debug: init ssl-tree
debug: init ca-tree
debug: init ssl-tree
debug: using "fs" queue backend
debug: using "ramqueue" scheduler backend
setup_done: ca[96213] done
debug: using "ram" stat backend
setup_peer: control -> pony express[21680] fd=6
setup_peer: pony express -> control[44050] fd=4
setup_peer: control -> queue[82925] fd=7
setup_peer: lookup -> control[44050] fd=4
setup_peer: pony express -> klondike[96213] fd=5
setup_peer: control -> scheduler[51194] fd=8
setup_peer: lookup -> pony express[21680] fd=5
setup_peer: pony express -> lookup[58540] fd=6
debug: init ssl-tree
debug: init ca-tree
debug: init ssl-tree
debug: using "fs" queue backend
debug: using "ramqueue" scheduler backend
debug: using "ram" stat backend
setup_proc: control done
setup_done: control[44050] done
setup_peer: lookup -> queue[82925] fd=6
setup_peer: pony express -> queue[82925] fd=7
setup_peer: queue -> control[44050] fd=4
setup_proc: lookup done
setup_done: lka[58540] done
setup_proc: pony express done
setup_peer: queue -> pony express[21680] fd=5
setup_done: pony[21680] done
setup_peer: queue -> lookup[58540] fd=6
setup_peer: queue -> scheduler[51194] fd=7
debug: init ssl-tree
debug: init ca-tree
debug: init ssl-tree
debug: using "fs" queue backend
debug: using "ramqueue" scheduler backend
debug: using "ram" stat backend
setup_proc: queue done
debug: ca_engine_init: using RSA privsep engine
setup_done: queue[82925] done
setup_peer: scheduler -> control[44050] fd=4
setup_peer: scheduler -> queue[82925] fd=5
setup_proc: scheduler done
debug: bounce warning after 4h
setup_done: scheduler[51194] done
smtpd: setup done
debug: queue: done loading queue into scheduler
debug: parent_send_config_ruleset: reloading
debug: parent_send_config: configuring pony process
debug: parent_send_config: configuring ca process
debug: smtp: listen on IPv6:::1 port 25 flags 0x400 pki "" ca ""
debug: init private ssl-tree
debug: smtp: listen on IPv6:fe80::1%lo0 port 25 flags 0x400 pki "" ca ""
debug: smtp: listen on 127.0.0.1 port 25 flags 0x400 pki "" ca ""
debug: smtp: will accept at most 501 clients
debug: smtpd: scanning offline queue...
debug: smtpd: offline scanning done
debug: smtp: new client on listener: 0xe8882c55000
ec30efb21d77a7c5 smtp event=connected address=local host=
odin.troja.mff.cuni.cz
smtp: 0xe88a4f5b000: fd 13 from queue
smtp: 0xe88a4f5b000: message fd 13
debug: 0xe88a4f5b000: end of message, error=0
ec30efb21d77a7c5 smtp event=message address=local host=
odin.troja.mff.cuni.cz msgid=a28bb908 from=
to= size=381 ndest=1 proto=ESMTP
debug: scheduler: evp:a28bb908e6f62646 scheduled (mta)
ec30efb21d77a7c5 smtp event=closed address=local host=odin.troja.mff.cuni.cz
reason=quit
debug: smtp: 0xe88a4f5b000: deleting session: done
debug: mta: received evp:a28bb908e6f62646 for 
debug: mta: draining [relay:smtp.gmail.com,starttls,smtps,auth=secrets:A,mx]
refcount=1, ntask=1, nconnector=0, nconn=0
debug: mta: querying secret for [relay:smtp.gmail.com
,starttls,smtps,auth=secrets:A,mx]...
debug: control -> client: pipe closed
debug: mta: querying MX for [relay:smtp.gmail.com
,starttls,smtps,auth=secrets:A,mx]...
debug: clearing p=client, fd=11, pid=0
debug: mta: [relay:smtp.gmail.com,starttls,smtps,auth=secrets:A,mx] waiting
for MX secret
debug: mta: ... got secret for
[relay:smtp.gmail.com,starttls,smtps,auth=secrets:A,mx]:
AHJ1ZG9sZi5zeWtvcmFAZ21haWwuY29tAHBvaG9kYWpheno=
debug: mta: draining [relay:smtp.gmail.com,starttls,smtps,auth=secrets:A,mx]
refcount=2, ntask=1, nconnector=0, nconn=0
debug: mta: [relay:smtp.gmail.com,starttls,smtps,auth=secrets:A,mx] waiting
for MX
debug: MXs for domain smtp.gmail.com:
 66.102.1.108 preference -1
 66.102.1.109 preference -1
debug: mta: ... got mx 

Re: dhclient expects IPv4 address in dhclient.conf

2018-05-02 Thread Janne Johansson
2018-05-02 16:06 GMT+02:00 Marc Peters :

> Hi misc,
> dhclient hates me. I would like to prepend an IPv6 nameserver in the
> dhclient configuration on my router when connecting to my ISP, but
> dhclient gives me following error:
>
> em1: /etc/dhclient.conf line 17: expecting IPv4 address.
> em1: prepend domain-name-servers "::1"
> em1: ^
> dhclient.conf ist plain simple:
> ~ $ grep -v "#" /etc/dhclient.conf
>
> supersede host-name "router";
>
> prepend domain-name-servers 127.0.0.1;
>
> prepend domain-name-servers "::1";
>
> Is this intended?
>
>
Seems common on other dhcpd's too:
https://lists.isc.org/pipermail/dhcp-users/2012-May/015511.html


-- 
May the most significant bit of your life be positive.


dhclient expects IPv4 address in dhclient.conf

2018-05-02 Thread Marc Peters
Hi misc,

dhclient hates me. I would like to prepend an IPv6 nameserver in the
dhclient configuration on my router when connecting to my ISP, but
dhclient gives me following error:

em1: /etc/dhclient.conf line 17: expecting IPv4 address.
em1: prepend domain-name-servers "::1"
em1: ^

dhclient.conf ist plain simple:
~ $ grep -v "#" /etc/dhclient.conf  
  
supersede host-name "router";   
  
prepend domain-name-servers 127.0.0.1;  
  
prepend domain-name-servers "::1";

Is this intended?

Best,
Marc

--
dmesg:
OpenBSD 6.3 (GENERIC.MP) #1: Sat Apr 21 14:26:25 CEST 2018

r...@syspatch-63-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8151306240 (7773MB)
avail mem = 7897186304 (7531MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xeaf40 (52 entries)
bios0: vendor American Megatrends Inc. version "0306" date
08/18/2011
bios0: ASUSTeK Computer INC. E45M1-I DELUXE
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG HPET SSDT SSDT
acpi0: wakeup devices SBAZ(S4) UAR1(S4) P0PC(S4) UHC1(S4) UHC2(S4)
USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4)
RLAN(S4) PE22(S4) PE23(S4) BR14(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD E-450 APU with Radeon(tm) HD Graphics, 1650.41 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,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache,
512KB 64b/line 16-way L2 cache
cpu0: 8 4MB entries fully associative
cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully
associative
acpitimer0: recalibrated TSC frequency 1649918204 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD E-450 APU with Radeon(tm) HD Graphics, 1649.93 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,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache,
512KB 64b/line 16-way L2 cache
cpu1: 8 4MB entries fully associative
cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully
associative
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 21, 24 pins
, remapped to apid 0
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318180 Hz
acpihpet0: recalibrated TSC frequency 1649928660 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (PE20)
acpiprt2 at acpi0: bus 4 (PE21)
acpiprt3 at acpi0: bus -1 (PE22)
acpiprt4 at acpi0: bus -1 (PE23)
acpiprt5 at acpi0: bus -1 (BR15)
acpiprt6 at acpi0: bus -1 (PCE6)
acpiprt7 at acpi0: bus -1 (PCE7)
acpiprt8 at acpi0: bus -1 (PCE8)
acpiprt9 at acpi0: bus 1 (BR14)
acpicpu0 at acpi0: C2(0@100 io@0x1771), C1(@1 halt!), PSS
acpicpu1 at acpi0: C2(0@100 io@0x1771), C1(@1 halt!), PSS
acpibtn0 at acpi0: PWRB
"PNP0C14" at acpi0 not configured
cpu0: 1650 MHz: speeds: 1650 1320 825 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD AMD64 14h Host" rev 0x00
radeondrm0 at pci0 dev 1 function 0 "ATI Radeon HD 6320" rev 0x00
drm0 at radeondrm0
radeondrm0: msi
azalia0 at pci0 dev 1 function 1 "ATI Radeon HD 6310 HD Audio" rev
0x00: msi
azalia0: no supported codecs
ppb0 at pci0 dev 4 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
pci1 at ppb0 bus 1
em0 at pci1 dev 0 function 0 "Intel 82576" rev 0x01: msi, address
90:e2:ba:e9:1a:3a
em1 at pci1 dev 0 function 1 "Intel 82576" rev 0x01: msi, address
90:e2:ba:e9:1a:3b
ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x40: apic 0
int 19, AHCI 1.2
ahci0: port 0: 6.0Gb/s
ahci0: port 1: 6.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3
0/direct fixed naa.50014ee60409ed8f
sd0: 953869MB, 512 bytes/sector, 1953525168 sectors
sd1 at scsibus1 targ 1 lun 0:  SCSI3
0/direct fixed naa.50014ee604099ed2
sd1: 953869MB, 512 bytes/sector, 1953525168 sectors
ohci0 at pci0 dev 18 function 0 "ATI SB700 USB" rev 0x00: apic 0 int
18, version 1.0, legacy support
ehci0 at pci0 dev 18 function 2 "ATI SB700 USB2" rev 0x00: apic 0
int 17
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "ATI EHCI root hub" rev
2.00/1.00 addr 1
ohci1 at pci0 dev 19 function 0 "ATI SB700 USB" rev 0x00: 

neovim :Man command not working on 6.3 -stable and only partially on -current

2018-05-02 Thread devmsv
Hi, I am using editors/neovim the :Man command to view man pages without
exiting vim does not work on 6.3.
In -current (6.3 GENERIC.MP#22 amd64) I am able to read manpages
specifying the section:

:Man 1 man

I have seen that devel/msgpack as been updated between 6.3 and -current
so don't know it it has something to do or is neovim but it should have
been fixed according to https://github.com/neovim/neovim/pull/6766

Does anybody experience similar problem?



Re: crash of OpenBSD 6.3 -stable (amd64 MP kernel) - unswapping kills connections

2018-05-02 Thread Infoomatic
thats good news, thanks Philip for the info! In the meantime I disabled
swap (as well as ntopng) on my firewalls - this is of course not needed
on a firewall and was just a left-over from the initial default install.
regards,infoomatic Gesendet: Freitag, 27. April 2018 um 13:50 Uhr
Von: "Philip Guenther" 
An: Infoomatic 
Cc: "OpenBSD Misc" 
Betreff: Re: crash of OpenBSD 6.3 -stable (amd64 MP kernel) - unswapping
kills connectionsOn Thu, Apr 26, 2018 at 11:21 PM, Infoomatic 

wrote:

  thanks for your input! Actually, I was never really satisfied with
  the stability of ntopng, so this problem of the memory leak does not
  really surprise me. However, when killing the process, which also
  means freeing swap space, I think it is not an expected behaviour
  that the system does not handle any tcp/ip or icmp connections any
  more until the swap space is fully freed (which, in my case when
  ntopng used 3 out of 4GB swap, lastet for nearly 20 minutes). IMHO,
  unswapping a process should not influence network connectivity that
  much.

You're correct that we don't want the clean up of an exiting process to
affect network processing.  The issue is that our UVM is still under the
kernel lock; work into using more fine-grained locking there has begun
but nothing has really hit the tree yet. Philip Guenther


Troobleshooting help for UVM

2018-05-02 Thread sven falempin
6.3 + syspatch

UVM: pid  (perl), uid 0 killed: out of swap

no ddb, i m not using swap in perl afaik, and it seems strange
a userland script can 'kill' UVM


OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2080227328 (1983MB)
avail mem = 2010144768 (1917MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf68b0 (9 entries)
bios0: vendor SeaBIOS version "2:1.10.2-58953eb7" date 04/01/2014
bios0: OpenStack Foundation OpenStack Nova
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel Core Processor (Haswell, no TSX), 2394.83 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,VMX,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,ARAT,MELTDOWN
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 999MHz
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
"ACPI0006" at acpi0 not configured
acpicmos0 at acpi0
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
pvbus0 at mainbus0: KVM
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 disabled (no drives)
uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int 9
iic0 at piixpm0
vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
vio0 at virtio0: address fa:16:3e:ec:59:66
virtio0: msix shared
virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00
vioblk0 at virtio1
scsibus1 at vioblk0: 2 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct fixed
sd0: 10240MB, 512 bytes/sector, 20971520 sectors
virtio1: msix shared
virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory" rev 0x00
viomb0 at virtio2
virtio2: apic 0 int 10
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev
1.00/1.00 addr 1
vmm0 at mainbus0: VMX/EPT
uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB
Tablet" rev 2.00/0.00 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 3 buttons, Z dir
wsmouse1 at ums0 mux 0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (fe232e2f6ab8c86a.a) swap on sd0b dump on sd0b
WARNING: / was not properly unmounted
fd0 at fdc0 drive 1: density unknown

No swap actually :

fe232e2f6ab8c86a.a / ffs rw,wxallowed 1 1
swap /var/run mfs rw,nodev,nosuid,-s=32M 0 0



-- 
--
-
Knowing is not enough; we must apply. Willing is not enough; we must do



6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

2018-05-02 Thread Jan Vlach
R440 WAS( Re: Dell PowerEdge R430/R440 support)
Reply-To: 
In-Reply-To: <20180425150215.gh20...@diehard.n-r-g.com>

Hello misc@


the Dell PowerEdge R440 server arrived for testing and it panics on boot
to installed system. Installer works fine, it's the reboot into
installed system that fails. Both 6.3-release and 6.3-current behave the
same. (OpenBSD 6.3-current (RAMDISK_CD) #12: Wed Apr 25 22:56:41 MDT
2018; dmesg below)

I've turned PERC H330 into HBA mode and setup raid1 softraid from 3
disks.

last screen on monitor with panic (rewritten by hand, sorry for possible typos, 
photo at
https://synchronicity.cz/bsd/ )

### LAST PANIC SCREEN
acpiprt81 at acpi0: bus -1 (SR3A)
acpiprt82 at acpi0: bus -1 (SR3B)
acpiprt83 at acpi0: bus -1 (SR3C)
acpiprt84 at acpi0: bus -1 (SR3D)
acpiprt85 at acpi0: bus -1 (MCP6)
acpiprt86 at acpi0: bus -1 (MCP7)
acpicpu0 at acpi0LoadTable
0140 Called: \_SB_.SCK0.CP00.ISTT
0140 Called: \_SB_.SCK0.CP00.ISTT
034d Called: \_SB_.SCK0.CP00._OSC
  arg0: 0x80620488 cnt:05 stk: 00 buffer: 10 {16, a6, 77, 40,
0c, 29, be, 47, 9e, bd, d8, 70, 58, 71, 39, 53}
  arg1: 0x80627988 cnt:01 stk:00 integer: 1 arg2: 0x80629388 
cnt:01 stk:00 integer: 2
  arg3: 0x8061d188 cnt:04 stk:00 buffer: 0c {00, 00, 00, 00, 3b,
03, 00, 00, ff, ff, ff, ff}
034d Called: \_SB_.SCK0.CP00._OSC
  arg0: 0x80620488 cnt:05 stk: 00 buffer: 10 {16, a6, 77, 40,
0c, 29, be, 47, 9e, bd, d8, 70, 58, 71, 39, 53}
  arg1: 0x80627988 cnt:01 stk:00 integer: 1
  arg2: 0x80629388 cnt:01 stk:00 integer: 2
  arg3: 0x8061d188 cnt:04 stk:00 buffer: 0c {00, 00, 00, 00, 3b,
03, 00, 00, ff, ff, ff, ff}
panic: aml_die aml_parse:4194

This is reproducible at every boot.  I've tried to boot bsd.rd and mount root 
fs to
run acpidump, but it just says Abort trap.

Disabling acpi in UKC gets me to different panic, but this is probably
barking at wrong tree at this point. 

There's also MARVELL 88SE9230 AHCI driver with two SSD drives I don't
need. Installer complains about port softreset, haven't tried the
functionality yet. 

There are some performance settings in bios
(https://synchronicity.cz/bsd/bios/IMG_20180430_150250.jpg) but random
fiddling without understanding didn't help me at this point.

Is there anything else to help debug this? I should have this box for
another week or so (2 weeks from this monday 30.4.). 

Cluestick please?

Thank you,
Jan

### Screenshots and boot video at: https://synchronicity.cz/bsd/ ; installer
dmesg follows.

files:
- https://synchronicity.cz/bsd/dmesg.txt # same as below
- https://synchronicity.cz/bsd/openbsd%206.3-release.mp4 # boot
  including BIOS for 6.3-release
- https://synchronicity.cz/bsd/openbsd%20installer.mp4 # boot into
  6.3-current installer
- https://synchronicity.cz/bsd/panic%20bsd.mp%206.3-current.jpg # panic
  with bsd.mp
- https://synchronicity.cz/bsd/panic%20bsd.sp%206.3-curent.jpg # panic
  with bsd.sp


### DMESG

OpenBSD 6.3-current (RAMDISK_CD) #12: Wed Apr 25 22:56:41 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 101524992000 (96821MB)
avail mem = 98444308480 (93883MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x6cb09000 (62 entries)
bios0: vendor Dell Inc. version "1.3.7" date 02/09/2018
bios0: Dell Inc. PowerEdge R440
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP SSDT TPM2 WD__ HPET APIC MCFG MIGT MSCT NFIT PCAT PCCT 
RASF SLIT SRAT SVOS OEM4 SSDT SSDT SSDT DMAR HEST BERT ERST EINJ
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz, 2494.65 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,MPX,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,AVX512CD,AVX512BW,AVX512VL,PKU,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: cannot disable silicon debug
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2, 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
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
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
cpu at 

cohesive configuration parameters between various OpenBSD systems

2018-05-02 Thread Vivek Vinod
Dear Misc,

Various parts of OpenBSD base refer to AddressFamily and accepted values are 
different. Examples listed below.

Any reason why we have “inet” in sshd_config and “inet4” in smtpd.conf? I’m 
assuming OpenSMTPD released after inet6 was in wide(r) use and old programs, 
utilities, etc. were released when there was no ipv6 around, hence the 
difference. 

This is not an important issue, just asking if there are plans to migrate to a 
common reference.

Regards,
Vivek

$man sshd_config
…
AddressFamily
Specifies which address family should be used by sshd(8).  Valid
arguments are any (the default), inet (use IPv4 only), or inet6
 (use IPv6 only).
…

$man smtpd.conf
…
listen on interface [family] [port port]
…
Specify an interface and optional port to listen on for incoming
connections.  An interface group, an IP address or a domain name
may be used in place of interface.  The family parameter can be
used to listen only on specific address family.  Accepted values
are inet4 and inet6.
…

$man netstat
…
The following address families are recognized:
Address FamilyConstant  Description
InetAF_INET   IP Version 4
inet6   AF_INET6  IP Version 6
…





Re: no route to host (when there is a route )

2018-05-02 Thread Tom Smyth
Ingo , Martin,  All,

i can confirm
when the issue occured the command

arp -s  gateway-ip-address gateway-mac-address
worked  to restore connectivity

Cheers,

Tom Smyth

On 1 May 2018 at 21:16, Tom Smyth  wrote:
> Hello Ingo, Martin,All,
>
> I think you hit the nail on the head, (I was too busy looking at the
> routing table (and forgot the fundamental principle of longest prefix
> match)
>
>  so if I have a static arp entry before adding in the
>  (more specific than the connected route) i should be OK
>
> just to explain (the method in my madness )
>  (what i agree in hindsight is a fragile setup)
> basically I have a /22 network the clients are isolated from each
> other on Layer 2 (so the clients cant see each others
> arp requests / replys)  (Bridge horizon / protected ports / privatevlan)
> to limit  bandwith wasting stuff such as broadcasts and other
> security issues such as rogue DHCP servers etc.
>
> The clients can only see the gateway
> and the gateway can see all the clients ..  I have heard of people
> using some proxy arp solutions on the gateway and perhaps
>  that is what I should be doing rather than the ( more specific
>  than connected static routes)
>
> Does anyone who operate Access layer in ISPS have suggestions
> I appreciate the help and the reminder of the longest prefix match
> rule :)
>
> Thanks again
>
> On 1 May 2018 at 21:03, Martin Pieuchot  wrote:
>> On 01/05/18(Tue) 21:28, Ingo Schwarze wrote:
>>> [...]
>>> So what you are doing seems fragile to me.  It may sometimes work
>>> due to order of configuration, timeouts, whatever, i'm not sure.
>>
>> It can work if the ARP entry, what Ingo called the /32 is created
>> before you add your /23.
>>
>>> But once part of it gets broken for whatever reason, i don't see
>>> how it could possibly automatically recover via the normal RTF_CLONING
>>> mechanism.
>>
>> It can't because as you described the /23 will be a better match.  And the
>> reason will be the expiration of the ARP cache.