From: Anton Blanchard <anton@samba.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
hch@infradead.org, linux-mm@kvack.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: mapped page in prep_new_page()..
Date: Fri, 27 Feb 2004 18:31:27 +1100 [thread overview]
Message-ID: <20040227073127.GC5801@krispykreme> (raw)
In-Reply-To: <Pine.LNX.4.58.0402262305000.2563@ppc970.osdl.org>
> Yeah, I wouldn't be surprised if it is an architecture bug (possibly
> one that has been common but has long been fixed on x86).
Its possible, I think Ive seen this before on a pseries box before.
> The ppc64 page fault oops thing seems to be braindead, and not even print
> out the address. Stupid. Somebody is too used to debuggers, and as a
> result users aren't helped to make good reports, hint hint..
DAR is the address. I should probably make it more obvious, Ive been
somewhat IBMized with my TLAs.
> Who would write the value quadword 0x0000005F00000000 to the physical
> address 1<<24? And is that a valid "struct page *" in the first place?
> Probably.
>
> Bad pointer crapola? Or some subtle CPU bug with address arithmetic that
> crosses the 16MB border? Anton, BenH, any ideas?
Interesting, but nothing springs to mind yet.
Anton
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-02-27 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 6:46 Linus Torvalds
2004-02-27 6:58 ` Andrew Morton
2004-02-27 7:11 ` Anton Blanchard
2004-02-27 7:21 ` Andrew Morton
2004-02-27 7:30 ` Linus Torvalds
2004-02-27 7:31 ` Anton Blanchard [this message]
2004-02-27 10:38 ` Benjamin Herrenschmidt
2004-02-27 15:32 ` Linus Torvalds
2004-02-27 15:38 ` Anton Blanchard
2004-02-27 22:06 ` Benjamin Herrenschmidt
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=20040227073127.GC5801@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@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