> While this patch may be useful, you are likely to lose data when you
> suspend unless you either unmount the card first or set the module
> option removable=0 on the mmc module.
>
> Ben.
>

Older kernels used to do the same.
I understand (and believe that others do) that placing something crucial on
removable media is not a good idea. But at the moment I lose data for sure
when trying to suspend.

(With 2.6.30 I had to use CONFIG_MMC_UNSAFE_RESUME, didn't know that the same
could be done in runtime)




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: E1P0Bq6-00039g-00.ibragimovrinat-mail-ru@f230.mail.ru">http://lists.debian.org/E1P0Bq6-00039g-00.ibragimovrinat-mail-ru@f230.mail.ru

On Mon, 2010-09-27 at 15:25 +0400, Ibragimov Rinat wrote:
> > While this patch may be useful, you are likely to lose data when you
> > suspend unless you either unmount the card first or set the module
> > option removable=0 on the mmc module.
> >
> > Ben.
> >
>
> Older kernels used to do the same.
> I understand (and believe that others do) that placing something crucial on
> removable media is not a good idea. But at the moment I lose data for sure
> when trying to suspend.
>
> (With 2.6.30 I had to use CONFIG_MMC_UNSAFE_RESUME, didn't know that the same
> could be done in runtime)

It's a new feature I implemented.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.