[lkml]   [2002]   [Nov]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Call trace at mm/page-writeback.c in 2.5.47
Mark Haverkamp wrote:
> While running a memory stress workload test on a 16 processor numa
> system, I received a number of call traces like the following:

What is the workload? And in which journalling mode was ext3
being used?

Was the workload actually being run against ext3?

> buffer layer error at mm/page-writeback.c:559
> Pass this trace through ksymoops for reporting
> Call Trace:
> [<c013f1fb>] __set_page_dirty_buffers+0x3b/0x150
> [<c012d746>] zap_pte_range+0x1d6/0x2c0
> [<c0183401>] do_get_write_access+0x4a1/0x4d0
> [<c012d89c>] zap_pmd_range+0x6c/0x80

A non-uptodate page mapped into pagetables. I _think_ I
can see how that can happen. If the workload was, say,

If it is reproducible, does the removal of the ClearPageUptodate
statement from mm/truncate.c:truncate_complete_page() make it
go away?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:31    [W:0.061 / U:4.204 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site