From: Rodolfo Giometti <giometti@linux.it>
To: linux-mips@linux-mips.org
Subject: USB sleep & mount
Date: Tue, 23 May 2006 15:24:18 +0200 [thread overview]
Message-ID: <20060523132418.GA28124@enneenne.com> (raw)
Hello,
I'm working on sleep for USB host on au1x00 CPUs and I have the
following problem.
When I put the system to sleep and then it wakes up everything works
well _if_ the USB key is not mounted before the sleep. For instance,
if I mount partition "/dev/sda1" (first USB key partition) and then go
to sleep, at wake up the system forgets device "/dev/sda" and
registers a new device "/dev/sdb" so, obviously, the filesystem
previously mounted is not accessible anymore.
My question is: is that correct since the userland, before going to
sleep, should umount all external filesystems or it's a bug? :)
Thanks,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@gnudd.com
Embedded Systems giometti@linux.it
UNIX programming phone: +39 349 2432127
next reply other threads:[~2006-05-23 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 13:24 Rodolfo Giometti [this message]
2006-05-23 15:11 ` USB sleep & mount Jordan Crouse
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=20060523132418.GA28124@enneenne.com \
--to=giometti@linux.it \
--cc=linux-mips@linux-mips.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