mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: David Greaves <david@dgreaves.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	linux-xfs@oss.sgi.com
Subject: Re: Bad page state in process 'nfsd' with xfs
Date: Mon, 1 May 2006 08:04:27 +1000	[thread overview]
Message-ID: <20060501080427.H1771752@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <4452797F.70700@dgreaves.com>; from david@dgreaves.com on Fri, Apr 28, 2006 at 09:22:23PM +0100

Hi there,

On Fri, Apr 28, 2006 at 09:22:23PM +0100, David Greaves wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> This was with 2.6.16.9
> 
> There's an nfs export from an xfs on an lvm on a raid5 on some
> libata/sata disks.
> (cc'ing xfs since I recall rumoured(?) badness in old nfs/xfs/md/lvm
> setups and xfs_sendfile is mentioned)

Really old (early 2.6) or previously with 4Kstacks this used to be
a problem, but should not be with your kernel version.

> Bad page state in process 'nfsd'
> page:b1602060 flags:0x80000008 mapping:00000000 mapcount:0 count:16777216
> Trying to fix it up, but a reboot is needed
> Backtrace:
>  [<b013bda2>] bad_page+0x62/0x90
>  [<b013c1c8>] prep_new_page+0x78/0x80
>  [<b013c6b6>] buffered_rmqueue+0xf6/0x1f0
>  [<b013c8e2>] get_page_from_freelist+0x92/0xb0

Hmm... so, your page flags field there (0x80000008) has the 33rd and
4th bits set - 4 is pageuptodate, which is fine, but 33 seems odd
(perhaps some arch-specific bit?  or a single bit error...).

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.

cheers.

-- 
Nathan

  parent reply	other threads:[~2006-04-30 23:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 20:22 David Greaves
2006-04-30  2:06 ` Nick Piggin
2006-04-30 22:04 ` Nathan Scott [this message]
2006-05-01  9:41   ` David Greaves
2006-05-01 15:21     ` Chris Wedgwood
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=20060501080427.H1771752@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=david@dgreaves.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.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 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®