mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Pierre Ossman <drzeus-mmc@drzeus.cx>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: MMC/SD Root filesystem suspend/resume problems
Date: Thu, 19 Jul 2007 17:42:54 +0100	[thread overview]
Message-ID: <1184863375.29634.17.camel@localhost.localdomain> (raw)
In-Reply-To: <1184860419.29634.10.camel@localhost.localdomain>

On Thu, 2007-07-19 at 16:57 +0100, Richard Purdie wrote:
> Lots of Linux handhelds use MMC/SD devices as the root file system. This
> has worked quite reliably for many kernel versions. In 2.6.22, it seems
> that if you suspend such a system then resume it, the device locks up.
> Trying to execute anything on the filesystem results in a "Permission
> Denied" message. I did see a message from the MMC subsystem saying it
> had redetected the card. There are also messages on the console like
> "MMC: killing requests for dead queue" each time you suspend/resume.
> 
> I'm away from my serial cables at the moment but I may be able to
> provide more debug when I have them over the weekend. Have you any ideas
> on why this is breaking?
> 
> For reference, I've reproduced the problem with both the PXA host driver
> and different driver not merged into mainline (ASIC3).

Just to follow up, if I boot with a rootfs from elsewhere and mount the
mmc card then suspend/resume, it corrupts the data on the card too so it
looks like some general suspend/resume problem on mounted filesystems.

Richard


  reply	other threads:[~2007-07-19 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 15:53 Richard Purdie
2007-07-19 16:42 ` Richard Purdie [this message]
2007-07-19 17:03 ` Pierre Ossman
2007-07-22 13:18   ` Richard Purdie
2007-07-22 14:05     ` Pierre Ossman
2007-07-22 14:28       ` Richard Purdie
2007-07-22 14:59         ` Pierre Ossman
2007-07-25 19:01     ` Pavel Machek
2007-07-25 19:20       ` Richard Purdie
2007-07-25 22:47         ` Pavel Machek

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=1184863375.29634.17.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@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

Powered by JetHome