From: Catalin Marinas <catalin.marinas@arm.com>
To: Sudeep K N <sudeepholla.maillist@gmail.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
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 15:26:29 +0100 [thread overview]
Message-ID: <1245680789.15580.85.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <366f00c80906220713o7ad61a8elb6b278b7313107d8@mail.gmail.com>
On Mon, 2009-06-22 at 19:43 +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.
This sounds familiar: SMP -> writealloc cache policy (could be forced by
hardware) -> cache corruption in user space with ext2.
Does you driver use the DMA API? If not, does your eMMC driver flush the
cache (in case you hit one of the long-standing problems with PIO
drivers).
It's worth trying this hack:
http://article.gmane.org/gmane.linux.ports.arm.kernel/51556
--
Catalin
next prev parent reply other threads:[~2009-06-22 14:26 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 [this message]
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
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=1245680789.15580.85.camel@pc1117.cambridge.arm.com \
--to=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=linux@arm.linux.org.uk \
--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