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 17:46:04 +0100	[thread overview]
Message-ID: <20090622164604.GG29188@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1245687196.15580.122.camel@pc1117.cambridge.arm.com>

On Mon, Jun 22, 2009 at 05:13:16PM +0100, Catalin Marinas wrote:
> Well, I get this kind of errors (with /sbin/init) every time I try ext2
> on CompactFlash (with pata_platform). You could try with USB as well on
> a RealView/EB+ARM11MPCore board.

Is USB now usable on the rev.B board I have?

> Could you or Sudeep clarify whether the driver uses DMA or PIO?

If I knew what this "eMMC" was...

> In my case (ext2 over pata_platform), there is no flush_dcache_page()
> call after the page was written with data from the CompactFlash (neither
> the driver nor the VFS layer do this and we used hardware tracing to
> double-check). When the page is mapped into user space,
> update_mmu_cache() is called but the page hasn't been marked as dirty
> and no D-cache flushing occurs. Calling flush_dcache_page() in
> mpage_end_io_read() works around this issue.

As already covered, there's no chance of adding such a call to the
generic kernel.  It's the responsibility of the drivers to ensure that
data they read in hits the underlying page - in the same way that DMA
does.

  reply	other threads:[~2009-06-22 16:47 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
2009-06-22 16:13           ` Catalin Marinas
2009-06-22 16:46             ` Russell King - ARM Linux [this message]
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=20090622164604.GG29188@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