All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Joshua M. Kwan" <joshk@ludicrus.ath.cx>, linux-kernel@vger.kernel.org
Subject: Re: intense disk or tty activity SEGV's X
Date: Mon, 13 Jan 2003 22:43:31 -0800	[thread overview]
Message-ID: <200301132243.31071.akpm@digeo.com> (raw)
In-Reply-To: <20030114063457.GA11073@kanoe.ludicrus.net>

On Mon January 13 2003 22:34, Joshua M. Kwan wrote:
>
> Lately, using the nForce IDE driver I have noticed a few glitches with 
> it that affect stability.
> 
> I use the BK tree for my kernel source. Lately, if I 1) clone a fresh 
> tree (i pull from a few places so sometimes there are some boggling 
> conflicts that a fresh tree fixes) or 2) run a bk pull, X will SEGV out 
> of nowhere. At first I thought it was the amount of disk activity.
> 
> But after reading the saga of the flukey tty code in the kernel, I am 
> thinking this could also be because of that? Lots of stuff scrolls by 
> when doing a bk clone, and when resolve runs after a bk pull there is 
> often lots of output.
> 
> There is no oops at all, nor anything that might be of help in dmesg.
> Any ideas? I started noticing it around halfway through 2.5.56...
> 

You could just do something like

	while true
	do
		cat /usr/src/linux/MAINTAINERS
	done

and see if that kills it.  If so then yeah, it could be a tty thing.  If not
then it may be mm/fs/vm/harware related.  Confirm that by running
dbench/tiobench/etc.

Basically: separate it out, eliminate some variables.

The most valuable thing you can do is to narrow it down to a particular
changeset.




      reply	other threads:[~2003-01-14  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  6:34 intense disk or tty activity SEGV's X Joshua M. Kwan
2003-01-14  6:43 ` Andrew Morton [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=200301132243.31071.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=joshk@ludicrus.ath.cx \
    --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 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.