Re: OpenBGPd and ARIN allocations smaller than /24

2015-09-11 Thread Denis Fondras 
On Fri, Sep 11, 2015 at 05:10:42PM +0200, Peter Hessler wrote:
> I just committed an example configuration line to the sample OpenBGPd
> filter set:
> 
> allow from any inet prefix 23.128.0.0/10 prefixlen 24 - 28
> 

With OpenBSD5.7 amd64, adding this filter results in :
# bgpd -dnv
...
/etc/bgpd.conf:103: "prefix" already specified

Removing the "inet" keyword allows the config to validate.

Denis

Re: Question - test lab

2015-09-11 Thread Miod Vallat 
> General hints for picking up an alpha:
[...]
> If you intend to be in the same room as the machine, pick a workstation
> model and not a server.

DS25 are supposed to be deskside workstations, but their noise level
fits in the `server' category.

Re: System clock hours behind, network hangs (amd64, -current)

2015-09-11 Thread Mark Patruck 
dmesg below is currently running, but it also didn't work with a 2 week
old snapshot from the local mirror. (system was freshly installed)

Note: the machine hasn't been used over the last two months, so i've
double checked battery, memory, psu.

OpenBSD 5.8-current (GENERIC.MP) #0: Mon Sep  7 15:54:34 CEST 2015
bu...@aquila.paccotec.de:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4277665792 (4079MB)
avail mem = 4144119808 (3952MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP APIC MCFG OEMB HPET EINJ BERT ERST HEST
acpi0: wakeup devices P0P1(S4) PS2K(S4) PS2M(S4) USB0(S4) USB1(S4) USB2(S4) 
USB5(S4) EUSB(S4) USB3(S4) USB4(S4) USB6(S4) USBE(S4) P0P4(S4) P0P5(S4) 
P0P6(S4) P0P7(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) Atom(TM) CPU D525 @ 1.80GHz, 1800.26 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 512KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu0: mwait min=64, max=64, C-substates=0.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1800.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,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 512KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 3 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 1, remapped to apid 3
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P0P1)
acpiprt2 at acpi0: bus 1 (P0P4)
acpiprt3 at acpi0: bus 2 (P0P8)
acpiprt4 at acpi0: bus 3 (P0P9)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Pineview DMI" rev 0x02
ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x02: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 4 "Intel 82801I PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address 
00:25:90:91:cd:d0
ppb2 at pci0 dev 28 function 5 "Intel 82801I PCIE" rev 0x02: msi
pci3 at ppb2 bus 3
em1 at pci3 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address 
00:25:90:91:cd:d1
uhci0 at pci0 dev 29 function 0 "Intel 82801I USB" rev 0x02: apic 3 int 23
uhci1 at pci0 dev 29 function 1 "Intel 82801I USB" rev 0x02: apic 3 int 19
ehci0 at pci0 dev 29 function 7 "Intel 82801I USB" rev 0x02: apic 3 int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x92
pci4 at ppb3 bus 4
vga1 at pci4 dev 4 function 0 "Matrox MGA G200eW" rev 0x0a
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 31 function 0 "Intel 82801IR LPC" rev 0x02
ahci0 at pci0 dev 31 function 2 "Intel 82801I AHCI" rev 0x02: msi, AHCI 1.2
ahci0: port 0: 3.0Gb/s
ahci0: port 1: 3.0Gb/s
ahci0: port 2: 3.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct fixed 
naa.50025388a03f4c8d
sd0: 114473MB, 512 bytes/sector, 234441648 sectors, thin
sd1 at scsibus1 targ 1 lun 0:  SCSI3 0/direct 
fixed naa.50014ee2b6f03098
sd1: 5723166MB, 512 bytes/sector, 11721045168 sectors
sd2 at scsibus1 targ 2 lun 0:  SCSI3 0/direct 
fixed naa.50014ee2619a15e0
sd2: 3815447MB, 512 bytes/sector, 7814037168 sectors
ichiic0 at pci0 dev 31 function 3 "Intel 82801I SMBus" rev 0x02: apic 3 int 18
iic0 at ichiic0
lm1 at iic0 addr 0x2d: W83627DHG
spdmem0 at iic0 addr 0x50: 2GB DDR3 SDRAM PC3-10600 SO-DIMM
spdmem1 at iic0 addr 0x51: 2GB DDR3 SDRAM PC3-10600 SO-DIMM
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
wbsio0 at isa0 port 0x2e/2: W83627DHG rev 0x25
lm2 at wbsio0 port 0xca0/8: W83627DHG
lm1: disabling sensors due to alias with lm2
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (c289c6d345948119.a) swap on sd0b dump on sd0b



On Fri, Sep 11, 2015

Re: System clock hours behind, network hangs (amd64, -current)

2015-09-11 Thread Mark Patruck 
On Fri, Sep 11, 2015 at 06:27:36PM +0200, Martin Pieuchot wrote:
> On 11/09/15(Fri) 18:07, Mark Patruck wrote:
> > dmesg below is currently running, but it also didn't work with a 2 week
> > old snapshot from the local mirror. (system was freshly installed)
> > 
> > Note: the machine hasn't been used over the last two months, so i've
> > double checked battery, memory, psu.
> > 
> > OpenBSD 5.8-current (GENERIC.MP) #0: Mon Sep  7 15:54:34 CEST 2015
> > bu...@aquila.paccotec.de:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
> Since you build your kernel yourself, I can't tell when you did your
> checkout and I'll bet you hit the window when rtisvalid(9) was in.
> 
> Could you try a -current checkout with this diff an tell me if you can
> reproduce the problem?

Thanks Martin. I'll report back asap.

> Could you also tell me what are your nfs mounts? 

$ cat /etc/exports
/share/d0 -alldirs -mapall=umedia:media -ro mso
/share/d1 -alldirs -mapall=umedia:media -ro mso

$ mount | grep NFS
/dev/sd1a on /share/d0 type ffs (NFS exported, local, nodev, noexec, 
nosuid, softdep)
/dev/sd2a on /share/d1 type ffs (NFS exported, local, nodev, noexec, 
nosuid, softdep)


-- 
Mark Patruck ( mark at wrapped.cx )
GPG key 0xF2865E51 / 187F F6D3 EE04 1DCE 1C74  F644 0D3C F66F F286 5E51

http://www.wrapped.cx

Re: System clock hours behind, network hangs (amd64, -current)

2015-09-11 Thread Martin Pieuchot 
On 11/09/15(Fri) 18:07, Mark Patruck wrote:
> dmesg below is currently running, but it also didn't work with a 2 week
> old snapshot from the local mirror. (system was freshly installed)
> 
> Note: the machine hasn't been used over the last two months, so i've
> double checked battery, memory, psu.
> 
> OpenBSD 5.8-current (GENERIC.MP) #0: Mon Sep  7 15:54:34 CEST 2015
> bu...@aquila.paccotec.de:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Since you build your kernel yourself, I can't tell when you did your
checkout and I'll bet you hit the window when rtisvalid(9) was in.

Could you try a -current checkout with this diff an tell me if you can
reproduce the problem?

Could you also tell me what are your nfs mounts? 

Index: netinet/ip_output.c
===
RCS file: /cvs/src/sys/netinet/ip_output.c,v
retrieving revision 1.291
diff -u -p -r1.291 ip_output.c
--- netinet/ip_output.c 3 Sep 2015 14:59:23 -   1.291
+++ netinet/ip_output.c 11 Sep 2015 16:25:11 -
@@ -168,12 +168,13 @@ ip_output(struct mbuf *m0, struct mbuf *
dst = satosin(>ro_dst);
 
/*
-* If there is a cached route, check that it is to the same
-* destination and is still up.  If not, free it and try again.
+* If there is a cached route, check that it is to the
+* same destination and is still valid.  If not, free
+* it and try again.
 */
-   if (ro->ro_rt && ((ro->ro_rt->rt_flags & RTF_UP) == 0 ||
+   if (!rtisvalid(ro->ro_rt) ||
dst->sin_addr.s_addr != ip->ip_dst.s_addr ||
-   ro->ro_tableid != m->m_pkthdr.ph_rtableid)) {
+   ro->ro_tableid != m->m_pkthdr.ph_rtableid) {
rtfree(ro->ro_rt);
ro->ro_rt = NULL;
}
@@ -195,7 +196,9 @@ ip_output(struct mbuf *m0, struct mbuf *
ro->ro_rt = rtalloc_mpath(>ro_dst,
NULL, ro->ro_tableid);
 
-   if (ro->ro_rt == NULL) {
+   if (!rtisvalid(ro->ro_rt)) {
+   rtfree(ro->ro_rt);
+   ro->ro_rt = NULL;
ipstat.ips_noroute++;
error = EHOSTUNREACH;
goto bad;
@@ -296,12 +299,13 @@ reroute:
dst = satosin(>ro_dst);
 
/*
-* If there is a cached route, check that it is to the same
-* destination and is still up.  If not, free it and try again.
+* If there is a cached route, check that it is to the
+* same destination and is still valid.  If not, free
+* it and try again.
 */
-   if (ro->ro_rt && ((ro->ro_rt->rt_flags & RTF_UP) == 0 ||
+   if (!rtisvalid(ro->ro_rt) ||
dst->sin_addr.s_addr != ip->ip_dst.s_addr ||
-   ro->ro_tableid != m->m_pkthdr.ph_rtableid)) {
+   ro->ro_tableid != m->m_pkthdr.ph_rtableid) {
rtfree(ro->ro_rt);
ro->ro_rt = NULL;
}
@@ -323,7 +327,9 @@ reroute:
ro->ro_rt = rtalloc_mpath(>ro_dst,
>ip_src.s_addr, ro->ro_tableid);
 
-   if (ro->ro_rt == NULL) {
+   if (!rtisvalid(ro->ro_rt)) {
+   rtfree(ro->ro_rt);
+   ro->ro_rt = NULL;
ipstat.ips_noroute++;
error = EHOSTUNREACH;
goto bad;

azalia audio works, then stutters until reboot

2015-09-11 Thread luke350 
Short version: In OpenBSD 5.7 (with all the latest security
patches), after some video playing, it
starts to stutter, and doesn't recover until I reboot. Is there
a way to "reset all the audio" back so it works, short of rebooting?
I haven't found that in anything I've read so far, including from
faq 13 and manpages for audioctl and mixerctl etc.

The details:
After playing a video in chromium at youtube.com for a while, or
an .ogv file in smplayer, the video starts to replay the same ~.3 sec. of
audio repeatedly, and the video stops moving forward.  If I stop the
video, then sometimes after several hours it stops, but the last one
didn't stop stuttering even though I let it sit overnight. This then
affects all audio, I've tried, even trying to play a beep.  Turning mute
on/off using the laptop keyboard or jumping around in the video
stream (backing up to replay part, for example) seems to usually be
when the problem starts.

While it is stuttering, running 'audioctl -f /dev/audio0' or
trying a .mid file gets output like this:
$timidity aislean.mid
sio_open() failed
Couldn't open sndio mode (`s')

...but after enough time goes by the screen (but not sound) output
from those commands is normal again.  They work fully before
the audio stuttering starts.

The related lines from lspci seem to be:
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1308
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller (*rev 01)

The problems seem similar to those described in this thread:
http://marc.info/?l=openbsd-misc=134463946801823=2
...but a similar (though naive) change to azalia.c didn't fix
things for me (basically, instead of adding another case option,
I added a "default:" line just after the ones with various ...SERIES
constants suggested in the thread; don't laugh too hard: it was
just an attempt anyway...  :).

I haven't tried all the suggestions here in this thread:
http://marc.info/?l=openbsd-misc=143160717501387=2
...partly because I didn't see "-mplay" as an option in the manpage
for sndiod, but maybe I missed it or should just try that anyway. If
I should also try the debug etc suggestions there for this
case, let me know.

I did look for audio-related options in the BIOS but there was only one
whose name I forget but which is enabled (or "UNLOCK"ed).

The only other things other than from the above-linked
thread that I've thought of to try are:
- upgrading to CURRENT to see if it's any different
- debugging (I'd have to learn a lot, best with some guidance)
- discuss & learn more here...

/var/run/dmesg.boot follows (as the last thing in this msg). (Ps: i don't
expect that wifi will work on this laptop hardware--input welcome on
that though I realize it's a separate question: I'm curious only if you
notice something, but not focused on it now).

Thanks!

OpenBSD 5.7-stable (GENERIC.MP) #3: Tue Aug 18 16:23:25 MDT 2015
 r...@asusbsd.home:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 7443599360 (7098MB)
avail mem = 7241527296 (6906MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebf90 (49 entries)
bios0: vendor American Megatrends Inc. version "204" date 11/20/2014
bios0: ASUSTeK COMPUTER INC. X550ZA
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT ECDT MCFG MSDM HPET UEFI SSDT SSDT CRAT SSDT 
SSDT SSDT SSDT
acpi0: wakeup devices LOM_(S4) SBAZ(S4) ECIR(S4) OHC1(S4) EHC1(S4) OHC2(S4) 
EHC2(S4) OHC3(S4) EHC3(S4) OHC4(S4) XHC0(S4) XHC1(S4) ODD8(S3) GLAN(S4) 
LID_(S5) SLPB(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 A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.65 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,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,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: 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, C-substates=0.0.0.0.0, IBE
cpu1 at mainbus0: apid 17 (application processor)
cpu1: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.34 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,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,ITSC,FSGSBASE,BMI1
cpu1: 96KB

kernel compile error

2015-09-11 Thread Hrvoje Popovski 
cvs update from half an hour ago ...

log:

cc  -Werror -Wall -Wimplicit-function-declaration  -Wno-main
-Wno-uninitialized  -Wframe-larger-than=2047 -mcmodel=kernel
-mno-red-zone -mno-sse2 -mno-sse -mno-3dnow  -mno-mmx -msoft-float
-fno-omit-frame-pointer -fno-builtin-printf -fno-builtin-snprintf
-fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
-fno-builtin-malloc -fno-pie -O2 -pipe -nostdinc -I../../../.. -I.
-I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS
-DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
-DUVM_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA
-DEXT2FS -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO
-DTMPFS -DFUSE -DSOCKET_SPLICE -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE
-DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DPIPEX -DMROUTING -DMPLS
-DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DMTRR -DNTFS -DHIBERNATE
-DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL
-DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
-DWSDISPLAY_COMPAT_PCVT -DX86EMU -DONEWIREVERBOSE -DMULTIPROCESSOR
-DMAXUSERS=80 -D_KERNEL -MD -MP  -c ../../../../dev/ic/aic7xxx.c
cc1: warnings being treated as errors
ioconf.c:861: warning: initialization from incompatible pointer type
ioconf.c:863: warning: initialization from incompatible pointer type
ioconf.c:865: warning: initialization from incompatible pointer type
ioconf.c:867: warning: initialization from incompatible pointer type
ioconf.c:869: warning: initialization from incompatible pointer type
ioconf.c:871: warning: initialization from incompatible pointer type
ioconf.c:873: warning: initialization from incompatible pointer type
ioconf.c:875: warning: initialization from incompatible pointer type
ioconf.c:877: warning: initialization from incompatible pointer type
ioconf.c:879: warning: initialization from incompatible pointer type
ioconf.c:881: warning: initialization from incompatible pointer type
ioconf.c:883: warning: initialization from incompatible pointer type
ioconf.c:885: warning: initialization from incompatible pointer type
ioconf.c:887: warning: initialization from incompatible pointer type
ioconf.c:889: warning: initialization from incompatible pointer type
ioconf.c:891: warning: initialization from incompatible pointer type
ioconf.c:893: warning: initialization from incompatible pointer type
ioconf.c:895: warning: initialization from incompatible pointer type
ioconf.c:897: warning: initialization from incompatible pointer type
ioconf.c:899: warning: initialization from incompatible pointer type
ioconf.c:901: warning: initialization from incompatible pointer type
ioconf.c:903: warning: initialization from incompatible pointer type
ioconf.c:905: warning: initialization from incompatible pointer type
ioconf.c:907: warning: initialization from incompatible pointer type
ioconf.c:909: warning: initialization from incompatible pointer type
ioconf.c:911: warning: initialization from incompatible pointer type
ioconf.c:913: warning: initialization from incompatible pointer type
ioconf.c:915: warning: initialization from incompatible pointer type
ioconf.c:917: warning: initialization from incompatible pointer type
ioconf.c:919: warning: initialization from incompatible pointer type
ioconf.c:921: warning: initialization from incompatible pointer type
ioconf.c:923: warning: initialization from incompatible pointer type
ioconf.c:925: warning: initialization from incompatible pointer type
ioconf.c:927: warning: initialization from incompatible pointer type
ioconf.c:929: warning: initialization from incompatible pointer type
ioconf.c:931: warning: initialization from incompatible pointer type
ioconf.c:933: warning: initialization from incompatible pointer type
ioconf.c:935: warning: initialization from incompatible pointer type
ioconf.c:937: warning: initialization from incompatible pointer type
ioconf.c:939: warning: initialization from incompatible pointer type
ioconf.c:941: warning: initialization from incompatible pointer type
ioconf.c:943: warning: initialization from incompatible pointer type
ioconf.c:945: warning: initialization from incompatible pointer type
ioconf.c:947: warning: initialization from incompatible pointer type
ioconf.c:949: warning: initialization from incompatible pointer type
ioconf.c:951: warning: initialization from incompatible pointer type
ioconf.c:953: warning: initialization from incompatible pointer type
ioconf.c:955: warning: initialization from incompatible pointer type
ioconf.c:957: warning: initialization from incompatible pointer type
ioconf.c:959: warning: initialization from incompatible pointer type
ioconf.c:961: warning: initialization from incompatible pointer type
ioconf.c:963: warning: initialization from incompatible pointer type
ioconf.c:965: warning: initialization from incompatible pointer type
ioconf.c:967: warning: initialization from incompatible pointer type
ioconf.c:969: warning: initialization from incompatible pointer type
ioconf.c:971: warning:

mysterious ulimit values

2015-09-11 Thread luke350 

Short version: I can't tell where ulimit of "data seg size" and "virtual
memory" for a console login is getting set: I don't see the in any
startup file or login.conf, and the values I do see for an ssh connection
while under X are larger than what is in login.conf, so I'm confused.

Details: Usernames on my system who aren't in the "staff" login class
can't run "java -version" from a console login (ie not in X), and
after some digging I realized it's probably because they have these
ulimit values:

data seg size (kbytes, -d) 131072
virtual memory (kbytes, -v) 133120

But those values are not found in /etc/profile, nor in those users' 
~/.profile

nor ~/.bashrc, nor does /etc/login.conf mention those ulimit values. Here's
the default section; the rest of it is as found in a stock openbsd 5.7 
install:

  default:\
  :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin 
/usr/local/bin /usr/l ocal/sbin:\

  :umask=022:\
  #(next2 lines changed for chrome, IIRC):
  #:datasize-max=512M:\
  #:datasize-cur=512M:\
  :datasize-max=2048M:\
  :datasize-cur=2048M:\
  :maxproc-max=256:\
  :maxproc-cur=128:\
  :openfiles-cur=512:\
  :stacksize-cur=4M:\
  :localcipher=blowfish,8:\
  :ypcipher=old:\
  :tc=auth-defaults:\
  :tc=auth-ftp-defaults:

There doesn't seem to be a problem, as those users show much larger
values, if I first login to the console as root, then 'su - ' to 
the users

with the problem. It also has much larger values when I ssh from one
user to another in an xterm window and test there.  These values are
larger than anything I see in login.conf, even for the 'staff' class: like,
33562624k ie 33G: I don't know where that is coming from either
as I didn't see it as defaults showing in 'man login.conf'.  Oh wait, that
is roughly my ram+swap size, so maybe it uses that as a default instead
of what's in login.conf, in some situations?

Where else could these ulimit values for datasize and virtual memory
of ~133120k be coming from, and how would I change them, for
a user who is only logged in to a console (not X)?  Or, is there a problem
with my use of login.conf, since at one point it seemed to matter for
opening many browser tabs in chrome, but now the value for that
user in X is so far beyond what is set there. As you see I'm confused, and
have probably done something somewhere that I've forgotten or has
escaped me.

Thanks again,

-Luke A Call
(ps: I'm not trying to be stuffy with the initial, just found it's more
unique; there's at least one other luke call, probably more)

Re: ftp.html

2015-09-11 Thread Stuart Henderson 
On 2015-09-11, Rob Pierce  wrote:
> Agreed about the word order. How about this?
> 
> Index: ftp.html
>===
> RCS file: /cvs/www/ftp.html,v
> retrieving revision 1.673
> diff -u -p -r1.673 ftp.html
> --- ftp.html  25 Jul 2015 19:24:18 -  1.673
> +++ ftp.html  11 Sep 2015 12:30:18 -
> @@ -61,7 +61,7 @@ upgrade your system very quickly.
> Download via
>HTTP/FTP
>  
> -OpenBSD can be also easily installed via HTTP or FTP.
> +OpenBSD can also be easily obtained via HTTP or FTP.
>  Typically you need a single small piece of boot media (e.g., a boot floppy)
>  and then the rest of the files can be installed from a number of locations,
>  including directly off the Internet.
>
>

I would just drop the word 'easily' here.

Also, see the line at the top of the file, you are patching the wrong file.

Re: ftp.html

2015-09-11 Thread Jérémie Courrèges-Anglas 
Stuart Henderson  writes:

> On 2015-09-11, Rob Pierce  wrote:
>> Agreed about the word order. How about this?
>> 
>> Index: ftp.html
>>===
>> RCS file: /cvs/www/ftp.html,v
>> retrieving revision 1.673
>> diff -u -p -r1.673 ftp.html
>> --- ftp.html 25 Jul 2015 19:24:18 -  1.673
>> +++ ftp.html 11 Sep 2015 12:30:18 -
>> @@ -61,7 +61,7 @@ upgrade your system very quickly.
>> Download via
>>HTTP/FTP
>>  
>> -OpenBSD can be also easily installed via HTTP or FTP.
>> +OpenBSD can also be easily obtained via HTTP or FTP.
>>  Typically you need a single small piece of boot media (e.g., a boot floppy)

Boot floppy, really? :)

>>  and then the rest of the files can be installed from a number of locations,
>>  including directly off the Internet.
>>
>>
>
> I would just drop the word 'easily' here.

+1

> Also, see the line at the top of the file, you are patching the wrong file.
>


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

Re: ftp.html

2015-09-11 Thread Rob Pierce 
Thanks Stuart - I totally missed that! I will also correct my anoncvs.html diff 
and resend against the correct file(s). Appreciate the response.

How about this?

Index: ftp.html.head
===
RCS file: /cvs/www/build/mirrors/ftp.html.head,v
retrieving revision 1.21
diff -u -p -r1.21 ftp.html.head
--- ftp.html.head   25 Jul 2015 19:16:47 -  1.21
+++ ftp.html.head   11 Sep 2015 21:09:36 -
@@ -61,7 +61,7 @@ upgrade your system very quickly.
 Download via
   HTTP/FTP
 
-OpenBSD can be also easily installed via HTTP or FTP.
+OpenBSD can also be obtained via HTTP or FTP.
 Typically you need a single small piece of boot media (e.g., a boot floppy)
 and then the rest of the files can be installed from a number of locations,
 including directly off the Internet.

Re: anoncvs.html.head

2015-09-11 Thread Rob Pierce 
See attached.

- Original Message -
From: "Rob Pierce" 
To: "misc" 
Sent: Friday, September 11, 2015 6:30:33 PM
Subject: anoncvs.html.head

This diff is a resend against the correct file:

 - some punctuation, line spacing and minor grammar fixes
 - "file sets" has a special meaning, so don't refer to src.tar.gz, 
xenocara.tar.gc,ports.tar.gz as "file sets"
 - cvs(1) hrefs
 - "diffs" is already used earlier on the page, so don't quote it

Rob
Index: anoncvs.html.head
===
RCS file: /cvs/www/build/mirrors/anoncvs.html.head,v
retrieving revision 1.42
diff -u -p -r1.42 anoncvs.html.head
--- anoncvs.html.head   2 Sep 2015 13:11:30 -   1.42
+++ anoncvs.html.head   11 Sep 2015 22:10:15 -
@@ -39,7 +39,7 @@ source repositories:
 
   src - Houses all source code for the OpenBSD Operating System.
   ports - Houses the OpenBSD 
Ports.
-  www - Houses all OpenBSD web pages. (Including this one).
+  www - Houses all OpenBSD web pages (including this one).
   xenocara - Houses OpenBSD's active X.org v7 source tree.
   X11 and XF4 - Houses OpenBSD's adaptation of the
   http://www.XFree86.org/;>XFree86-3 and XFree86-4
@@ -122,7 +122,7 @@ with only one part of the tree.  The two
 which contains the files used to create the kernel, and src.tar.gz
 which contains all the other "userland" utilities.
 In general, however, you will usually want both of them installed.
-Assuming the downloaded files, src.tar.gz,
+Assuming the downloaded files src.tar.gz,
 sys.tar.gz and xenocara.tar.gz are in /usr:
 
 
@@ -135,11 +135,13 @@ Assuming the downloaded files, src.t
 
 
 
-Not all people will wish to unpack all the file sets, but as the system
+Not all people will wish to unpack all the source file, but as the system
 must be kept in sync, you will generally need to set up all trees.
 
 
-You can also just use cvs(1) to "checkout" the source repository
+You can also just use
+http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1)
+to "checkout" the source repository
 for you. This is discussed in the next section.
 
 
@@ -160,16 +162,12 @@ from the erratahere.
 
-Once you have decided which tree to follow, you must choose which Anonymous
-CVS server you are going to use.  A list of these servers is
-below.
-
 
-Once you have chosen which Anonymous CVS Server you will
-use, you can start using cvs. For those of you
+Once you have decided which tree to follow, and which Anonymous CVS Server you will
+use, you can start using http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1).
 For those of you
 who have CDs you can start with the CVS checkout that is on the CD by using
 the method above to get the sources onto your system.
-If you don't have a CD handy, use the method below to checkout the sources.
+If you don't have a CD handy, use the method below to checkout the sources:
 
 
 First, start out by `get'-ing an initial tree:
@@ -210,9 +208,11 @@ Confirm this, and the fingerprint will t
...
 
 
+
 Note that the above format with SHA256 fingerprints was added after the
 release of OpenBSD 5.6; older versions only use MD5 fingerprints.
 
+
  Anytime afterwards, to `update' this tree:
  (If you are following current):
 
@@ -234,7 +234,7 @@ to merge changes in.
  NOTE:
 If you are updating a source tree that you initially fetched
 from a different server, or from a CD, you must
-add the -d [cvsroot] option to cvs.
+add the -d [cvsroot] option to cvs:
 
# cd /usr/src
# cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd
@@ -295,11 +295,11 @@ directory, and a subsequent update will 
 
 
 The anoncvs service gives fledgling developers a chance to learn CVS
-operation and get thoroughly involved in the development process
+operations and get thoroughly involved in the development process
 before getting "commit" access -- as a result of showing useful
 skills and high quality results they will naturally later be given
 developer access.
-As well, people providing patches can create their "diff"s relative
+As well, people providing patches can create their diffs relative
 to the CVS tree, which will ease integration.
 
 Example usages for cvs(1)

Re: ftp.html

2015-09-11 Thread Stuart Henderson 
On 2015/09/11 22:05, Jérémie Courrèges-Anglas wrote:
> Stuart Henderson  writes:
> 
> > On 2015-09-11, Rob Pierce  wrote:
> >> Agreed about the word order. How about this?
> >> 
> >> Index: ftp.html
> >>===
> >> RCS file: /cvs/www/ftp.html,v
> >> retrieving revision 1.673
> >> diff -u -p -r1.673 ftp.html
> >> --- ftp.html   25 Jul 2015 19:24:18 -  1.673
> >> +++ ftp.html   11 Sep 2015 12:30:18 -
> >> @@ -61,7 +61,7 @@ upgrade your system very quickly.
> >> Download via
> >>HTTP/FTP
> >>  
> >> -OpenBSD can be also easily installed via HTTP or FTP.
> >> +OpenBSD can also be easily obtained via HTTP or FTP.
> >>  Typically you need a single small piece of boot media (e.g., a boot 
> >> floppy)
> 
> Boot floppy, really? :)

Oh yeah :-) "USB stick" would be good here.

anoncvs.html.head

2015-09-11 Thread Rob Pierce 
This diff is a resend against the correct file:

 - some punctuation, line spacing and minor grammar fixes
 - "file sets" has a special meaning, so don't refer to src.tar.gz, 
xenocara.tar.gc,ports.tar.gz as "file sets"
 - cvs(1) hrefs
 - "diffs" is already used earlier on the page, so don't quote it

Rob


Index: anoncvs.html.head
===
RCS file: /cvs/www/build/mirrors/anoncvs.html.head,v
retrieving revision 1.42
diff -u -p -r1.42 anoncvs.html.head
--- anoncvs.html.head   2 Sep 2015 13:11:30 -   1.42
+++ anoncvs.html.head   11 Sep 2015 22:10:15 -
@@ -39,7 +39,7 @@ source repositories:
 
   src - Houses all source code for the OpenBSD Operating System.
   ports - Houses the OpenBSD 
Ports.
-  www - Houses all OpenBSD web pages. (Including this one).
+  www - Houses all OpenBSD web pages (including this one).
   xenocara - Houses OpenBSD's active X.org v7 source tree.
   X11 and XF4 - Houses OpenBSD's adaptation of the
   http://www.XFree86.org/;>XFree86-3 and XFree86-4
@@ -122,7 +122,7 @@ with only one part of the tree.  The two
 which contains the files used to create the kernel, and src.tar.gz
 which contains all the other "userland" utilities.
 In general, however, you will usually want both of them installed.
-Assuming the downloaded files, src.tar.gz,
+Assuming the downloaded files src.tar.gz,
 sys.tar.gz and xenocara.tar.gz are in /usr:
 
 
@@ -135,11 +135,13 @@ Assuming the downloaded files, src.t
 
 
 
-Not all people will wish to unpack all the file sets, but as the system
+Not all people will wish to unpack all the source file, but as the system
 must be kept in sync, you will generally need to set up all trees.
 
 
-You can also just use cvs(1) to "checkout" the source repository
+You can also just use
+http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1)
+to "checkout" the source repository
 for you. This is discussed in the next section.
 
 
@@ -160,16 +162,12 @@ from the erratahere.
 
-Once you have decided which tree to follow, you must choose which Anonymous
-CVS server you are going to use.  A list of these servers is
-below.
-
 
-Once you have chosen which Anonymous CVS Server you will
-use, you can start using cvs. For those of you
+Once you have decided which tree to follow, and which Anonymous CVS Server you will
+use, you can start using http://www.openbsd.org/cgi-bin/man.cgi?query=cvssektion=1format=html;>cvs(1).
 For those of you
 who have CDs you can start with the CVS checkout that is on the CD by using
 the method above to get the sources onto your system.
-If you don't have a CD handy, use the method below to checkout the sources.
+If you don't have a CD handy, use the method below to checkout the sources:
 
 
 First, start out by `get'-ing an initial tree:
@@ -210,9 +208,11 @@ Confirm this, and the fingerprint will t
...
 
 
+
 Note that the above format with SHA256 fingerprints was added after the
 release of OpenBSD 5.6; older versions only use MD5 fingerprints.
 
+
  Anytime afterwards, to `update' this tree:
  (If you are following current):
 
@@ -234,7 +234,7 @@ to merge changes in.
  NOTE:
 If you are updating a source tree that you initially fetched
 from a different server, or from a CD, you must
-add the -d [cvsroot] option to cvs.
+add the -d [cvsroot] option to cvs:
 
# cd /usr/src
# cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd
@@ -295,11 +295,11 @@ directory, and a subsequent update will 
 
 
 The anoncvs service gives fledgling developers a chance to learn CVS
-operation and get thoroughly involved in the development process
+operations and get thoroughly involved in the development process
 before getting "commit" access -- as a result of showing useful
 skills and high quality results they will naturally later be given
 developer access.
-As well, people providing patches can create their "diff"s relative
+As well, people providing patches can create their diffs relative
 to the CVS tree, which will ease integration.
 
 Example usages for cvs(1)

[demime 1.01d removed an attachment of type text/x-patch which had a name of 
cvs.diff.anoncvs.html.head]

Re: mysterious ulimit values

2015-09-11 Thread Chris Cappuccio 
luke...@onemodel.org [luke...@onemodel.org] wrote:
>   default:\
>   :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin
> /usr/l ocal/sbin:\
>   :umask=022:\
>   #(next2 lines changed for chrome, IIRC):
>   #:datasize-max=512M:\
>   #:datasize-cur=512M:\
>   :datasize-max=2048M:\
>   :datasize-cur=2048M:\
>   :maxproc-max=256:\
>   :maxproc-cur=128:\
>   :openfiles-cur=512:\
>   :stacksize-cur=4M:\
>   :localcipher=blowfish,8:\
>   :ypcipher=old:\
>   :tc=auth-defaults:\
>   :tc=auth-ftp-defaults:

You fucked the pooch when you put pound signs in there. Just delete
those lines, or uncomment them and use appropriate values. Remove the
commented line with no values entirely. The commented lines prevent
the rest of default: class from being read.

Question about quotation rules

2015-09-11 Thread Rob Pierce 
Good evening,

Is there a written/unwritten rule for using quotation marks? Do man pages and 
web pages follow the same rules?

When would I use 'this', "this", `this', ``this'', “this“, etc.?

I guess this can be both a source problem as well as a display problem.

Any suggestions regarding reasonable expectations for web page/man page 
consistency?

U+0022  QUOTATION MARK  "
U+0027  APOSTROPHE  '
U+0060  GRAVE ACCENT`
U+00B4  ACUTE ACCENT´ 
U+2018  LEFT SINGLE QUOTATION MARK  ‘
U+2019  RIGHT SINGLE QUOTATION MARK ’
U+201C  LEFT DOUBLE QUOTATION MARK  “
U+201D  RIGHT DOUBLE QUOTATION MARK ”

Many thanks.

Rob

Re: kernel compile error

2015-09-11 Thread Philip Guenther 
On Fri, Sep 11, 2015 at 12:01 PM, Hrvoje Popovski  wrote:
> cvs update from half an hour ago ...
>
> log:
...
> cc1: warnings being treated as errors
> ioconf.c:861: warning: initialization from incompatible pointer type

Update in /usr/src/usr.bin/config, build and install there, then
re-config your kernel config.


Philip Guenther

Re: ftp.html

2015-09-11 Thread Rob Pierce 
Agreed about the word order. How about this?

Index: ftp.html
===
RCS file: /cvs/www/ftp.html,v
retrieving revision 1.673
diff -u -p -r1.673 ftp.html
--- ftp.html25 Jul 2015 19:24:18 -  1.673
+++ ftp.html11 Sep 2015 12:30:18 -
@@ -61,7 +61,7 @@ upgrade your system very quickly.
 Download via
   HTTP/FTP
 
-OpenBSD can be also easily installed via HTTP or FTP.
+OpenBSD can also be easily obtained via HTTP or FTP.
 Typically you need a single small piece of boot media (e.g., a boot floppy)
 and then the rest of the files can be installed from a number of locations,
 including directly off the Internet.

Re: Question about quotation rules

2015-09-11 Thread Anthony J. Bentley 
Hi Rob,

Rob Pierce writes:
> Good evening,
> 
> Is there a written/unwritten rule for using quotation marks? Do man pages and
>  web pages follow the same rules?
> 
> When would I use 'this', "this", `this', ``this'', “this“, etc.?

Generally:

In manuals, use .Dq and .Sq for double and single quotes.

In www, use " and '.


There are some other macros in mdoc(7) that generate quote marks (.Qq
and friends), when you specifically need straight quotes (e.g., code
listings) and can't just type " directly (e.g., on a macro line).

For personal webpages I use UTF-8 quotes (U+2019/A, U+201C/D) directly.
But for pages with many authors, like www.openbsd.org, it's best to go
with what's simple and works: " and '. Keep the burden on authors light.
The text is what's important.

`` '' is an artifact. The only place they look balanced is on the console
and in troff's PDF output. Everywhere else (such as the xterm and firefox
defaults) has displayed this unbalanced for years. " looks better and is
easier to type.

-- 
Anthony J. Bentley

Re: kernel compile error

2015-09-11 Thread Paul de Weerd 
Did you update config(8) before building?

http://www.openbsd.org/faq/current.html#20150911

Cheers,

Paul 'WEiRD' de Weerd

On Fri, Sep 11, 2015 at 12:01:31PM +0200, Hrvoje Popovski wrote:
| cvs update from half an hour ago ...
| 
| log:
| 
| cc  -Werror -Wall -Wimplicit-function-declaration  -Wno-main
| -Wno-uninitialized  -Wframe-larger-than=2047 -mcmodel=kernel
| -mno-red-zone -mno-sse2 -mno-sse -mno-3dnow  -mno-mmx -msoft-float
| -fno-omit-frame-pointer -fno-builtin-printf -fno-builtin-snprintf
| -fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
| -fno-builtin-malloc -fno-pie -O2 -pipe -nostdinc -I../../../.. -I.
| -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS
| -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
| -DUVM_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA
| -DEXT2FS -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO
| -DTMPFS -DFUSE -DSOCKET_SPLICE -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE
| -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DPIPEX -DMROUTING -DMPLS
| -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DMTRR -DNTFS -DHIBERNATE
| -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL
| -DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
| -DWSDISPLAY_COMPAT_PCVT -DX86EMU -DONEWIREVERBOSE -DMULTIPROCESSOR
| -DMAXUSERS=80 -D_KERNEL -MD -MP  -c ../../../../dev/ic/aic7xxx.c
| cc1: warnings being treated as errors
| ioconf.c:861: warning: initialization from incompatible pointer type
| ioconf.c:863: warning: initialization from incompatible pointer type
| ioconf.c:865: warning: initialization from incompatible pointer type
| ioconf.c:867: warning: initialization from incompatible pointer type
| ioconf.c:869: warning: initialization from incompatible pointer type
| ioconf.c:871: warning: initialization from incompatible pointer type
| ioconf.c:873: warning: initialization from incompatible pointer type
| ioconf.c:875: warning: initialization from incompatible pointer type
| ioconf.c:877: warning: initialization from incompatible pointer type
| ioconf.c:879: warning: initialization from incompatible pointer type
| ioconf.c:881: warning: initialization from incompatible pointer type
| ioconf.c:883: warning: initialization from incompatible pointer type
| ioconf.c:885: warning: initialization from incompatible pointer type
| ioconf.c:887: warning: initialization from incompatible pointer type
| ioconf.c:889: warning: initialization from incompatible pointer type
| ioconf.c:891: warning: initialization from incompatible pointer type
| ioconf.c:893: warning: initialization from incompatible pointer type
| ioconf.c:895: warning: initialization from incompatible pointer type
| ioconf.c:897: warning: initialization from incompatible pointer type
| ioconf.c:899: warning: initialization from incompatible pointer type
| ioconf.c:901: warning: initialization from incompatible pointer type
| ioconf.c:903: warning: initialization from incompatible pointer type
| ioconf.c:905: warning: initialization from incompatible pointer type
| ioconf.c:907: warning: initialization from incompatible pointer type
| ioconf.c:909: warning: initialization from incompatible pointer type
| ioconf.c:911: warning: initialization from incompatible pointer type
| ioconf.c:913: warning: initialization from incompatible pointer type
| ioconf.c:915: warning: initialization from incompatible pointer type
| ioconf.c:917: warning: initialization from incompatible pointer type
| ioconf.c:919: warning: initialization from incompatible pointer type
| ioconf.c:921: warning: initialization from incompatible pointer type
| ioconf.c:923: warning: initialization from incompatible pointer type
| ioconf.c:925: warning: initialization from incompatible pointer type
| ioconf.c:927: warning: initialization from incompatible pointer type
| ioconf.c:929: warning: initialization from incompatible pointer type
| ioconf.c:931: warning: initialization from incompatible pointer type
| ioconf.c:933: warning: initialization from incompatible pointer type
| ioconf.c:935: warning: initialization from incompatible pointer type
| ioconf.c:937: warning: initialization from incompatible pointer type
| ioconf.c:939: warning: initialization from incompatible pointer type
| ioconf.c:941: warning: initialization from incompatible pointer type
| ioconf.c:943: warning: initialization from incompatible pointer type
| ioconf.c:945: warning: initialization from incompatible pointer type
| ioconf.c:947: warning: initialization from incompatible pointer type
| ioconf.c:949: warning: initialization from incompatible pointer type
| ioconf.c:951: warning: initialization from incompatible pointer type
| ioconf.c:953: warning: initialization from incompatible pointer type
| ioconf.c:955: warning: initialization from incompatible pointer type
| ioconf.c:957: warning: initialization from incompatible pointer type
| ioconf.c:959: warning: initialization from incompatible pointer type
| ioconf.c:96

Re: kernel compile error

2015-09-11 Thread Hrvoje Popovski 
On 11.9.2015. 12:11, Paul de Weerd wrote:
> Did you update config(8) before building?
> 
> http://www.openbsd.org/faq/current.html#20150911
> 
> Cheers,
> 
> Paul 'WEiRD' de Weerd
> 

yes, yes ... thank you ... now it's compile perfectly


> On Fri, Sep 11, 2015 at 12:01:31PM +0200, Hrvoje Popovski wrote:
> | cvs update from half an hour ago ...
> | 
> | log:
> | 
> | cc  -Werror -Wall -Wimplicit-function-declaration  -Wno-main
> | -Wno-uninitialized  -Wframe-larger-than=2047 -mcmodel=kernel
> | -mno-red-zone -mno-sse2 -mno-sse -mno-3dnow  -mno-mmx -msoft-float
> | -fno-omit-frame-pointer -fno-builtin-printf -fno-builtin-snprintf
> | -fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
> | -fno-builtin-malloc -fno-pie -O2 -pipe -nostdinc -I../../../.. -I.
> | -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS
> | -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
> | -DUVM_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA
> | -DEXT2FS -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO
> | -DTMPFS -DFUSE -DSOCKET_SPLICE -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE
> | -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DPIPEX -DMROUTING -DMPLS
> | -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DMTRR -DNTFS -DHIBERNATE
> | -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL
> | -DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
> | -DWSDISPLAY_COMPAT_PCVT -DX86EMU -DONEWIREVERBOSE -DMULTIPROCESSOR
> | -DMAXUSERS=80 -D_KERNEL -MD -MP  -c ../../../../dev/ic/aic7xxx.c
> | cc1: warnings being treated as errors
> | ioconf.c:861: warning: initialization from incompatible pointer type
> | ioconf.c:863: warning: initialization from incompatible pointer type
> | ioconf.c:865: warning: initialization from incompatible pointer type
> | ioconf.c:867: warning: initialization from incompatible pointer type
> | ioconf.c:869: warning: initialization from incompatible pointer type
> | ioconf.c:871: warning: initialization from incompatible pointer type
> | ioconf.c:873: warning: initialization from incompatible pointer type
> | ioconf.c:875: warning: initialization from incompatible pointer type
> | ioconf.c:877: warning: initialization from incompatible pointer type
> | ioconf.c:879: warning: initialization from incompatible pointer type
> | ioconf.c:881: warning: initialization from incompatible pointer type
> | ioconf.c:883: warning: initialization from incompatible pointer type
> | ioconf.c:885: warning: initialization from incompatible pointer type
> | ioconf.c:887: warning: initialization from incompatible pointer type
> | ioconf.c:889: warning: initialization from incompatible pointer type
> | ioconf.c:891: warning: initialization from incompatible pointer type
> | ioconf.c:893: warning: initialization from incompatible pointer type
> | ioconf.c:895: warning: initialization from incompatible pointer type
> | ioconf.c:897: warning: initialization from incompatible pointer type
> | ioconf.c:899: warning: initialization from incompatible pointer type
> | ioconf.c:901: warning: initialization from incompatible pointer type
> | ioconf.c:903: warning: initialization from incompatible pointer type
> | ioconf.c:905: warning: initialization from incompatible pointer type
> | ioconf.c:907: warning: initialization from incompatible pointer type
> | ioconf.c:909: warning: initialization from incompatible pointer type
> | ioconf.c:911: warning: initialization from incompatible pointer type
> | ioconf.c:913: warning: initialization from incompatible pointer type
> | ioconf.c:915: warning: initialization from incompatible pointer type
> | ioconf.c:917: warning: initialization from incompatible pointer type
> | ioconf.c:919: warning: initialization from incompatible pointer type
> | ioconf.c:921: warning: initialization from incompatible pointer type
> | ioconf.c:923: warning: initialization from incompatible pointer type
> | ioconf.c:925: warning: initialization from incompatible pointer type
> | ioconf.c:927: warning: initialization from incompatible pointer type
> | ioconf.c:929: warning: initialization from incompatible pointer type
> | ioconf.c:931: warning: initialization from incompatible pointer type
> | ioconf.c:933: warning: initialization from incompatible pointer type
> | ioconf.c:935: warning: initialization from incompatible pointer type
> | ioconf.c:937: warning: initialization from incompatible pointer type
> | ioconf.c:939: warning: initialization from incompatible pointer type
> | ioconf.c:941: warning: initialization from incompatible pointer type
> | ioconf.c:943: warning: initialization from incompatible pointer type
> | ioconf.c:945: warning: initialization from incompatible pointer type
> | ioconf.c:947: warning: initialization f

Re: Question about quotation rules

2015-09-11 Thread Random832 
Rob Pierce  writes:

> Good evening,
>
> Is there a written/unwritten rule for using quotation marks? Do man
> pages and web pages follow the same rules?
>
> When would I use 'this', "this", `this', ``this'', “this“, etc.?
>
> I guess this can be both a source problem as well as a display problem.
>
> Any suggestions regarding reasonable expectations for web page/man
> page consistency?

There are macros for quotes in manpages in mdoc(7). The rendering is
device-dependent - on terminals, it will be unicode quotation marks in
unicode locales, and ``this'' in non-unicode locales.

Re: Running roundcube over httpd

2015-09-11 Thread Steve Shockley 

On 9/9/2015 7:03 PM, Alexander Hall wrote:

Hi!

Does anyone have an example for a functional configuration for
roundcube[mail] over the new httpd?


I use the following to have roundcubemail in a subdirectory with 
unrelated content above it.  Note that I do not consider myself to be an 
httpd configuration expert, so this may not be optimal.


directory index index.php

location "/roundcube/.*" { block }
location "/roundcube/SQL/*"  { block }
location "/roundcube/bin/*"  { block }
location "/roundcube/config/*"   { block }
location "/roundcube/logs/*" { block }
location "/roundcube/temp/*" { block }
location "/roundcube/tests/*"{ block }
location "/roundcube/program/include/*"  { block }
location "/roundcube/program/lib/*"  { block }
location "/roundcube/program/localization/*" { block }
location "/roundcube/program/steps/*"{ block }
location "/roundcube/README.md"  { block }
location "/roundcube/composer.json-dist" { block }
location "/roundcube/composer-json"  { block }
location "/roundcube/package.xml"{ block }
location "/roundcube/Dockerfile" { block }
location "/roundcube/installer/*"{ block }

location "/roundcube/*.php*" {
# Roundcube dir is outside of htdocs
# Strip 1 means remove /roundcube/ from root
root { "/roundcubemail", strip 1 }

fastcgi socket "/run/php-fpm.sock"
directory index index.php
}

location "/roundcube/*" {
root { "/roundcubemail", strip 1 }
directory index index.php
}

requesting help working around boot failures with supermicro atom board

2015-09-11 Thread Dewey Hylton 
hi all. i’m having difficulty with OpenBSD on this board:

Supermicro X7SPE-HD-D525 rev1

i have several similar systems, each running an older version of OpenBSD
for a few years without incident. except this one …

running OpenBSD 5.7 i386 as well as latest amd64 snapshot, from cold start
it boots just fine and runs until rebooted. once rebooted, however, prior
to anything being displayed (i assume this is early in the bios post phase)
i get one very long beep. super micro tells me this indicates inability to
correctly initialize the memory. okay, so i’ve changed memory for known
working components and have the same issue. at this point, the only thing
that gets me booting again is to remove power and then restore power. it
then boots fine from cold start, and fails on the next reboot (as in,
“reboot” from the command line). once in long-beep failure mode, neither
the hardware reset button nor the power button can make the machine boot
again. the only thing that works is removing power. every once in a while
it will reboot successfully, only to fail in the same manner on the next
attempt.

super micro has had me flash bios, clear cmos, boot from different devices
and with nothing connected, etc. the results are the same: when rebooting
from openbsd, next boot fails until power is removed/restored. super micro
blames openbsd.

i installed linux (same hardware, overwrite openbsd 5.7) and scheduled a
reboot every 5 minutes and left it overnight. i logged 554 successful
reboots.

i’m wondering if something could be disabled (boot -c ?) or if something
else raises a red flag and might have a workaround. this has me stumped. i
would very much appreciate a clue stick.

dmesg follows:

OpenBSD 5.8-current (GENERIC.MP) #1364: Wed Sep  9 17:32:01 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4277665792  (4079MB)
avail mem = 4144070656  (3952MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP APIC MCFG OEMB HPET EINJ BERT ERST HEST
acpi0: wakeup devices P0P1(S4) PS2K(S4) PS2M(S4) USB0(S4) USB1(S4) USB2(S4)
USB5(S4) EUSB(S4) USB3(S4) USB4(S4) USB6(S4) USBE(S4) P0P4(S4) P0P5(S4)
P0P6(S4) P0P7(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) Atom(TM) CPU D525 @ 1.80GHz, 1800.23 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,
CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 512KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, C-substates=0.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1800.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,
CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 512KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1800.00 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,
CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu2: 512KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1800.00 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,
CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu3: 512KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 1, remapped to apid 4
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P0P1)
acpiprt2 at acpi0: bus 1 (P0P4)
acpiprt3 at acpi0: bus 2 (P0P8)
acpiprt4 at acpi0: bus 3 (P0P9)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
acpicpu2 at acpi0: C1(@1 halt!)
acpicpu3 at acpi0: C1(@1 halt!)
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Pineview DMI" rev 0x02
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x02: apic 4 int 16
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x02: apic 4 int 21
uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x02: apic 4 int 19
ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x02: apic 4 int 18
usb0 at ehci0: USB revision 2.0

requesting help working around boot failures with supermicro atom board

2015-09-11 Thread dewey.hyl...@gmail.com 
hi all. i’m having difficulty with this board:

Supermicro X7SPE-HD-D525 rev1

i have several similar systems, each running an older version of OpenBSD for a 
few years without incident. except this one …

running OpenBSD 5.7 i386, from cold start it boots just fine and runs until 
rebooted. once rebooted, however, prior to anything being displayed (i assume 
this is early in the bios post phase) i get one very long beep. super micro 
tells me this indicates inability to correctly initialize the memory. okay, so 
i’ve changed memory for known working components and have the same issue. at 
this point, the only thing that gets me booting again is to remove power and 
then restore power. it then boots fine from cold start, and fails on the next 
reboot (as in, “reboot” from the command line). once in long-beep failure mode, 
neither the hardware reset button nor the power button can make the machine 
boot again. the only thing that works is removing power. every once in a while 
it will reboot successfully, only to fail in the same manner on the next 
attempt.

super micro has had me flash bios, clear cmos, boot from different devices and 
with nothing connected, etc. the results are the same: when rebooting from 
openbsd, next boot fails until power is removed/restored. super micro blames 
openbsd.

i installed linux (same hardware, overwrite openbsd 5.7) and scheduled a reboot 
every 5 minutes and left it overnight. i logged 554 successful reboots.

i have since installed the latest available openbsd amd64 snapshot, and am 
seeing the same failures.

i’m wondering if something could be disabled (boot -c ?) or if something else 
raises a red flag and might have a workaround. this has me stumped. i would 
very much appreciate a clue stick. 

dmesg follows:

OpenBSD 5.8-current (GENERIC.MP) #1364: Wed Sep  9 17:32:01 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4277665792 (4079MB)
avail mem = 4144070656 (3952MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP APIC MCFG OEMB HPET EINJ BERT ERST HEST
acpi0: wakeup devices P0P1(S4) PS2K(S4) PS2M(S4) USB0(S4) USB1(S4) USB2(S4) 
USB5(S4) EUSB(S4) USB3(S4) USB4(S4) USB6(S4) USBE(S4) P0P4(S4) P0P5(S4) 
P0P6(S4) P0P7(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) Atom(TM) CPU D525 @ 1.80GHz, 1800.23 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 512KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, C-substates=0.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1800.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,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 512KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1800.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,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu2: 512KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1800.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,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR
cpu3: 512KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 1, remapped to apid 4
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P0P1)
acpiprt2 at acpi0: bus 1 (P0P4)
acpiprt3 at acpi0: bus 2 (P0P8)
acpiprt4 at acpi0: bus 3 (P0P9)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
acpicpu2 at acpi0: C1(@1 halt!)
acpicpu3 at acpi0: C1(@1 halt!)
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Pineview DMI" rev 0x02
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x02: apic 4 int 16
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x02: apic 4 int 21
uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x02: apic 4 int 19
ehci0 at pci0 dev 26 function 7 "Intel 82801I

Re: I354 initialization error on DFF 2220

2015-09-11 Thread Paul Levlin 
Thank you for the quick response, and sorry for the delay in the
result (also sorry for top-posting, don't know how to avoid it in
this setting)..
With the patch applied, the interface seems to be working fine
(as it's only a 2-port system, the 2 extra interfaces that are
unable to initialize are expected I guess?). The MAC addresses
are retrieved successfully in the proper dmesg, but I've replaced
the NIC-specific parts with ? in the output below.

Thanks again for the quick reply and patch!


--Paul


===
OpenBSD 5.8-current (GENERIC.MP) #2: Sat Sep 12 01:26:21 CEST 2015
p...@elcheapo.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2126372864 (2027MB)
avail mem = 2058027008 (1962MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP SPCR HPET APIC MCFG SSDT
acpi0: wakeup devices EHC1(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Atom(TM) CPU C2338 @ 1.74GHz, 1166.89 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,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,
ERMS,SENSOR,ARAT
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 83MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU C2338 @ 1.74GHz, 1166.66 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,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,
ERMS,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 1 (RP01)
acpiprt1 at acpi0: bus 2 (RP02)
acpiprt2 at acpi0: bus 3 (RP03)
acpiprt3 at acpi0: bus 4 (RP04)
acpiprt4 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!), PSS
acpicpu1 at acpi0: C1(@1 halt!), PSS
cpu0: Enhanced SpeedStep 1166 MHz: speeds: 2100, 1800, 1600, 1400 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x1f0f
 rev 0x02
ppb0 at pci0 dev 1 function 0 "Intel Atom C2000 PCIE" rev 0x02: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 2 function 0 "Intel Atom C2000 PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 3 function 0 "Intel Atom C2000 PCIE" rev 0x02: msi
pci3 at ppb2 bus 3
ppb3 at pci0 dev 4 function 0 "Intel Atom C2000 PCIE" rev 0x02: msi
pci4 at ppb3 bus 4
pchb1 at pci0 dev 14 function 0 "Intel Atom C2000 RAS" rev 0x02
"Intel Atom C2000 RCEC" rev 0x02 at pci0 dev 15 function 0
 not configured
"Intel Atom C2000 SMBus" rev 0x02 at pci0 dev 19 function 0
 not configured
em0 at pci0 dev 20 function 0 "Intel I354 SGMII" rev 0x03: msi,
 address 00:08:a2:??:??:??
em1 at pci0 dev 20 function 1 "Intel I354 SGMII" rev 0x03: msi,
 address 00:08:a2:??:??:??
em2 at pci0 dev 20 function 2 "Intel I354 SGMII" rev 0x03: msiem2:
 Hardware Initialization Failedem2: Unable to initialize the hardware
em3 at pci0 dev 20 function 3 "Intel I354 SGMII" rev 0x03: msiem3:
 Hardware Initialization Failedem3: Unable to initialize the hardware
ehci0 at pci0 dev 22 function 0 "Intel Atom C2000 USB" rev 0x02:
 apic 2 int 22
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ahci0 at pci0 dev 23 function 0 "Intel Atom C2000 AHCI" rev 0x02:
 msi, AHCI 1.3
scsibus1 at ahci0: 32 targets
ahci1 at pci0 dev 24 function 0 "Intel Atom C2000 AHCI" rev 0x02:
 msi, AHCI 1.3
scsibus2 at ahci1: 32 targets
pcib0 at pci0 dev 31 function 0 "Intel Atom C2000 PCU" rev 0x02
ichiic0 at pci0 dev 31 function 3 "Intel Atom C2000 PCU SMBus"
 rev 0x02: apic 2 int 22
iic0 at ichiic0
iic0: addr 0x2e 00=3a words 00=3a3a 01= 02= 03= 04=
 05= 06= 07=
spdmem0 at iic0 addr 0x50: 2GB DDR3 SDRAM PC3-12800
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
com1: console
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
uhub1 at uhub0 port 1 "Intel product 0x07db" rev 2.00/0.02 addr 2
umass0 at uhub1 port 3 configuration 1 interface 0
 "Generic Ultra Fast Media" rev 2.00/1.98 addr 3
umass0: using SCSI over Bulk-Only
scsibus3 at umass0: 2 targets, initiator 0
sd0 at scsibus3 targ 1 lun 0:
 SCSI0 0/direct removable serial.0424224000225001
sd0: 3776MB, 512 bytes/sector, 7733248 sectors
vscsi0 at root
scsibus4 at vscsi0: 256 targets
softraid0 at

Re: I354 initialization error on DFF 2220

2015-09-11 Thread Jonathan Gray 
On Sat, Sep 12, 2015 at 12:44:55AM +, Paul Levlin wrote:
> Thank you for the quick response, and sorry for the delay in the
> result (also sorry for top-posting, don't know how to avoid it in
> this setting)..
> With the patch applied, the interface seems to be working fine
> (as it's only a 2-port system, the 2 extra interfaces that are
> unable to initialize are expected I guess?). The MAC addresses
> are retrieved successfully in the proper dmesg, but I've replaced
> the NIC-specific parts with ? in the output below.
> 
> Thanks again for the quick reply and patch!

The I354 MAC is part of the Atom SoC.  It seems the people responsible
for the board neglected to disable the unused pci functions.

Enabling all the em debugging can be very vebose, it might
be interesting to see what the other interfaces claim
for a phy id though:

Index: if_em.c
===
RCS file: /cvs/src/sys/dev/pci/if_em.c,v
retrieving revision 1.304
diff -u -p -r1.304 if_em.c
--- if_em.c 11 Sep 2015 13:02:28 -  1.304
+++ if_em.c 12 Sep 2015 02:53:53 -
@@ -1851,7 +1851,7 @@ em_hardware_init(struct em_softc *sc)
INIT_DEBUGOUT("\nHardware Initialization Deferred ");
return (EAGAIN);
}
-   printf("%s: Hardware Initialization Failed",
+   printf("\n%s: Hardware Initialization Failed\n",
   sc->sc_dv.dv_xname);
return (EIO);
}
Index: if_em_hw.c
===
RCS file: /cvs/src/sys/dev/pci/if_em_hw.c,v
retrieving revision 1.88
diff -u -p -r1.88 if_em_hw.c
--- if_em_hw.c  12 Sep 2015 02:38:14 -  1.88
+++ if_em_hw.c  12 Sep 2015 02:53:57 -
@@ -5368,6 +5368,7 @@ em_match_gig_phy(struct em_hw *hw)
 
hw->phy_id |= (uint32_t) (phy_id_low & PHY_REVISION_MASK);
hw->phy_revision = (uint32_t) phy_id_low & ~PHY_REVISION_MASK;
+printf("\nPHY ID 0x%X detected\n", hw->phy_id);
 
switch (hw->mac_type) {
case em_82543:

ftp.html

2015-09-11 Thread Rob Pierce 
Reword since FTP is no longer used for installation (although the files can 
still be obtained via FTP).

Index: ftp.html
===
RCS file: /cvs/www/ftp.html,v
retrieving revision 1.673
diff -u -p -r1.673 ftp.html
--- ftp.html25 Jul 2015 19:24:18 -  1.673
+++ ftp.html11 Sep 2015 12:30:18 -
@@ -61,7 +61,7 @@ upgrade your system very quickly.
 Download via
   HTTP/FTP
 
-OpenBSD can be also easily installed via HTTP or FTP.
+OpenBSD can be also easily obtained via HTTP or FTP.
 Typically you need a single small piece of boot media (e.g., a boot floppy)
 and then the rest of the files can be installed from a number of locations,
 including directly off the Internet.

Re: ftp.html

2015-09-11 Thread Raf Czlonka 
On Fri, Sep 11, 2015 at 01:33:16PM BST, Rob Pierce wrote:

> Reword since FTP is no longer used for installation (although the
> files can still be obtained via FTP).
> 
> Index: ftp.html
> ===
> RCS file: /cvs/www/ftp.html,v
> retrieving revision 1.673
> diff -u -p -r1.673 ftp.html
> --- ftp.html  25 Jul 2015 19:24:18 -  1.673
> +++ ftp.html  11 Sep 2015 12:30:18 -
> @@ -61,7 +61,7 @@ upgrade your system very quickly.
>  Download via
>HTTP/FTP
>  
> -OpenBSD can be also easily installed via HTTP or FTP.
> +OpenBSD can be also easily obtained via HTTP or FTP.
>  Typically you need a single small piece of boot media (e.g., a boot floppy)
>  and then the rest of the files can be installed from a number of locations,
>  including directly off the Internet.

Hi Rob,

A while back I had posted a similar diff (see below) as part of a larger
"FTP install" removal but yours fits better. I'd still change the word
order as it seems to read better - at least for me anyway :^)

Regards,

Raf

Index: ftp.html
===
RCS file: /cvs/www/ftp.html,v
retrieving revision 1.673
diff -u -p -r1.673 ftp.html
--- ftp.html25 Jul 2015 19:24:18 -  1.673
+++ ftp.html20 Aug 2015 19:55:50 -
@@ -61,7 +61,7 @@ upgrade your system very quickly.
 Download via
   HTTP/FTP
 
-OpenBSD can be also easily installed via HTTP or FTP.
+OpenBSD can also be easily installed via HTTP.
 Typically you need a single small piece of boot media (e.g., a boot floppy)
 and then the rest of the files can be installed from a number of locations,
 including directly off the Internet.

OpenBGPd and ARIN allocations smaller than /24

2015-09-11 Thread Peter Hessler 
When ARIN prepared for the IPv4-pocolypse[1], they put aside a /10 for
**smaller than /24 allocations**.  Our default ruleset will not allow
those, even though they will be for various pieces of critical dual-stack
infrastructure to help IPv6-only systems survive.

RIPE is currently[2] announcing smaller blocks to test how wide spread
acceptance of these blocks are.  The results are not so good, but better
than last time :).

I just committed an example configuration line to the sample OpenBGPd
filter set:

allow from any inet prefix 23.128.0.0/10 prefixlen 24 - 28

You may need to adjust your filter set to accept these addresses.  With
this rule, I now see the test announcements over my AMS-IX link.

According to the RIR Comparative Policy Overview 2015-02[3], no other RIR
has such a policy, so you don't need to add other filters to cover other
regions.


[1] https://www.arin.net/announcements/2014/20140130.html
[2] 
https://labs.ripe.net/Members/emileaben/has-the-routability-of-longer-than-24-prefixes-changed
[3] 
https://www.nro.net/rir-comparative-policy-overview/rir-comparative-policy-overview-2015-02#2-6

-- 
Pardon this fortune.  Database under reconstruction.

Re: System clock hours behind, network hangs (amd64, -current)

2015-09-11 Thread Martin Pieuchot 
On 11/09/15(Fri) 17:12, Mark Patruck wrote:
> I had to reboot the system last evening and 'unfortunately' the error
> doesn't show up right now. However...there were lots of changes to src
> the last hours, so i'll try with a new snap today/tomorrow and report
> back. This way i also have fresh values (vmstat -i, netstat -m, ...)
> before and after the issue occurs. 

Please send me your dmesg before upgrading.  The date of the kernel
that showed the bug is a very important piece of information to me.

Re: System clock hours behind, network hangs (amd64, -current)

2015-09-11 Thread Mark Patruck 
I had to reboot the system last evening and 'unfortunately' the error
doesn't show up right now. However...there were lots of changes to src
the last hours, so i'll try with a new snap today/tomorrow and report
back. This way i also have fresh values (vmstat -i, netstat -m, ...)
before and after the issue occurs. 

On Thu, Sep 10, 2015 at 06:22:31PM +, Martin Pieuchot wrote:
> Mark Patruck  wrapped.cx> writes:
> > 
> > over the last few weeks i'm having a strange issue here running amd64
> > -current (last updated 3 days before)
> > 
> > ### system
> > Supermicro X7SPA-HF-D525 1,8Ghz Atom
> > 4 GB RAM
> > 1x 128GB SSD (system)
> > 1x 6TB /1x 4TB HDD (NFS exported)
> > 
> > Everything works fine the first few hours, then suddenly
> > 
> > - the system clock is few seconds/minutes behind (up to 2 hours after
> > 3 days)
> > 
> > - the network connection hangs/is unresponsive for ~1-2 seconds
> >   * ping response increases from 0.500ms -> 1.600 ms 
> > 
> >   * if i type a command when logged in via ssh
> >   $ ifc.onfig,
> >   $ ...
> >   $ 10x ifconfig works w/o issues
> >   $ ifc.onfig
> > 
> >   * throughput via nfs drops
> > 
> > Right now, the system is in this state again and only a reboot helps.
> > I'm not sure if it's hardware or software related, so hopefully anybody
> > has an idea. 
> 
> Hello Mark,
> 
> Thanks for the report.
> 
> hard to tell without a full dmesg, we need to know which snapshot
> you're running in order to identify which commit could be the cause
> of this regression.
> 
> Could you send it again making sure the "OpenBSD 5.8-current..." is
> present?
> 
> Could you also include the output of "ifconfig", "netstat -nf inet" and
> "netsat -rn"?
> 
> Thanks,
> Martin
> 

-- 
Mark Patruck ( mark at wrapped.cx )
GPG key 0xF2865E51 / 187F F6D3 EE04 1DCE 1C74  F644 0D3C F66F F286 5E51

http://www.wrapped.cx

Re: ftp.html

2015-09-11 Thread Raf Czlonka 
On Fri, Sep 11, 2015 at 03:06:25PM BST, Rob Pierce wrote:

> Agreed about the word order. How about this?

I like it, FWIW :^)

> Index: ftp.html
> ===
> RCS file: /cvs/www/ftp.html,v
> retrieving revision 1.673
> diff -u -p -r1.673 ftp.html
> --- ftp.html  25 Jul 2015 19:24:18 -  1.673
> +++ ftp.html  11 Sep 2015 12:30:18 -
> @@ -61,7 +61,7 @@ upgrade your system very quickly.
>  Download via
>HTTP/FTP
>  
> -OpenBSD can be also easily installed via HTTP or FTP.
> +OpenBSD can also be easily obtained via HTTP or FTP.
>  Typically you need a single small piece of boot media (e.g., a boot floppy)
>  and then the rest of the files can be installed from a number of locations,
>  including directly off the Internet.

Re: Question - test lab

2015-09-11 Thread Christian Weisgerber 
On 2015-09-09, "Bryan C. Everly"  wrote:

> I'm trying to put together a multiple CPU architecture test lab for
> work I'm doing on some ports and I have the following:
>
> * Thinkpad T21 (i386)
> * Powerbook G4 (32-bit PPC)
> * Sun Blade 100 (sparc64)
> * Thinkpad x220 (amd64)
>
> I'm wondering if anyone could recommend a low-cost Alpha or PA-RISC
> machine for me to add to this?

General hints for picking up an alpha:

Make sure the machine has an SRM console, i.e., boots to a ">>>"
prompt.  Some models only support AlphaBIOS or ARC(BIOS) and these
don't run BSD.

CPU generations:
21064: Skip.  They are far too slow.
21164: If you're happy with the speed of the Blade 100, then these
   are in the same ballpark.
21264: Nowadays there's probably no point in bothering with anything
   less.

If you intend to be in the same room as the machine, pick a workstation
model and not a server.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de