> On Oct 30, 2015, at 01:42, Dag-Erling Smørgrav wrote:
>
> David Wolfskill writes:
>> ...
>> bound to 172.17.1.245 -- renewal in 43200 seconds.
>> pid 544 (ntpd), uid 0: exited on signal 11 (core dumped)
>> Starting Network: lo0 em0 iwn0 lagg0.
>> ...
>
>
NGie Cooper writes:
> Dag-Erling Smørgrav writes:
> > David Wolfskill writes:
> > > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped)
> > Did you find a solution? [...]
> https://svnweb.freebsd.org/changeset/base/287591 ?
Are
David Wolfskill writes:
> ...
> bound to 172.17.1.245 -- renewal in 43200 seconds.
> pid 544 (ntpd), uid 0: exited on signal 11 (core dumped)
> Starting Network: lo0 em0 iwn0 lagg0.
> ...
Did you find a solution? I'm wondering if the ntpd problems people are
reporting on
On 10/30/2015 1:57 PM, NGie Cooper wrote:
> Hi Bryan/Simon!
> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
> and I ran into this linker issue below. I have no idea (yet) why it’s trying
> to compile an x64 object when I specify powerpc/powerpc — and more
>
Hi Bryan/Simon!
I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
and I ran into this linker issue below. I have no idea (yet) why it’s trying to
compile an x64 object when I specify powerpc/powerpc — and more importantly,
why is the object not being put in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL on head has been updated to 1.0.2d. Please make sure to
recompile all binaries depending on libcrypto.so.7 or libssl.so.7.
Cheers!
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
On 10/30/2015 2:21 PM, Bryan Drewery wrote:
> On 10/30/2015 1:57 PM, NGie Cooper wrote:
>> Hi Bryan/Simon!
>> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
>> and I ran into this linker issue below. I have no idea (yet) why it’s trying
>> to compile an x64 object when
On Fri, Oct 30, 2015 at 04:01:27PM -0700, Bryan Drewery wrote:
> On 10/30/2015 3:03 PM, NGie Cooper wrote:
> > On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote:
> >> On 10/30/2015 2:21 PM, Bryan Drewery wrote:
> >>> On 10/30/2015 1:57 PM, NGie Cooper wrote:
> Hi
On 10/30/2015 4:08 PM, Mark Johnston wrote:
> On Fri, Oct 30, 2015 at 04:01:27PM -0700, Bryan Drewery wrote:
>> On 10/30/2015 3:03 PM, NGie Cooper wrote:
>>> On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote:
On 10/30/2015 2:21 PM, Bryan Drewery wrote:
> On
Franco Fichtner writes:
> Well, it’s on stable/10 since September 16 and somebody reported that
> this particular branch would not trigger the crash along with HEAD,
> but any 10.x would. Can’t find the reference right now though.
OK, we should do an EN with that patch
> On Oct 30, 2015, at 02:32, Franco Fichtner wrote:
>
> Well, it’s on stable/10 since September 16 and somebody reported that
> this particular branch would not trigger the crash along with HEAD,
> but any 10.x would. Can’t find the reference right now though.
You’re
Well, it’s on stable/10 since September 16 and somebody reported that
this particular branch would not trigger the crash along with HEAD,
but any 10.x would. Can’t find the reference right now though.
> On 30 Oct 2015, at 10:24 am, NGie Cooper wrote:
>
>
>> On Oct 30,
On 10/30/15 09:32, Franco Fichtner wrote:
> Well, it’s on stable/10 since September 16 and somebody reported that
> this particular branch would not trigger the crash along with HEAD,
> but any 10.x would. Can’t find the reference right now though.
That was me, amongst others. There are threads
> On Oct 30, 2015, at 02:05, Dag-Erling Smørgrav wrote:
>
> NGie Cooper writes:
>> Dag-Erling Smørgrav writes:
>>> David Wolfskill writes:
pid 544 (ntpd), uid 0: exited on signal 11 (core dumped)
>>> Did you find a
Hi all,
I did a quick test build and this seems to solve the ntpd crash issue
on top of releng/10.1.
Cheers,
Franco
> On 30 Oct 2015, at 10:09 am, NGie Cooper wrote:
>
>
>> On Oct 30, 2015, at 02:05, Dag-Erling Smørgrav wrote:
>>
>> NGie Cooper
> On Oct 30, 2015, at 02:18, Franco Fichtner wrote:
>
> Hi all,
>
> I did a quick test build and this seems to solve the ntpd crash issue
> on top of releng/10.1.
Makes sense … looking through my email r287591 was never MFCed back to stable/9
or stable/10 :/ .
HTH,
Unsubscribe me please
-Original Message-
From: owner-freebsd-curr...@freebsd.org
[mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of
freebsd-current-requ...@freebsd.org
Sent: 30 October 2015 12:00
To: freebsd-current@freebsd.org
Subject: freebsd-current Digest, Vol 627, Issue 5
Hiya,
Here's a panic from arptimer:
(kgdb) bt
#0 doadump (textdump=0) at pcpu.h:221
#1 0x803666b6 in db_fncall (dummy1=,
dummy2=, dummy3=,
dummy4=) at
/usr/home/adrian/work/freebsd/head/src/sys/ddb/db_command.c:568
#2 0x8036614e in db_command (cmd_table=0x0) at
NGie Cooper wrote:
> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
> and I ran into this linker issue below. I have no idea (yet) why it’s trying
> to compile an x64 object when I specify powerpc/powerpc — and more
> importantly, why is the
On 10/29/2015 16:56, Bryan Drewery wrote:
> On 10/29/2015 9:46 AM, Bryan Drewery wrote:
>> On 10/29/15 9:42 AM, Eric van Gyzen wrote:
>>> On 10/29/2015 11:25, Bryan Drewery wrote:
# ifconfig
igb0: flags=8843 metric 0 mtu 1500
On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote:
> On 10/30/2015 2:21 PM, Bryan Drewery wrote:
>> On 10/30/2015 1:57 PM, NGie Cooper wrote:
>>> Hi Bryan/Simon!
>>> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
>>> and I ran into this linker
On 10/30/2015 3:03 PM, NGie Cooper wrote:
> On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote:
>> On 10/30/2015 2:21 PM, Bryan Drewery wrote:
>>> On 10/30/2015 1:57 PM, NGie Cooper wrote:
Hi Bryan/Simon!
I tried doing buildworld on powerpc/powerpc with
30.10.2015, 00:57, "Bryan Drewery" :
> On 10/29/2015 9:46 AM, Bryan Drewery wrote:
>> On 10/29/15 9:42 AM, Eric van Gyzen wrote:
>>> On 10/29/2015 11:25, Bryan Drewery wrote:
# ifconfig
igb0: flags=8843 metric 0 mtu 1500
FreeBSD_HEAD_amd64_gcc4.9 - Build #719 - Fixed:
Build information:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/719/
Full change log:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/719/changes
Full build log:
On Fri, Oct 30, 2015 at 4:09 PM, Bryan Drewery wrote:
...
> The example output must be a mistake as they are correct on ref11:
>
> ref11-amd64% find
> /scratch/tmp/ngie/obj/*/scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json
> -name tst.usdt.o -exec file {} +
>
Not sure if it's the same issue, but it sure looks like it is.
I have upgraded a couple of hosts (amd64) from 10.2-RELEASE-p5
to 10.2-RELEASE-p6, i.e. the freebsd-upgrade essentially just
replaced the /usr/sbin/ntpd with a new one; then I restarted
the ntpd.
On all host but one this was
On Fri, Oct 30, 2015 at 09:42:07AM +0100, Dag-Erling Smørgrav wrote:
> David Wolfskill writes:
> > ...
> > bound to 172.17.1.245 -- renewal in 43200 seconds.
> > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped)
> > Starting Network: lo0 em0 iwn0 lagg0.
> > ...
>
>
27 matches
Mail list logo