search for: msg00542

...79EBB: read_message (xs.c:1143) > ==5722== by 0x427A89B: read_thread (xs.c:1219) > ==5722== by 0x40E7953: start_thread (pthread_create.c:304) > ==5722== by 0x41CF95D: clone (clone.S:130) I've posted a fix for this upstream: http://lists.xen.org/archives/html/xen-devel/2014-11/msg00542.html I've requested that it go into the next 4.4.x release. I also plan to backport it to the package regardless once it is accepted into the dev branch. Ian.

On 11/06/2014 09:12 AM, Ian Campbell wrote: > I've posted a fix for this upstream: > http://lists.xen.org/archives/html/xen-devel/2014-11/msg00542.html > > I've requested that it go into the next 4.4.x release. I also plan to > backport it to the package regardless once it is accepted into the dev > branch. > > Ian. So I've tried building xen 4.4.1-3 with this patch (attached), and I replaced the binary packages li...

On Wed, 2014-10-29 at 17:36 -0400, Gedalya wrote: > When booting domU's running amd64 jessie, I notice some memory problems > with xl. I ran it (actually, upstream staging-4.4) under valgrind and it reported after a reboot: ==5722== 24 bytes in 1 blocks are definitely lost in loss record 35 of 72 ==5722== at 0x4026B2D: malloc (vg_replace_malloc.c:299) ==5722== by 0x41739FF:

On Fri, 2014-11-07 at 21:32 -0500, Gedalya wrote: > On 11/06/2014 09:12 AM, Ian Campbell wrote: > > I've posted a fix for this upstream: > > http://lists.xen.org/archives/html/xen-devel/2014-11/msg00542.html > > > > I've requested that it go into the next 4.4.x release. I also plan to > > backport it to the package regardless once it is accepted into the dev > > branch. > > > > Ian. > > So I've tried building xen 4.4.1-3 with this patch (attached)...