LKML Archive on
help / color / mirror / Atom feed
From: Matthew Hodgson <>
Subject: BUG: at fs/nfs/pagelist.c:339 nfs_scan_dirty()
Date: Mon, 12 Feb 2007 01:37:34 +0000	[thread overview]
Message-ID: <> (raw)


I just upgraded from to 2.6.20 on a Pentium M, and on booting 
off an NFS root encountered the following bug somewhere after loading 
the w83627hf module and before ohci1394:

BUG: at fs/nfs/pagelist.c:339 nfs_scan_dirty()
  [<c01da1b6>] nfs_scan_dirty+0x168/0x17d
  [<c01dd54a>] nfs_wait_on_requests_locked+0x9c/0xac
  [<c01dda9b>] nfs_sync_mapping_wait+0xad/0x256
  [<c01de35a>] nfs_sync_mapping_range+0x83/0x9e
  [<c01d8037>] nfs_getattr+0x37/0x98
  [<c01d8000>] nfs_getattr+0x0/0x98
  [<c014be19>] vfs_getattr+0x21/0x30
  [<c014c203>] vfs_stat_fd+0x2e/0x40
  [<c0224ec4>] __copy_to_user_ll+0xc9/0xd4
  [<c014c2a2>] sys_stat64+0xf/0x23
  [<c010f5bb>] do_page_fault+0x277/0x528
  [<c0149c61>] vfs_read+0xfa/0x134
  [<c010f344>] do_page_fault+0x0/0x528
  [<c0102c98>] syscall_call+0x7/0xb

So far the machine appears stable other than this - but after having had 
a year or so of perfect uptime on the box under with no such 
kernel errors, I thought you might like to know in case this indicates 
something more serious.

The kernel options given to boot off NFS were...

root=/dev/nfs rw 

...and the full dmesg, kernel config, lspci and lsmod output may be 
found at  The NFS server is 
running the default NFS v3 options on 2.6.20 on Core 2 Duo.  No patches 
have been applied to either kernel.

Any advice on whether I should be worried by this, whether it indicates 
that something significant is wrong, and how I might help debug it would 
be appreciated.



                 reply	other threads:[~2007-02-12  2:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: BUG: at fs/nfs/pagelist.c:339 nfs_scan_dirty()' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).