From: Andrew Morton <akpm@osdl.org>
To: "admin@wodkahexe.de" <admin@wodkahexe.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with OOMKiller 2.6.8-rc3
Date: Fri, 6 Aug 2004 22:03:51 -0700 [thread overview]
Message-ID: <20040806220351.5e2b69b0.akpm@osdl.org> (raw)
In-Reply-To: <20040806195709.160722fa.admin@wodkahexe.de>
"admin@wodkahexe.de" <admin@wodkahexe.de> 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.
> 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.
next prev parent reply other threads:[~2004-08-07 5:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 17:57 admin
2004-08-07 5:03 ` Andrew Morton [this message]
2004-08-07 11:57 ` Seabastian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040806220351.5e2b69b0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=admin@wodkahexe.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome