Re: DigitalOcean offers VMs with FreeBSD!
On Fri, Jan 16, 2015 at 7:13 AM, Lyndon Nerenberg wrote: > Beware that they (DO) do not at all grok ipv6. They hand out /124s, or > something equally silly. > My DO instance has /64 and I have no problems with using ipv6 to login. --Nikolay ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: DigitalOcean offers VMs with FreeBSD!
On Fri, 16 Jan 2015, Jamie Landeg-Jones wrote: > Bernhard Fröhlich wrote: > > I don't know what's unusual with the DO virtualisation, but vultr just > works like a normal server (though they do restrict to virtio devices > where applicable rather than emulated harware) They use Avahi for autodisovery of the IPv4 "link layer" address to further boostrap the configuration. Unfortuately avahi-autoipd seems to needs lots of dependencies, including gobject-introspection. bsd-cloudinit is written in Python and they use it to get a proper IPv4 addresses. This configuration gets sucked into rc. On Fri, 16 Jan 2015, Nikolay Denev wrote: > On Fri, Jan 16, 2015 at 7:13 AM, Lyndon Nerenberg wrote: > > > Beware that they (DO) do not at all grok ipv6. They hand out /124s, or > > something equally silly. > > > > My DO instance has /64 and I have no problems with using ipv6 to login. It's /64 formally here, but I am told only to use 16 (sixteen) addresses :2000 ... :200f Sounds like neighbour discovery scalability issues? //Marcin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: DigitalOcean offers VMs with FreeBSD!
On Fri, Jan 16, 2015 at 10:38 AM, Marcin Cieslak wrote: > On Fri, 16 Jan 2015, Jamie Landeg-Jones wrote: > > > Bernhard Fröhlich wrote: > > > > I don't know what's unusual with the DO virtualisation, but vultr just > > works like a normal server (though they do restrict to virtio devices > > where applicable rather than emulated harware) > > They use Avahi for autodisovery of the IPv4 "link layer" address > to further boostrap the configuration. Unfortuately avahi-autoipd > seems to needs lots of dependencies, including gobject-introspection. > > bsd-cloudinit is written in Python and they use it to get a proper > IPv4 addresses. This configuration gets sucked into rc. > > On Fri, 16 Jan 2015, Nikolay Denev wrote: > > > On Fri, Jan 16, 2015 at 7:13 AM, Lyndon Nerenberg > wrote: > > > > > Beware that they (DO) do not at all grok ipv6. They hand out /124s, or > > > something equally silly. > > > > > > > My DO instance has /64 and I have no problems with using ipv6 to login. > > It's /64 formally here, but I am told only to use 16 (sixteen) addresses > :2000 ... :200f > > Sounds like neighbour discovery scalability issues? > > //Marcin > On the timecounter sysctl: unixbench with TSC-low: INDEX VALUES TESTBASELINE RESULT INDEX Dhrystone 2 using register variables116700.0 25145739.3 2154.7 Double-Precision Whetstone 55.0 4021.2 731.1 Execl Throughput43.0 2334.0 542.8 File Copy 1024 bufsize 2000 maxblocks 3960.0 1309.03.3 File Copy 256 bufsize 500 maxblocks 1655.0 353.02.1 File Copy 4096 bufsize 8000 maxblocks 5800.0 4771.08.2 Pipe Throughput 12440.0 1179433.3 948.1 Pipe-based Context Switching 4000.0 259704.9 649.3 Process Creation 126.0 8010.6 635.8 Shell Scripts (8 concurrent) 6.0 538.8 898.0 System Call Overhead 15000.0 987460.5 658.3 = FINAL SCORE 189.7 unixbench with HPET(default): INDEX VALUES TESTBASELINE RESULT INDEX Dhrystone 2 using register variables116700.0 24582513.8 2106.5 Double-Precision Whetstone 55.0 3941.6 716.7 Execl Throughput43.0 2275.7 529.2 File Copy 1024 bufsize 2000 maxblocks 3960.0 1102.02.8 File Copy 256 bufsize 500 maxblocks 1655.0 259.01.6 File Copy 4096 bufsize 8000 maxblocks 5800.0 4604.07.9 Pipe Throughput 12440.0 1186331.6 953.6 Pipe-based Context Switching 4000.0 255294.8 638.2 Process Creation 126.0 6451.6 512.0 Shell Scripts (8 concurrent) 6.0 445.8 743.0 System Call Overhead 15000.0 971475.1 647.7 = FINAL SCORE 173.0 --Nikolay ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
kernel: MCA: CPU 0 COR (1) internal parity error
Hello, I'm running since some days a recent -HEAD r276659 on an Acer C720 Chromebook which works very nicely and fast (I really have never seen such a fast KDE4 desktop). >From time to time (let's say 2-3 times a day) I see messages like this in /var/log/messages: Jan 16 12:04:24 c720-r276659 kernel: MCA: Bank 0, Status 0x904f0005 Jan 16 12:04:24 c720-r276659 kernel: MCA: Global Cap 0x0c07, Status 0x Jan 16 12:04:24 c720-r276659 kernel: MCA: Vendor "GenuineIntel", ID 0x40651, APIC ID 0 Jan 16 12:04:24 c720-r276659 kernel: MCA: CPU 0 COR (1) internal parity error the kernel is: # uname -a FreeBSD c720-r276659 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r276659M: Tue Jan 6 12:55:25 CET 2015 guru@vm-poudriere-r269739:/usr/local/acerC720/obj/usr/local/acerC720/src/sys/GENERIC i386 i.e. the i386 version (because I compile everything in a VM) Are the above messages really a hardware problem? Thanks matthias -- Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211 1989-2014: The Wall was torn down so that we go to war together again. El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez. Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel: MCA: CPU 0 COR (1) internal parity error
On 01/16/2015 14:45, Matthias Apitz wrote: > Jan 16 12:04:24 c720-r276659 kernel: MCA: Bank 0, Status 0x904f0005 > Jan 16 12:04:24 c720-r276659 kernel: MCA: Global Cap 0x0c07, > Status 0x > Jan 16 12:04:24 c720-r276659 kernel: MCA: Vendor "GenuineIntel", ID 0x40651, > APIC ID 0 > Jan 16 12:04:24 c720-r276659 kernel: MCA: CPU 0 COR (1) internal parity error Try ports/sysutils/mcelog. Eric ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel: MCA: CPU 0 COR (1) internal parity error
On Fri, 16 Jan 2015 20:45:39 +0100 Matthias Apitz wrote > Hello, > > I'm running since some days a recent -HEAD r276659 on an Acer C720 > Chromebook which works very nicely and fast (I really have never seen > such a fast KDE4 desktop). > > >From time to time (let's say 2-3 times a day) I see messages like this > in /var/log/messages: > > Jan 16 12:04:24 c720-r276659 kernel: MCA: Bank 0, Status 0x904f0005 > Jan 16 12:04:24 c720-r276659 kernel: MCA: Global Cap 0x0c07, > Status 0x Jan 16 12:04:24 c720-r276659 kernel: MCA: Vendor > "GenuineIntel", ID 0x40651, APIC ID 0 Jan 16 12:04:24 c720-r276659 kernel: > MCA: CPU 0 COR (1) internal parity error > > the kernel is: > > # uname -a > FreeBSD c720-r276659 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r276659M: Tue Jan > 6 12:55:25 CET 2015 > guru@vm-poudriere-r269739:/usr/local/acerC720/obj/usr/local/acerC720/src/sys/ > GENERIC i386 > > i.e. the i386 version (because I compile everything in a VM) > > Are the above messages really a hardware problem? Last time I saw this, it was cache on one of the CPU's going south (bad). My experience, anyway. --Chris > > Thanks > > matthias > > -- > Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211 > 1989-2014: The Wall was torn down so that we go to war together again. > El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez. > Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen. > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
1/17/2015 2:33:23 AM
http://bestsolutionroofing.com/mz/yxeakxokrkexzjpivfejou.wmmrrtknexcesb Joe Nosay 1/17/2015 2:33:23 AM ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
