From: Tupshin Harper <tupshin@tupshin.com>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: paging oops with 2.4.20-rc2
Date: Sat, 23 Nov 2002 21:35:59 -0800 [thread overview]
Message-ID: <3DE0653F.7000000@tupshin.com> (raw)
In-Reply-To: 20021122095450.A8056@namesys.com
Well, after further examination and manipulations, I determined that
both the paging oops and the report of BUG page_alloc.c that I was
getting are eliminated after moving my swap partition off of the
raid0+lvm volume that it was on and onto a separate disk.
Still a bug, but a fairly obscure one. It's obviously not necessary for
performance reasons since the kernel stripes swaps itself, but it
certainly caused me a lot of headache until I figured out what was going on.
-Tupshin
Oleg Drokin wrote:
>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
>
>
>
prev parent reply other threads:[~2002-11-24 5:28 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
2002-11-22 8:58 ` Tupshin Harper
2002-11-24 5:35 ` Tupshin Harper [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=3DE0653F.7000000@tupshin.com \
--to=tupshin@tupshin.com \
--cc=green@namesys.com \
--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