2 VoIP phones on one line
Years ago I bought a Minitar VoIP ATA and it was great. Then SWMBO wanted one too and I set up siproxd which mostly worked. Then I go two global IPs and put one ATA/Phone on each. Perfect! No Siproxd! Now I am about to need those 2 IPs. Neither phone needs to recieve incoming calls. Anybody using some of the more recent additions inthe Telephony ports? Ones to avoid or ones to love? Thanx, *** NOTE *** Please DO NOT CC me. I am subscribed to the list. Mail to the sender address that does not originate at the list server is tarpitted. The reply-to: address is provided for those who feel compelled to reply off list. Thankyou. Rod/ --- This life is not the real thing. It is not even in Beta. If it was, then OpenBSD would already have a man page for it.
Re: multiple calls to OpenSSL_add_all_algorithms
On 2014-10-22, Martijn van Duren martijn...@gmail.com wrote: I'm currently trying to write a library that heavily relies on libcrypto. Because I don't want applications linking to it, to have to call OpenSSL_add_all_algorithms, for convenience, I added those calls to the appropriate places in my library. Because of this nature, the function is called multiple times, and even if I shielded it within my library it could still be called outside of it by an application using my library. fwiw, Asterisk ran into this, this was the result: http://reviewboard.asterisk.org/r/1006/
HEADS-UP: issues with chromium in -current
This has been discussed internally, but chromium is partly broken these days. Most specifically, windows refresh does strange things under some circumstances. The circumstances are well-known (thanks to matthieu@): modern systems use some composition manager for eye-candy on their display. So if you're using a shiny window manager, you won't see an issue. Old-style window managers, such as fvwm, fvwm2 (from ports) and cwm don't. Hence the breakage. Work-around: start a composition manager, such as xcompmgr from base xenocara. Cry since you lost your background image or moire pattern (fvwm-root, from ports, does know about composition managers). We're currently in the process of reporting the problem upstream. Outside of OpenBSD, most people don't use primitive window managers, so they don't see the issue. It probably started around when chromium switched to Aura for its gfx system...
Re: HEADS-UP: issues with chromium in -current
On Thu, Oct 23, 2014 at 12:14:03PM +0200, Marc Espie wrote: This has been discussed internally, but chromium is partly broken these days. Most specifically, windows refresh does strange things under some circumstances. The circumstances are well-known (thanks to matthieu@): modern systems use some composition manager for eye-candy on their display. So if you're using a shiny window manager, you won't see an issue. Old-style window managers, such as fvwm, fvwm2 (from ports) and cwm don't. Hence the breakage. Work-around: start a composition manager, such as xcompmgr from base xenocara. Cry since you lost your background image or moire pattern (fvwm-root, from ports, does know about composition managers). We're currently in the process of reporting the problem upstream. Outside of OpenBSD, most people don't use primitive window managers, so they don't see the issue. For information. I'm using Slackware 14.1 with fvwm2 and Chromium, I see no issue at all. It probably started around when chromium switched to Aura for its gfx system... -- Stéphane Tougard steph...@unices.org
Re: HEADS-UP: issues with chromium in -current
On Thu, Oct 23, 2014 at 12:58 PM, Stephane Tougard steph...@unices.org wrote: I'm using Slackware 14.1 with fvwm2 and Chromium, I see no issue at all. fvwm2 with or without a compositor (like xcompmgr or compton)? And what version of chromium? Ciao David -- If you try a few times and give up, you'll never get there. But if you keep at it... There's a lot of problems in the world which can really be solved by applying two or three times the persistence that other people will. -- Stewart Nelson
Re: HEADS-UP: issues with chromium in -current
On Thu, Oct 23, 2014 at 12:14:03PM +0200, Marc Espie wrote: This has been discussed internally, but chromium is partly broken these days. Most specifically, windows refresh does strange things under some circumstances. The circumstances are well-known (thanks to matthieu@): modern systems use some composition manager for eye-candy on their display. So if you're using a shiny window manager, you won't see an issue. Old-style window managers, such as fvwm, fvwm2 (from ports) and cwm don't. Hence the breakage. Work-around: start a composition manager, such as xcompmgr from base xenocara. Cry since you lost your background image or moire pattern (fvwm-root, from ports, does know about composition managers). We're currently in the process of reporting the problem upstream. Outside of OpenBSD, most people don't use primitive window managers, so they don't see the issue. It probably started around when chromium switched to Aura for its gfx system... Does this issue include highlighted links becoming invisible? I ask as using xcompmgr does not solve this problem for me in Chromium. My set up: port:fred ~ dmesg|head -2; chrome --version; awesome --version OpenBSD 5.6-current (GENERIC.MP) #462: Tue Oct 21 16:17:54 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Chromium 38.0.2125.101 awesome v3.5.5 (Kansas City Shuffle) ?? Build: Oct 19 2014 10:55:35 for amd64 by gcc version 4.2.1 (@amd64.ports.openbsd.org) ?? Compiled against Lua 5.2.3 (running with Lua 5.2) ?? D-Bus support: ? cheers Fred
Re: Tor and Polipo
Hello! Thank you so much. You're most right, there was no need for Polipo, uncommenting the control port in `torrc` was enough. I really appreciate the help, and I hope that I one day can make it up to you. Sharing with you a little bit of music for what it's worth: https://soundcloud.com/jakarta-records/radio-jakarta-003-radio-juicy-radio-juicy-for-jakarta Take care! O.D. On 22. oktober 2014 at 9:15 PM, Dawe dawed...@gmx.de wrote: On Oct 22, 2014 20:44, openda...@hushmail.com wrote: Hi! On 22. oktober 2014 at 8:23 PM, Dawe dawed...@gmx.de wrote: Could you try a connection without the control port? I'm afraid that's mandatory. Can you test with firefox or another browser to make sure it's a tor/polipo problem? Do I even need Polipo, can't I just use Tor directly? Well, Tor speaks socks on the 9050 port. If the client can speak that, you don't need a web proxy like polipo. Also, the default control port is 9051. My bad. Just to be sure: Is your browser inside of the vm? Yes, everything is inside of the vm. What does a telnet 127.0.0.1 9050 telnet 127.0.0.1 8123 say? % telnet 127.0.0.1 9050 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. ^CConnection closed by foreign host. % telnet 127.0.0.1 8123 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. ^CConnection closed by foreign host. Ok, and telnet 127.0.0.1 9051? The control port isn't open if you don't change the torrc. Hope
Re: HEADS-UP: issues with chromium in -current
On Thu, Oct 23, 2014 at 3:06 PM, Stephane Tougard steph...@unices.org wrote: On Thu, Oct 23, 2014 at 01:04:04PM +0200, David Coppa wrote: I'm using Slackware 14.1 with fvwm2 and Chromium, I see no issue at all. fvwm2 with or without a compositor (like xcompmgr or compton)? Original version of the Slackware. xcompmgr is as well originally part of Slackware. And what version of chromium? 33 This is an older (still gtk+2 based) version of chromium: it doesn't have this bug. The bug started manifesting itself, when they switched to the new Aura toolkit (since version 37 iirc). Ciao, David
Re: Pidgin/Lync success stories?
Hi Please see the update on ports@ Cheers Tom On Thu, Oct 2, 2014 at 5:22 PM, Stuart Henderson s...@spacehopper.org wrote: On 2014-10-01, Leonardo Santagostini lsantagost...@gmail.com wrote: Ok, here i go, i downloaded pidgin from original web and sipe from their web too. This procedure does not adjust to the procedures folllowed by openbsd but, its valid to get pidgin / sipe working =) Not a great idea. If the packages do not work, please work with maintainers to try and track things down. In this case it's probably best to talk to the maintainer of pidgin-sipe. As a last resort try ports@ - misc@ posts are much less likely to be seen by the right people.
Re: poor network performance after wake from suspend
bunch. no. thanks! On Wed, Oct 22, 2014 at 11:21 AM, Mike Larkin mlar...@azathoth.net wrote: On Fri, Sep 26, 2014 at 11:46:04AM +0400, ÐиÑилл wrote: Hello. After apm -z and wake by wol (re0) sometimes machine becomes very slow on network operations (even ssh!) Help, please. Here is dmesg and ifconfig: ... snip ... re0: watchdog timeout Do you see only one of these watchdog timeouts or a bunch? And does this problem happen with non-WOL wakeups? -ml ifconfig re0 re0: flags=108843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,WOL mtu 1500 lladdr 00:21:85:52:d5:ea priority: 0 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::221:85ff:fe52:d5ea%re0 prefixlen 64 scopeid 0x1 inet 192.168.1.4 netmask 0xff00 broadcast 192.168.1.255
Re: Retired 4.4-beta
Clint Pachl pa...@ecentryx.com writes: I just wanted to share my story ... I finally retired my old AOpen desktop router which was running 4.4-beta from July 2008 until now. I originally set it up to test pf and routing for my company's network. It seemed to work fine so I put it into production. Then I just kind of forgot about it. I originally installed an old WD Caviar 3.4 GB drive, which I bought in bulk, used on Ebay (like 20 drives for $10). During those 6 years of commission, I only had two hardware failures. I replaced the old spinning disk, which died a couple years ago, with a compact flash drive. The power supply fan was also replaced. Other than taking the machine down for those repairs, it ran 365/24/7. No crashing. No problems. Just routing/filtering traffic and offering DHCP leases. Talk about set it, and for get it! And that was on a BETA version. This machine was replaced with the much smaller, more efficient, and quieter Lanner FW-7541 with a dual core Atom D525 1.8GHz, 4GB DDR3, and 8GB Transcend SSD. Unlike its predecessor, I plan to upgrade this machine with every release. Anyway, I just wanted to share. I also wanted to thank the devs for a solid OS, time and time again. OpenBSD 4.4-beta (GENERIC) #979: Wed Jul 16 09:40:32 MDT 2008 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium II (GenuineIntel 686-class, 512KB L2 cache) 401 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real mem = 268005376 (255MB) avail mem = 250929152 (239MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/24/00, BIOS32 rev. 0 @ 0xfb280, SMBIOS rev. 2.2 @ 0xf0800 (29 entries) bios0: vendor Award Software International, Inc. version 4.60 PGMA date 07/24/00 apm0 at bios0: Power Management spec V1.2 (slowidle) apm0: AC on, battery charge unknown acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xf/0xb6f8 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdd90/144 (7 entries) pcibios0: PCI Exclusive IRQs: 10 11 12 pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371SB ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xc000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82443BX AGP rev 0x02 ppb0 at pci0 dev 1 function 0 Intel 82443BX AGP rev 0x02 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 Trident 3DImage 9850 rev 0xf3 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) agp0 at vga1: aperture at 0xe500, size 0x40 piixpcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x02 pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility atapiscsi0 at pciide0 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets, initiator 7 cd0 at scsibus0 targ 0 lun 0: ATAPI, CD-ROM DRIVE-36X, 36FP ATAPI 5/cdrom removable cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 wd0 at pciide0 channel 1 drive 0: TRANSCEND wd0: 1-sector PIO, LBA, 1983MB, 4061232 sectors wd0(pciide0:1:0): using PIO mode 4, DMA mode 2 uhci0 at pci0 dev 7 function 2 Intel 82371AB USB rev 0x01: irq 10 piixpm0 at pci0 dev 7 function 3 Intel 82371AB Power rev 0x02: SMI iic0 at piixpm0 dc0 at pci0 dev 9 function 0 ADMtek AN983 rev 0x11: irq 10, address 00:04:5a:81:8f:44 ukphy0 at dc0 phy 1: Generic IEEE 802.3u media interface, rev. 1: OUI 0x000749, model 0x0001 dc1 at pci0 dev 10 function 0 ADMtek AN983 rev 0x11: irq 12, address 00:12:17:52:7a:33 ukphy1 at dc1 phy 1: Generic IEEE 802.3u media interface, rev. 1: OUI 0x000749, model 0x0001 dc2 at pci0 dev 13 function 0 ADMtek AN983 rev 0x11: irq 10, address 00:03:6d:18:72:e8 acphy0 at dc2 phy 1: AC_UNKNOWN 10/100 PHY, rev. 0 isa0 at piixpcib0 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 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec usb0 at uhci0: USB revision 1.0 uhub0 at usb0 Intel UHCI root hub rev 1.00/1.00 addr 1 biomask ef65 netmask ff65 ttymask mtrr: Pentium Pro MTRR support softraid0 at root wd0(pciide0:1:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:1:0: bus-master DMA error: missing interrupt, status=0x21 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0(pciide0:1:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:1:0: bus-master DMA error: missing
is this normal or problematic?
I have a tcpdump set in the background on OpenBSD 5.5-current from: mercury$ sysctl kern.version kern.version=OpenBSD 5.5-current (MERCURY.MP) #2: Sat Jun 21 08:24:41 CEST 2014 r...@mercury.centroid.eu:/usr/src/sys/arch/amd64/compile/MERCURY.MP late June (waiting for 5.6). Now my problem is a certain WRT router, I'm supposed to be able to reach it with an IPv6 address made of its MAC address, but ndp doesn't recognize it, and it should. While this was on my laptop which is off (it is 5.5) right now I can duplicate what i saw in a tcpdump on my workstation and it goes a little something like this: mercury# ping6 fe80::1234:56ff:fe78:9abc%em0 PING6(56=40+8+8 bytes) fe80::beee:7bff:fedd:2e5a%em0 -- fe80::1234:56ff:fe78:9abc%em0 18:43:39.537023 bc:ee:7b:dd:2e:5a 33:33:ff:78:9a:bc 86dd 86: fe80::beee:7bff:fedd:2e5a ff02::1:ff78:9abc: icmp6: neighbor sol: who has fe80::1234:56ff:fe78:9abc(src lladdr: bc:ee:7b:dd:2e:5a) [icmp6 cksum ok] (len 32, hlim 255) ^C --- fe80::1234:56ff:fe78:9abc%em0 ping6 statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss mercury# 18:43:40.532913 bc:ee:7b:dd:2e:5a 33:33:ff:78:9a:bc 86dd 86: fe80::beee:7bff:fedd:2e5a ff02::1:ff78:9abc: icmp6: neighbor sol: who has fe80::1234:56ff:fe78:9abc(src lladdr: bc:ee:7b:dd:2e:5a) [icmp6 cksum ok] (len 32, hlim 255) 18:43:41.532915 bc:ee:7b:dd:2e:5a 33:33:ff:78:9a:bc 86dd 86: fe80::beee:7bff:fedd:2e5a ff02::1:ff78:9abc: icmp6: neighbor sol: who has fe80::1234:56ff:fe78:9abc(src lladdr: bc:ee:7b:dd:2e:5a) [icmp6 cksum ok] (len 32, hlim 255) notice the 33:33:ff for the beginning mac address, I can not find the code for that grepping through /sys/netinet6/* where would that be defined? Or is this a brokenness that we encountered with this article concerning vlan(4): http://permalink.gmane.org/gmane.os.openbsd.misc/212691 Is it really a cause with 5.5, and fixed in 5.6, or is it normal behaviour of ndp to add 33:33:ff, a multicast address after all but I'm unsure if it's proper due to lack of knowledge of IPv6 and ND6. Regards, -peter
document apmd -C replacement : perfpolicy
Hi, I wanted to use the new performance throttling system but I had to look for what to change so if I can prevent others from doing it. Feel free to modify the wording :) Cheers, Daniel Index: sysctl.8 === RCS file: /cvs/src/sbin/sysctl/sysctl.8,v retrieving revision 1.184 diff -u -p -u -p -r1.184 sysctl.8 --- sysctl.827 Aug 2014 14:04:15 - 1.184 +++ sysctl.823 Oct 2014 16:48:57 - @@ -358,6 +358,7 @@ and a few require a kernel compiled with .It hw.uuid Ta string Ta no .It hw.ncpufound Ta integer Ta no .It hw.allowpowerdown Ta integer Ta yes +.It hw.perfpolicy Ta string Ta yes .It machdep.console_device Ta dev_t Ta no .It machdep.unaligned_print Ta integer Ta yes .It machdep.unaligned_fix Ta integer Ta yes Index: faq/current.html === RCS file: /cvs/www/faq/current.html,v retrieving revision 1.562 diff -u -p -u -p -r1.562 current.html --- faq/current.html19 Oct 2014 13:21:42 - 1.562 +++ faq/current.html23 Oct 2014 17:00:56 - @@ -77,6 +77,7 @@ lia href=#201409192014/09/19 - rc.conf(8) moved to the base set/a lia href=#201409252014/09/25 - [ports] collectd updated to 5.4.1/a lia href=#201410132014/10/13 - lkm removed/a +lia href=#201410232014/10/23 - Performance throttling in the kernel/a /ul hr @@ -914,6 +915,19 @@ and the lkm directory should be deleted: rm -f /usr/share/man/man4/lkm.4 rm -f /usr/share/mk/bsd.lkm.mk /usr/include/sys/lkm.h /pre + +a name=20141023/a +h32014/10/23 - Performance throttling in the kernel/h3 +Perfomance throttling is now available from the kernel. It replaces +apmd's -C flag which has been removed. If you used this flag, remove it +from your /etc/rc.conf.local. +To use the new performance throttling system, set the sysctl +hw.perfpolicy to auto with: +pre +sysctl hw.perfpolicy=auto +/pre +Remember to edit your /etc/sysctl.conf if you want to keep it after +your next reboot. br hr
Re: is this normal or problematic?
On 10/23/14 18:55, Peter J. Philipp wrote: I have a tcpdump set in the background on OpenBSD 5.5-current from: mercury$ sysctl kern.version kern.version=OpenBSD 5.5-current (MERCURY.MP) #2: Sat Jun 21 08:24:41 CEST 2014 r...@mercury.centroid.eu:/usr/src/sys/arch/amd64/compile/MERCURY.MP late June (waiting for 5.6). Now my problem is a certain WRT router, I'm supposed to be able to reach it with an IPv6 address made of its MAC address, but ndp doesn't recognize it, and it should. While this was on my laptop which is off (it is 5.5) right now I can duplicate what i saw in a tcpdump on my workstation and it goes a little something like this: mercury# ping6 fe80::1234:56ff:fe78:9abc%em0 PING6(56=40+8+8 bytes) fe80::beee:7bff:fedd:2e5a%em0 -- fe80::1234:56ff:fe78:9abc%em0 18:43:39.537023 bc:ee:7b:dd:2e:5a 33:33:ff:78:9a:bc 86dd 86: fe80::beee:7bff:fedd:2e5a ff02::1:ff78:9abc: icmp6: neighbor sol: who has fe80::1234:56ff:fe78:9abc(src lladdr: bc:ee:7b:dd:2e:5a) [icmp6 cksum ok] (len 32, hlim 255) ^C --- fe80::1234:56ff:fe78:9abc%em0 ping6 statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss mercury# 18:43:40.532913 bc:ee:7b:dd:2e:5a 33:33:ff:78:9a:bc 86dd 86: fe80::beee:7bff:fedd:2e5a ff02::1:ff78:9abc: icmp6: neighbor sol: who has fe80::1234:56ff:fe78:9abc(src lladdr: bc:ee:7b:dd:2e:5a) [icmp6 cksum ok] (len 32, hlim 255) 18:43:41.532915 bc:ee:7b:dd:2e:5a 33:33:ff:78:9a:bc 86dd 86: fe80::beee:7bff:fedd:2e5a ff02::1:ff78:9abc: icmp6: neighbor sol: who has fe80::1234:56ff:fe78:9abc(src lladdr: bc:ee:7b:dd:2e:5a) [icmp6 cksum ok] (len 32, hlim 255) notice the 33:33:ff for the beginning mac address, I can not find the code for that grepping through /sys/netinet6/* where would that be defined? Or is this a brokenness that we encountered with this article concerning vlan(4): http://permalink.gmane.org/gmane.os.openbsd.misc/212691 Is it really a cause with 5.5, and fixed in 5.6, or is it normal behaviour of ndp to add 33:33:ff, a multicast address after all but I'm unsure if it's proper due to lack of knowledge of IPv6 and ND6. Regards, -peter To save someone doing the work, I have found where that is defined, in /sys/net/if_ethersubr.c, sorry for the noise. it's legitimate then and I'm still trying to figure out why I can't reach the WRT router. Thanks! -peter
pool_do_get panic
i had no visible ddb prompt unfortunately, so no show registers, etc but i managed a boot dump blindly. (i did not have enough space at reboot time, so i ran savecore manually later) $ sudo savecore /var/crash savecore: reboot after panic: pool_do_get: mcl2k free list modified: page 0xd7e2c000; item addr 0xd7e2c000; offset 0x0=0x754208 != 0xa39ee339 savecore: system went down at Thu Oct 23 18:08:04 2014 savecore: /var/crash/bounds: No such file or directory savecore: writing core to /var/crash/bsd.0.core savecore: writing kernel to /var/crash/bsd.0 it is not the first time i meet mr. pool_do_get, but it is not something i can reproduce at will. $ gdb GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-openbsd5.6. (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 0xd0560284 in boot () (gdb) where #0 0xd0560284 in boot () #1 0xd03c49d6 in reboot () #2 0xd0385a42 in db_boot_crash_cmd () #3 0xd03860f4 in db_command () #4 0xd038633c in db_command_loop () #5 0xd038a52a in db_trap () #6 0xd055c8db in kdb_trap () #7 0xd056d007 in trap () #8 0xd0200b31 in alltraps () #9 0xd055c5f7 in Debugger () #10 0xd03d2d81 in panic () #11 0xd03d57d2 in assertwaitok () #12 0xd03b22dd in malloc () #13 0xd075a704 in intel_crtc_mode_get () #14 0xd072a397 in drm_fb_helper_restore_fbdev_mode () #15 0xd076025e in intel_fb_restore_mode () #16 0xd0736f77 in inteldrm_doswitch () #17 0xd0737022 in inteldrm_show_screen () #18 0xd083c424 in wsdisplay_switchtoconsole () #19 0xd055c7e4 in kdb_trap () #20 0xd056d007 in trap () #21 0xd0200b31 in alltraps () #22 0xd055c5f7 in Debugger () #23 0xd03d2d81 in panic () #24 0xd03d050f in pool_do_get () #25 0xd03cfdff in pool_get () #26 0xd03e7681 in m_clget () #27 0xd02c56c6 in ath_getmbuf () ---Type return to continue, or q return to quit--- #28 0xd02c57ed in ath_rxbuf_init () #29 0xd02c5eec in ath_rx_proc () #30 0xd02c2d84 in ath_intr1 () #31 0xd055f168 in intr_handler () #32 0xd0202742 in Xintr_ioapic2 () OpenBSD 5.6-current (GENERIC.MP) #381: Sun Oct 12 15:53:21 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF real mem = 2137354240 (2038MB) avail mem = 2090033152 (1993MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 04/18/07, BIOS32 rev. 0 @ 0xfd690, SMBIOS rev. 2.4 @ 0xe0010 (67 entries) bios0: vendor LENOVO version 7BETC9WW (2.10 ) date 04/18/2007 bios0: LENOVO 1705CTO acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 97 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4629 serial 327 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) bios0: ROM list: 0xc/0xea00! 0xcf000/0x1000 0xd/0x1000 0xdc000/0x4000! 0xe/0x1! cpu0:
Re: HEADS-UP: issues with chromium in -current
Marc Espie, 23 Oct 2014 12:14: This has been discussed internally, but chromium is partly broken these days. Most specifically, windows refresh does strange things under some circumstances. my funny story is with dual head under openbox. when i switch back to the virtual desktop where chrome is, it is gone. until i mouse over it, then it reappears. quite the hide and seek game. Outside of OpenBSD, most people don't use primitive window managers, so they don't see the issue. as 99% of the primitive window managers are developed outside of openbsd, i'd say that is a contradiction. -f -- never test for an error you don't know how to handle.
Re: HEADS-UP: issues with chromium in -current
On 23 October 2014, Marc Espie es...@nerim.net wrote: This has been discussed internally, but chromium is partly broken these days. Most specifically, windows refresh does strange things under some circumstances. The circumstances are well-known (thanks to matthieu@): modern systems use some composition manager for eye-candy on their display. So if you're using a shiny window manager, you won't see an issue. Old-style window managers, such as fvwm, fvwm2 (from ports) and cwm don't. Hence the breakage. Work-around: start a composition manager, such as xcompmgr from base xenocara. Cry since you lost your background image or moire pattern (fvwm-root, from ports, does know about composition managers). We're currently in the process of reporting the problem upstream. According to Linux guys, there's a world of pain in that general direction: http://www.iuculano.it/linux/apt-get-purge-chromium/ Some of the comments there are enlightening too. Outside of OpenBSD, most people don't use primitive window managers, so they don't see the issue. It probably started around when chromium switched to Aura for its gfx system... Regards, Liviu Daia
Re: is this normal or problematic?
On Thu, Oct 23, 2014 at 06:55:11PM +0200, Peter J. Philipp wrote: I have a tcpdump set in the background on OpenBSD 5.5-current from: mercury$ sysctl kern.version kern.version=OpenBSD 5.5-current (MERCURY.MP) #2: Sat Jun 21 08:24:41 What (and why) did you change in GENERIC.MP?
Re: is this normal or problematic?
On 10/23/14 21:10, Mike Larkin wrote: On Thu, Oct 23, 2014 at 06:55:11PM +0200, Peter J. Philipp wrote: I have a tcpdump set in the background on OpenBSD 5.5-current from: mercury$ sysctl kern.version kern.version=OpenBSD 5.5-current (MERCURY.MP) #2: Sat Jun 21 08:24:41 What (and why) did you change in GENERIC.MP? Oh that's the patched version with the /sys/dev/ic/ahci.c revision 1.14 patch if I recall correctly. I don't remember the details but I think I was left satisfied that a /bsd.rd would boot and didn't update the system. Cheers! -peter
Libretto 70CT
Hi Sebastian, I've just installed -current on my Libretto 70CT - as you can see from the output below it stoped with: kernel: integer divide fault trap, code=0 Rebooted it and disable it, schsio and softraid and it has now made it to the end of boot - but it has not yet made it to a login prompt. Last time I tried this I left it running for about a week - and still did not make it to a login prompt. hth Fred PS I've CC misc@ for the archives rather than clog up ports@ Script started on Thu Oct 23 21:10:34 2014 port:fred ~ cu -l /dev/cuaU0 Connected to /dev/cuaU0 (speed 9600) OpenBSD/i386 BOOT 3.26 boot \|/-\|/booting hd0a:/bsd: -\|/-9699132\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\+1067500 [72+403280|/-\|/-\|/-\|/-\|/-\|/-\+397651|/-\|/-\|/-\|/-\|/-\|/-\|]=0xb083b0 entry point at 0x200120 [ using 801416 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.6-current (GENERIC) #415: Wed Oct 22 11:33:32 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 121 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX real mem = 16412672 (15MB) avail mem = 3915776 (3MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/11/97 apm0 at bios0: Power Management spec V1.2 pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xe4000/0xc000 cpu0 at mainbus0: (uniprocessor) cpu0: F00F bug workaround installed isa0 at mainbus0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 vga0 at isa0 port 0x3b0/48 iomem 0xa/131072 wsdisplay0 at vga0 mux 1: console (80x25, vt100 emulation), using wskbd0 wsdisplay0: screen 1-5 added (80x25, vt100 emulation) wdc0 at isa0 port 0x1f0/8 irq 14 wd0 at wdc0 channel 0 drive 0: IBM-DDLA-21620 wd0: 16-sector PIO, LBA, 1551MB, 3177216 sectors wd0(wdc0:0:0): using BIOS timings sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v3.01 midi0 at sb0: SB MIDI UART audio0 at sb0 opl at sb0 not configured wss0 at isa0 port 0x530/8 irq 10 drq 0: CS4231 or AD1845 (vers 4) audio1 at wss0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pcic0 at isa0 port 0x3e0/2 iomem 0xd/65536 pcic0 controller 0: Intel 82365SL rev 1 has sockets A and B pcmcia0 at pcic0 controller 0 socket 0 xe0 at pcmcia0 function 0 Xircom, CreditCard 10Base-T, PS-CE2-10 port 0x340/16, irq 9: address 00:80:c7:42:37:d9 pcmcia1 at pcic0 controller 0 socket 1 pcic0: irq 11, polling enabled vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets kernel: integer divide fault trap, code=0 Stopped at cpu_switchto+0x64: popl%ebx ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND 13605 0 0 0 2 0x14200crypto 21232 0 0 0 2 0x14200pfpurge 18646 0 0 0 2 0x14200pcic0,0,1 14390 0 0 0 2 0x14200pcic0,0,0 28330 0 0 0 2 0x14200apm0 1636 0 0 0 2 0x14200systqmp 12593 0 0 0 2 0x14200systq 9503 0 0 0 2 0x14200syswq 25602 0 0 0 1 0x14200idle0 2351 0 0 0 2 0x14200kmthread *1 0 0 0 7 0swapper 0 -1 0 0 3 0x10200 wdccmdswapper ddb trace cpu_switchto(d0e91014,d0e91000,d0d0af18,d03bc36c,0) at cpu_switchto+0x64 (null)(102,0,0,0,0) at 0xcdb22063 ddb machine sysregs acpi ddb machine sysregs idtr: 0xf0621fc8/07ff gdtr: 0xd037f060c000/ ldtr: 0x0018 tr: 0x0070 cr0:0x8001003b cr2:0x cr3:0x00faa000 cr4:0x ddb machie e ne acpi disasm showval
Re: HEADS-UP: issues with chromium in -current
On 2014-10-23, David Coppa dco...@gmail.com wrote: On Thu, Oct 23, 2014 at 3:06 PM, Stephane Tougard steph...@unices.org wrote: On Thu, Oct 23, 2014 at 01:04:04PM +0200, David Coppa wrote: I'm using Slackware 14.1 with fvwm2 and Chromium, I see no issue at all. fvwm2 with or without a compositor (like xcompmgr or compton)? BTW has anyone looked at writing a port for compton? It is meant to be much better than xcompmgr (from which it originally derived). Original version of the Slackware. xcompmgr is as well originally part of Slackware. And what version of chromium? 33 This is an older (still gtk+2 based) version of chromium: it doesn't have this bug. The bug started manifesting itself, when they switched to the new Aura toolkit (since version 37 iirc). It happened _after_ the switch to Aura which was in 36.0.1985.125 which is the version that will be in 5.6 release packages, that one was ok. Looking at chat logs, I first mentioned it in September, and I recall that the problem definitely existed with the version immediately before the use GPU accelerated cross process image transport on openbsd as well commit - as I was hoping that might fix it :-). I'm not totally sure because of the lock and lack of snapshots, but I think 36.0.1985.143 is probably okay.
Re: 2 VoIP phones on one line
On 2014-10-23, Rod Whitworth glis...@witworx.com wrote: Years ago I bought a Minitar VoIP ATA and it was great. Then SWMBO wanted one too and I set up siproxd which mostly worked. Then I go two global IPs and put one ATA/Phone on each. Perfect! No Siproxd! Now I am about to need those 2 IPs. Neither phone needs to recieve incoming calls. Anybody using some of the more recent additions inthe Telephony ports? Ones to avoid or ones to love? Thanx, I would first try it with standard NAT. It depends on the exact setup on both sides, but it's common for VoIP providers these days to handle various NAT based configurations in their border controllers or SIP servers - the first troubleshooting step from their side would often be to *disable* any nat helpers. If that's no good, try restricting each ATA/phone to a different RTP port range and port-forward them.
Re: multiple calls to OpenSSL_add_all_algorithms
On 10/23/14 11:33, Stuart Henderson wrote: On 2014-10-22, Martijn van Duren martijn...@gmail.com wrote: I'm currently trying to write a library that heavily relies on libcrypto. Because I don't want applications linking to it, to have to call OpenSSL_add_all_algorithms, for convenience, I added those calls to the appropriate places in my library. Because of this nature, the function is called multiple times, and even if I shielded it within my library it could still be called outside of it by an application using my library. fwiw, Asterisk ran into this, this was the result: http://reviewboard.asterisk.org/r/1006/ To me it sounds like something that would be nice to see fixed in libressl. I'm by far an expert in this code, so this is pretty much a shot in the dark, but when I added an extra NULL-check to obj_name_cmp it resolved my problem and the application didn't crash anymore, nor did I notice any (new) strange behavior in the regress tests of my library, nor in the libcrypto regress test. Although I do suspect that the problem itself lays somewhere else in the libcrypto source, and that n1-data shouldn't be NULL in the first place. Attached is the my patch for completeness and I hope that someone on this list can could look into this further or point me in the right direction. Sincerely, Martijn van Duren [demime 1.01d removed an attachment of type text/x-patch which had a name of o_names.diff]
Re: Libretto 70CT
On Thu, Oct 23, 2014 at 09:59:04PM +0100, Fred wrote: Hi Sebastian, I've just installed -current on my Libretto 70CT - as you can see from the output below it stoped with: kernel: integer divide fault trap, code=0 Rebooted it and disable it, schsio and softraid and it has now made it to the end of boot - but it has not yet made it to a login prompt. Last time I tried this I left it running for about a week - and still did not make it to a login prompt. hth Fred PS I've CC misc@ for the archives rather than clog up ports@ Script started on Thu Oct 23 21:10:34 2014 port:fred ~ cu -l /dev/cuaU0 Connected to /dev/cuaU0 (speed 9600) OpenBSD/i386 BOOT 3.26 boot \|/-\|/booting hd0a:/bsd: -\|/-9699132\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\+1067500 [72+403280|/-\|/-\|/-\|/-\|/-\|/-\+397651|/-\|/-\|/-\|/-\|/-\|/-\|]=0xb083b0 entry point at 0x200120 [ using 801416 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.6-current (GENERIC) #415: Wed Oct 22 11:33:32 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 121 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX real mem = 16412672 (15MB) avail mem = 3915776 (3MB) For what it's worth, 16MB doesn't appear to be enough anymore. qemu with 16MB hangs at the same place as you're reporting, but configuring it for 20MB RAM seems to boot ok. It's pretty slow but it does work. -ml mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/11/97 apm0 at bios0: Power Management spec V1.2 pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xe4000/0xc000 cpu0 at mainbus0: (uniprocessor) cpu0: F00F bug workaround installed isa0 at mainbus0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 vga0 at isa0 port 0x3b0/48 iomem 0xa/131072 wsdisplay0 at vga0 mux 1: console (80x25, vt100 emulation), using wskbd0 wsdisplay0: screen 1-5 added (80x25, vt100 emulation) wdc0 at isa0 port 0x1f0/8 irq 14 wd0 at wdc0 channel 0 drive 0: IBM-DDLA-21620 wd0: 16-sector PIO, LBA, 1551MB, 3177216 sectors wd0(wdc0:0:0): using BIOS timings sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v3.01 midi0 at sb0: SB MIDI UART audio0 at sb0 opl at sb0 not configured wss0 at isa0 port 0x530/8 irq 10 drq 0: CS4231 or AD1845 (vers 4) audio1 at wss0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pcic0 at isa0 port 0x3e0/2 iomem 0xd/65536 pcic0 controller 0: Intel 82365SL rev 1 has sockets A and B pcmcia0 at pcic0 controller 0 socket 0 xe0 at pcmcia0 function 0 Xircom, CreditCard 10Base-T, PS-CE2-10 port 0x340/16, irq 9: address 00:80:c7:42:37:d9 pcmcia1 at pcic0 controller 0 socket 1 pcic0: irq 11, polling enabled vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets kernel: integer divide fault trap, code=0 Stopped at cpu_switchto+0x64: popl%ebx ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND 13605 0 0 0 2 0x14200crypto 21232 0 0 0 2 0x14200pfpurge 18646 0 0 0 2 0x14200pcic0,0,1 14390 0 0 0 2 0x14200pcic0,0,0 28330 0 0 0 2 0x14200apm0 1636 0 0 0 2 0x14200systqmp 12593 0 0 0 2 0x14200systq 9503 0 0 0 2 0x14200syswq 25602 0 0 0 1 0x14200idle0 2351 0 0 0 2 0x14200kmthread *1 0 0 0 7 0swapper 0 -1 0 0 3 0x10200 wdccmdswapper ddb trace
Re: Libretto 70CT
On 10/23/14 23:30, Mike Larkin wrote: On Thu, Oct 23, 2014 at 09:59:04PM +0100, Fred wrote: Hi Sebastian, I've just installed -current on my Libretto 70CT - as you can see from the output below it stoped with: kernel: integer divide fault trap, code=0 Rebooted it and disable it, schsio and softraid and it has now made it to the end of boot - but it has not yet made it to a login prompt. Last time I tried this I left it running for about a week - and still did not make it to a login prompt. hth Fred PS I've CC misc@ for the archives rather than clog up ports@ Script started on Thu Oct 23 21:10:34 2014 port:fred ~ cu -l /dev/cuaU0 Connected to /dev/cuaU0 (speed 9600) OpenBSD/i386 BOOT 3.26 boot \|/-\|/booting hd0a:/bsd: -\|/-9699132\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\+1067500 [72+403280|/-\|/-\|/-\|/-\|/-\|/-\+397651|/-\|/-\|/-\|/-\|/-\|/-\|]=0xb083b0 entry point at 0x200120 [ using 801416 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.6-current (GENERIC) #415: Wed Oct 22 11:33:32 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 121 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX real mem = 16412672 (15MB) avail mem = 3915776 (3MB) For what it's worth, 16MB doesn't appear to be enough anymore. qemu with 16MB hangs at the same place as you're reporting, but configuring it for 20MB RAM seems to boot ok. It's pretty slow but it does work. -ml Memory is definately an issue on my Libretto 70CT - but I think there might be more to it especially when you go back to 4.4 when if first displayed this issue... I might consign it to OpenBSD 4.3 :~) Cheers Fred
The Dao of pf?
Hi all, I'm getting set to build my third OpenBSD/pf firewall/NAT/router. The first two I did with a lot of research and trial and error. This time, I'd like to understand what I'm doing a little more. What are some broad principles of pf? Does pf have an overarching philosophy or architecture? Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance
Re: 2 VoIP phones on one line
On Thu, 23 Oct 2014 21:24:56 + (UTC), Stuart Henderson wrote: On 2014-10-23, Rod Whitworth glis...@witworx.com wrote: Years ago I bought a Minitar VoIP ATA and it was great. Then SWMBO wanted one too and I set up siproxd which mostly worked. Then I go two global IPs and put one ATA/Phone on each. Perfect! No Siproxd! Now I am about to need those 2 IPs. Neither phone needs to recieve incoming calls. Anybody using some of the more recent additions inthe Telephony ports? Ones to avoid or ones to love? Thanx, I would first try it with standard NAT. It depends on the exact setup on both sides, but it's common for VoIP providers these days to handle various NAT based configurations in their border controllers or SIP servers - the first troubleshooting step from their side would often be to *disable* any nat helpers. If that's no good, try restricting each ATA/phone to a different RTP port range and port-forward them. None of the STUN etc that have arrived, since I last looked, any good? Thanx. *** NOTE *** Please DO NOT CC me. I am subscribed to the list. Mail to the sender address that does not originate at the list server is tarpitted. The reply-to: address is provided for those who feel compelled to reply off list. Thankyou. Rod/ --- This life is not the real thing. It is not even in Beta. If it was, then OpenBSD would already have a man page for it.
Re: The Dao of pf?
On 23-10-2014 21:49, Steve Litt wrote: I'm getting set to build my third OpenBSD/pf firewall/NAT/router. The first two I did with a lot of research and trial and error. Don't worry about this. Even if you read the documentation you'll need to try and test your rules. This time, I'd like to understand what I'm doing a little more. What are some broad principles of pf? Does pf have an overarching philosophy or architecture? I can point you to this: http://bulabula.org/papers/2013/rubsd/ I believe this is one of the latest papers regarding the future of pf. Also, besides the excellent manual pages, and the pf user guide on the openbsd site, there is a great book by Peter Hansteen: http://www.bsdly.net/~peter/ Besides this, perhaps Henning could weigh in. But as far as I know the principles of pf are the same of the OpenBSD project: security. Even more, given it's a packet filter. Cheers [demime 1.01d removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
Question about FAQ section 10.3
Processes local and package scripts in /etc/rc.d is listed as the last thing rc does after boot. What does Processes mean in this context? Naively I would think this means that the scripts are all executed. But that seems odd in this context as most of (all of?) the scripts take an argument that they pass to rc_cmd from rc.subr, and rc is not passing start to all those scripts. Looking at https://en.wikipedia.org/wiki/Init it seems my naive assumption is correct, but why run all those scripts? I am puzzled. Worik -- Why is the legal status of chardonnay different to that of cannabis? worik.stan...@gmail.com 021-1680650, (03) 4821804 Aotearoa (New Zealand)
Re: Question about FAQ section 10.3
On 10/23/14 21:36, worik wrote:
Processes local and package scripts in /etc/rc.d is listed as the last
thing rc does after boot.
What does Processes mean in this context?
like processing food -- do whatever needs to be done.
(not my best analogy, I'll admit)
But yeah. run the scripts that are indicated as needing to be run, they
do whatever they need to do. USUALLY start daemons, but could be lots
of other things, too.
Naively I would think this means that the scripts are all executed. But
that seems odd in this context as most of (all of?) the scripts take an
argument that they pass to rc_cmd from rc.subr, and rc is not passing
start to all those scripts.
why do you say that?
Look at the /etc/rc script...yes it does execute each of the rc.d
scripts, and yes it DOES pass start to them:
start_daemon()
{
local _n
for _n; do
eval _do=\${${_n}_flags}
if [ X${_do} != XNO ]; then
/etc/rc.d/${_n} start # - start!!
fi
done
}
now look how start_daemon is invoked...
Looking at https://en.wikipedia.org/wiki/Init it seems my naive
assumption is correct, but why run all those scripts?
um. because that's how we do it?
Before 4.9 or so...we hard-coded the startup process for each daemon in
/etc/rc, we decided to switch to the rc.d process for some additional
flexibility.
I'll admit I was dubious when it was first done, fearing we might be
heading down the idiotic everything.d directories that many Linux
distros are now doing, but it turns out I rather like it.
Nick.
Re: Libretto 70CT
On 10/23/14 19:17, Fred wrote: On 10/23/14 23:30, Mike Larkin wrote: On Thu, Oct 23, 2014 at 09:59:04PM +0100, Fred wrote: Hi Sebastian, I've just installed -current on my Libretto 70CT - as you can see from the output below it stoped with: kernel: integer divide fault trap, code=0 Rebooted it and disable it, schsio and softraid and it has now made it to the end of boot - but it has not yet made it to a login prompt. Last time I tried this I left it running for about a week - and still did not make it to a login prompt. hth Fred PS I've CC misc@ for the archives rather than clog up ports@ Script started on Thu Oct 23 21:10:34 2014 port:fred ~ cu -l /dev/cuaU0 Connected to /dev/cuaU0 (speed 9600) OpenBSD/i386 BOOT 3.26 boot \|/-\|/booting hd0a:/bsd: -\|/-9699132\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\+1067500 [72+403280|/-\|/-\|/-\|/-\|/-\|/-\+397651|/-\|/-\|/-\|/-\|/-\|/-\|]=0xb083b0 entry point at 0x200120 [ using 801416 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.6-current (GENERIC) #415: Wed Oct 22 11:33:32 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 121 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX real mem = 16412672 (15MB) avail mem = 3915776 (3MB) For what it's worth, 16MB doesn't appear to be enough anymore. qemu with 16MB hangs at the same place as you're reporting, but configuring it for 20MB RAM seems to boot ok. It's pretty slow but it does work. -ml Memory is definately an issue on my Libretto 70CT - but I think there might be more to it especially when you go back to 4.4 when if first displayed this issue... I might consign it to OpenBSD 4.3 :~) Really, that's about when 16M became Just Too Little, it has been a long time. And...you know, I'm not going to apologize for that. :) 2.7 worked pretty well on 16M RAM, iirc. By 3.4, I'm pretty sure you were swapping before you completed a login. As a labor of love, you could strip a lot of stuff out of the kernel and see if you could make something that worked, but it really isn't worth it. Nick.
Re: Question about FAQ section 10.3
On 24/10/14 14:53, Nick Holland wrote: On 10/23/14 21:36, worik wrote: Processes local and package scripts in /etc/rc.d is listed as the last thing rc does after boot. What does Processes mean in this context? like processing food -- do whatever needs to be done. (not my best analogy, I'll admit) [snip] Look at the /etc/rc script...yes it does execute each of the rc.d scripts, and yes it DOES pass start to them: [snip] now look how start_daemon is invoked... Interesting. In /etc/rc start_daemon is called for specific named scripts. Except that (at line 520) it runs it for all scripts in $pkg_scripts My shell scripting is really bad (I am going to have to up my game there if I am going to stick around here) but it seems it is set to an empty string in rc.conf (Mis)reading the FAQ I thought it meant *all* scripts in /etc/rc.d were Processed. . It actually says ...local and packaged scripts So if a package wants to be sure it is run at startup does it write that into the rc.conf where mine says... # rc.d(8) packages scripts # started in the specified order and stopped in reverse order pkg_scripts= I installed postgresql (with pkg_add) and it did not change this, I had to change /etc/rc.local by hand. Is there some reason why postgresql should not be started after a reboot? Have I completely got the wrong end of the stick? Worik Looking at https://en.wikipedia.org/wiki/Init it seems my naive assumption is correct, but why run all those scripts? um. because that's how we do it? Before 4.9 or so...we hard-coded the startup process for each daemon in /etc/rc, we decided to switch to the rc.d process for some additional flexibility. I'll admit I was dubious when it was first done, fearing we might be heading down the idiotic everything.d directories that many Linux distros are now doing, but it turns out I rather like it. Nick. -- Why is the legal status of chardonnay different to that of cannabis? worik.stan...@gmail.com 021-1680650, (03) 4821804 Aotearoa (New Zealand) I voted for love [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: The Dao of pf?
Steve Litt wrote: This time, I'd like to understand what I'm doing a little more. What are some broad principles of pf? Does pf have an overarching philosophy or architecture? Read the book :) http://www.amazon.com/Book-PF-No-Nonsense-OpenBSD-Firewall/dp/1593275897/ref=asap_B001JPCK0S_1_1?s=booksie=UTF8qid=1414126274sr=1-1 -- Jack Woehr # There's too much emphasis on things Box 51, Golden CO 80402 # like pawn structure in modern chess. http://www.softwoehr.com # Checkmate ends the game. - N. Short
