public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: odd phenomenon.
Date: Sat, 4 Jan 2003 11:57:24 +0000	[thread overview]
Message-ID: <20030104115724.GA3876@codemonkey.org.uk> (raw)
In-Reply-To: <1041677313.642.2.camel@zion.wanadoo.fr>

On Sat, Jan 04, 2003 at 11:48:33AM +0100, Benjamin Herrenschmidt wrote:

 > > 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 ;)

Ha! Conclusive proof I'm not losing my marbles.

 > 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).

Maybe, but bk was the only disk-thrashing type app I regularly
have running when I've tried to reproduce this.

Is your PPC32 box SMP ?  I'm wondering why I don't see it on my
athlon/P3 boxes, just on my dual P4.

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk

  reply	other threads:[~2003-01-04 11: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
2003-01-04 10:48 ` Benjamin Herrenschmidt
2003-01-04 11:57   ` Dave Jones [this message]
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=20030104115724.GA3876@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=benh@kernel.crashing.org \
    --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