Re: API explosion (Re: [RFC/RFT] calloutng)

2012-12-22 Thread Poul-Henning Kamp
In message <2012125025.ga46...@stack.nl>, Jilles Tjoelker writes: >> Either way, such a facility should be layered on top of the callout >> facility, which should always run in "elapsed time"[1] with no attention >> paid to what NTPD might do to the UTC estimate. > >POSIX specifies fu

Re: API explosion (Re: [RFC/RFT] calloutng)

2012-12-22 Thread Jilles Tjoelker
On Wed, Dec 19, 2012 at 11:00:06AM +, Poul-Henning Kamp wrote: > > In message <50d192e8.3020...@freebsd.org>, Alexander Motin writes: > >Linux uses 32.32 format in their eventtimers code. > (And that is no accident, I know who they got the number from :-) > >But if at some point we

Re: protoc crash in libstdc++

2012-12-22 Thread Dimitry Andric
On 2012-12-18 22:12, George Liaskos wrote: Try removing --gc-sections from the link flags for protoc, that should solve it for now. I am still looking at the root cause, which seems to be something in our ld; it does not seem to be related to either clang or libstdc++. Whoa, thank you! Removin

Re: ipv6_addrs_IF aliases in rc.conf(5)

2012-12-22 Thread Kimmo Paasiala
On Sat, Dec 22, 2012 at 4:25 PM, Łukasz Wąsikowski wrote: > W dniu 2012-12-22 04:41, Kimmo Paasiala pisze: > It looks like the reason for the difference to ipv4_addrs_IF is that the "alias" parameter for ifconfig(8) operates differently for IPv6 addresses, the first address of an in

Re: ipv6_addrs_IF aliases in rc.conf(5)

2012-12-22 Thread Łukasz Wąsikowski
W dniu 2012-12-22 04:41, Kimmo Paasiala pisze: >>> It looks like the reason for the difference to ipv4_addrs_IF is that >>> the "alias" parameter for ifconfig(8) operates differently for IPv6 >>> addresses, the first address of an interface can't be added with >>> "alias", for IPv4 it does not car

Re: double fault [Was: clang compiled kernel panic when mounting zfs root on i386]

2012-12-22 Thread Dimitry Andric
On 2012-12-22 12:11, Andriy Gapon wrote: on 21/12/2012 18:38 Hans Petter Selasky said the following: I've built a 10-current i386 kernel as of today, and I see double fault when USB audio is allocating memory. Anyone knows why? kdb_enter() vpanic() panic() dblfault_handler() vm_map_lookup() vm_

Re: Fatal trap 1

2012-12-22 Thread Konstantin Belousov
On Sat, Dec 22, 2012 at 01:44:49PM +0200, Andriy Gapon wrote: > on 22/12/2012 13:21 Konstantin Belousov said the following: > > This is due to the vtoslab() returning NULL. Since slabref is dereferenced > > later, clang tries to be helpful as usual and converts the !(p->flags & > > PG_SLAB) case fr

Re: Fatal trap 1

2012-12-22 Thread Andriy Gapon
on 22/12/2012 13:21 Konstantin Belousov said the following: > This is due to the vtoslab() returning NULL. Since slabref is dereferenced > later, clang tries to be helpful as usual and converts the !(p->flags & > PG_SLAB) case from vtoslab() into the jump to un2 instruction if vtoslab() > result is

Re: Fatal trap 1 [Was: "Memory modified after free" - by whom?]

2012-12-22 Thread Konstantin Belousov
On Sat, Dec 22, 2012 at 01:08:10PM +0200, Andriy Gapon wrote: > on 22/12/2012 02:21 Garrett Cooper said the following: > > Fatal trap 1: privileged instruction fault while in kernel mode > > Fatal trap 1: privileged instruction fault while in kernel mode > > Unrelated to the original topic - this

double fault [Was: clang compiled kernel panic when mounting zfs root on i386]

2012-12-22 Thread Andriy Gapon
on 21/12/2012 18:38 Hans Petter Selasky said the following: > I've built a 10-current i386 kernel as of today, and I see double fault when > USB audio is allocating memory. Anyone knows why? > > kdb_enter() > vpanic() > panic() > dblfault_handler() > vm_map_lookup() > vm_fault_hold() > vm_fault()

Fatal trap 1 [Was: "Memory modified after free" - by whom?]

2012-12-22 Thread Andriy Gapon
on 22/12/2012 02:21 Garrett Cooper said the following: > Fatal trap 1: privileged instruction fault while in kernel mode > Fatal trap 1: privileged instruction fault while in kernel mode Unrelated to the original topic - this looks very weird. I mean all the CPUs getting this unusual trap... Could