From: David Greaves <david@dgreaves.com>
To: Nathan Scott <nathans@sgi.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
linux-xfs@oss.sgi.com, nickpiggin@yahoo.com.au
Subject: Re: Bad page state in process 'nfsd' with xfs
Date: Mon, 01 May 2006 10:41:59 +0100 [thread overview]
Message-ID: <4455D7E7.1040203@dgreaves.com> (raw)
In-Reply-To: <20060501080427.H1771752@wobbly.melbourne.sgi.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Nathan Scott wrote:
> Hi there,
>
> On Fri, Apr 28, 2006 at 09:22:23PM +0100, David Greaves wrote:
>
> But, the warning is triggered by the page count (16777216 above), and
> that is 0x1000000 -- which is a huge, improbable count; that looks to
> me like it could very well be the result of a single bit error too.
>
> You may have a hardware problem - try running memtest I guess.
Thanks guys
It's in use a lot so I'll schedule some downtime, blow out the dust
and run memtest (though I've done that before and it has been clean).
I'll let you know how it goes...
David
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEVdfn8LvjTle4P1gRAiHTAKCBakrWQCpHgo8qyfN6ZNryAxi3bQCdFkDn
vQe781l5bQvq1a5BG2nF5sk=
=jdAy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-05-01 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 20:22 Bad page state in process 'nfsd' with xfs David Greaves
2006-04-30 2:06 ` Nick Piggin
2006-04-30 22:04 ` Nathan Scott
2006-05-01 9:41 ` David Greaves [this message]
2006-05-01 15:21 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2006-04-30 15:19 Zoltan Boszormenyi
2006-05-01 0:24 ` Nathan Scott
2006-05-01 8:07 ` Zoltan Boszormenyi
2006-05-01 21:33 ` Nathan Scott
2006-05-01 22:08 ` Zoltan Boszormenyi
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=4455D7E7.1040203@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@sgi.com \
--cc=nickpiggin@yahoo.com.au \
/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