Re: Problems building BIND 9.10.3 on OpenBSD 5.7

2015-09-17 Thread Stuart Henderson 
On 2015-09-17, Research  wrote:
> Hello,
>
> I am currently having issues compiling BIND 9.10.3 (released by ISC this week 
> to correct for DoS vulnerabilities), on my OpenBSD 5.7 test machine.  I am 
> running the OpenBSD 5.7 release build with the 14 errata patches successfully 
> applied and with the userland also rebuilt.

9.10.3 is a feature release, it's in -current ports but I don't intend to
backport to -stable yet. The security fixes are in 9.10.2-P4 which is
in -stable ports.

> I can successfully make configure, but when I attempt make build, I receive:
>
> …previous successful build messages removed...
>
> making all in /home/developer/bind-9.10.3/lib/samples
> gcc -pthread  -I/home/developer/bind-9.10.3 -I../.. -I./include 
> -I../dns/include  -I/home/developer/bind-9.10.3/lib/dns/include  
> -I../../lib/dns/include -I/home/developer/bind-9.10.3/lib/isc/include  
> -I../../lib/isc  -I../../lib/isc/include  -I../../lib/isc/unix/include  
> -I../../lib/isc/pthreads/include  -I../../lib/isc/x86_32/include  
> -I../../lib/irs/include  -I../../lib/irs/include   -D_REENTRANT 
> -DVERSION=\"9.10.3\" -DSYSCONFDIR=\"/etc/bind\"  -g -O2   -W -Wall 
> -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wformat -Wpointer-arith 
> -fno-strict-aliasing -fno-delete-null-pointer-checks  -c resolve.c
> gcc -pthread -g -O2  -o resolve  resolve.o ../irs/libirs.a ../dns/libdns.a  
> -lcrypto ../isccfg/libisccfg.a ../isc/libisc.a -lpthread 
> ../irs/libirs.a(getnameinfo.o)(.text+0x18f): In function `getnameinfo':
> /home/developer/bind-9.10.3/lib/irs/getnameinfo.c:220: warning: strcpy() is 
> almost always misused, please use strlcpy()
> ../dns/libdns.a(resolver.o)(.text+0x9774): In function 
> `dns_resolver_createfetch3':
> /home/developer/bind-9.10.3/lib/dns/resolver.c:4155: warning: strcat() is 
> almost always misused, please use strlcat()
> ../dns/libdns.a(name.o)(.text+0x426b): In function `dns_name_tofilenametext':
> /home/developer/bind-9.10.3/lib/dns/name.c:1636: warning: sprintf() is often 
> misused, please use snprintf()
> ../dns/libdns.a(openssldh_link.o)(.text+0xed5): In function 
> `openssldh_generate':
> /home/developer/bind-9.10.3/lib/dns/openssldh_link.c:212: undefined reference 
> to `BN_GENCB_new'
> ../dns/libdns.a(openssldh_link.o)(.text+0xf23):/home/developer/bind-9.10.3/lib/dns/openssldh_link.c:234:
>  undefined reference to `BN_GENCB_free'
> ../dns/libdns.a(openssldh_link.o)(.text+0xffe):/home/developer/bind-9.10.3/lib/dns/openssldh_link.c:229:
>  undefined reference to `BN_GENCB_free'

Our OPENSSL_VERSION_NUMBER #defines don't (and can't) directly map from
libressl's api to openssl's. If you have a requirement to use 9.10.3 now
then either run -current, backport my patches, or disable crypto support
if you don't need it (untested but should work).

Re: bootparamd and non-default subnet masks

2015-09-17 Thread Marko Cupać 
On Mon, 14 Sep 2015 13:59:15 +0200
Marko Cupać  wrote:

> Hi,
> 
> I am trying to implement diskless setup in VLAN-segmented network.
> Server which hosts dhcpd, tftpd, nfsd, rarpd and bootparamd is on
> 10.30.7.38/27, on separate vlan from client which should be on
> 10.30.7.51/27.
> 
> Client obtains IP address, executes pxeboot and boots bsd from tftp
> successfully. However, after that I get messages:
> nfs_boot: using interface rl0, with revarp & bootparams
> nfs_boot: client_addr=10.30.7.51
> RPC timeout for server 10.255.255.255 (0xaff) prog 10
> 
> The problem is apparently with non-standard subnet mask for class A
> network, but AFAIK rarpd does not supply subnet mask information. How
> can I make this work?
> 
> Regards,

Guys,

is this really so irrelevant? Or should I interpret silence on topic
somewhere along the lines of "None of the great masters who wrote and
understood this are no longer with us" :P

-- 
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/

Re: 5.8-stable: panic: mtx_enter locking against myself

2015-09-17 Thread mxb 
It is from CVS.
dmesg below.

OpenBSD 5.8-stable (GENERIC.MP) #0: Tue Sep 15 22:38:07 CEST 2015
r...@fw1.home.unixconn.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17051418624 (16261MB)
avail mem = 16530747392 (15764MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed8a0 (122 entries)
bios0: vendor American Megatrends Inc. version "1.0b" date 01/06/2015
bios0: Supermicro X10DRT-PT
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT SPMI MCFG UEFI BDAT HPET MSCT PMCT SLIT 
SRAT WDDT SSDT SSDT SSDT PRAD DMAR HEST BERT ERST EINJ
acpi0: wakeup devices IP2P(S4) EHC1(S4) EHC2(S4) RP01(S4) RP02(S4) RP03(S4) 
RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) BR1A(S4) BR1B(S4) BR2A(S4) 
BR2B(S4) BR2C(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz, 3500.45 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,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,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 100MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz, 3500.01 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,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 8 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz, 3500.01 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,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,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 0, core 4, package 0
cpu3 at mainbus0: apid 10 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz, 3500.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,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,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 0, core 5, package 0
cpu4 at mainbus0: apid 16 (application processor)
cpu4: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz, 3495.42 MHz
cpu4: 
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,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 0, core 0, package 1
cpu5 at mainbus0: apid 18 (application processor)
cpu5: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz, 3500.00 MHz
cpu5: 
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,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 0, core 1, package 1
cpu6 at mainbus0: apid 24 (application processor)
cpu6: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz, 3500.00 MHz
cpu6: 
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,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu6: 256KB 64b/line 8-way L2 cache
cpu6: smt 0, core 4, package 1
cpu7 at mainbus0: apid 26 (application processor)
cpu7: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz, 3500.00 MHz
cpu7:

Re: bootparamd and non-default subnet masks

2015-09-17 Thread Marko Cupać 
On Thu, 17 Sep 2015 09:24:16 + (UTC)
Stuart Henderson  wrote:

> RARP (RFC 903) d

Hi Stuart,

thank you for the information.

Would there be some bad consequences if OpenBSD changed its diskless
booting process so it respects DHCP's root path option?

Regards,
-- 
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/

Re: spamdb

2015-09-17 Thread Adam Wolk 
On Tue, 15 Sep 2015 19:26:22 +0200
"Fran. J Ballesteros"  wrote:

> just FYI. our spamd indeed had problems leading to corrupt db entries
> so some where never white listed. 
> 
> I changed it to use a simple in memory db and it now white lists as
> it should. the change is ok for us but not for openbsd, so I didn't
> submit any patch anywhere. 
> 
> the symptom of the problem is that some mails get rejected with
> temporary failures forever. I would pay attention to the logs and the
> db if using the stock spamd. 
> 
> Also, in case it affects, we are using the software raid. 
> 
> hth others googling for spamd. 
> 
> > El 10/9/2015, a las 15:41, Peter N. M. Hansteen 
> > escribió:
> > 
> >> On Thu, Sep 10, 2015 at 03:04:26PM +0200, Fran. J Ballesteros
> >> wrote:
> >> 
> >> with 5.7 our spamdb becomes corrupt after a while. Are we the only
> >> ones with this problem? Anyone else using it?
> > 
> > using spamd with related tools including spamdb through the 5.7
> > cycle and past, yes.
> > 
> > seeing spamdb corrupted, not that I've noticed. What are the
> > symptoms more specifically?
> > 
> > 
> > -- 
> > Peter N. M. Hansteen, member of the first RFC 1149 implementation
> > team http://bsdly.blogspot.com/ http://www.bsdly.net/
> > http://www.nuug.no/ "Remember to set the evil bit on all malicious
> > network traffic" delilah spamd[29949]: 85.152.224.147: disconnected
> > after 42673 seconds.
> 

I have been hitting issues with spamdb since April. Ended up disabling
it as it's just a private server for 2 people so not really hurt much
by being disabled. You can see the problem I reported on the mailing
list here:

 http://marc.info/?t=14301581823=1=2

I do wonder if you are having the same issues as I did back then.

5.8-stable: panic: mtx_enter locking against myself

2015-09-17 Thread mxb 
Hey,
getting panics with 5.8-STABLE kernel.

panic: mix_enter: locking against myself
Starting stack trace…
panic() at panic+0x10b
mtx_enter() at mtx_enter+0x60
sofree() at sofree+0xa0
in_pcbdetach() at in_pcbdetach+0x40
tcp_close() at tcp_close+0xad
tcp_timer_2msl() at tcp_timer_2msl+0x90
softclock() at softclock+0x315
softintr_dispatch() at softintr_dispatch+0x8b
Xsoftclock() at Xsoftclock+0x1f
——interrupt———
(null)() at 0x8
end of kernel
end trace frame: 0x1120001, count: 247
end of stack trace

Re: 5.8-stable: panic: mtx_enter locking against myself

2015-09-17 Thread mxb 
and this is for a crash just 10min ago.

(gdb) file /var/crash/bsd.0
Reading symbols from /var/crash/bsd.0...(no debugging symbols found)...done.
(gdb) target kvm /var/crash/bsd.0.core
#0  0x8131cae4 in dumpsys ()
(gdb) where
#0  0x8131cae4 in dumpsys ()
#1  0x00030272 in ?? ()
#2  0x0005 in ?? ()
#3  0x8135e990 in sd_flush ()
Previous frame inner to this frame (corrupt stack?)


Any ideas?

> On 17 sep. 2015, at 10:35, mxb  wrote:
> 
> 
> Hey,
> getting panics with 5.8-STABLE kernel.
> 
> panic: mix_enter: locking against myself
> Starting stack trace…
> panic() at panic+0x10b
> mtx_enter() at mtx_enter+0x60
> sofree() at sofree+0xa0
> in_pcbdetach() at in_pcbdetach+0x40
> tcp_close() at tcp_close+0xad
> tcp_timer_2msl() at tcp_timer_2msl+0x90
> softclock() at softclock+0x315
> softintr_dispatch() at softintr_dispatch+0x8b
> Xsoftclock() at Xsoftclock+0x1f
> ——interrupt———
> (null)() at 0x8
> end of kernel
> end trace frame: 0x1120001, count: 247
> end of stack trace

Re: bootparamd and non-default subnet masks

2015-09-17 Thread Stuart Henderson 
On 2015-09-17, Marko Cupać  wrote:
> On Mon, 14 Sep 2015 13:59:15 +0200
> Marko Cupać  wrote:
>
>> Hi,
>> 
>> I am trying to implement diskless setup in VLAN-segmented network.
>> Server which hosts dhcpd, tftpd, nfsd, rarpd and bootparamd is on
>> 10.30.7.38/27, on separate vlan from client which should be on
>> 10.30.7.51/27.
>> 
>> Client obtains IP address, executes pxeboot and boots bsd from tftp
>> successfully. However, after that I get messages:
>> nfs_boot: using interface rl0, with revarp & bootparams
>> nfs_boot: client_addr=10.30.7.51
>> RPC timeout for server 10.255.255.255 (0xaff) prog 10
>> 
>> The problem is apparently with non-standard subnet mask for class A
>> network, but AFAIK rarpd does not supply subnet mask information. How
>> can I make this work?
>> 
>> Regards,
>
> Guys,
>
> is this really so irrelevant? Or should I interpret silence on topic
> somewhere along the lines of "None of the great masters who wrote and
> understood this are no longer with us" :P
>

RARP (RFC 903) does not support CIDR.

Re: 5.8-stable: panic: mtx_enter locking against myself

2015-09-17 Thread koko 
On Thu, 17 Sep 2015 10:35:46 +0200
mxb  wrote:

> getting panics with 5.8-STABLE kernel.
> 
5.8-STABLE not released yet. you mean 5.8-CURRENT?

Re: 5.8-stable: panic: mtx_enter locking against myself

2015-09-17 Thread Stuart Henderson 
On 2015-09-17, mxb  wrote:
> Hey,
> getting panics with 5.8-STABLE kernel.
>
> panic: mix_enter: locking against myself
> Starting stack trace…
> panic() at panic+0x10b
> mtx_enter() at mtx_enter+0x60
> sofree() at sofree+0xa0
> in_pcbdetach() at in_pcbdetach+0x40
> tcp_close() at tcp_close+0xad
> tcp_timer_2msl() at tcp_timer_2msl+0x90
> softclock() at softclock+0x315
> softintr_dispatch() at softintr_dispatch+0x8b
> Xsoftclock() at Xsoftclock+0x1f
> ——interrupt———
> (null)() at 0x8
> end of kernel
> end trace frame: 0x1120001, count: 247
> end of stack trace
>
>

A bit more information about when this is happening might be useful..

Re: requesting help working around boot failures with supermicro atom board

2015-09-17 Thread Dewey Hylton 
Dewey Hylton  gmail.com> writes:

> 
> Mike Larkin  azathoth.net> writes:
> 
> > 
> > On Tue, Sep 15, 2015 at 07:16:40PM +, Dewey Hylton wrote:
> > > Dewey Hylton  gmail.com> writes:
> > > 
> > > > 
> > > > Mike Larkin  azathoth.net> writes:
> > > 
> > > > > acpidump please.

> motherboard: supermicro x7spe-hf-d525 rev 1.0
> bios: 1.2b
> 
> at the end of this link is an archive containing acpidump output for all
> three acpi settings in the bios (1.0, 2.0, 3.0). 
> 
> https://goo.gl/tWGL6C
> 
> i apologize for the somewhat hidden link; gmane wouldn't allow me to post
> the full link because it's greater than 80 characters.
> 
> please let me know if i can help in any way; i honestly know nothing about
> acpi but am willing to learn or assist otherwise if it means understanding
> and potentially fixing this issue.

i was able to export the DSDT files into something human-readable. while i
don't really understand much of what i'm seeing in the resulting text files,
diff shows that the differences between the three acpi versions are
nonexistent. i have no idea about the other files, of which there are several.

Mike, does the acpidump output help at all? if not, am i simply at the point
where this hardware is not compatible with OpenBSD?

Re: requesting help working around boot failures with supermicro atom board

2015-09-17 Thread Mike Larkin 
On Thu, Sep 17, 2015 at 12:40:12PM +, Dewey Hylton wrote:
> Dewey Hylton  gmail.com> writes:
> 
> > 
> > Mike Larkin  azathoth.net> writes:
> > 
> > > 
> > > On Tue, Sep 15, 2015 at 07:16:40PM +, Dewey Hylton wrote:
> > > > Dewey Hylton  gmail.com> writes:
> > > > 
> > > > > 
> > > > > Mike Larkin  azathoth.net> writes:
> > > > 
> > > > > > acpidump please.
> 
> > motherboard: supermicro x7spe-hf-d525 rev 1.0
> > bios: 1.2b
> > 
> > at the end of this link is an archive containing acpidump output for all
> > three acpi settings in the bios (1.0, 2.0, 3.0). 
> > 
> > https://goo.gl/tWGL6C
> > 
> > i apologize for the somewhat hidden link; gmane wouldn't allow me to post
> > the full link because it's greater than 80 characters.
> > 
> > please let me know if i can help in any way; i honestly know nothing about
> > acpi but am willing to learn or assist otherwise if it means understanding
> > and potentially fixing this issue.
> 
> i was able to export the DSDT files into something human-readable. while i
> don't really understand much of what i'm seeing in the resulting text files,
> diff shows that the differences between the three acpi versions are
> nonexistent. i have no idea about the other files, of which there are several.
> 
> Mike, does the acpidump output help at all? if not, am i simply at the point
> where this hardware is not compatible with OpenBSD?
> 

Haven't had a chance to look at it yet.

-ml

EDID checksum is invalid

2015-09-17 Thread Raimo Niskanen 
Hello misc@

I just installed OpenBSD 5.8 from CD (i386) on an MSI MS 9A19, and it all
went well, but when I put it in the server rack on the KVM it started to
produce lots of error messages about "EDID checksum is invalid".  The error
repeats almost once every minute.

I do not run X on it, but this seems to concern recognizing the attached
display.  The printed EDID data is apparently random.

The KVM is attached to the machine's DVI connector with a DVI-to-VGA
adapter, if that would matter.

Here is the dmesg:

OpenBSD 5.7 (GENERIC.MP) #767: Sun Mar  8 11:04:48 MDT 2015
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF
real mem  = 2138324992 (2039MB)
avail mem = 2090995712 (1994MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 07/27/11, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.4
@ 0xfd520 (18 entries)
bios0: vendor American Megatrends Inc. version "V5.0" date 07/27/2011
bios0: MSI MS-9A19
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG OEMB SSDT
acpi0: wakeup devices P0P2(S4) P0P1(S4) PS2K(S4) PS2M(S4) USB0(S4) USB1(S4)
USB2(S4) USB3(S4) EUSB(S4) MC97(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4)
P0P8(S4) P0P9(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
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 133MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60
GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 1, remapped to apid 2
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (P0P4)
acpiprt2 at acpi0: bus 2 (P0P5)
acpiprt3 at acpi0: bus -1 (P0P6)
acpiprt4 at acpi0: bus -1 (P0P7)
acpiprt5 at acpi0: bus -1 (P0P8)
acpiprt6 at acpi0: bus -1 (P0P9)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
acpivideo0 at acpi0: IGD_
bios0: ROM list: 0xc/0xec00!
cpu0: Enhanced SpeedStep 1597 MHz: speeds: 1600, 1333, 1067, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GME Host" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82945GME Video" rev 0x03
intagp0 at vga1
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
inteldrm0: 1024x768
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Realtek ALC888
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 2 int 16
pci1 at ppb0 bus 1
em0 at pci1 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address
44:8a:5b:34:4f:f4
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 2 int 17
pci2 at ppb1 bus 2
em1 at pci2 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address
44:8a:5b:34:4f:f5
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 2 int 23
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 2 int 19
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 2 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 2 int 16
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 2 int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb2 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci3 at ppb2 bus 3
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM
disabled
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 ignored (disabled)
pciide1 at pci0 dev 31 function 2 "Intel 82801GBM SATA" rev 0x02: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide1: using apic 2 int 19 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0: 
wd0: 1-sector PIO, LBA48, 76319MB, 156301488 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 6
ichiic0 at pci0 dev 31 function 3 "Intel 82801GB SMBus" rev 0x02: apic 2
int 19
iic0 at

Using a Wacom (CTH-480) graphic tablet with OpenBSD ?

2015-09-17 Thread Christoph R. Murauer 
Hello !

Is someone using a Wacom graphics tablet with OpenBSD ? Are there some 
instructions to get it to work ? I tried a snapshot from August and, it don't 
worked after the installation.

Thanks for ideas.

Re: 5.8-stable: panic: mtx_enter locking against myself

2015-09-17 Thread mxb 
Seems to happen very random.
I have two systems which do this. Both are 2-node CARP.
It is only kernel which is -STABLE on those two. Userland is from a snap 
approx. 14 days old.
Update to stable kernel is done recently, because of those crashes.
Kernel before is running OK on more heavily loaded machines.

Here is a trace from a crash just 50min ego.
I can’t do any thing directly in gdb (ddb.panic=1) as this is IPMI console and 
kbd not working.

(gdb) file /var/crash/bsd.0
Reading symbols from /var/crash/bsd.0...(no debugging symbols found)...done.
(gdb) target kvm /var/crash/bsd.0.core
#0  0x8131c7d4 in dumpsys ()
(gdb) where
#0  0x8131c7d4 in dumpsys ()
#1  0x00038000 in ?? ()
#2  0x0003024c in ?? ()
#3  0x0005 in ?? ()
#4  0x8135e680 in chopen ()
#5  0x8131c90b in dumpsys ()
#6  0x0021 in ?? ()
#7  0x80002127be68 in ?? ()
#8  0x81328434 in amd_cpu_cacheinfo ()
#9  0x81328340 in x86_print_cacheinfo ()
#10 0x80002127be68 in ?? ()
#11 0x811958d6 in srp_enter ()
#12 0x811958d6 in srp_enter ()
#13 0x811a4986 in addlog ()
#14 0x0038 in ?? ()
#15 0x80002127bf78 in ?? ()
#16 0x80002127be98 in ?? ()
#17 0x757ff7a94f468953 in ?? ()
#18 0x in ?? ()
(gdb)

[prdsrv0003.sto1.se]-[21:42:31]# ps -N /var/crash/bsd.0 -M 
/var/crash/bsd.0.core -O paddr
  PIDPADDR TT  STAT   TIME COMMAND
25250 ff0401574dc0 ??  Is+ 0:00.00 (ksh)
12560 ff0401574280 ??  Is+ 0:00.01 (getty)
30357 ff04015744c0 ??  Is+ 0:00.01 (getty)
12471 ff0401574700 ??  Is+ 0:00.01 (getty)
 8797 ff0401574940 ??  Is+ 0:00.01 (getty)
21030 ff0401574b80 ??  Is+ 0:00.01 (getty)

[prdsrv0003.sto1.se]-[21:45:12]# vmstat -N /var/crash/bsd.0 -M 
/var/crash/bsd.0.core -m
Memory statistics by bucket size
Size   In Use   Free   Requests  HighWater  Couldfree
  16 3320264  223931280  0
  32 1226 54   4254 640  0
  64 2992 80   6582 320  0
 12823616   1056  65855 160292
 256  339 29   4879  80  0
 512  284 12930  40  0
1024  318  6     20 36
2048   51   1027   1618  10757
4096   36  2442   5  0
8192   17  8 47   5  2
   163844  0  6   5  0
   327686  0  9   5  0
   655363  0543   5  0
  1310723  0  3   5  0
  2621441  0  1   5  0
  5242882  0  2   5  0

Memory usage type by bucket size
Size  Type(s)
  16  devbuf, pcb, routetbl, UFS mount, dirhash, ACPI, ip_moptions, exec,
  VM swap, UVM amap, UVM aobj, USB, USB device, temp
  32  devbuf, pcb, routetbl, ifaddr, UFS mount, sem, dirhash, ACPI,
  in_multi, exec, UVM amap, USB, USB device, temp
  64  devbuf, routetbl, ifaddr, vnodes, UFS mount, dirhash, ACPI, proc,
  in_multi, ether_multi, VM swap, UVM amap, USB, NDP, temp
 128  devbuf, pcb, routetbl, ifaddr, sem, dirhash, ACPI, NFS srvsock,
  ip_moptions, in_multi, ttys, pfkey data, UVM amap, USB, USB device,
  temp
 256  devbuf, routetbl, ifaddr, ioctlops, iov, vnodes, UFS mount, shm,
  VM map, ACPI, exec, xform_data, UVM amap, USB, USB device, NDP, temp
 512  devbuf, ifaddr, ioctlops, iov, UFS mount, dirhash, ACPI, file desc,
  ttys, xform_data, newblk, UVM amap, USB device, temp
1024  devbuf, pcb, ioctlops, iov, mount, shm, ACPI, file desc, proc, ttys,
  exec, UVM amap, USB device, crypto data, temp
2048  devbuf, pcb, ioctlops, UFS mount, ACPI, VM swap, UVM amap, UVM aobj,
  temp
4096  devbuf, pcb, ifaddr, ioctlops, UFS mount, proc, UVM amap, USB,
  memdesc, temp
8192  devbuf, pcb, ttys, pagedep, UVM amap, USB, temp
   16384  devbuf, pcb, NFS daemon, MSDOSFS mount, temp
   32768  devbuf, pcb, UFS quota, UFS mount, ISOFS mount, inodedep
   65536  devbuf, pcb, temp
  131072  devbuf, pcb
  262144  devbuf
  524288  VM swap

Memory statistics by type   Type  Kern
  Type InUse MemUse HighUse  Limit Requests Limit Limit Size(s)
devbuf  1326   838K   3078K 78644K 61420 0  
16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536,131072,262144
   pcb   119   276K404K 78644K  1770 0  
16,32,128,1024,2048,4096,8192,16384,32768,65536,131072
  routetbl   23211K 12K 78644K  9990 0  16,32,64,128,256
ifaddr   11629K 29K

UEFI boot attempt on AM1 platform with logs (9/16 snapshot)

2015-09-17 Thread Brian Conway 
The NUC 2820 I was previously testing snapshots with has moved on to a
better place (and lacked any meaningful serial console support), but
here are some logs from an MSI AM1I motherboard, both the attempted
UEFI boot and the successful BIOS boot. It also appears to hang during
kernel load. Let me know if I can provide any more info.

Side note: Is com0 console not yet support by EFIBOOT? I got an error
along those lines when attempting 'set tty com0', I assume this is
already known.

Thanks.

UEFI-booted:

>> OpenBSD/amd64 EFIBOOT 3.29
boot> machine memory
Region 0: type 1 at 0x0 for 634KB
Region 1: type 2 at 0x9e800 for 6KB
Region 2: type 2 at 0xe for 128KB
Region 3: type 1 at 0x10 for 2577304KB
Region 4: type 2 at 0x9d5e6000 for 192KB
Region 5: type 1 at 0x9d616000 for 236KB
Region 6: type 4 at 0x9d651000 for 760KB
Region 7: type 2 at 0x9d70f000 for 13440KB
Region 8: type 1 at 0x9e42f000 for 4KB
Region 9: type 4 at 0x9e43 for 32KB
Region 10: type 1 at 0x9e438000 for 4328KB
Region 11: type 2 at 0x9e872000 for 7684KB
Region 12: type 1 at 0x9eff3000 for 52KB
Region 13: type 1 at 0x1 for 5226496KB
Region 14: type 2 at 0xfec0 for 8KB
Region 15: type 2 at 0xfec1 for 4KB
Region 16: type 2 at 0xfed0 for 4KB
Region 17: type 2 at 0xfed4 for 20KB
Region 18: type 2 at 0xfed8 for 64KB
Region 19: type 2 at 0xff00 for 16384KB
Low ram: 634KB  High ram: 2577304KB
Total free memory: 7809054KB
boot> machine disk
DiskBIOS#   TypeCylsHeads   SecsFlags   Checksum
hd0 0x80label   956 64  32  0x2 0xe4afa028
hd1 0x81label   1023255 63  0x0 0x0
boot>
cannot open hd0a:/etc/random.seed: No such file or directory
booting hd0a:/5.8/amd64/bsd.rd: 3271588|

BIOS-booted:

>> OpenBSD/amd64 BOOT 3.29
boot>
cannot open hd0a:/etc/random.seed: No such file or directory
booting hd0a:/5.8/amd64/bsd.rd: 3271588+1393616+2409472+0+569344
[72+363552+237211]=0x7ded88
entry point at 0x1000160 [7205c766, 3404, 24448b12, 2680a304]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2015 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 5.8-current (RAMDISK_CD) #1249: Wed Sep 16 21:19:28 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 7979794432 (7610MB)
avail mem = 7736233984 (7377MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebe50 (48 entries)
bios0: vendor American Megatrends Inc. version "V10.2" date 12/24/2014
bios0: MSI MS-7865
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT CRAT SSDT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) 5350 APU with Radeon(tm) R3, 2046.43 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,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,ITSC,BMI1
cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 5 pa 0xfec0, version 21, 24 pins
ioapic1 at mainbus0: apid 6 pa 0xfec01000, version 21, 32 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (GPP0)
acpiprt2 at acpi0: bus -1 (GPP3)
acpiprt3 at acpi0: bus 1 (BR11)
acpiprt4 at acpi0: bus -1 (GPP2)
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD AMD64 16h Host" rev 0x00
vga1 at pci0 dev 1 function 0 vendor "ATI", unknown product 0x9830 rev 0x00
vga1: aperture needed
wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
vendor "ATI", unknown product 0x9840 (class multimedia subclass
hdaudio, rev 0x00) at pci0 dev 1 function 1 not configured
pchb1 at pci0 dev 2 function 0 vendor "AMD", unknown product 0x1538 rev 0x00
ppb0 at pci0 dev 2 function 1 "AMD AMD64 16h PCIE" rev 0x00: msi
pci1 at ppb0 bus 1
em0 at pci1 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address
68:05:ca:24:f3:3e
xhci0 at pci0 dev 16 function 0 vendor "AMD", unknown product 0x7814
rev 0x01: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 "AMD xHCI root hub" rev 3.00/1.00 addr 1
ahci0 at pci0 dev 17 function 0 "AMD Hudson-2 SATA" rev 0x40: msi, AHCI 1.3
ahci0: port 0: 6.0Gb/s
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0:  SCSI3
0/direct fixed naa.50014ee058ae4af4
sd0: 953869MB, 512 bytes/sector, 1953525168 sectors
ohci0 at pci0 dev 18 function 0 "AMD Hudson-2 USB" rev 0x39: apic 5
int 18, version 1.0, legacy support

Re: Problems building BIND 9.10.3 on OpenBSD 5.7

2015-09-17 Thread Research 
Hi Raf and Stuart,


On Sep 17, 2015, at 3:36 AM, Stuart Henderson  wrote:

> 9.10.3 is a feature release, it's in -current ports but I don't intend to
> backport to -stable yet. The security fixes are in 9.10.2-P4 which is
> in -stable ports.

Ok.  I believe Raf was mentioning this as well, that the security fixes are in 
9.10.2-P4, which I currently have.  I misread the ISC release notes and thought 
there was a new patch included in 9.10.3.  I have 9.10.2-P4 successfully 
running and will stick with this until 9.10.3 is backported to stable.

> Our OPENSSL_VERSION_NUMBER #defines don't (and can't) directly map from
> libressl's api to openssl's. If you have a requirement to use 9.10.3 now
> then either run -current, backport my patches, or disable crypto support
> if you don't need it (untested but should work).

Ah, ok - that’s good to know.  Wasn’t entirely sure what the build error meant 
but this makes sense.

Raf, thanks for pointer regarding @ports - will remember that going forward.

Regards,

- Scott