All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] arc: Re-enable MMU upon die()
Date: Fri, 1 Sep 2017 12:42:08 +0000	[thread overview]
Message-ID: <1504269727.15144.6.camel@synopsys.com> (raw)
In-Reply-To: <c6f2e929-d431-8fc3-3940-7e2aba4d00cf@synopsys.com>

Hi Jose,

On Fri, 2017-09-01@13:33 +0100, Jose Abreu wrote:
> Hi Alexey,
> 
> On 01-09-2017 12:48, Alexey Brodkin wrote:
> > 
> > Hi Jose,
> > 
> > On Fri, 2017-09-01@12:39 +0100, Jose Abreu wrote:
> > > 
> > > I recently came upon a scenario where I would get a double fault
> > > after a machine check error. It turns out that for Ksymbol lookup
> > > to work with modules we need to have MMU enabled because module
> > > address is mapped in the cached space.
> > > 
> > > This patch re-enables the MMU before start printing the stacktrace
> > > making stacktracing of modules work upon a fatal exception.
> > I'm wondering how do we end up with MMU disabled?
> > From ARC700 databook I cannot find any condition on which MMU could be
> > silently disabled by hardware and IIRC there's no code in Linux kernel
> > that disables MMU.
> 
> According to ARC 700 databook a machine check exception causes
> Global TLB enable to be cleared. (See ARC 700 databook, page 687).

Thanks for pointing to that.
I didn't expect to see that note far below "Global TLB enable" bit description.

So then your change makes perfect sense.

Reviwed-by: Alexey Brodkin <abrodkin at synopsys.com>

  reply	other threads:[~2017-09-01 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 11:39 [PATCH] arc: Re-enable MMU upon die() Jose Abreu
2017-09-01 11:48 ` Alexey Brodkin
2017-09-01 12:33   ` Jose Abreu
2017-09-01 12:42     ` Alexey Brodkin [this message]
2017-09-01 15:30 ` Vineet Gupta

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=1504269727.15144.6.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=linux-snps-arc@lists.infradead.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.