Linux NFS development
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: linux-kernel@vger.kernel.org
Cc: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: 2.6.19.2 nfs BUG: warning at mm/truncate.c:398/invalidate_inode_pages2_range()
Date: Thu, 15 Feb 2007 19:52:28 +0100	[thread overview]
Message-ID: <20070215185228.GA3181@janus> (raw)

FYI,

Just captured this one, I'm not sure it's NFS at fault because I saw
at least another AIO related mm/truncate.c:398 report with a totally
different stack trace.

The machine seems still running happily, as usual with a considerable
load. kernel is tainted by fglrx.

kernel: BUG: warning at mm/truncate.c:398/invalidate_inode_pages2_range()
kernel:  [<c0104897>] dump_trace+0x227/0x240
kernel:  [<c010498f>] show_trace_log_lvl+0x2f/0x50
kernel:  [<c01049d7>] show_trace+0x27/0x30
kernel:  [<c0104b06>] dump_stack+0x26/0x30
kernel:  [<c015a495>] invalidate_inode_pages2_range+0x305/0x310
kernel:  [<c015a4c1>] invalidate_inode_pages2+0x21/0x30
kernel:  [<c01f7aa8>] nfs_revalidate_mapping+0x98/0x180
kernel:  [<c01f5726>] nfs_file_read+0x46/0xb0
kernel:  [<c017441e>] do_sync_read+0xde/0x130
kernel:  [<c0174511>] vfs_read+0xa1/0x1b0
kernel:  [<c0174947>] sys_read+0x47/0x70
kernel:  [<c0103387>] syscall_call+0x7/0xb
kernel:  [<b7ec0cbe>] 0xb7ec0cbe
kernel:  =======================

-- 
Frank

             reply	other threads:[~2007-02-15 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 18:52 Frank van Maarseveen [this message]
2007-02-15 19:06 ` 2.6.19.2 nfs BUG: warning at mm/truncate.c:398/invalidate_inode_pages2_range() Trond Myklebust

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=20070215185228.GA3181@janus \
    --to=frankvm@frankvm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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