Re: Problem with OOMKiller 2.6.8-rc3
From: Seabastian
Date: Sat Aug 07 2004 - 04:59:18 EST
On Fri, 6 Aug 2004 22:03:51 -0700
Andrew Morton <akpm@xxxxxxxx> wrote:
> "admin@xxxxxxxxxxxx" <admin@xxxxxxxxxxxx> wrote:
> >
> > today i tried to burn a cd (bin+cue image) that was located on an
> > nfs share.
> >
> > - boot 2.6.8-rc3
> > - startx
> > - start k3b
> > - burn image
> >
> > after ~50% of burning the mouse stopped moving over the screen. the
> > keyboard was dead.
>
> What sort of CD was it? Audio? Judging by k3b.org, I'd say it was.
it was an svcd
>
> > the maschine was reachable via network, so i ssh'd and saw the
> > following in dmesg:
> >
> > laptop oom-killer: gfp_mask=0x1d2
> > laptop DMA per-cpu:
> > laptop cpu 0 hot: low 2, high 6, batch 1
> > laptop cpu 0 cold: low 0, high 2, batch 1
> > laptop Normal per-cpu:
> > laptop cpu 0 hot: low 32, high 96, batch 16
> > laptop cpu 0 cold: low 0, high 32, batch 16
> > laptop HighMem per-cpu: empty
> > laptop
> > laptop Free pages: 2192kB (0kB HighMem)
> > laptop Active:2113 inactive:643 dirty:0 writeback:0 unstable:0 free:548 slab:2233 mapped:1518 pagetables:210
> > laptop DMA free:1376kB min:20kB low:40kB high:60kB active:0kB inactive:0kB present:16384kB
> > laptop protections[]: 10 354 354
> > laptop Normal free:816kB min:688kB low:1376kB high:2064kB active:8452kB inactive:2572kB present:491456kB
>
> All your memory seems to have gone away. There's a memory leak associated
> with audio writing which we haven't yet tracked down - it's probably that.
>
since it was an svcd, it may not be this one.
i tried to burn the image again, while not being on an nfs share.
but i got the same problem again.
with 2.6.8-rc2 i can burn this image. (from nfs share or local)
-> no problem.
so it may be 2.6.8-rc3 related.
thanks
sebastian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/