firewire not detected on resume from suspend

This is tracked as an upstream bug at http://bugzilla.kernel.org/show_bug.cgi?id=7072 . You could add your e-mail address there if you are interested in latest news. Don't expect a fix soon.

As a workaround, mark ohci1394 (and perhaps the other IEEE 1394 drivers) to be unloaded before suspend. I don't know though how to do this in Ubuntu.

PS: Of course you should unmount any FireWire storage devices before unloading ohci1394.

fixed in upstream sources (kernel.org's sources) in linux-2.6.21

I can replicate the problem on Ubuntu Feisty with Kernel 2.6.20-16-generic.

Currently running linux-image-2.6.20-16.28

System can system/resume but the error means attempts to suspend are reported as failures even though the work.

The following is reported in the kernel log

[ 1606.058603] ohci1394 0000:00:14.0: suspend
[ 1606.058610] ohci1394 does not fully support suspend and resume yet

This was the fix in 2.6.21 relative to 2.6.20:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3360177c62e86f476c4f1a057e13163383652f7b
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=3360177c62e86f476c4f1a057e13163383652f7b
I'm not sure but I think it can be directly applied to 2.6.20.

PS: Even after the fix, the sbp2 driver may still have problems to transparently reconnect to the disk after resume. It could happen that the SCSI device is destroyed (during suspend or right after resume) and then re-created as a different SCSI device. It may even be necessary to unplug and replug the disk. Therefore it's still advisable to umount before suspend. I have vague ideas how to improve this but I haven't had time to get hacking on this.

Upstream appears to have committed a patch for this. This should have made it into Gutsy.
Can anyone verify this?

Thank you again for taking the time to report this bug. This bug report is being closed due to comments regarding this being fixed with an update. If you find the bug was not fixed, please re-open it by changing the status to New.