From: Andrew Morton <akpm@digeo.com>
To: Mark Haverkamp <markh@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Call trace at mm/page-writeback.c in 2.5.47
Date: Wed, 20 Nov 2002 11:07:06 -0800 [thread overview]
Message-ID: <3DDBDD5A.F76AAD0E@digeo.com> (raw)
In-Reply-To: <1037808468.6367.41.camel@markh1.pdx.osdl.net>
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,
bash-shared-mapping...
If it is reproducible, does the removal of the ClearPageUptodate
statement from mm/truncate.c:truncate_complete_page() make it
go away?
Thanks.
next prev parent reply other threads:[~2002-11-20 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 16:07 Mark Haverkamp
2002-11-20 19:07 ` Andrew Morton [this message]
2002-11-20 21:14 Mark Haverkamp
2002-11-20 22:02 ` Andrew Morton
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=3DDBDD5A.F76AAD0E@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@osdl.org \
/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®