public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Elvis Dowson <elvis.dowson@mac.com>
Cc: Linux OMAP Users <linux-omap@vger.kernel.org>
Subject: Re: MMC card corruption during suspend/resume operation
Date: Tue, 19 May 2009 07:52:42 -0700	[thread overview]
Message-ID: <87k54d87r9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <B9DAA81F-383F-4DCE-88BD-E20F13F22EC1@mac.com> (Elvis Dowson's message of "Tue\, 19 May 2009 09\:03\:11 +0400")

Elvis Dowson <elvis.dowson@mac.com> writes:

> Hi,
>         I have a problem with my TI OMAP 3503 platform, where the
> microSD card that I have, gets corrupted during a suspend/resume
> operation. Do the existing power management drivers, cleanly unmount/
> mount the mmc card during a suspend/resume operation?

Is your rootfs on MMC?  If so, be sure you have 
CONFIG_MMC_UNSAFE_RESUME=y in your .config.

MMC on rootfs on PM branch works fine for me on OMAP3 Beagle.

Kevin


> I am using the TI OMAP linux 2.6.29 kernel version, with the
> android-2.6.29 kernel updates. I have installed
>
> Doing a search for the mmc card corruption issues, it would appear
> that a lot of people are facing the same issues on other platforms as
> well. It appears to be a platform issue for both the older 1.1 and 1.5
> android versions.
>
> http://forum.xda-developers.com/archive/index.php/t-495899.html
>
> http://androidforums.com/updates-cupcakes/5202-did-cupcake-eat-my-sd-card.html
>
> http://forums.t-mobile.com/tmbl/board/message?board.id=Android3&message.id=10928
>
> The problem might be because of the application or system not cleanly
> un-mounting the mmc card, thus causing it to get corrupted, e.g during
> a suspend/resume operation.
>
> So, I thought I'd ask if the existing power management drivers do a
> clean mount/unmount when it does a suspend/resume operation.
>
> Best regards,
>
> Elvis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

           reply	other threads:[~2009-05-19 14:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <B9DAA81F-383F-4DCE-88BD-E20F13F22EC1@mac.com>]

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=87k54d87r9.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=elvis.dowson@mac.com \
    --cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox