mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudeep K N <sudeepholla.maillist@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.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: Tue, 23 Jun 2009 11:28:23 +0530	[thread overview]
Message-ID: <366f00c80906222258l2c577b4eq7c97d0430f7f7104@mail.gmail.com> (raw)
In-Reply-To: <1245687196.15580.122.camel@pc1117.cambridge.arm.com>

> Could you or Sudeep clarify whether the driver uses DMA or PIO?
>
I have option to use both. I tried you patch(rather hack) for PIO mode i.e
(flush_dcache_page called in the VFS layer). This solves the crash in polling
mode. I need to work for proper way of flushing in the MMC driver.
I am yet to try with DMA as I am not much familiar with the DMA driver and
need some time.

> 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.

Looks like the crash I am getting is similar to one you are explaining with
your experience with CF cards.


Thanks to both Catalin and Russell for making such a informative discussion on
ARM SMP and related cache know hows.

-- 
Regards,
Sudeep

      parent reply	other threads:[~2009-06-23  5:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  9:18 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
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 [this message]

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=366f00c80906222258l2c577b4eq7c97d0430f7f7104@mail.gmail.com \
    --to=sudeepholla.maillist@gmail.com \
    --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=linux@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®