On 06/13/2013 08:50 AM, Catalin Marinas wrote:
On Wed, Jun 12, 2013 at 01:28:13AM +0100, Ben Greear wrote:
On 06/11/2013 12:52 PM, Ben Greear wrote:
On 06/10/2013 03:32 PM, Catalin Marinas wrote:
On 10 June 2013 19:22, Ben Greear wrote:
We had a system go OOM while doing lots of wireless
sta
On Wed, Jun 12, 2013 at 01:28:13AM +0100, Ben Greear wrote:
> On 06/11/2013 12:52 PM, Ben Greear wrote:
> > On 06/10/2013 03:32 PM, Catalin Marinas wrote:
> >> On 10 June 2013 19:22, Ben Greear wrote:
> >>> We had a system go OOM while doing lots of wireless
> >>> stations. (System had 8GB of RAM
On Tue, Jun 11, 2013 at 08:52:41PM +0100, Ben Greear wrote:
> On 06/10/2013 03:32 PM, Catalin Marinas wrote:
> > On 10 June 2013 19:22, Ben Greear wrote:
> >> We had a system go OOM while doing lots of wireless
> >> stations. (System had 8GB of RAM, so I suspect a leak).
> >>
> >> I enabled kmeml
On 06/11/2013 12:52 PM, Ben Greear wrote:
On 06/10/2013 03:32 PM, Catalin Marinas wrote:
On 10 June 2013 19:22, Ben Greear wrote:
We had a system go OOM while doing lots of wireless
stations. (System had 8GB of RAM, so I suspect a leak).
I enabled kmemleak in a 3.9.5 (plus some local patches
On 06/10/2013 03:32 PM, Catalin Marinas wrote:
On 10 June 2013 19:22, Ben Greear wrote:
We had a system go OOM while doing lots of wireless
stations. (System had 8GB of RAM, so I suspect a leak).
I enabled kmemleak in a 3.9.5 (plus some local patches) and
I see the entries below. Any idea if
On 06/10/2013 03:32 PM, Catalin Marinas wrote:
On 10 June 2013 19:22, Ben Greear wrote:
We had a system go OOM while doing lots of wireless
stations. (System had 8GB of RAM, so I suspect a leak).
I enabled kmemleak in a 3.9.5 (plus some local patches) and
I see the entries below. Any idea if
On 10 June 2013 19:22, Ben Greear wrote:
> We had a system go OOM while doing lots of wireless
> stations. (System had 8GB of RAM, so I suspect a leak).
>
> I enabled kmemleak in a 3.9.5 (plus some local patches) and
> I see the entries below. Any idea if these are real or not?
>
> unreferenced
We had a system go OOM while doing lots of wireless
stations. (System had 8GB of RAM, so I suspect a leak).
I enabled kmemleak in a 3.9.5 (plus some local patches) and
I see the entries below. Any idea if these are real or not?
unreferenced object 0x880212281c80 (size 128):
comm "systemd
8 matches
Mail list logo