From: Oleg Drokin <green@namesys.com>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: paging oops with 2.4.20-rc2
Date: Fri, 22 Nov 2002 09:54:50 +0300 [thread overview]
Message-ID: <20021122095450.A8056@namesys.com> (raw)
In-Reply-To: <3DDD8339.2040409@tupshin.com>
Hello!
On Thu, Nov 21, 2002 at 05:07:05PM -0800, Tupshin Harper wrote:
> I'm experiencing frequent oops when doing much of anything
> cpu/memory/disk intensive. I've yet to get through a kernel compilation
> on this machine.
Is the oops always the same and looks like the one you've posted here?
Or is it different from time to time?
If it always the same, can you please try to compile your kernel with
CONFIG_REISERFS_CHECK (reiserfs debug) option enabled and see what happens?
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2002-11-22 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 1:07 paging oops with 2.4.20-rc2 Tupshin Harper
2002-11-22 6:54 ` Oleg Drokin [this message]
2002-11-22 8:58 ` Tupshin Harper
2002-11-24 5:35 ` Tupshin Harper
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=20021122095450.A8056@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tupshin@tupshin.com \
/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.