Hi Bob, Hi Erich;
thanks for the profound work on this bug.
I've contacted the maintainer of uClibc-ng and received some homework to track
this issue. The proposed patch by by ddrown needs testing and if successful,
might be accepted.
kp
Am Mittwoch, 3. Mai 2017, 22:04:53 schrieb Erich Titl:
Hi Bob
(copying this to leaf-devel)
Sorry, I was too fast, I did not look into the i386 code but the one in
x86_64
Am 03.05.2017 um 20:03 schrieb Robert K Coffman Jr. -Info From Data Corp.:
Eric,
IRC user ddrown confirmed the x64 patch I mentioned earlier seems to fix
the issue on i386 as w
Hi Bob
(copying this to leaf-devel)
Am 03.05.2017 um 20:03 schrieb Robert K Coffman Jr. -Info From Data Corp.:
Eric,
IRC user ddrown confirmed the x64 patch I mentioned earlier seems to fix
the issue on i386 as well. I'm not really sure what to do with that
information. Is it possible to pat
Eric,
IRC user ddrown confirmed the x64 patch I mentioned earlier seems to fix
the issue on i386 as well. I'm not really sure what to do with that
information. Is it possible to patch Leaf with it?
https://gist.github.com/ddrown/15e943b8fe1da398320b0c0518c95554
- Bob
> So it really appears
I'm running 6.0.2-rc1 x86_64 and have been for months. I haven't had any
problems with ntpd (4.2.8p9).
John
On 02/05/17 16:56, Erich Titl wrote:
> Hi Bob
>
> Am 02.05.2017 um 17:52 schrieb Robert K Coffman Jr. -Info From Data Corp.:
>>> So now there have been a few releases between 5.1.3 and 6.
Hi Bob
Am 02.05.2017 um 17:52 schrieb Robert K Coffman Jr. -Info From Data Corp.:
So now there have been a few releases between 5.1.3 and 6.0.2. It might
be interesting to know if 5.2.8 still runs fine.
It appears to be fine, with uClibc 0.9.33.2 and ntpd 4.2.8p7.
I also loaded the current nt
> So now there have been a few releases between 5.1.3 and 6.0.2. It might
> be interesting to know if 5.2.8 still runs fine.
It appears to be fine, with uClibc 0.9.33.2 and ntpd 4.2.8p7.
I also loaded the current ntpd (4.2.8p10) on 5.2.8 and it works fine.
- Bob
---
Am 02.05.2017 um 16:31 schrieb Robert K Coffman Jr. -Info From Data Corp.:
Did you verify that uclibc and/or ntpd had any changes between the two
releases affected?
I'm using the i686 release.
If I run it under VMWare ESXi with two cores, it crashes. If I reduce
the cores to one, it works f
> Did you verify that uclibc and/or ntpd had any changes between the two
> releases affected?
I'm using the i686 release.
If I run it under VMWare ESXi with two cores, it crashes. If I reduce
the cores to one, it works fine. It seems to affect any machine I run
it on that has more than one co
Hi Bob
Am 02.05.2017 um 14:30 schrieb Robert K Coffman Jr. -Info From Data Corp.:
ddrown https://gist.github.com/ddrown/15e943b8fe1da398320b0c0518c95554
- I isolated this code out of ntpd and verified it has a race condition
under uclibc pthreads
ddrown this looks like a b
User ddrown on IRC looked into this, and confirmed he also experienced
this issue.
ddrown ok, ntpd works for me on leaf with one processor, trying it with two
ddrown yup, two processors = ntpd crash on leaf
ddrown ok, that's very odd
ddrown cd /usr/sbin ; ./ntpd -- wor
>> On HP DC7600 and using Bering-uClibc_6.0.2_i686_syslinux_vga, ntpd
>> segfaults at startup (even something like ntpd --version).
This appears to affect machines with multiple cores and/or machines with
a single core and hyperthreading. I am still looking into it, but I'd
like to hear from a
> On 4/27/2017 7:52 PM, Robert K Coffman Jr. -Info From Data Corp. wrote:
> On HP DC7600 and using Bering-uClibc_6.0.2_i686_syslinux_vga, ntpd
> segfaults at startup (even something like ntpd --version).
I'm working this with NTP people, however I have found this occurring
with the NTPD that sh
On HP DC7600 and using Bering-uClibc_6.0.2_i686_syslinux_vga, ntpd
segfaults at startup (even something like ntpd --version).
Seems to be something with that particular hardware, as I have other
machines with the same release loaded that are working fine.
I've examined the executables, package
14 matches
Mail list logo
