*** This bug is a duplicate of bug 460126 ***
https://bugs.launchpad.net/bugs/460126
** This bug has been marked a duplicate of bug 460126
USB freezes/resets during suspend
--
USB hard drive not remounted after resume from suspend
https://bugs.launchpad.net/bugs/440059
You received this
devicekit does not exist any more.
** Changed in: devicekit
Status: New = Invalid
--
USB hard drive not remounted after resume from suspend
https://bugs.launchpad.net/bugs/440059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also happens on karmic beta with a filesystem mounted from an sdcard.
Prior to suspend, the filesystem (ext3fs on TrueCrypt) is available;
after suspend, it still shows as mounted, but any attempt to access any
files or directories results in an i/o error.
--
USB hard drive not remounted after
This might be related. I noticed before the system suspends, it gets a
usb reset before completing the suspend process
Oct 18 00:35:44 Epic kernel: [ 1074.128065] usb 1-1: reset full speed USB
device using uhci_hcd and address 14
Oct 18 00:35:52 Epic kernel: [ 1082.112152] usb 1-1: reset full
Might be a devicekit bug as the problem persists with Jaunty's kernel on Karmic.
I also have some debug output from debugfs and usbmon from a suspend/resume
cycle.
** Also affects: devicekit
Importance: Undecided
Status: New
** Attachment added: usbmon.txt
** Description changed:
After resuming from suspend, my external USB hard drive does not get
remounted. It's still recognized by the system because it shows up in
lsusb, but it never gets remounted. The only way to get it to mount
- again is to power off the hard drive and then turn it back
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
After fooling around with this a little bit, I think I see what is
happening. Right before suspend something puts the drive into a bad
state. By bad state I mean that the drive is basically frozen (not
literally, it's still spinning) but it won't
[This is an automated message. Apologies if it has reached you
inappropriately.]
This bug was reported against the linux-meta package when it likely
should have been reported against the linux package instead. We are
automatically transitioning this to the linux kernel package so that the
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/32782871/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/32782872/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/32782873/ArecordDevices.txt
