mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: martin sepulveda <msepulveda@joydivision.com.ar>
To: linux-kernel@vger.kernel.org
Subject: Re: load 1 at idle, 2.4.12-ac3
Date: Tue, 16 Oct 2001 14:29:59 -0300	[thread overview]
Message-ID: <20011016142959.75fd63b9.msepulveda@joydivision.com.ar> (raw)
In-Reply-To: <20011018161607.D2467@mikef-linux.matchmail.com>
In-Reply-To: <20011016135322.02ed0f97.martin@joydivision.com.ar> <20011016140041.2f26c95c.msepulveda@joydivision.com.ar> <20011018161607.D2467@mikef-linux.matchmail.com>

what it was? a paused xmms plugin in development (xmms was stoped)

talk about shame :)

M.


On Thu, 18 Oct 2001 16:16:07 -0700
Mike Fedyk <mfedyk@matchmail.com> wrote:

> On Tue, Oct 16, 2001 at 02:00:41PM -0300, martin sepulveda wrote:
> > forget it!
> > i've found what it was, and it is certainly *not* the kernel :)
> > 
> > thanks anyway, and sorry
> > 
> 
> What was it?  A process stuck in D state?  Something like dist.net or seti?
> 
> Reminds me of recently when my X server (a couple days ago from
> debian-unstable) cought a memory leak, and my system was swapping like
> crazy.  I thought it was something to do with the shmem problem I found a
> while back, but I looked at /proc/meminfo and no errors with shmem.  Finally
> I checked top...
> 
> Unfortunately, the OOM killer killed a few things, all except for my X
> server that was causing the problem.
> 
> Mike

-- 
Talent does what it can, genius what it must.
I do what I get paid to do.

      reply	other threads:[~2001-10-18 23:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 23:16 Mike Fedyk
2001-10-16 16:53 ` martin sepulveda
2001-10-16 17:00   ` martin sepulveda
2001-10-16 17:29     ` martin sepulveda [this message]

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=20011016142959.75fd63b9.msepulveda@joydivision.com.ar \
    --to=msepulveda@joydivision.com.ar \
    --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

all inboxes | Powered by JetHome®