So getting back to this issue. It still happens with a relatively
upstream kernel version 3.4-rc3. When experimenting a bit more it seems
that there are various cases:
1. automatically mounted by udisk under /media and not having a shell changed
into that mount dir.
-> this seems to work, after resuming a new nautilus window appears as with
a freshly inserted card
2. automatically mounted by udisk but having a shell changed into the mount dir.
-> Shows the mount error, the mountpoint does _not_ show up in df or
/proc/mounts and typing ls
in the shell results in an IO error.
3. manually mounted (to /mnt) without shell changed into the mount dir.
-> Shows the mount error, df and /proc/mounts do contain the mount point,
typing ls results
in the IO error.
4. manually mounted and changing into the mount dir seems the same as 3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913860
Title:
Suepend/resume causes problems with mounted and active mmcblk device
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/913860/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
