public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Sudeep K N <sudeepholla.maillist@gmail.com>,
	linux-arm-kernel@lists.arm.linux.org.uk, drzeus-mmc@drzeus.cx,
	linux-kernel@vger.kernel.org
Subject: Re: Rootfs in eMMC: Kernel panic ...Attempted to kill init!
Date: Mon, 22 Jun 2009 16:56:59 +0100	[thread overview]
Message-ID: <20090622155659.GE29188@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1245685846.15580.107.camel@pc1117.cambridge.arm.com>

On Mon, Jun 22, 2009 at 04:50:46PM +0100, Catalin Marinas wrote:
> On Mon, 2009-06-22 at 16:43 +0100, Russell King - ARM Linux wrote:
> > On Mon, Jun 22, 2009 at 07:43:40PM +0530, Sudeep K N wrote:
> > > Thanks for the suggestion.
> > > With the logs it is clear that crash is in the userspace.
> > > I am getting one of the 2 logs(below) randomly.
> > > >From trial#2,
> > > pgd = c60bc000
> > > [00000000] *pgd=061ee031, *pte=00000000, *ppte=00000000
> > > I could understand that the page tables are not proper.
> > > I am not able understand how to proceed.
> > > 
> > > Trial#1:
> > > VFS: Mounted root (ext2 filesystem).
> > > Freeing init memory: 108K
> > > linuxrc (1): undefined instruction: pc=40008100
> > > Code: e08e3003 eb002842 e2801008 e58c217c (e0812103)
> > 
> > Your processor is misbehaving; none of the above hex codes are undefined
> > instructions, so you shouldn't be taking an undefined instruction trap.
> 
> The undefined instruction aborts are possible in this situation since
> instructions are fetched via the I-cache while the abort handler shows
> the code via the D-cache.

However, you're missing a very important point.

This early on, the I-cache for the non-kernel pages won't contain any
entries except those placed there by this first binary - it's the very
first user process which is receiving these exceptions.

Second point is that the page concerned has only recently been mapped
into that page.  I would be very very surprised if speculative
instruction prefetch managed to dirty the exact right page via the
kernel mapping to always cause the first process to fail in some way.

  reply	other threads:[~2009-06-22 15:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  9:18 Rootfs in eMMC: Kernel panic ...Attempted to kill init! Sudeep K N
2009-06-19 13:44 ` Russell King - ARM Linux
2009-06-22 14:13   ` Sudeep K N
2009-06-22 14:26     ` Catalin Marinas
2009-06-22 14:32       ` Catalin Marinas
2009-06-22 15:43     ` Russell King - ARM Linux
2009-06-22 15:50       ` Catalin Marinas
2009-06-22 15:56         ` Russell King - ARM Linux [this message]
2009-06-22 16:13           ` Catalin Marinas
2009-06-22 16:46             ` Russell King - ARM Linux
2009-06-22 21:37               ` Catalin Marinas
2009-06-23  9:23               ` Linus Walleij
2009-06-23 14:34               ` Catalin Marinas
2009-07-13 15:44                 ` Dirk Behme
2009-07-13 15:48                   ` Russell King - ARM Linux
2009-07-16 10:39                   ` Catalin Marinas
2009-06-23  5:58             ` Sudeep K N

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=20090622155659.GE29188@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=catalin.marinas@arm.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudeepholla.maillist@gmail.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