From: Scott Wood <scottwood@freescale.com>
To: Nathan Lynch <ntl@pobox.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kernel oops while duming user core.
Date: Thu, 31 Jan 2008 15:58:24 -0600 [thread overview]
Message-ID: <47A24480.8060103@freescale.com> (raw)
In-Reply-To: <47A235AD.9050107@freescale.com>
Scott Wood wrote:
> Nathan Lynch wrote:
>> Is the crashing program multithreaded? The first report had firefox
>> triggering the oops.
>
> OK, I've got a test program that triggers it now. I'll see if I can
> figure out what's going on.
The problem seems to be that update_mmu_cache() is called on a guard
page with no access rights.
Changing update_mmu_cache() to always call flush_dcache_icache_page()
fixes it, though a better performing fix would probably be to add an
exception table entry for the dcbst.
-Scott
next prev parent reply other threads:[~2008-01-31 21:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 13:45 Kernel oops while duming user core Rune Torgersen
2008-01-31 16:15 ` Nathan Lynch
2008-01-31 16:26 ` Rune Torgersen
2008-01-31 17:40 ` Rune Torgersen
2008-01-31 19:15 ` Kumar Gala
2008-01-31 19:18 ` Rune Torgersen
2008-01-31 20:16 ` Scott Wood
2008-01-31 20:19 ` Rune Torgersen
2008-01-31 20:38 ` Rune Torgersen
2008-01-31 20:41 ` Nathan Lynch
2008-01-31 20:45 ` Rune Torgersen
2008-01-31 20:55 ` Scott Wood
2008-01-31 21:58 ` Scott Wood [this message]
2008-01-31 22:10 ` Rune Torgersen
2008-02-03 7:34 ` Benjamin Herrenschmidt
2008-02-04 18:23 ` Kernel oops while dumping " Scott Wood
2008-01-31 19:15 ` Kernel oops while duming " Kumar Gala
2008-01-31 19:23 ` Rune Torgersen
2008-01-31 19:54 ` Nathan Lynch
2008-02-01 17:38 ` Scott Wood
2008-02-02 12:05 ` Clemens Koller
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=47A24480.8060103@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
/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;
as well as URLs for NNTP newsgroup(s).