All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Andrew Morton <akpm@osdl.org>,
	hch@infradead.org, linux-mm@kvack.org
Subject: Re: mapped page in prep_new_page()..
Date: Sat, 28 Feb 2004 02:38:47 +1100	[thread overview]
Message-ID: <20040227153846.GO5801@krispykreme> (raw)
In-Reply-To: <Pine.LNX.4.58.0402270709152.2563@ppc970.osdl.org>

 
> Yeah, that makes complete sense now. "DAR" and "300 trap". I should have 
> seen it immediately.

Glad you see it our way. Want a job at IBM?

...
 
> and here's what ppc64 prints out:
> 
> 	Oops: Kernel access of bad area, sig: 11 [#1]
> 	NIP: C00000000008D7C4 XER: 0000000020000000 LR: C000000000086F70
> 	REGS: c00000007a43b7f0 TRAP: 0300    Not tainted
> 	...
> 
> And I'm sure it's clear as glass what that's all about.

Yeah it needs to be made clearer. We are also missing a dump of a few
instructions around the fail, especially useful when you dont have the
vmlinux or the fail is in modules somewhere.

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>

  reply	other threads:[~2004-02-27 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27  6:46 mapped page in prep_new_page() 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
2004-02-27 10:38     ` Benjamin Herrenschmidt
2004-02-27 15:32       ` Linus Torvalds
2004-02-27 15:38         ` Anton Blanchard [this message]
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=20040227153846.GO5801@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.