mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: odd phenomenon.
Date: 04 Jan 2003 11:48:33 +0100	[thread overview]
Message-ID: <1041677313.642.2.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <20030103103816.GA2567@codemonkey.org.uk>

On Fri, 2003-01-03 at 11:38, 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..

Happens all the time here too (ppc32), and did so for ages, with 2.4
(didn't specifically notice it with 2.5 yet, but I rarely use galeon
when testing 2.5 ;)

Typically happens with any kind of intense disk activity slowing down
galeon's launch process. (Not only bk, but also for example updatedb
running in the background).

I'm currently running galeon 1.2.6 (happened with all earlier versions
at least).

Ben.





  parent reply	other threads:[~2003-01-04 10:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 10:38 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
2003-01-04 10:48 ` Benjamin Herrenschmidt [this message]
2003-01-04 11:57   ` Dave Jones
2003-01-04 12:13     ` Benjamin Herrenschmidt
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=1041677313.642.2.camel@zion.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=davej@codemonkey.org.uk \
    --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®