On Tue, Sep 27, 2016 at 06:24:20PM +0200, Aurelien Jarno wrote:
> On 2016-09-27 16:00, Florian Weimer wrote:
> Ok. I have seen this change in 4.7.5:
>
> | commit bec4e55b55867ed948a3afd9f9ccf3506bfdad24
> | Author: Michal Hocko
> | Date: Thu Sep 1 16:14:41 2016 -0700
> |
> |
On 2016-09-27 16:00, Florian Weimer wrote:
> * Aurelien Jarno:
>
> > On 2016-09-27 13:44, Florian Weimer wrote:
> >> * Aurelien Jarno:
> >>
> >> > Hmm, rsync doesn't use libpthread, so that clearly rules out a
> >> > libpthread issue. That said, all the example you gave fail to allocate
> >> >
On 2016-09-27 15:22, Fernando Santagata wrote:
> On Tue, Sep 27, 2016 at 03:10:17PM +0200, Florian Weimer wrote:
> > * Fernando Santagata:
> >
> > >> Usually it manifests in premature OOM killer invocations, but maybe
> > >> something the reporter's system configuration changes that (perhaps it
>
* Aurelien Jarno:
> On 2016-09-27 13:44, Florian Weimer wrote:
>> * Aurelien Jarno:
>>
>> > Hmm, rsync doesn't use libpthread, so that clearly rules out a
>> > libpthread issue. That said, all the example you gave fail to allocate
>> > the memory correctly, either through malloc (glibc) or mmap
On Tue, Sep 27, 2016 at 03:10:17PM +0200, Florian Weimer wrote:
> * Fernando Santagata:
>
> >> Usually it manifests in premature OOM killer invocations, but maybe
> >> something the reporter's system configuration changes that (perhaps it
> >> runs with vm.overcommit_memory=2?).
> >
> > That's
* Fernando Santagata:
>> Usually it manifests in premature OOM killer invocations, but maybe
>> something the reporter's system configuration changes that (perhaps it
>> runs with vm.overcommit_memory=2?).
>
> That's it. I found this in /var/log/kern.log at the time I run a program
> that
On Tue, Sep 27, 2016 at 01:44:34PM +0200, Florian Weimer wrote:
> * Aurelien Jarno:
>
> > Hmm, rsync doesn't use libpthread, so that clearly rules out a
> > libpthread issue. That said, all the example you gave fail to allocate
> > the memory correctly, either through malloc (glibc) or mmap
On 2016-09-27 13:44, Florian Weimer wrote:
> * Aurelien Jarno:
>
> > Hmm, rsync doesn't use libpthread, so that clearly rules out a
> > libpthread issue. That said, all the example you gave fail to allocate
> > the memory correctly, either through malloc (glibc) or mmap (kernel)
> > which returns
* Aurelien Jarno:
> Hmm, rsync doesn't use libpthread, so that clearly rules out a
> libpthread issue. That said, all the example you gave fail to allocate
> the memory correctly, either through malloc (glibc) or mmap (kernel)
> which returns -ENOMEM. This points to either a kernel issue, or a
>
control: tag -1 + moreinfo
control: retitle -1 libc6: memory allocation issues
On 2016-09-26 14:10, Fernando Santagata wrote:
> Package: libc6
> Version: 2.24-3
> Severity: important
>
> Dear Maintainer,
>
> One month ago everything worked fine on my Debian sid computer.
> After an
* Fernando Santagata:
> One month ago everything worked fine on my Debian sid computer.
> After an update/dist-upgrade cycle in which libc6 was updated I
> started noticing some malfunctions.
Did you upgrade the kernel at the same time?
Package: libc6
Version: 2.24-3
Severity: important
Dear Maintainer,
One month ago everything worked fine on my Debian sid computer.
After an update/dist-upgrade cycle in which libc6 was updated I started
noticing some malfunctions.
I couldn't use rakudobrew (the Perl6 installation program)
12 matches
Mail list logo