From: "Joshua M. Kwan" <joshk@ludicrus.ath.cx>
To: linux-kernel@vger.kernel.org
Subject: intense disk or tty activity SEGV's X
Date: Mon, 13 Jan 2003 22:34:57 -0800 [thread overview]
Message-ID: <20030114063457.GA11073@kanoe.ludicrus.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
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...
Regards
Josh
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-01-14 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 6:34 Joshua M. Kwan [this message]
2003-01-14 6:43 ` Andrew Morton
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=20030114063457.GA11073@kanoe.ludicrus.net \
--to=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 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®