On Thu, 2007-02-15 at 19:52 +0100, Frank van Maarseveen wrote:
> 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: =======================
That is a known issue. The warning was bogus after we fixed up the NFS
client to handle the case where invalidate_inode_pages2() returns and
error, and so the warning was removed in 2.6.20.
Cheers
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
