From: Peter Horton <pdh@colonel-panic.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1-pre8 losing pages
Date: Sun, 28 Jan 2001 12:11:47 +0000 [thread overview]
Message-ID: <20010128121147.A1877@colonel-panic.com> (raw)
In-Reply-To: <20010126194605.A923@colonel-panic.com> <200101261948.f0QJm6q09263@flint.arm.linux.org.uk>
In-Reply-To: <200101261948.f0QJm6q09263@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Fri, Jan 26, 2001 at 07:48:05PM +0000
On Fri, Jan 26, 2001 at 07:48:05PM +0000, Russell King wrote:
> Peter Horton writes:
> > The corruption is dependent on having a swapped on swap partition. If I
> > "swapoff" the corruption goes away, but it comes back when I "swapon"
> > again. I feel this a kernel bug, but as I'm the only person out here who's
> > seeing it I'm at a loss ...
>
> The reason I ask is that on an ARM box running plain 2.4.0 with swap
> enabled I get rather a lot of SEGVs. Turn swap off, and I don't see
> any.
>
> It sounds like it may be related.
>
Okay, scratch that. It does still happen when there's no swap, but for
some reason it happens a lot less often. Looks like it's timing related,
it only fails when using 7200rpm drives, not older 5400rpm ones (even
though they too are using UDMA33). I've ruled out the filing system, the
IDE controller, the drives and the RAM, so that leaves the kernel or the
CPU - I'll try and beg/borrow/steal another CPU and try that. I can
compile kernels / run X whilst the test is running without a problem so it
looks like it's the bulk write that's the problem.
P.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-28 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 23:16 2.4.1-pre8 losing pages Peter Horton
2001-01-26 2:28 ` Xuan Baldauf
[not found] ` <3A70DEF1.80ECEF80@baldauf.org>
2001-01-26 9:24 ` Peter Horton
2001-01-26 19:46 ` Peter Horton
2001-01-26 19:48 ` Russell King
2001-01-28 12:11 ` Peter Horton [this message]
2001-01-28 16:33 ` Andre Hedrick
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=20010128121147.A1877@colonel-panic.com \
--to=pdh@colonel-panic.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