All of lore.kernel.org
 help / color / mirror / Atom feed
From: ZHAO Wei <zw@netspeed-tech.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: odd phenomenon.
Date: Fri, 03 Jan 2003 18:56:09 +0800	[thread overview]
Message-ID: <3E156C49.5090702@netspeed-tech.com> (raw)
In-Reply-To: <20030103103816.GA2567@codemonkey.org.uk>

Dave Jones wrote:
> Something strange I've noticed on all recent 2.4 and 2.5 kernels.
> 
> If I start galeon whilst I've got a bk pull in operation, the
> galeon process starts, opens its window, and then dies instantly.
> Starting it a second time works.
> 
> Its not OOM, as theres plenty of free RAM, and half gig of free (unused) swap.
> 
> It's almost 100% reproducable here.  Only seen it do it on this box
> though which is a P4 with HT, so it could be SMP related..

I used to have a small system with 96M RAM and no swap, only OpenSSH 
and bash and some kernel threads were running, when I got a big BK 
pull, it would catch sig 11 and die. Maybe this is unrelated. 
Indeed, at first I had only 64M RAM installed, only after some sig 
11, had I got more RAM installed. But this probably has nothing to 
do with your situation.


  parent reply	other threads:[~2003-01-03 10:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 10:38 odd phenomenon Dave Jones
2003-01-03 10:48 ` William Lee Irwin III
2003-01-03 11:09   ` Dave Jones
2003-01-03 11:12     ` William Lee Irwin III
2003-01-03 11:31       ` Dave Jones
2003-01-03 18:54         ` Robert Love
2003-01-03 10:56 ` ZHAO Wei [this message]
2003-01-04 10:48 ` Benjamin Herrenschmidt
2003-01-04 11:57   ` Dave Jones
2003-01-04 12:13     ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2003-01-04 13:25 sfr

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=3E156C49.5090702@netspeed-tech.com \
    --to=zw@netspeed-tech.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhaoway@public1.ptt.js.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.